diff --git a/docs/releases/1.17.1.9.md b/docs/releases/1.17.1.9.md index 13a4345f8..c0b289ac2 100644 --- a/docs/releases/1.17.1.9.md +++ b/docs/releases/1.17.1.9.md @@ -142,9 +142,11 @@ attached, so these checks do not measure CPU sleep or button wake. The subsequen `ebf2f082` V4 button-wake profile correction passed host tests and linked-image checks, followed by another unchanged native GUI fresh-flash connection and 180-second open/closed console checks with power saving on and USB logging. -Original settings, identity and ACL response were restored. Physical button -wake, CPU sleep and current draw were not tested here; the new source's GitHub -unit workflow remains in progress. +Original settings, identity and ACL response were restored. On 2026-10-06 the +user separately confirmed V4 button screen wake, without specifying the +firmware revision or CPU sleep state. The operator USB tests did not include +an actual button press or measure CPU sleep/current draw; the new source's +GitHub unit workflow remains in progress. Build qualification does not establish physical compatibility on every board. Hardware CDC has finite buffers, and closing a Linux TTY does not necessarily diff --git a/docs/test-results/hardware_validation_esp32_web_console_ota_2026-10-05.md b/docs/test-results/hardware_validation_esp32_web_console_ota_2026-10-05.md index 33c2442a9..1c593b035 100644 --- a/docs/test-results/hardware_validation_esp32_web_console_ota_2026-10-05.md +++ b/docs/test-results/hardware_validation_esp32_web_console_ota_2026-10-05.md @@ -101,4 +101,6 @@ firmware profile, or radio traffic load. USB-attached console checks do not establish CPU sleep, measured current or button wake. The subsequent V4 button-wake profile correction passed host/build validation and another native GUI fresh-flash plus 180-second open/closed console check, as recorded in that -linked report; physical button wake remains untested. +linked report. On 2026-10-06 the user separately confirmed V4 button screen wake; +its firmware revision and CPU sleep state were not specified. The operator +USB tests included no actual button press or sleep/current measurement. diff --git a/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.md b/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.md index 735c93fe4..a48792911 100644 --- a/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.md +++ b/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.md @@ -15,6 +15,11 @@ and another native fresh-flash GUI connection with 180-second open/closed console intervals. That updated-source checkpoint is recorded separately below; it does not extend the older source's 600-second measurements to the new image. +On 2026-10-06, the user separately confirmed that a Heltec V4 button press wakes +the screen. This is a user-reported manual confirmation; its firmware revision +and CPU sleep state were not specified. It does not supply a current measurement +or a V4-R8 manual result. + These results extend the [earlier startup investigation](hardware_validation_esp32_web_console_startup_2026-10-05.md) to the current normal Full image and native hardware CDC. They are physical console stability checks, not a measurement of sleep current, radio traffic @@ -143,10 +148,11 @@ qualified results. The USB cable remained attached throughout these trials. The native-host sleep guard keeps CPU command service available while the USB host is connected, including when its serial port is closed. Power saving on is therefore not -proof of CPU light-sleep entry, measured current, or physical button wake. +proof of CPU light-sleep entry, measured current, or an operator button test. At this source, V4 lacks the momentary-button wake profile flag. Its subsequent -software/build and console validation is recorded below. No physical button -access is available in this setup, so physical button wake remains unqualified. +software/build and console validation is recorded below. The operator had no +physical button access in this setup. The user's separate screen-wake +confirmation does not establish this historical image's CPU sleep state. These checks qualify this historical `c88885a3` Full application, native Pi Chromium setup, protected active-slot application flash, and measured intervals. They do not @@ -203,7 +209,9 @@ service states were restored, and no Pi network configuration changed. The compact safe audit records this as `updated_source_checkpoint`, separate from the older 600-second trials. The updated source qualifies these -180-second console intervals; physical button wake, CPU sleep and current draw -remain untested with USB attached. GitHub unit run `37426156162` for this new +180-second console intervals. The operator did not physically press the button; +the user's manual screen-wake confirmation is recorded above without assigning +it a firmware SHA or CPU sleep state. CPU sleep and current draw were not +measured in these USB-attached tests. GitHub unit run `37426156162` for this new source is still in progress at this checkpoint. Release 1.17.1.9 remains held and unpublished. diff --git a/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.safe.json b/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.safe.json index 46e909fb9..6ba42142a 100644 --- a/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.safe.json +++ b/docs/test-results/hardware_validation_heltec_v4_native_console_2026-10-06.safe.json @@ -90,7 +90,7 @@ "Failed flasher preparations remain failed and did not exercise the GUI five-second command timer.", "Merged artifact is audited; actual browser tests flashed only the protected active application slot.", "No measured sleep current, factory erase/cold-cycle, heavy logging or RF traffic-soak claim.", - "USB-attached CPU sleep guard means no physical light-sleep/button-wake or current-draw qualification; Updated profile host/build and native USB console checks are recorded separately; physical button wake remains untested.", + "The controlled operator USB tests included no actual button press or CPU-sleep/current measurement. The user separately confirmed V4 button screen wake without a firmware SHA or CPU sleep state.", "Original host service states restored; MQTT packet delivery was not measured." ], "qualified_trials": [ @@ -233,9 +233,9 @@ "native_host_sleep_guard_present": true, "CPU_light_sleep_entry_measured": false, "current_draw_measured": false, - "physical_button_wake_tested": false, "c888_V4_momentary_button_wake_profile_flag_present": false, - "new_button_fix_qualification": "Host/build and updated-source native USB console180s qualified; physical button/CPU sleep/current untested." + "new_button_fix_qualification": "Host/build and updated-source native USB console180s qualified. Operator did not press a physical button; user separately confirmed V4 screen wake. CPU sleep/current not measured.", + "operator_physical_button_press_tested": false }, "updated_source_checkpoint": { "source_commit": "ebf2f0823ef8413987d31ccb2d044a2090e88469", @@ -367,9 +367,22 @@ }, "limitations": [ "Updated-source180s intervals are separate from historical c888600s trials.", - "USB cable remained attached; no physical button wake, measured CPU sleep or current draw.", + "Operator USB cable remained attached and no actual button was pressed; CPU sleep/current were not measured. The separate user V4 screen-wake report has no firmware SHA or CPU sleep state.", "Host services restored; no MQTT delivery or loaded-RF qualification.", "Release held and unpublished." - ] + ], + "user_manual_confirmation_reference": "user_reported_manual_confirmation; firmware revision not specified" + }, + "user_reported_manual_confirmation": { + "date": "2026-10-06", + "source": "user report", + "board_family": "Heltec V4", + "outcome": "button press wakes screen", + "firmware_SHA_provided": false, + "firmware_version_provided": false, + "CPU_sleep_state_provided": false, + "current_draw_measurement_provided": false, + "V4_R8_manual_result_provided": false, + "scope": "Separate manual screen-wake confirmation; not assigned to a source SHA or controlled operator sleep/current test." } }