Skip to content

omamobile-device-tegu 0.2.22: auto-sleep on by default on the Pixel 9a, and its Suspend cell to works - #912

Open
W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:device-tegu-auto-sleep
Open

W4HO-ham wants to merge 1 commit into
derekross:mainfrom
W4HO-ham:device-tegu-auto-sleep

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

omamobile-device-tegu now installs /usr/share/omamobile/auto-sleep-default, so omamobile-shell's user setup turns the shell's auto-sleep on once for a 9a user (the owner's later choice stays, as on the 7 Pro, #737). With the modem up the 9a still doesn't sleep: the modem's boot unit holds its sleep inhibitor, and that is unchanged here.

What it rests on, all on the published branch (omamobile at 26867fc4e, with kernel #224, #232, #247 and #258):

The touchscreen question (#846): it wakes with none. The input log has no frame at all for the day, so neither early wake came with a touch, and the driver (synaptics-tcm) logged nothing at either (no unexpected status, no resync, no bad header). Whatever the controller sent was one of the messages the driver drops silently: an idle status, an identify, a heat-map frame or a report with no contact. One more thing the kernel's own timestamps show (_SOURCE_MONOTONIC_TIMESTAMP; journald's receive time is useless here, since it is frozen too): the freezes lasted 0.16 s and 3.09 s, and last night's four lasted 2.7, 3.3, 1.6 and 3.8 s. All six early wakes so far came within 4 s of the freeze's start, none later in the minute, so it looks like something the controller does shortly after the host stops reading it rather than noise at random times. tcm_suspend() only disables the interrupt and tells the controller nothing (the driver's own comment says Google's driver turns the heat-map report off at suspend; this one does that once, at probe). For the auto-sleep default it costs a dark wake and a sleep again after the shell's 5 s grace, about one sleep in 80 (6 of 470).

DEVICES: the Suspend cell goes from "works (opt-in)" to "works", saying the auto-sleep is on by default from 0.2.22 and what the touchscreen does. SLEEP-PLAN S1 gets today's row. MODEM-PLAN: the line you asked for in #846, naming commit ec597afa where it said "0.3.44, #837's branch".

Tests: the package's test/all checks the file is staged; tests/all and tools/pr-check origin/main pass.

…leep on by default on the Pixel 9a, its Suspend cell to works

The package now installs /usr/share/omamobile/auto-sleep-default, so omamobile-shell's user setup turns the shell's auto-sleep on once for a 9a user, as on the 7 Pro (derekross#737); the owner's later choice stays, and with the modem up the 9a still doesn't sleep, because the modem's boot unit keeps its sleep inhibitor. What it rests on is on the published branch: 300 of 300 timer-woken sleeps on the night of 2026-11-17, and on 2026-11-18 the series derekross#846 asked for, with the touchscreen's input events logged: 170 of 170, the two the touchscreen ended early (0.16 and 3.09 s into the freeze) with no touch reported and no line from its driver. All six early wakes so far came within 4 s of the freeze's start. SLEEP-PLAN S1 gets that run's row, DEVICES the cell, and MODEM-PLAN names commit ec597af where it said 0.3.44, as asked in derekross#846.
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.

1 participant