From 6cfc7ea079cae94e20925639da92a929a77e82f8 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Wed, 18 Nov 2026 22:19:54 -0649 Subject: [PATCH 1/3] DEVICES, device/tegu MODEM-PLAN: the Pixel 9a's GNSS cell to works (opt-in), with the runs on the published branch Location now works whenever the modem is up, and the modem's start at boot is opt-in for the reason the Modem cell names, so the cell takes the same form as the Modem and Suspend cells. The record has the runs on the published omamobile at 26867fc4e with #864 and #921: a GNSS fix in 25 of 28 boots from a request made before gnssd was up, each reboot made during a session, none skipping GNSS; GeoClue's own start stalled in the other 3, cause open; and five switch-offs and -ons with a fix 7.5 to 9.4 s after each request. --- device/tegu/MODEM-PLAN.md | 58 +++++++++++++++++++++++++++++++++++++++ docs/DEVICES.md | 2 +- 2 files changed, 59 insertions(+), 1 deletion(-) diff --git a/device/tegu/MODEM-PLAN.md b/device/tegu/MODEM-PLAN.md index 7014ed8c7..fa3b3227a 100644 --- a/device/tegu/MODEM-PLAN.md +++ b/device/tegu/MODEM-PLAN.md @@ -2007,6 +2007,64 @@ with the modem up is one whose link cycles all day; and a timer-woken sleep with the modem up has not been seen, because the modem ends every sleep within half a minute. +### Location on the published branch (2026-11-19) + +All runs on the palmtop, on the charger, with Location on, Wi-Fi up and the +palmtop indoors at one spot. The kernel was the published `omamobile` at +26867fc4e (`7.3.0-rc6-omamobile-push1-g26867fc4e826`, defconfig plus main's +`omamobile.config`, with the overlays `public-ramoops` and `modem-cpif`), so +the CP and GNSS ran from the in-tree drivers, and `omamobile-tegu-modem-boot` +started the modem. Packages: omamobile-modem 0.1.27-1, omamobile-device-tegu +0.2.21-1, and omamobile-gnss 0.2.11-1 from #864 with #921's start script, +unit and `gnss-slsi` profile in place. Each run printed each position's +accuracy and GeoClue's description of its source, never a position. + +**At boot.** Each boot was a clean `systemctl reboot`, then `where-am-i -t +240` as the session user at 15 to 16 s of uptime. That is before gnssd +listened, which it did at 38 to 40 s. The next reboot came with that +session still running (the bridge's idle exit is 60 s), which is how a +reboot during a session is tested. + +| | boots | GNSS fix | first GNSS fix, s after boot | without one | +| --- | --- | --- | --- | --- | +| #921 without the client's SIGPIPE fix | 8 | 3 | 82 to 85 | 1 GeoClue start stall; 4 boots skipped GNSS | +| both of #921's changes | 28 | 25 | 75 to 119 | 3 GeoClue start stalls, all in the first 8 | + +A GNSS fix here is GeoClue's "GPS GGA" at 3 m. Every boot that reached +GeoClue also had its IP position (25 km) at 17 to 18 s. In the first run, +the fourth reboot came while a session was running; the profile stopped +itself before systemd's stop, the hang marker stayed, and the next four +boots skipped GNSS. #921's second change fixes that (the client survives +the bridge going first). With it, none of the 28 boots found a marker. +GeoClue's debug log was on for 12 of the 28 boots. On the daily kernel +(`7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`), 16 more boots +the same way each had a GNSS fix, 76 to 114 s after the boot. + +**After the switch.** Five rounds of Location off and on as the +quick-settings tile does it (`omamobile-gnss` run from the session), +followed each time by `where-am-i`: + +- After off: the setting read false, the agent and the stack were stopped, + and the socket was disabled and stopped. +- After on: the setting read true, the agent ran, and the socket was + enabled and listening. +- GeoClue's IP position came 1.1 s after each request, and a GNSS fix came + 7.5 to 9.4 s after it, five of five. + +**Open: GeoClue's start stall.** In 3 of the first 8 boots with both +changes, and once before, GeoClue's own start stopped after "Failed to +connect to avahi service" and never took its bus name. where-am-i's call to +start it timed out after 25 s ("Error calling StartServiceByName"), and +systemd logged GeoClue as started only at the shutdown, 44 s later. Each +time the request came about 16 s into the boot, while the session and its +GeoClue agent were starting. + +It never happened with GeoClue's debug log on (12 boots), nor in the 8 +boots after that without it, nor in the 16 on the daily kernel. So it is a race in GeoClue's start that the +log's timing hides. It is not understood yet, and it is GeoClue's own start, +not the GNSS path. Not checked: whether a later request in such a boot gets +through once systemd's start timeout (90 s) ends the stalled GeoClue. + ### M2: the link only (modem link driver, `allow_hw=1`; risk: medium) One step per run, the CPIF overlay not applied, the link overlay applied diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 22a8d46a7..52161754d 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -26,7 +26,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); native test image on one phone; slot B marked successful and `vbmeta_b` verification turned off, both without project approval; see notes) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); guarded `userdata` root on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); connected output on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); Panfrost render node present) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); touchscreen detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); gpio-keys detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); USB network and SSH on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); link up; traffic not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); controller powered; pairing not checked) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charge and temperature reported) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | | Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - | | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | -| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (Omarchy's Location switch serves fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up; `omamobile-device-tegu`'s boot unit, opt-in ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), starts gnssd with the modem: on 2026-11-03, after a reboot with nothing started by hand, a session through the switch's socket had 133 of 135 GGA sentences fixed, first fix 48 s after the client connected, 18 satellites; on 2026-11-09 the same from the in-tree drivers (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 (omamobile-gnss 0.2.5's start, by hand, the modem link left to cycle) had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); not on by default because the modem isn't (the Modem cell); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (opt-in) (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; on the published branch (derek/omamobile 26867fc4e) the palmtop hung awake twice on 2026-11-16 at a power-up of the modem's link, once between the sleeps of a series and once in everyday use with Wi-Fi connected, with no oops and no UFS line, cause open ([record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | works (opt-in) (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on; opt-in, not on by default: `omamobile-device-tegu` doesn't install the file that turns auto-sleep on for a phone (`/usr/share/omamobile/auto-sleep-default`, [#737](https://github.com/derekross/omarchy-mobile/pull/737)) yet; the power key lights the lock screen on the first press, and the RTC wakes it ([kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10); the three ways a wake failed are fixed on the published branch (kernel-2026.11.15 has the first two; kernel #247 comes with the next release): dead storage after a wake (the UFS pads came back as plain inputs; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), merged 2026-11-12, re-applies the pin state at resume), a silent no-wake with C2 entered through s2idle's own path ([#591](https://github.com/derekross/omarchy-mobile/pull/591)'s sleep hook), and a core locked up in the noirq resume of an HSI0 USI ([kernel #247](https://github.com/derekross/linux-omarchy-mobile/pull/247), merged 2026-11-15, keeps those clocks on: 300 of 300 on the published tip with it, 2026-11-13); on the published branch as it is (derek/omamobile 26867fc4e, with kernel #224 and #247, and #232 and #258 for the modem) 300 of 300 sleeps with a 60 s alarm woke with the modem off, 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop (the night of 2026-11-17, [plan](../device/tegu/SLEEP-PLAN.md) S1), and 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, with the modem ONLINE and mobile data back after every one (2026-11-16, [record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); a new sleep test still runs attended first, and with the modem up the modem's sleep inhibitor stays, the owner's palmtop under [#809](https://github.com/derekross/omarchy-mobile/issues/809) excepted (AGENTS.md); that day the palmtop also hung twice while awake at a power-up of the modem's link, which is in the Modem cell; the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [plan](../device/tegu/SLEEP-PLAN.md) S1, [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | +| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (Omarchy's Location switch serves GNSS fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up, and the modem's start at boot is opt-in, as the Modem cell says: `omamobile-device-tegu`'s boot unit ([#372](https://github.com/derekross/omarchy-mobile/pull/372)) starts gnssd with it. On the published branch (`omamobile` at 26867fc4e) with [#864](https://github.com/derekross/omarchy-mobile/pull/864) and [#921](https://github.com/derekross/omarchy-mobile/pull/921) (2026-11-19, [record](../device/tegu/MODEM-PLAN.md#location-on-the-published-branch-2026-11-19)): a request made 15 to 16 s into a boot, before gnssd was up, had a GNSS fix (3 m) in 25 of 28 boots, 75 to 119 s after the boot, each reboot made during a session; in the other 3 GeoClue's own start stalled (not seen in the last 20 boots, cause open); the switch off and on gave a fix 7.5 to 9.4 s after each of five requests. Earlier, from the in-tree drivers on 2026-11-09 (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (opt-in) (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; on the published branch (derek/omamobile 26867fc4e) the palmtop hung awake twice on 2026-11-16 at a power-up of the modem's link, once between the sleeps of a series and once in everyday use with Wi-Fi connected, with no oops and no UFS line, cause open ([record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | works (opt-in) (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on; opt-in, not on by default: `omamobile-device-tegu` doesn't install the file that turns auto-sleep on for a phone (`/usr/share/omamobile/auto-sleep-default`, [#737](https://github.com/derekross/omarchy-mobile/pull/737)) yet; the power key lights the lock screen on the first press, and the RTC wakes it ([kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10); the three ways a wake failed are fixed on the published branch (kernel-2026.11.15 has the first two; kernel #247 comes with the next release): dead storage after a wake (the UFS pads came back as plain inputs; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), merged 2026-11-12, re-applies the pin state at resume), a silent no-wake with C2 entered through s2idle's own path ([#591](https://github.com/derekross/omarchy-mobile/pull/591)'s sleep hook), and a core locked up in the noirq resume of an HSI0 USI ([kernel #247](https://github.com/derekross/linux-omarchy-mobile/pull/247), merged 2026-11-15, keeps those clocks on: 300 of 300 on the published tip with it, 2026-11-13); on the published branch as it is (derek/omamobile 26867fc4e, with kernel #224 and #247, and #232 and #258 for the modem) 300 of 300 sleeps with a 60 s alarm woke with the modem off, 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop (the night of 2026-11-17, [plan](../device/tegu/SLEEP-PLAN.md) S1), and 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, with the modem ONLINE and mobile data back after every one (2026-11-16, [record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); a new sleep test still runs attended first, and with the modem up the modem's sleep inhibitor stays, the owner's palmtop under [#809](https://github.com/derekross/omarchy-mobile/issues/809) excepted (AGENTS.md); that day the palmtop also hung twice while awake at a power-up of the modem's link, which is in the Modem cell; the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [plan](../device/tegu/SLEEP-PLAN.md) S1, [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | | Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | works (gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, merged, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (panthor on the Mali-G715 with the ACPM GPU clock and a thermal zone, merged, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | partial (BCM4398 on PCIe, merged through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); no P2P, and reloading after a firmware crash is untested, [NOTES](../device/husky/NOTES.md#2026-10-31-wi-fi)) | works (BCM4398D0 on the APM UART, merged, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); pairing and A2DP verified on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | partial (the gauge, temperature, MFD and pack EEPROM, merged, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163), [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175), the bus on by default with [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205), read at boot on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone); no battery model in the published tree, so the percentage is the gauge's default (Google's ATL model only through a bring-up overlay); [BATTERY-NOTES](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: sink at the Type-C 3 A level (input limit 0xc2 0x13 to 0x77); +1.5 A measured from a 30 W charger without the driver (1.485 A is the device-tree cap); no host mode, [#282](https://github.com/derekross/omarchy-mobile/pull/282); [notes](../device/husky/BATTERY-NOTES.md), [#1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)) | works (CS40L26, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); felt on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | works (LM3644, 50 mA cap, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); seen on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | no (first steps as drafts: [kernel #210](https://github.com/derekross/linux-omarchy-mobile/pull/210), [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211)) | testing (loads and runs through the GSA and Trusty on a test kernel; plan and results [AOC-PLAN](../device/husky/AOC-PLAN.md)) | testing (stereo speakers and one microphone through UCM2 and PipeWire on a test kernel, [kernel #203](https://github.com/derekross/linux-omarchy-mobile/pull/203), [#204](https://github.com/derekross/linux-omarchy-mobile/pull/204), package [#453](https://github.com/derekross/omarchy-mobile/pull/453)) | no | no | testing (a test kernel reads tags; [kernel #208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)) | no | no | no | | Pixel 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B boots Omarchy's root image from `userdata` with the session and the lock, and a second boot comes up clean, [BRINGUP-M2](../device/akita/BRINGUP-M2.md) gate (e), 2026-11-10; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md)) | testing (UFS at HS-G4 behind the storage guard, Omarchy's image on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206) and the device package and storage plan, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | testing (the GT9895 touchscreen: the PIN pad unlocks by touch, and the shell and on-screen keyboard work by hand, [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (g), 2026-11-11; merged, [kernel #241](https://github.com/derekross/linux-omarchy-mobile/pull/241)) | testing (Power wakes and locks, volume keys; [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (f); merged, [kernel #238](https://github.com/derekross/linux-omarchy-mobile/pull/238)) | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | From 808aa51ee9e213f188f7c3067e63a23e155a5410 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Thu, 19 Nov 2026 20:22:46 -0649 Subject: [PATCH 2/3] device/tegu MODEM-PLAN, DEVICES: the 9a's location record on #921's final head, and the GeoClue stall's cause Eight more boots on the published kernel with #921's final head had a GNSS fix in seven; the eighth was GeoClue's start stall again, and this time its backtrace was taken. It is a lock-order deadlock between GLib's VFS and proxy resolver setups, reproduced without a boot (7 of 80 cold starts) and gone with GLib's built-in resolver (#942). The record no longer calls the cause open, and says which overlay isn't in the tree. --- device/tegu/MODEM-PLAN.md | 46 +++++++++++++++++++++++++++------------ docs/DEVICES.md | 2 +- 2 files changed, 33 insertions(+), 15 deletions(-) diff --git a/device/tegu/MODEM-PLAN.md b/device/tegu/MODEM-PLAN.md index fa3b3227a..2abec3cfe 100644 --- a/device/tegu/MODEM-PLAN.md +++ b/device/tegu/MODEM-PLAN.md @@ -2012,7 +2012,8 @@ sleep within half a minute. All runs on the palmtop, on the charger, with Location on, Wi-Fi up and the palmtop indoors at one spot. The kernel was the published `omamobile` at 26867fc4e (`7.3.0-rc6-omamobile-push1-g26867fc4e826`, defconfig plus main's -`omamobile.config`, with the overlays `public-ramoops` and `modem-cpif`), so +`omamobile.config`, with the overlays `modem-cpif` and `public-ramoops`, a +bring-up overlay that only adds the pstore region and isn't in the tree), so the CP and GNSS ran from the in-tree drivers, and `omamobile-tegu-modem-boot` started the modem. Packages: omamobile-modem 0.1.27-1, omamobile-device-tegu 0.2.21-1, and omamobile-gnss 0.2.11-1 from #864 with #921's start script, @@ -2051,19 +2052,36 @@ followed each time by `where-am-i`: - GeoClue's IP position came 1.1 s after each request, and a GNSS fix came 7.5 to 9.4 s after it, five of five. -**Open: GeoClue's start stall.** In 3 of the first 8 boots with both -changes, and once before, GeoClue's own start stopped after "Failed to -connect to avahi service" and never took its bus name. where-am-i's call to -start it timed out after 25 s ("Error calling StartServiceByName"), and -systemd logged GeoClue as started only at the shutdown, 44 s later. Each -time the request came about 16 s into the boot, while the session and its -GeoClue agent were starting. - -It never happened with GeoClue's debug log on (12 boots), nor in the 8 -boots after that without it, nor in the 16 on the daily kernel. So it is a race in GeoClue's start that the -log's timing hides. It is not understood yet, and it is GeoClue's own start, -not the GNSS path. Not checked: whether a later request in such a boot gets -through once systemd's start timeout (90 s) ends the stalled GeoClue. +**On #921's final head (2026-11-20).** The same kernel, packages and method, +with #921's head (f326aef6) in place of its first two changes: 8 boots with +a request at 18 to 20 s, a GNSS fix in 7 (79 to 117 s after the boot), and +one GeoClue start stall. The seven reboots a later boot looked back at each +stopped their session with the runner's "stopping", and no boot found a +marker. Five more rounds of Location off and on each gave a GNSS fix 12.2 +to 12.3 s after the request. On the daily kernel, 8 boots the same way each +had a GNSS fix, 69 to 93 s after the boot. + +**GeoClue's start stall.** In 5 of these 44 boots on the published kernel +(one before #921's second change, three in the first 8 boots with it, one +on 11-20), GeoClue's own start stopped after "Failed to connect to avahi +service" and never took its bus name. where-am-i's call to start it timed +out after 25 s ("Error calling StartServiceByName"), and systemd logged +GeoClue as started only at the shutdown. Each time the request came 16 to +20 s into the boot, while the session and its GeoClue agent were starting. +It is not the GNSS path, and it is not the 9a's alone. + +It is a deadlock in GLib's one-time setups. The backtraces of two stalled +starts show the main thread in `g_vfs_get_default()`, holding the VFS's +init and waiting for GIO's default-modules lock, and a pool thread in +`g_proxy_resolver_get_default()`, holding that lock while libproxy's +resolver is created, whose init opens a GFile and waits for the VFS's init +(geoclue 2.8.2, glib2 2.90.1, libproxy 0.5.12). It needs no boot: with the +file cache dropped before each start, 7 of 80 starts of GeoClue stalled on +the daily kernel. With `GIO_USE_PROXY_RESOLVER=dummy` for `geoclue.service` +none of 80 did, and none of 200 with a warm cache (2 of 180 without it): +omarchy-mobile#942. Not run: boots with that drop-in from a package. Not +checked: whether a later request in a stalled boot gets through once +systemd's start timeout (90 s) ends the stalled GeoClue. ### M2: the link only (modem link driver, `allow_hw=1`; risk: medium) diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 52161754d..ba323446d 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -26,7 +26,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); native test image on one phone; slot B marked successful and `vbmeta_b` verification turned off, both without project approval; see notes) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); guarded `userdata` root on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); connected output on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); Panfrost render node present) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); touchscreen detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); gpio-keys detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); USB network and SSH on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); link up; traffic not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); controller powered; pairing not checked) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charge and temperature reported) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | | Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - | | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | -| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (Omarchy's Location switch serves GNSS fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up, and the modem's start at boot is opt-in, as the Modem cell says: `omamobile-device-tegu`'s boot unit ([#372](https://github.com/derekross/omarchy-mobile/pull/372)) starts gnssd with it. On the published branch (`omamobile` at 26867fc4e) with [#864](https://github.com/derekross/omarchy-mobile/pull/864) and [#921](https://github.com/derekross/omarchy-mobile/pull/921) (2026-11-19, [record](../device/tegu/MODEM-PLAN.md#location-on-the-published-branch-2026-11-19)): a request made 15 to 16 s into a boot, before gnssd was up, had a GNSS fix (3 m) in 25 of 28 boots, 75 to 119 s after the boot, each reboot made during a session; in the other 3 GeoClue's own start stalled (not seen in the last 20 boots, cause open); the switch off and on gave a fix 7.5 to 9.4 s after each of five requests. Earlier, from the in-tree drivers on 2026-11-09 (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (opt-in) (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; on the published branch (derek/omamobile 26867fc4e) the palmtop hung awake twice on 2026-11-16 at a power-up of the modem's link, once between the sleeps of a series and once in everyday use with Wi-Fi connected, with no oops and no UFS line, cause open ([record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | works (opt-in) (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on; opt-in, not on by default: `omamobile-device-tegu` doesn't install the file that turns auto-sleep on for a phone (`/usr/share/omamobile/auto-sleep-default`, [#737](https://github.com/derekross/omarchy-mobile/pull/737)) yet; the power key lights the lock screen on the first press, and the RTC wakes it ([kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10); the three ways a wake failed are fixed on the published branch (kernel-2026.11.15 has the first two; kernel #247 comes with the next release): dead storage after a wake (the UFS pads came back as plain inputs; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), merged 2026-11-12, re-applies the pin state at resume), a silent no-wake with C2 entered through s2idle's own path ([#591](https://github.com/derekross/omarchy-mobile/pull/591)'s sleep hook), and a core locked up in the noirq resume of an HSI0 USI ([kernel #247](https://github.com/derekross/linux-omarchy-mobile/pull/247), merged 2026-11-15, keeps those clocks on: 300 of 300 on the published tip with it, 2026-11-13); on the published branch as it is (derek/omamobile 26867fc4e, with kernel #224 and #247, and #232 and #258 for the modem) 300 of 300 sleeps with a 60 s alarm woke with the modem off, 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop (the night of 2026-11-17, [plan](../device/tegu/SLEEP-PLAN.md) S1), and 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, with the modem ONLINE and mobile data back after every one (2026-11-16, [record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); a new sleep test still runs attended first, and with the modem up the modem's sleep inhibitor stays, the owner's palmtop under [#809](https://github.com/derekross/omarchy-mobile/issues/809) excepted (AGENTS.md); that day the palmtop also hung twice while awake at a power-up of the modem's link, which is in the Modem cell; the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [plan](../device/tegu/SLEEP-PLAN.md) S1, [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | +| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (Omarchy's Location switch serves GNSS fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up, and the modem's start at boot is opt-in, as the Modem cell says: `omamobile-device-tegu`'s boot unit ([#372](https://github.com/derekross/omarchy-mobile/pull/372)) starts gnssd with it. On the published branch (`omamobile` at 26867fc4e) with [#864](https://github.com/derekross/omarchy-mobile/pull/864) and [#921](https://github.com/derekross/omarchy-mobile/pull/921) (2026-11-19, [record](../device/tegu/MODEM-PLAN.md#location-on-the-published-branch-2026-11-19)): a request made 15 to 16 s into a boot, before gnssd was up, had a GNSS fix (3 m) in 25 of 28 boots, 75 to 119 s after the boot, each reboot made during a session; in the other 3 GeoClue's own start stalled, a deadlock in GLib's setup that [#942](https://github.com/derekross/omarchy-mobile/pull/942) removes; on #921's final head on 2026-11-20, 7 of 8 more boots (one more such stall); the switch off and on gave a fix 7.5 to 9.4 s after each of five requests. Earlier, from the in-tree drivers on 2026-11-09 (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 (omamobile-gnss 0.2.5's start, by hand, the modem link left to cycle) had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (opt-in) (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; on the published branch (derek/omamobile 26867fc4e) the palmtop hung awake twice on 2026-11-16 at a power-up of the modem's link, once between the sleeps of a series and once in everyday use with Wi-Fi connected, with no oops and no UFS line, cause open ([record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | works (opt-in) (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on; opt-in, not on by default: `omamobile-device-tegu` doesn't install the file that turns auto-sleep on for a phone (`/usr/share/omamobile/auto-sleep-default`, [#737](https://github.com/derekross/omarchy-mobile/pull/737)) yet; the power key lights the lock screen on the first press, and the RTC wakes it ([kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10); the three ways a wake failed are fixed on the published branch (kernel-2026.11.15 has the first two; kernel #247 comes with the next release): dead storage after a wake (the UFS pads came back as plain inputs; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), merged 2026-11-12, re-applies the pin state at resume), a silent no-wake with C2 entered through s2idle's own path ([#591](https://github.com/derekross/omarchy-mobile/pull/591)'s sleep hook), and a core locked up in the noirq resume of an HSI0 USI ([kernel #247](https://github.com/derekross/linux-omarchy-mobile/pull/247), merged 2026-11-15, keeps those clocks on: 300 of 300 on the published tip with it, 2026-11-13); on the published branch as it is (derek/omamobile 26867fc4e, with kernel #224 and #247, and #232 and #258 for the modem) 300 of 300 sleeps with a 60 s alarm woke with the modem off, 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop (the night of 2026-11-17, [plan](../device/tegu/SLEEP-PLAN.md) S1), and 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, with the modem ONLINE and mobile data back after every one (2026-11-16, [record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); a new sleep test still runs attended first, and with the modem up the modem's sleep inhibitor stays, the owner's palmtop under [#809](https://github.com/derekross/omarchy-mobile/issues/809) excepted (AGENTS.md); that day the palmtop also hung twice while awake at a power-up of the modem's link, which is in the Modem cell; the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [plan](../device/tegu/SLEEP-PLAN.md) S1, [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | | Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | works (gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, merged, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (panthor on the Mali-G715 with the ACPM GPU clock and a thermal zone, merged, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | partial (BCM4398 on PCIe, merged through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); no P2P, and reloading after a firmware crash is untested, [NOTES](../device/husky/NOTES.md#2026-10-31-wi-fi)) | works (BCM4398D0 on the APM UART, merged, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); pairing and A2DP verified on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | partial (the gauge, temperature, MFD and pack EEPROM, merged, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163), [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175), the bus on by default with [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205), read at boot on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone); no battery model in the published tree, so the percentage is the gauge's default (Google's ATL model only through a bring-up overlay); [BATTERY-NOTES](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: sink at the Type-C 3 A level (input limit 0xc2 0x13 to 0x77); +1.5 A measured from a 30 W charger without the driver (1.485 A is the device-tree cap); no host mode, [#282](https://github.com/derekross/omarchy-mobile/pull/282); [notes](../device/husky/BATTERY-NOTES.md), [#1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)) | works (CS40L26, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); felt on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | works (LM3644, 50 mA cap, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); seen on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | no (first steps as drafts: [kernel #210](https://github.com/derekross/linux-omarchy-mobile/pull/210), [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211)) | testing (loads and runs through the GSA and Trusty on a test kernel; plan and results [AOC-PLAN](../device/husky/AOC-PLAN.md)) | testing (stereo speakers and one microphone through UCM2 and PipeWire on a test kernel, [kernel #203](https://github.com/derekross/linux-omarchy-mobile/pull/203), [#204](https://github.com/derekross/linux-omarchy-mobile/pull/204), package [#453](https://github.com/derekross/omarchy-mobile/pull/453)) | no | no | testing (a test kernel reads tags; [kernel #208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)) | no | no | no | | Pixel 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B boots Omarchy's root image from `userdata` with the session and the lock, and a second boot comes up clean, [BRINGUP-M2](../device/akita/BRINGUP-M2.md) gate (e), 2026-11-10; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md)) | testing (UFS at HS-G4 behind the storage guard, Omarchy's image on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206) and the device package and storage plan, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | testing (the GT9895 touchscreen: the PIN pad unlocks by touch, and the shell and on-screen keyboard work by hand, [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (g), 2026-11-11; merged, [kernel #241](https://github.com/derekross/linux-omarchy-mobile/pull/241)) | testing (Power wakes and locks, volume keys; [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (f); merged, [kernel #238](https://github.com/derekross/linux-omarchy-mobile/pull/238)) | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | From c6886b415d523ed4b042f8348b8f18ce23126efb Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Thu, 19 Nov 2026 20:51:47 -0649 Subject: [PATCH 3/3] device/tegu MODEM-PLAN: the GeoClue stall is GLib issue 4078 The record names the upstream issue, so the workaround in #942 has a known end. --- device/tegu/MODEM-PLAN.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/device/tegu/MODEM-PLAN.md b/device/tegu/MODEM-PLAN.md index 2abec3cfe..16d10289f 100644 --- a/device/tegu/MODEM-PLAN.md +++ b/device/tegu/MODEM-PLAN.md @@ -2070,7 +2070,8 @@ GeoClue as started only at the shutdown. Each time the request came 16 to 20 s into the boot, while the session and its GeoClue agent were starting. It is not the GNSS path, and it is not the 9a's alone. -It is a deadlock in GLib's one-time setups. The backtraces of two stalled +It is a deadlock in GLib's one-time setups, known upstream as GLib issue +4078 (). The backtraces of two stalled starts show the main thread in `g_vfs_get_default()`, holding the VFS's init and waiting for GIO's default-modules lock, and a pool thread in `g_proxy_resolver_get_default()`, holding that lock while libproxy's