Repository navigation
DEVICES: the Pixel 9a row as the device package runs it - #165
Conversation
|
Thank you for this. The row was badly out of date, and the split you've made is the right one: works for what the package starts at boot, testing for what's still started by hand, WIP for GNSS and the modem. Your #152 boot at 19:29 (graphics start at 120 Hz, the GPU, haptics, torch, gauge and Bluetooth up, 19 of 19 in the smoke report) is good evidence that the package really runs the "works" set by default. A matrix row is what people read before they buy a phone, though, so each cell has to rest on notes that are on main, and it has to say when it depends on code that's still in review. Here's what I'd ask for before merging:
None of this is a doubt about what the palmtop does. It's about making the page say exactly what's published, what's in review, and where the record is. Thanks for keeping the 9a's status honest. |
|
All eight at 6c1f54f, in the order you gave:
|
|
Thank you, this is a big step up. I checked all eight points against Two small things before it can merge:
Optional: the Wi-Fi line says every S1 sleep "reconnected", but #166's S1 only says Wi-Fi was kept. Either drop "reconnected" or add it to S1. For "reconnects after a replug" in the USB cell, a pointer to the replug line in #100's USB-C paragraph would do. #100 is merged now, with its own version of the 9a row, so merging |
|
Both in, and main merged (this row kept over #100's, both NOTES entries kept, newest first), head e385511:
Optional ones: the Wi-Fi line now says kept, not reconnected (S1 only shows kept), and the USB cell points at #100's replug record. The NOTES conflict with #166 at the top is yours to resolve at merge, as you offered. |
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, both points are exactly right: the Display cell now claims only what the record shows, #92 reads as merged, and the Wi-Fi and USB wording is tighter too. I've pushed one more change to your branch ( I'll merge #166 first and then this one, putting the S1 entry above your package entry in NOTES. |
|
Your Suspend wording is right, and thanks for catching it: my palmtop has the omamobile-sleep toggle on, so "on by default" was true here and not on a fresh install. Nothing I'd change. Merge order as you say. |
|
Updated the 9a's GNSS cell: the Location switch serves the receiver to GeoClue's clients now (46 of 52 GGA fixed, 9-13 satellites, first fix about 80 s after a client connects), and the cell names what it needs: kernel #150 and #151 and the package in #114. It also says what still limits a session, the modem's PCIe link. Everything else in the row is unchanged. |
|
Changed the 9a's GNSS cell again, and I want to be plain about the judgement in it. The owner asked for the row to read works; what the palmtop actually does is give a fix and serve it to GeoClue's clients through the Location switch, and then lose the session when the modem's PCIe link fails, a minute or two in. So the cell now says "works on a bring-up kernel" and names that limit in the same sentence, with the fix counts and the three PRs it needs. If you read that as too strong for the matrix, downgrade it as you did with Suspend and I won't put it back; the facts behind it are in MODEM-PLAN "G3, resolved" and on kernel #137, and the link is the open item I'm working on. |
|
Reworded the GNSS cell once more so it follows the table's own pattern, works with the detail in parentheses, as the 7 Pro's cells do. The detail still says what it rests on (kernel #150 and #151 and this repo's #114), the numbers, that it is started by hand, and that a session lasts as long as the modem's PCIe link. Nothing else in the row changed. |
|
All three in, on top of today's main: the Pixel 8 Pro and Pixel 7 rows are main's (so #187, #177 and #208 stand); GNSS reads WIP, started by hand, with the detail kept in the cell (your legend is the right call: it is on by hand, not by default, and the record lands with #202); and the kernel cells now say merged for #81 (with #80 in it), #82, #88, #126 and #131, with #100 noted as closed into #131. If your DEVICES pass lands first, say so and I'll rebase this onto it. |
3c0b80e to
19c0541
Compare
|
Rebased onto your pass (8efed1a), and reduced to the one thing it still carries that the pass doesn't: the GNSS cell, which read "no (the engine faulted ...)" and now records the fix, as WIP by the legend, with the numbers, what it needs (kernel #150 and #114), the one-to-five-minute session limit and the links to the plan and #202. Every other cell is yours as you left it. If you'd rather carry that cell into your own pass, close this and I'll not mind. |
…ns it Restores the row and its record from #165 (3c0b80e), which were dropped when that pull request was rebased onto the 2026-10-31 DEVICES pass: works for what omamobile-device-tegu brings up at boot (boot, storage, display, GPU, touch, buttons, USB networking, Bluetooth, battery, haptics, torch; the kernel pieces marked unpublished or in review, as raven's are), testing for what runs by hand (Wi-Fi, charging, AoC, speakers and mics, sensors, NFC, cameras, fingerprint), WIP for the modem and suspend. The GNSS cell is the one merged in #165. The NOTES entry is the record the row links to. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Follow-up: your rebase onto my DEVICES pass dropped more than it needed to. My pass didn't carry your works/testing/partial row or the "2026-10-29: the device package boot, and what this row rests on" NOTES entry the row links to, so after the merge the 9a still read WIP everywhere. I restored both from your 3c0b80e as 74e0afd, authored by you: 11 works, 8 testing, WIP for GNSS (the cell merged here), the modem and suspend. The kernel PRs it calls "in review" are all still open, so those stand. It'll be on omamobile.org/devices after the deploy that's running now. Shout if anything in it moved since 3c0b80e. |
… rounds L-348 to L-361: shared drivers judged against every int-line user (#150), board pins against every stock user (#151), ownership flags under the consumer's lock (#152), /chosen children and Google's panel constants (#154), same-day notes PRs on one device (#208/#209), merge simulations for DEVICES rows, ours included (#165), stacked PRs that merged main (#115/#117), titles behind renumbered versions, a contributor merge that dropped the PR (#99), smoke package lists as provenance and "owner-authorized" writes (#200), promised fixes and named tags checked on the remote (#153/#157/#158), and file swaps into old packages (#193). C-23 (usbc-deadman's device scope, kernel #107) and C-24 (BNEP in a lynx-only fragment, #98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Twelve lessons from round 33: sleep lengths from the RTC rather than dmesg, Device-scope batteries, probing an --adopt style mode, shared fragment =y and unknown symbols, descriptors checked with the loader, parent buses before enabling a node, charge-rate arithmetic, merge-tree with duplicate commits, contributor claims about our branch, CI after a retarget, and board supplies against Google's dtsi. C-25 records our wrong min = max request on kernel #165. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
) The 9a's GNSS cell goes from "no" to WIP: a position fix on 2026-10-30 and Omarchy's Location switch serving it on 2026-10-31, started by hand (46 of 52 GGA sentences fixed, 9-13 satellites, first fix about 80 s after a client connects). It needs kernel derekross#150 (merged) and derekross#114, and a session lasts as long as the modem's PCIe link, one to five minutes, which is the open item. The record lands with derekross#202.
…ns it Restores the row and its record from derekross#165 (3c0b80e), which were dropped when that pull request was rebased onto the 2026-10-31 DEVICES pass: works for what omamobile-device-tegu brings up at boot (boot, storage, display, GPU, touch, buttons, USB networking, Bluetooth, battery, haptics, torch; the kernel pieces marked unpublished or in review, as raven's are), testing for what runs by hand (Wi-Fi, charging, AoC, speakers and mics, sensors, NFC, cameras, fingerprint), WIP for the modem and suspend. The GNSS cell is the one merged in derekross#165. The NOTES entry is the record the row links to. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… rounds L-348 to L-361: shared drivers judged against every int-line user (derekross#150), board pins against every stock user (derekross#151), ownership flags under the consumer's lock (derekross#152), /chosen children and Google's panel constants (derekross#154), same-day notes PRs on one device (derekross#208/derekross#209), merge simulations for DEVICES rows, ours included (derekross#165), stacked PRs that merged main (derekross#115/derekross#117), titles behind renumbered versions, a contributor merge that dropped the PR (derekross#99), smoke package lists as provenance and "owner-authorized" writes (derekross#200), promised fixes and named tags checked on the remote (derekross#153/derekross#157/derekross#158), and file swaps into old packages (derekross#193). C-23 (usbc-deadman's device scope, kernel derekross#107) and C-24 (BNEP in a lynx-only fragment, derekross#98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oss#165 Twelve lessons from round 33: sleep lengths from the RTC rather than dmesg, Device-scope batteries, probing an --adopt style mode, shared fragment =y and unknown symbols, descriptors checked with the loader, parent buses before enabling a node, charge-rate arithmetic, merge-tree with duplicate commits, contributor claims about our branch, CI after a retarget, and board supplies against Google's dtsi. C-25 records our wrong min = max request on kernel derekross#165. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
The Pixel 9a row in docs/DEVICES.md still reads WIP in nearly every column, from before omamobile-device-tegu merged (#152). This replaces it with what the palmtop runs today, in the legend's terms:
Links go only to files on main and to the kernel pull requests named in device/tegu/SUPPORT-STATUS. One row, no other change; tools/pr-check passes.