Skip to content

device/tegu SLEEP-PLAN, DEVICES: the overnight series, 126 of 127 sleeps woke - #347

Merged
derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-sleep-overnight
Nov 3, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-sleep-overnight

Conversation

@W4HO-ham

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

Copy link
Copy Markdown
Contributor

The palmtop ran an overnight series of 120 s sleeps from 2026-11-01 to 11-02: systemctl suspend with an RTC alarm, auto-sleep off for the run, the console kept through the freeze, cable in, the modem never loaded, NFC polling stopped by the sleep hook. 126 woke clean (suspend_stats 126 and 0, wake IRQ 56 each time, no UFS or ACPM lines, Wi-Fi back each time). The 127th never woke and needed Power + Volume Up in the morning; it entered that sleep exactly like the others, and nothing was kept in ramoops, so a button reset doesn't keep that region either.

SLEEP-PLAN gets the record after "A day of use with auto-sleep on" and a status line that counts six no-wakes since 10-28. DEVICES' Suspend cell says six instead of five, with the two rates (one in 21 on 11-01, one in 127 overnight). Suspend stays at testing.

@derekross

Copy link
Copy Markdown
Owner

Thank you, 126 of 127 is a useful number, and the counts now agree between the plan and the matrix. One note for next time: AGENTS asks for attended sleep tests on the 9a, and this series ran unattended overnight; please check with me before another unattended run. I'll update the AGENTS gotcha's counts myself. Merging; whichever of this and #372 lands second resolves the DEVICES row.

…eps woke

Two hundred 120 s sleeps were planned overnight from 2026-11-01 to 11-02 with the console kept through the freeze: 126 woke clean and the 127th never did, and a Power + Volume Up reset kept nothing in ramoops. The status lines count six no-wakes now.
@W4HO-ham
W4HO-ham force-pushed the tegu-sleep-overnight branch from 44f67c7 to a6a32dc Compare November 3, 2026 05:40
@derekross

Copy link
Copy Markdown
Owner

I tried to merge this, but the DEVICES row now conflicts with main (other PRs landed in the same table today). Could you merge main and keep both changes in that row? Then it goes straight in.

@W4HO-ham

W4HO-ham commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

Done: rebased on main. The 9a's row keeps main's cells (the modem cell from #356 and the rest) with this PR's Suspend cell.

@derekross

Copy link
Copy Markdown
Owner

Thanks for the rebase. The 9a row keeps main's modem cell and takes your Suspend cell, and the counts match the plan. Merging; one of the telephony PRs will have to rebase this row again when it lands after this.

@derekross
derekross merged commit 7c8928f into derekross:main Nov 3, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…eps woke (derekross#347)

Two hundred 120 s sleeps were planned overnight from 2026-11-01 to 11-02 with the console kept through the freeze: 126 woke clean and the 127th never did, and a Power + Volume Up reset kept nothing in ramoops. The status lines count six no-wakes now.
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