Skip to content

device/tegu SLEEP-PLAN: a day of use with auto-sleep on, and the morning's no-reaction wake explained - #284

Closed
W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:tegu-sleep-autosleep-day
Closed

W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:tegu-sleep-autosleep-day

Conversation

@W4HO-ham

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

Copy link
Copy Markdown
Contributor

The record of today's auto-sleep use, which #256 didn't cover. W4HO turned the shell's auto-sleep on this morning, and a temporary hook logged each sleep's real length by the RTC. Seven sleeps in real use (11 s to 22 minutes) all woke, with no UFS errors.

The one wake that looked like a hang at the time ('pressed Power, no reaction', then Power + Volume Up) wasn't one. The journal shows the press woke the palmtop at 12:11:04, and sleepd took it for a dark resume and slept again 5 s later (the 9a's power key reads Power in /proc/interrupts). The second press, during the Power + Volume Up hold, woke it again. #268 recognises the key, and #275 brought the time from a press to a lit screen down from about 1.2 s to about 0.25 s.

The status paragraph now says auto-sleep is on by the owner's choice since 2026-11-01. The paragraph says plainly that this adds evidence but doesn't retire the hangs of 10-28 to 10-30. Docs only; tools/pr-check passes.

…ing's no-reaction wake explained

Seven real-use sleeps on 2026-11-01 all woke. The one that looked like a hang was a power-key wake that sleepd took for a dark resume and slept again 5 s later; derekross#268 and derekross#275 fix that and the late lock screen.
@derekross

Copy link
Copy Markdown
Owner

Thank you for writing up the day, and for timing each sleep with the RTC: the kernel log's clock stops during s2idle, so those are the lengths that count. Seven real-use sleeps from 11 s to about 22 minutes, all woken, is useful evidence. The 12:11 "no reaction" turning out to be a wake that sleepd put straight back to sleep, rather than a hang, is a good piece of digging. I also like that the paragraph says plainly this doesn't retire the 10-28 to 10-30 hangs. tools/pr-check is clean and it merges cleanly.

Two things to change, and a question:

  1. omamobile-shell 0.2.68: a wake by the Pixel 9a's power key lights the lock screen #268 isn't merged yet: it's open, and it conflicts with main now that main's shell is 0.2.69, so it will land as a later version than 0.2.68. "omamobile-shell 0.2.68 (omamobile-shell 0.2.68: a wake by the Pixel 9a's power key lights the lock screen #268) recognises the 9a's power key" reads as if it shipped. I'd say the palmtop ran omamobile-shell 0.2.68: a wake by the Pixel 9a's power key lights the lock screen #268's 0.2.68 build, which stays true whichever lands first.
  2. AGENTS.md still says, in the 9a's sleep gotcha, that the auto-sleep toggle has been off on the palmtop since the 10-30 shell reinstall. With your status line changed, that sentence is now out of date. I'd have it say the package ships the toggle off, that you turned it back on on 11-01 with seven clean sleeps that day, and that keeping it on is your call.

I can make both edits at merge if you're happy with that (you've allowed edits). Nothing else in the PR needs to change.

The question: how was "no UFS errors" checked? One dmesg | grep -E "link startup failed|Host init failed|I/O error" at the end of the boot covers all seven sleeps if they were in a single boot (I take it the Power + Volume Up hold was released before it reset). If so, a few words saying that would let a reader see what the claim rests on.

One practical note, now that auto-sleep is on and the palmtop sleeps unattended: the dead-storage failure from 10-30 looks like a dark palmtop that ignores the power key. If you see that, the AGENTS check (dmesg for those lines, then echo b > /proc/sysrq-trigger) is the way out, so it's worth having SSH or Tailscale to hand.

@derekross derekross closed this in c7ab1c9 Nov 1, 2026
@derekross

Copy link
Copy Markdown
Owner

Landed on main as c7ab1c9 (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
…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