Repository navigation
DEVICES: the Pixel 9a's Suspend cell to works (opt-in), with the runs on the published branch - #846
Conversation
|
Thank you for this, and for asking the release question up front. You've done both halves of what the cell asked for: #247 is merged, and the sleeps on the published branch as it is all woke. Before the word changes I'd like four things in the cell and its notes, and I owe you two decisions.
One wording point: the 86 sleeps were each ended by the modem within 29 s, so none reached its alarm; please say that, so nobody reads them as 86 timer wakes. My two decisions, and I'd like your view on the second. On the release: the 9a has no release image, so what a 9a owner builds is the published branch, and I'm inclined not to wait for the tag as long as the cell keeps "kernel #247 comes with the next release". On the series: the three failures were all found in timer-woken sleeps with the modem off, and nobody has run that plain series from the published branch as it is yet. A I'll also open an issue for the awake hang on the kernel side, so it has a home outside #758. |
|
Yes to all four, and yes to the series.
The 86 will read as what they were: each ended by the modem within 29 s, and none reached its alarm. On the release I agree: the cell keeps "kernel #247 comes with the next release". On the series: I'll run it tonight, timer-woken, on the charger, with the modem off for the boot, from derek/omamobile as it is, a few hundred sleeps with the switches that showed the third failure ( |
…ell to works (opt-in), with the runs on the published branch The cell's old condition was a fix for the third no-wake and a series from the published kernel as it is. Kernel derekross#247 is merged, and on derek/omamobile at 26867fc4e (derekross#224, derekross#232, derekross#247, derekross#258) 300 of 300 sleeps with a 60 s alarm woke with the modem off on the night of 2026-11-17: 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop. On 2026-11-16, 86 of 86 sleeps entered with the modem up woke, each ended by the modem within 29 s, so none of those reached its alarm. From the review of derekross#846: the word is "works (opt-in)", since auto-sleep ships off on the 9a (omamobile-device-tegu doesn't install /usr/share/omamobile/auto-sleep-default); the cell says again that a new sleep test runs attended first and that the modem's inhibitor stays, the owner's palmtop under derekross#809 excepted; and it cites merged notes, not derekross#758's comments. MODEM-PLAN gains the 2026-11-16 section: the runs on the test kernel and on the published branch under derekross#809's terms, the route finding that became derekross#837, and the palmtop hanging awake twice at a power-up of the modem's link (once between the sleeps of a series, once in everyday use with Wi-Fi connected), with the NV check after each. The Modem cell names those hangs. SLEEP-PLAN's S1 table gains a row for the 86 modem-up sleeps and one for the night's 300, and its status line is brought up to date.
1a0595b to
85ca091
Compare
|
The series ran last night, and the four changes are pushed (85ca091). The title and description are updated too. The series.
The changes.
The 86 now read as each ended by the modem within 29 s, none reaching its alarm. For plain "works" I have the device-tegu change ready: it installs |
|
On the four early wakes: nothing in last night's record ties them to the charger. upower had the pack at fully-charged from 21:00:53, a minute into the series, until the end. Its voltage history has a reading at every wake, and it falls from 4.317 V to 4.303 V over the seven hours, in steps of 3 mV or less after the first two cycles. Across the 29th, 199th and 247th the reading stays within 1 mV (4.308, 4.305 and 4.304 V before and after). For the 298th the history ends two minutes before it. The journal has no line from the touchscreen's driver at any of them, only sleepd's |
|
Thank you. All four changes are in as I asked, and the series is the one the old cell was waiting for: 300 of 300 from the published branch as it is, 296 on the alarm, with the wake source and the length of every one written down. The 86 now read as what they were, the hangs are in the Modem cell with the NV check after each, and the cell cites merged notes. I compared the row with main's cell by cell (only Suspend and Modem change), checked that the release tag doesn't have #247 yet, and followed the anchors. Merging it. On how the night ran: the row says the first two cycles were followed from the laptop and the rest ran alone with your yes for that night, on a build that already had its first sleeps behind it. That is within the sleep entry as I read it, and writing it into the row is exactly what I want from a record. Three things for afterwards:
|
The 9a's Suspend cell said "works once that no-wake is found and fixed and a series has run from the published kernel as it is, with kernel #224 in it". Both are done now:
omamobile.configwith nothing added, so with AGENTS: on the Pixel 9a a plain fastboot flash of slot B clears its successful flag too #224, device-panther 0.1.3: USB comes back after a replug, and the battery plan #247, omamobile-omarchy 0.1.23: no launch toast for a desktop entry that runs omarchy-shell #232 and device-panther 0.1.4: display brightness, and the display plan #258. On the night of 2026-11-17, with the modem off for the boot, 300 of 300 sleeps with a 60 s alarm woke: 296 on the alarm after 59.2 to 60.3 s, and 4 after 3 to 5 s on the touchscreen's interrupt with nobody at the palmtop.After the review, this pull request:
omamobile-device-tegudoesn't install the file that turns it on (/usr/share/omamobile/auto-sleep-default);device/tegu/MODEM-PLAN.md(the test kernel and the published branch, the route finding that became omamobile-modem-sit 0.3.45: mobile data back at once after a wake with no Wi-Fi, and a reconnect that comes back IPv6 only tried again #837, and both hangs awake at a power-up of the modem's link, with the NV check after each), and cites that section instead of device/tegu MODEM-PLAN: the 9a sleeps with the modem up on a test kernel with the sleep guard (2026-11-13) #758;The cell keeps "kernel #247 comes with the next release" and the 300 mA drain caveat.