Skip to content

omamobile-shell 0.2.68: a wake by the Pixel 9a's power key lights the lock screen - #268

Closed
W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:shell-sleepd-power-label
Closed

W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:shell-sleepd-power-label

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

On the Pixel 9a, a power-key wake from auto-sleep left the screen off, and the palmtop went back to sleep 5 s later. It took a second press to wake it for real.

omamobile-sleepd recognises a power-key wake by the name in /proc/interrupts, and only matched KEY_POWER, the gpio-keys label in the Pixel 7 Pro's device tree. The 9a's labels the key Power, so its wake looked like a dark resume. From the palmtop's journal today:

omamobile-sleepd: resumed, woken by IRQ 59: 1 0 0 0 0 1 0 0 gpa4 0 Edge Power
omamobile-sleepd: sleeping (dark resume, 5 s grace)

The match is now [[:space:]](KEY_POWER|Power)$, the end of the line, so both labels light the PIN pad through omamobile-keys wake. test/sleepd.sh gains the 9a's line. It fails without the change and passes with it. The 7 Pro's case is unchanged. test/all passes.

On the palmtop: installed as 0.2.68 with tools/phone-install-package, auto-sleep on. Version 0.2.68 sits after #259's 0.2.67, so set whatever is free at merge.

… lock screen

sleepd recognised a power-key wake only by the gpio-keys label KEY_POWER, the 7 Pro's. The 9a's device tree labels the key Power, so its wake was taken for a dark resume and the palmtop went back to sleep 5 s later with the screen off.
@derekross

Copy link
Copy Markdown
Owner

Thanks, @W4HO-ham, nice find, and a clear write-up with the journal lines.

I checked the 7 Pro side: on our published kernel the power key is labelled KEY_POWER on cheetah (and on panther, felix and husky), and only tegu's device tree says Power. sleepd squeezes the /proc/interrupts line down to single spaces before the match, so anchoring on the end of the line is safe, and the 7 Pro's case matches as before. test/sleepd.sh passes merged onto today's main, and with the old line in place your new case fails, as you said.

One thing before I merge. The description says 0.2.68 is installed on the palmtop with auto-sleep on, but not what happened next. Could you paste the two journal lines from a power-key wake on this version (resumed, woken by IRQ 59: … Power, then a power-key wake: lighting the lock screen), with uname -r and pacman -Q omamobile-shell, and say that the PIN pad stayed up? That's all I need; no code change.

The version conflicts with main, so leave it. #259 goes in first, and this one keeps 0.2.68.

@W4HO-ham

W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

From a power-key wake just now on the palmtop, 7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty with omamobile-shell 0.2.68-1 and auto-sleep on:

15:23:25.854727 kernel: PM: suspend exit
15:23:25.989609 systemd-sleep[5682]: Successfully thawed unit 'user.slice'.
15:23:26.018652 omamobile-sleepd[1389]: omamobile-sleepd: resumed, woken by IRQ 59: 1 0 1 0 0 0 0 0 gpa4 0 Edge Power
15:23:26.020027 omamobile-sleepd[1389]: omamobile-sleepd: a power-key wake: lighting the lock screen

One press. W4HO says the screen lit about half a second later with the secure lock screen (the clock and the fingerprint icon) and it stayed up; he unlocked from there. Before this version, the same press was taken for a dark resume and slept again 5 s later (11:49-12:11 this morning, in the description). The thaw is 0.14 s after the exit now that #275's Wi-Fi hook no longer holds user.slice.

@derekross

Copy link
Copy Markdown
Owner

Thanks, that's exactly what I needed. The wake line ends in Power on IRQ 59 and the next line is the power-key path, both from 0.2.68, and the lock screen came up and stayed up after one press. That's the fix working.

One thing has changed since my last comment: #271 took omamobile-shell 0.2.69 on main, so this needs 0.2.70. That's the only conflict, and it's mine to fix at merge, so no need to push. I'll set 0.2.70 in the version file and the title. The automatic checks never ran on this branch, so I ran them myself on your branch merged onto today's main: the policy check is clean and the shell's tests pass, the new 9a case included.

I'll merge it with that change.

derekross pushed a commit that referenced this pull request Nov 1, 2026
…ing's no-reaction wake explained (#284)

A day of use on the Pixel 9a with auto-sleep on: seven real-use sleeps,
their lengths taken from the RTC, all of which woke, with the UFS check
after them. The morning's wake that didn't react is explained. AGENTS'
9a sleep gotcha now says the owner turned auto-sleep on on 11-01.

Maintainer edits at merge: the plan says the palmtop ran #268's 0.2.68
build (it lands as a later version), and the AGENTS line is updated.

Closes #284

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross derekross closed this in 784e5f7 Nov 1, 2026
@derekross

Copy link
Copy Markdown
Owner

Landed on main as 784e5f7 (squashed, authored by you), with the edits I described in my last comment. Thank you.

derekross pushed a commit that referenced this pull request Nov 2, 2026
…ing (#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel #178 on #156, both in review) and brcmfmac (kernel #56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after #178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (#268, #275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, #284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel #125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel #161, #96, #104 and #105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel #99), the panel ID (kernel #125), the RTC without the PMIC interrupt (kernel #55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes #307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ing's no-reaction wake explained (derekross#284)

A day of use on the Pixel 9a with auto-sleep on: seven real-use sleeps,
their lengths taken from the RTC, all of which woke, with the UFS check
after them. The morning's wake that didn't react is explained. AGENTS'
9a sleep gotcha now says the owner turned auto-sleep on on 11-01.

Maintainer edits at merge: the plan says the palmtop ran derekross#268's 0.2.68
build (it lands as a later version), and the AGENTS line is updated.

Closes derekross#284

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… lock screen (derekross#268)

On the Pixel 9a the power key's gpio-keys line is labelled "Power", not
KEY_POWER, so sleepd didn't recognise a power-key wake and the lock
screen stayed dark until a second press. sleepd now matches both labels;
the 7 Pro and the other boards keep KEY_POWER. Tested on the palmtop:
"resumed, woken by IRQ 59: ... gpa4 0 Edge Power", then "a power-key
wake: lighting the lock screen", and the lock screen lit on one press.
test/sleepd.sh covers the 9a's label.

Maintainer edit at merge: the version is 0.2.71 (main moved on).

Closes derekross#268

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ing (derekross#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (derekross#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel derekross#178 on derekross#156, both in review) and brcmfmac (kernel derekross#56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after derekross#178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (derekross#268, derekross#275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, derekross#284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel derekross#125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel derekross#161, derekross#96, derekross#104 and derekross#105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (derekross#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel derekross#99), the panel ID (kernel derekross#125), the RTC without the PMIC interrupt (kernel derekross#55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes derekross#307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants