Repository navigation
Conversation
… 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.
|
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 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 ( The version conflicts with main, so leave it. #259 goes in first, and this one keeps 0.2.68. |
|
From a power-key wake just now on the palmtop, 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 |
|
Thanks, that's exactly what I needed. The wake line ends in 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. |
…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>
|
Landed on main as 784e5f7 (squashed, authored by you), with the edits I described in my last comment. Thank you. |
…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>
…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>
… 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>
…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>
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-sleepdrecognises a power-key wake by the name in/proc/interrupts, and only matchedKEY_POWER, the gpio-keys label in the Pixel 7 Pro's device tree. The 9a's labels the keyPower, so its wake looked like a dark resume. From the palmtop's journal today:The match is now
[[:space:]](KEY_POWER|Power)$, the end of the line, so both labels light the PIN pad throughomamobile-keys wake.test/sleepd.shgains the 9a's line. It fails without the change and passes with it. The 7 Pro's case is unchanged.test/allpasses.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.