kuhyx/wake-alarm
1
0
Fork 0
mirror of https://github.com/kuhyx/wake-alarm.git synced 2026-11-11 12:07:31 +01:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Record what the Pixel run actually proved, and what it did not

Browse Source 
Three claims are now measured rather than assumed: the alarm fires from Doze
on time, wakes the screen over the lockscreen, and rings through DND with
zen_mode=1 (player state:started on USAGE_ALARM/STREAM_ALARM(4)).

The dismiss is still unverified. Three defects were found and fixed during the
attempt, but no fix has been confirmed on hardware — the run ended before a
successful tap. Recorded as unverified rather than implied by the commit that
fixed them.

Also recorded: requestDismissKeyguard raises the PIN prompt rather than
silently unlocking, so a no-touch NFC tap was never achievable on a secured
phone. Better stated now than discovered at 06:00.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EckWmyfetYq3Mi8MAnUudh
This commit is contained in:
Krzysztof Rudnicki 2026-08-27 22:23:41 +02:00
parent 08b44b4ca2
commit 859e6effbb
1 changed files with 23 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
TODO-hardening-continue.md
View File

@ -35,6 +35,29 @@ starting; this file deliberately does not duplicate it.
3. **Item 13, black screen.** Different repo (`~/testsAndMisc/
linux_configuration`), host-only, blocks nothing.
### Measured on the Pixel 6a, 2026-08-27
**Verified for real:** the alarm fires from Doze on time (22:03:01 for a
22:03 arm), wakes the screen (`Asleep`→`Awake`), puts `AlarmActivity` on top
over the lockscreen, posts the full-screen-intent notification, and **rings
through DND** — `zen_mode=1`, player `state:started` on
`usage=USAGE_ALARM`/`STREAM_ALARM(4)`, `mutedState:none`. The STREAM_ALARM
claim is no longer an assumption. NFC tag registration works end to end
(`0465dab3ce2a81` via Settings → Room proof).
**Still not verified: the actual dismiss.** Three real defects were found and
fixed in the attempt (see `08b44b4`), but none of the fixes has been confirmed
on hardware yet — the last test run ended before a successful tap. What needs
one more run: register/confirm the tag, fire a ring, unlock at the keyguard
prompt, tap the tag, solve the challenge, and confirm the sound stops **and**
the screen closes.
**`requestDismissKeyguard` does not silently unlock a secured phone.** It
raises the PIN/biometric prompt and returns to `ON_LOCKED` until the user
answers, so the NFC tap cannot work before that point. That is the agreed
behaviour, not a bug — but it means "tap the tag without touching the phone"
was never achievable on a secured device, and the docs should not imply it.
### Not yet verified on the phone
The ring itself has only been fired on the API 36 AVD. On the Pixel 6a the