Skip to content

DEVICES: the Pixel 9a row as the device package runs it - #165

Merged
derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:devices-tegu-row
Oct 31, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:devices-tegu-row

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

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:

  • works: what the package brings up at boot and what the kernel provides on its own (boot, storage, display, GPU, touch, buttons, USB networking, Bluetooth, battery, haptics, torch), each marked "unpublished kernel" the way raven's cells are, since the board device tree is still in review (kernel Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80);
  • testing: what works by hand and the package doesn't start yet (Wi-Fi, the charger driver, AoC, speakers and mics, sensors, NFC, cameras, fingerprint);
  • partial: suspend, on by default with its drain gap (SLEEP-PLAN);
  • WIP: GNSS (tracks satellites, no fix) and the modem (no SIM yet; the first SIM test is planned for 2026-11-03).

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.

@derekross

Copy link
Copy Markdown
Owner

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:

  1. Notes on main behind each cell. DEVICES.md and CONTRIBUTING §6.4 ask for a linked notes entry for each claim. Today most of the evidence is in open PRs, or only in threads. This repository's device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100, "what the device table's claims rest on" (display at 120 Hz, touch across sleep, power-key wake, Bluetooth, charging, haptics, torch) is still open. So is device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166's S1 result (the ~300 mA figure). The 0.2.0 boot and its smoke report are only in omamobile-device-tegu 0.2.0: the Pixel 9a's bring-up as a package #152's thread. For some claims I couldn't find a record anywhere: the gyroscope and the compass (the 10-26 and 10-29 smoke reports list accelerometer, light and proximity), NFC reading a payment card, GPU frequency scaling with a thermal throttle and runtime suspend, battery time estimates through UPower, and Wi-Fi kept loaded across sleep. Could you add a dated NOTES entry for the package boot (release, package versions, the smoke report) plus a line per claim, in the style of device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100's list, and link the entries from the cells? Or drop a claim until it has one. In practice that means device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 and device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166 land first. device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 changes this same row, so its DEVICES hunk and this PR conflict. I'd drop device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100's hunk and keep yours.

  2. Name the open kernel PRs as in review. "Unpublished kernel" covers the board DT, but several cells link only merged PRs, or none, and leave out the open ones the feature needs:

    (All of these are linux-omarchy-mobile numbers.) Please write them as derekross/linux-omarchy-mobile links with "in review", the way the Wi-Fi cell already does for kernel flame: split opt-in boot plumbing from pending writes #56.

  3. Suspend. "Partial" means on by default with a gap. Does the 9a suspend by itself when the screen goes off (idle sleep, or Power to sleep), or only when asked? The Pixel 7 Pro is WIP for exactly that reason. Also, "about 300 mA" contradicts SLEEP-PLAN on main (about 140 mA cable out) until device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166 merges.

  4. Boot. The package doesn't mark slot B, and AGENTS, device/tegu: a fallback to slot A on the 9a costs the Linux root #125 is still open, so a fallback to slot A costs the Linux root. If Boot stays "works", please say how slot B is marked today (the one approved omamobile-bootctl operation, by hand), or make it testing.

  5. Modem: please drop "the first SIM test is planned for 2026-11-03". It's a plan rather than a status, and it isn't in MODEM-PLAN.

  6. GNSS: "parked" belongs in the cell. The "tracks satellites" record is in device/tegu: GNSS G3's fifth to forty-fourth tries, the CP link hang, and GNSS parked #153, which I'm merging now.

  7. The rest of the page and the notes. The Wanted list's Pixel 9 line still says "9a (tegu): WIP … the board DTS isn't public yet". It's in review as kernel Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80, so please bring it in line with the row. NOTES on main also says "The matrix remains WIP until the kernel and prerequisites are public", and that sentence needs updating in the same PR.

  8. Small: "speakers capped below stock" would be clearer as the -10 dB ceiling that NOTES records. NOTES itself calls it a cautious number, not a comparison with stock.

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.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

All eight at 6c1f54f, in the order you gave:

  1. A dated NOTES entry, "2026-10-29: the device package boot, and what this row rests on": the 12:28 boot on 0.2.0, the release, the package versions, the 19-of-19 smoke report, then a line per claim that wasn't already in device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100's list. Every cell links it. Claims without a record are gone: no gyroscope or compass (only accelerometer, light and proximity have ever shown up here), and the GPU cell now says this boot runs at a fixed 160 MHz, so frequency scaling and the thermal zone count as in review. UPower's estimates (1.06 W, 18.5 h at 87 %), Wi-Fi kept across the S1 sleeps, and the 10-29 card read with the device/tegu: USB-C host mode through TCPM, and the 10-28 evening findings #131 modules each have their line. Agreed on the order: device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 and device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166 first, drop device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100's DEVICES hunk and keep this one; I'll rebase if you'd rather not.
  2. The open kernel PRs are named as in review with derekross/linux-omarchy-mobile links: device-lynx 0.2.0: the device package, the Arch root and the Wi-Fi plan #88 and Touch batch 4: landscape layouts for the home, call card, quick settings, drawer and recents (omamobile-shell 0.2.30) #90 (display), omamobile-shell: the home widgets collapse in landscape #85 and The screen lock never engages on a phone installed from our image #87 (GPU), omamobile-audio 0.5.3: the boost converter off below gain 17, DRE and the jump rule by stage; AOC-PLAN C9j #81 and initramfs, device-felix 0.1.4: unmask both display triggers #82 (touch), README, DEVICES, ROADMAP, AOC-PLAN: the speakers work #96 (haptics and torch), device/tegu: USB-C host mode through TCPM, and the 10-28 evening findings #131, device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 and device/cheetah, RELEASES: AVB footers on boot and init_boot (#11) #104 (NFC), DEVICES, README, ROADMAP, AGENTS: hardware status as of 2026-10-26 #63 and Some websites stop loading on Wi-Fi after unplugging the USB cable #103 (cameras), device-raven 0.1.26: the version #112 named #126 (fingerprint), Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80 (boot), flame: split opt-in boot plumbing from pending writes #56 (Wi-Fi), CONTRIBUTING: shared drivers leave the Pixel 7 Pro as it is #92 (charger).
  3. Suspend: the 9a sleeps by itself. The shell's sleep daemon suspends it once the screen is off and locked, and the power key or the RTC wakes it; the cell says so. The figure is device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166's; the cell reads "about 300 mA" and the NOTES line points at S1, so it is right once device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166 lands.
  4. Boot stays works and says how: slot B was marked by hand on 2026-10-28 with the devinfo write approved on 2026-10-22, now on hold (AGENTS, device/tegu: a fallback to slot A on the 9a costs the Linux root #125), and the package doesn't mark it. If you'd rather have testing until the marking is decided, say so and I'll change the word.
  5. The SIM date is gone.
  6. GNSS reads "parked: ... tracks satellites over SPI, no fix yet", with the plan link.
  7. The Wanted line now says the clocks and bindings are merged and the device tree is in review (Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80), and the NOTES sentence says the package provides the start-up and the row says per cell what is published, in review or by hand.
  8. "speakers at a -10 dB ceiling".

@derekross

Copy link
Copy Markdown
Owner

Thank you, this is a big step up. I checked all eight points against 6c1f54f. The NOTES entry with a line per claim, linked from every cell, is exactly what I hoped for. Dropping the gyroscope and compass and saying the GPU runs at a fixed 160 MHz keeps it honest. Suspend, Boot, the SIM date, GNSS, the Wanted line, the NOTES sentence and the speaker ceiling are all as I asked. Your Boot wording answers my question, so I'm happy with "works" there.

Two small things before it can merge:

  1. Display: "brightness, the panel sleeps when the screen is off". I couldn't find a record of either in the new entry, in device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 or in device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor #166. The older section of the same NOTES still says "Native display KMS, brightness, DPMS and GPU DVFS are not qualified". Could you add a dated line for each to the new entry (what you ran and on which boot), or drop the two from the cell for now?
  2. Charging: linux-omarchy-mobile CONTRIBUTING: shared drivers leave the Pixel 7 Pro as it is #92 is merged, so please drop "in review" after it. The cell stays "testing", since the driver is loaded by hand.

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 main into this branch will conflict in DEVICES: keep your row. Then #166, then this. #166 and this both add an entry at the top of NOTES, so I'll resolve that at merge unless you'd rather rebase.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Both in, and main merged (this row kept over #100's, both NOTES entries kept, newest first), head e385511:

  1. Display: I have no dated record of brightness or the panel's sleep on the package boot, so the cell drops both and says so until they have one.
  2. Charging: kernel CONTRIBUTING: shared drivers leave the Pixel 7 Pro as it is #92 is merged, so "in review" is gone; the cell stays testing.

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.

derekross added a commit that referenced this pull request Oct 30, 2026
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>
@derekross

Copy link
Copy Markdown
Owner

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 (e824483), and it fixes my mistake rather than yours: this morning I accepted "partial" for Suspend without checking the default. The shell's auto-sleep does nothing until the omamobile-sleep toggle is on, and the toggle ships off (packages/omamobile-shell/install says so, and the shell's tests fail if anything turns it on by default). So "on by default" held on your palmtop but not on a fresh install, which is the same reason the Pixel 7 Pro's Suspend is WIP. With #166's three sleeps that didn't wake, the cell now reads "WIP (s2idle when asked for, or through the shell's auto-sleep with the omamobile-sleep toggle on, which ships off; … three test sleeps have not woken, so sleep tests stay attended (SLEEP-PLAN S1); …)". The NOTES Suspend line says the same. Change anything you'd word differently.

I'll merge #166 first and then this one, putting the S1 entry above your package entry in NOTES.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Merged main again (kept your rows for the 8 Pro and the 7, and your Suspend wording from e824483). One new cell: GNSS moves from WIP to testing. The palmtop got its first fix this evening on a bring-up kernel; the record is a new line in the 9a NOTES entry, and the fixes are on kernel #137.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@derekross

Copy link
Copy Markdown
Owner

Thanks for keeping this row honest, and for saying plainly that the GNSS wording was a judgement call. Three things before it lands:

  1. The merge of my branch (b642bbb) brought back the old Pixel 8 Pro and Pixel 7 rows, so merging now would undo device/husky: UFS-PLAN: U4, the Omarchy image boots #187 and DEVICES: the matrix as of 2026-10-30 #177. Please take those two lines from main (husky has moved again today with device/husky: the buttons and touchscreen work on test kernels #208).
  2. GNSS: started by hand and ending with the modem link is WIP by the legend ("works" means on by default), and its record lands with device/tegu MODEM-PLAN, AGENTS: GNSS gets a fix on the 9a #202.
  3. Several linked kernel PRs have moved: Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80 landed with omamobile-audio 0.5.3: the boost converter off below gain 17, DRE and the jump rule by stage; AOC-PLAN C9j #81; omamobile-audio 0.5.3: the boost converter off below gain 17, DRE and the jump rule by stage; AOC-PLAN C9j #81, initramfs, device-felix 0.1.4: unmask both display triggers #82, device-lynx 0.2.0: the device package, the Arch root and the Wi-Fi plan #88 and device/tegu: USB-C host mode through TCPM, and the 10-28 evening findings #131 are merged; device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 #100 is closed. Could you refresh those cells?

I'm doing today's DEVICES pass myself for the merged kernel work, so if it's easier, rebase onto that once it's in.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

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.

@derekross
derekross merged commit 01b40fc into derekross:main Oct 31, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thanks for reducing it to the one cell, and for keeping it honest by the legend. Merged; #150 went in today too. I'm redeploying the site now so it shows on omamobile.org/devices. When #114 and the link fix land and Location works without starting it by hand, the cell can move to works.

derekross pushed a commit that referenced this pull request Oct 31, 2026
…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>
@derekross

Copy link
Copy Markdown
Owner

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.

derekross added a commit that referenced this pull request Oct 31, 2026
… 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>
derekross added a commit that referenced this pull request Nov 1, 2026
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
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
)

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.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… 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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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
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