From e39c769847d733c317c8908e3a60a3fef75c591f Mon Sep 17 00:00:00 2001 From: Lef Date: Sat, 7 Nov 2026 03:11:38 +0200 Subject: [PATCH 1/3] docs/husky: ROADMAP, DEVICES row and step 9 brought up to 2026-11-07 device/husky/ROADMAP.md was frozen at 2026-10-31, when GPU, Bluetooth, haptics, the AoC and the speakers were all 'no', and the husky row in DEVICES.md still had touch and buttons as 'testing' with their PRs in review. Touch and buttons are merged and verified on both phones, so they say works with their notes entries; everything that runs only on a test tree says testing with the PR it waits on; the rows with nothing started say what was read from the stock device tree and that it was not tested. Suspend says it has not been run, with what is known about idle power. NFC moves to testing: on a test kernel the ST54L answers and reads tags through nxp-nci (kernel #208 and #209, drafts). GNSS stays no, with its first steps in review (kernel #210 and #211, drafts). Written from the PR states (checked with gh today), the notes and what ran on a phone (kernel 7.3.0-rc6-omamobile-push1-g50ef3c279021 for the test-tree rows, a later test tree for NFC). Nothing was booted for this change. Signed-off-by: Lef --- device/husky/ROADMAP.md | 94 +++++++++++++++++++++++------------------ docs/DEVICES.md | 2 +- docs/ROADMAP.md | 2 +- 3 files changed, 55 insertions(+), 43 deletions(-) diff --git a/device/husky/ROADMAP.md b/device/husky/ROADMAP.md index fcd319fda..fff79e4b8 100644 --- a/device/husky/ROADMAP.md +++ b/device/husky/ROADMAP.md @@ -1,22 +1,31 @@ # Pixel 8 Pro (husky) roadmap: from "boots" to an everyday phone -Written 2026-10-31 by Lef ([@Somnius](https://github.com/Somnius)). The original roadmap for this port stops at "boots" ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1)), and that bar is met on the units tested so far: Omarchy runs from slot B and unlocks by touch. This page is the rest of it, one row per subsystem, in the order of the columns in [docs/DEVICES.md](../../docs/DEVICES.md). For each it says what works, who is on it, the closest finished work to copy from (the Pixel 9a, `tegu`, has a newer Tensor SoC (zumapro) than husky's zuma [I: neighbouring generations, so device-tree work should carry over in part], and the Pixel 7 Pro, `cheetah`, has a plan for almost everything), what is in the way, and a first step that is read-only (no flashing). Credits are at the end. +Written 2026-10-31 by Lef ([@Somnius](https://github.com/Somnius)). Last updated: 2026-11-07. The original roadmap for this port stops at "boots" ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1)), and that bar is met on the units tested so far: Omarchy runs from slot B and unlocks by touch. This page is the rest of it, one row per subsystem, in the order of the columns in [docs/DEVICES.md](../../docs/DEVICES.md). For each it says what works, who is on it, the closest finished work to copy from (the Pixel 9a, `tegu`, has a newer Tensor SoC (zumapro) than husky's zuma [I: neighbouring generations, so device-tree work should carry over in part], and the Pixel 7 Pro, `cheetah`, has a plan for almost everything), what is in the way, and a first step that is read-only (no flashing). Credits are at the end. -Facts are marked [V] (checked, with the source) or [I] (an inference, with what would settle it). Pull request states are as of 2026-10-31. Nothing here asks anyone to skip the safety rules: read-only first, one change per boot, a read-only backup of the modem and calibration partitions before radio, PMIC, AoC or Trusty work ([AGENTS.md](../../AGENTS.md) §1, [CONTRIBUTING.md](../../CONTRIBUTING.md) §3). Kernel PR numbers are in [derekross/linux-omarchy-mobile](https://github.com/derekross/linux-omarchy-mobile), written `kernel #N`. +Facts are marked [V] (checked, with the source) or [I] (an inference, with what would settle it). Pull request states are as of 2026-11-07. "Merged" means on `main` of this repository or on `omamobile` of the kernel; everything else ran only on a test tree, and the table says which pull request it waits on. Where a boot of Lef's test tree is the evidence, the kernel release was `7.3.0-rc6-omamobile-push1-g50ef3c279021` for most rows and a later test tree, `7.3.0-rc6-omamobile-push1-ge98a7a38a3ef`, for NFC (the test branches and tags are on his fork and listed in [#450](https://github.com/derekross/omarchy-mobile/pull/450)). Nothing here asks anyone to skip the safety rules: read-only first, one change per boot, a read-only backup of the modem and calibration partitions before radio, PMIC, AoC or Trusty work ([AGENTS.md](../../AGENTS.md) §1, [CONTRIBUTING.md](../../CONTRIBUTING.md) §3). Kernel PR numbers are in [derekross/linux-omarchy-mobile](https://github.com/derekross/linux-omarchy-mobile), written `kernel #N`. ## What works today -Two units are in play: Brett's (Samsung 128 GB UFS 3.1) and Lef's (Kioxia 256 GB UFS 4.0; see [NOTES.md](NOTES.md)). Results below say which unit unless both did them. Kernel: `omamobile` plus Brett's `husky-test-20261031-c6` tag. +Two units are in play: Brett's (Samsung 128 GB UFS 3.1) and Lef's (Kioxia 256 GB UFS 4.0; see [NOTES.md](NOTES.md)). Results below say which unit unless both did them. Kernel: `omamobile` plus Brett's `husky-test-20261031-c6` tag for the 2026-10-31 results; since then Lef's phone has run test trees made of Brett's open PRs plus the ones listed below. -- **Boot** from slot B, with stock or GrapheneOS on slot A as the way back. Slot B is deliberately never marked successful, so ABL gives it three boots ([BRINGUP-M1](BRINGUP-M1.md), [UFS-PLAN](UFS-PLAN.md)). +**On `main` (merged or landed):** boot, UFS, USB networking, the watchdog, the framebuffer display with its panel size (kernel #154), touch (kernel #153), buttons (kernel #148), the hsi2c_9 and hsi2c_11 buses with the gauge, the PMIC and the pack EEPROM (kernel #163, #175; the buses still need a bring-up overlay until kernel [#205](https://github.com/derekross/linux-omarchy-mobile/pull/205)), the `splash` command line ([#278](https://github.com/derekross/omarchy-mobile/pull/278)) and the device package's display start, USB replug rescue and retain-splash ([#228](https://github.com/derekross/omarchy-mobile/pull/228), [#250](https://github.com/derekross/omarchy-mobile/pull/250), [#285](https://github.com/derekross/omarchy-mobile/pull/285)). + +**On test trees only (open PRs):** the DRM display at 120 Hz (kernel #160), the GPU (kernel #157), CPU DVFS and thermal zones (kernel #158), Wi-Fi (kernel #156), Bluetooth (kernel #199), haptics and torch (kernel #200), the AoC with speakers and microphone (kernel #203, #204, package #453, plan #450), the Type-C sink and the charger under a dead-man tool ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). + +- **Boot** from slot B, with stock or GrapheneOS on slot A as the way back. Slot B is deliberately never marked successful, so ABL gives it three boots ([BRINGUP-M1](BRINGUP-M1.md), [UFS-PLAN](UFS-PLAN.md)). On 2026-11-01 Lef's phone ran out of retries and GrapheneOS wiped `userdata` on its next boot ([BATTERY-NOTES](BATTERY-NOTES.md) §9); he now sets the successful bit with a local unit that is not in any package. - **UFS** at HS-G4, two lanes, behind the read-only guard, on both device vendors ([UFS-PLAN](UFS-PLAN.md) U2 passed on the Kioxia unit). - **USB gadget** networking and SSH, and the watchdog driver (no 80 s reset). -- **Display** as a simple framebuffer: console, lock screen and the shell at 1344x2992. Its physical size is reported wrong (355x791 mm instead of about 70x155) until [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154), which adds the panel size. With the wrong size the on-screen keyboard is far too short (105 px, 11% of the screen); with 70x155 mm it is 196 px (21%) [V: measured on the Kioxia unit]. -- **Touch** (STMicroelectronics SALIXP over SPI) and **buttons** (`gpio-keys`) on the test tag: raw events decoded in the right corners, swipe, PIN pad, app launching, wake by tap and by Power (both units). In review as [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153) and [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148). -- **Foundations those PRs added:** the ALIVE pin controller, the CMU_TOP and CMU_HSI0 clocks, the ACPM mailbox and protocol driver, the main PMIC (S2MPG14), USI2 and its SPI. +- **Display** as a simple framebuffer on `main`: console, lock screen and the shell at 1344x2992, with the panel's physical size (70x155 mm) since [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154) (merged 2026-11-01), so the on-screen keyboard has its proper height (196 px, 21% of the screen, instead of 105 px) [V: measured on the Kioxia unit]. On a test tree with [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (open): gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, started by the device package ([#228](https://github.com/derekross/omarchy-mobile/pull/228), merged); Lef's phone has run it since 2026-11-01. +- **Touch** (STMicroelectronics SALIXP over SPI) and **buttons** (`gpio-keys`): raw events decoded in the right corners, swipe, PIN pad, app launching, wake by tap and by Power (both units). Merged 2026-10-31 as [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153) and [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148). +- **Foundations those PRs added:** the ALIVE pin controller, the CMU_TOP and CMU_HSI0 clocks, the ACPM mailbox and protocol driver, the main PMIC (S2MPG14), USI2 and its SPI; then CMU_PERIC1, USI9 and USI11 with the battery buses ([kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163), [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175), merged 2026-11-01). +- **Battery and charging** on `main` plus an overlay: the gauge with Google's ATL model, the PMIC, the pack EEPROM; the charger driver by hand under a dead-man tool; the Type-C controller driver as a sink (3 A, replug survives) in the same guarded runs ([BATTERY-NOTES](BATTERY-NOTES.md), [issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Host mode with VBUS out waits for the runbook review ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). +- **Wi-Fi, GPU, CPU DVFS and thermal zones** on test trees with Brett's open kernel PRs [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156), [#157](https://github.com/derekross/linux-omarchy-mobile/pull/157) and [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158): on Lef's phone 5 GHz Wi-Fi, panthor on the Mali-G715 and cpufreq with the four ACPM TMU zones ([NOTES](NOTES.md) for Wi-Fi; the GPU and DVFS results are in those PRs, not re-measured here). +- **Bluetooth** (BCM4398D0 on the APM UART): pairing and A2DP headphones, on [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199) (open); firmware from the owner's own vendor image. +- **Haptics and torch** (CS40L26, LM3644): felt and seen, on [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200) (open). +- **Sound**: the AoC firmware loads and runs (GSA, Trusty, System MMU v9, mailboxes, 94 services), both CS35L41 amplifiers probe with the speaker-protection firmware from the owner's vendor image, and the AoC sound card plays stereo through the speakers and records from one microphone, through UCM2 and PipeWire. Test tree only: [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), plan and results [#450](https://github.com/derekross/omarchy-mobile/pull/450) (all open). The AoC core port and the System MMU v9 file are not PRs yet. -Touch and Buttons are "testing" in `docs/DEVICES.md` since #208, on test kernels with kernel #148 and #153. +Touch and Buttons are in `docs/DEVICES.md` with their merged PRs; the rest of this list is "testing" or "WIP" there, with the PR it waits on. ## The table @@ -24,39 +33,40 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists | Subsystem | husky now | Who | Closest template | Needs / in the way | First safe step | | --- | --- | --- | --- | --- | --- | -| Display (DRM driver) | simplefb only | Brett (next, per #1) | 9a: [#88](https://github.com/derekross/linux-omarchy-mobile/pull/88) 120 Hz and per-panel DSIM timers (merged), [#89](https://github.com/derekross/linux-omarchy-mobile/pull/89) panel `google,tg4c` (merged), [#90](https://github.com/derekross/linux-omarchy-mobile/pull/90) DECON0 and DSIM0 device tree (open); cheetah [DISPLAY-PLAN](../cheetah/DISPLAY-PLAN.md) | Google's stock husky overlay has the panel as `samsung,s6e3hc3` on DSIM0 (reset gpa6; vci LDO14M, vddi BUCKA, vddd LDO22M) and a `1344x2992` DSIM mode [V: `dtbo.img` of the GrapheneOS husky 2026102101 package, board "ZUMA HUSKY MP"; choosing that overlay by board id is [I]]. Still needed: zuma's DSIM and DECON windows and clocks, and a `s6e3hc3` panel driver (the 9a's is TG4C) | Read the DSIM/DECON nodes in the stock device tree; write `DISPLAY-PLAN.md`. No flashing | -| GPU | no | Brett (next, per #1) | 9a: [#84](https://github.com/derekross/linux-omarchy-mobile/pull/84) `clk-acpm` with a paired GPU clock (merged), [#85](https://github.com/derekross/linux-omarchy-mobile/pull/85) panthor on the Mali-G715 (open), [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) CPU DVFS, thermal zones, GPU top levels (open); cheetah [GPU-PLAN](../cheetah/GPU-PLAN.md) | CMU_G3D clocks for zuma (the clock driver in #153 has TOP and HSI0 only; `clk-zuma.c` exists, so this extends it); a **zuma variant of `clk-acpm`**: #153's ACPM match data names `zuma-acpm-clk`, but no driver registers it, and the phone's module aliases list gs101, gs201 and zumapro only [V]; an OPP table and a GPU thermal zone (enable the G3D clocks only after thermal zones and DVFS exist, as 9a #87 does); whether husky's GPU is the same Mali generation as the 9a's [I: check Google's tree] | Read Google's G3D node and clock tables; write `GPU-PLAN.md`. Today there is no render node (`tools/phone-smoke`: "GPU: no render node" [V]), so the shell is drawn in software by Mesa [I: not profiled; `phone-smoke` only shows the missing render node] | -| Touch | testing (c6) | [Brett](https://github.com/greenbrettmichael) | done | [#153](https://github.com/derekross/linux-omarchy-mobile/pull/153) in review; the ACPM probe order fix (Brett); W4HO's [#150](https://github.com/derekross/linux-omarchy-mobile/pull/150) fixes the SPI FIFO flush for every port (not needed for touch) | none: re-test after each kernel | -| Buttons | testing (c6) | Brett | done | [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148) in review | none | +| Display (DRM driver) | simplefb with the panel size on `main` (kernel #154, merged); testing at 120 Hz on [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (open) | Brett | 9a: [#88](https://github.com/derekross/linux-omarchy-mobile/pull/88) 120 Hz and per-panel DSIM timers (merged), [#89](https://github.com/derekross/linux-omarchy-mobile/pull/89) panel `google,tg4c` (merged), [#90](https://github.com/derekross/linux-omarchy-mobile/pull/90) DECON0 and DSIM0 device tree; cheetah [DISPLAY-PLAN](../cheetah/DISPLAY-PLAN.md) | Kernel #160 has gs-decon, DSIM0 and an HK3 panel driver (the stock overlay names the panel `samsung,s6e3hc3` on DSIM0 [V: `dtbo.img` of the GrapheneOS husky 2026102101 package]; the bootloader passes `exynos_drm.panel_name=google-hk3...`). The device package's display start ([#228](https://github.com/derekross/omarchy-mobile/pull/228), merged) loads it hang-safe before the session, allows the panel's DSI commands only for that panel name, and restores brightness; on a kernel without DECON0 it is skipped. Open: the DRM master handover still shows a short black blink between the splash and the session [V: Lef's phone] | Test kernel #160 with the package on a second phone and report in the PR | +| GPU | testing on [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) (open) | Brett | 9a: [#84](https://github.com/derekross/linux-omarchy-mobile/pull/84) `clk-acpm` with a paired GPU clock (merged), [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) CPU DVFS, thermal zones, GPU top levels; cheetah [GPU-PLAN](../cheetah/GPU-PLAN.md) | Kernel #157 adds zuma's CMU_G3D, the zuma `clk-acpm` variant, panthor on the Mali-G715 and a GPU thermal zone; the device package lets the ACPM clock go up to stock's 890 MHz (`omamobile-husky-clk-acpm.conf`, #228). On Lef's phone panthor binds and gives a render node, GL and Vulkan enumerate [V: test tree since 2026-11-01]; panthor logs `no regulator (mali)` for its OPPs, not cause-checked. Video is still decoded on the CPU: no codec driver (see Cameras/video below) | Re-test #157 after each rebase; a GPU load with the thermal zone watched | +| Touch | works (kernel [#153](https://github.com/derekross/linux-omarchy-mobile/pull/153), merged 2026-10-31) | [Brett](https://github.com/greenbrettmichael) | done | W4HO's [#150](https://github.com/derekross/linux-omarchy-mobile/pull/150) fixes the SPI FIFO flush for every port (merged). Open: whether touch survives a long idle with the screen off (one 12 h idle on 2026-11-04 left only Power working on Lef's phone, not reproduced since; not cause-checked) | Leave the phone idle overnight, then one tap | +| Buttons | works (kernel [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148), merged 2026-10-31) | Brett | done | A held volume key stutters the session on Lef's phone until the key repeat is slowed (Hyprland `repeat_rate` 8, `repeat_delay` 350, local change, not in a package) | Decide where a phone key-repeat default belongs | | USB net | testing | Brett (per his comments on #1) | done | USB host and Type-C are in Charging | none | -| Wi-Fi | testing | [Brett](https://github.com/greenbrettmichael) | done | [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (draft): zuma's PCIe PHY and the BCM4398 (NCI backplane) in brcmfmac, stacked on #153, #143 (BCM4389) and #56 (API9), which have to land first; firmware from the owner's image with [#214](https://github.com/derekross/omarchy-mobile/pull/214). Open: P2P, recovery after a firmware crash, joining 5 GHz ([NOTES](NOTES.md)) | Test #156 on a second phone: `tools/extract-vendor-firmware -d husky -s `, then check the scan and a join | -| Bluetooth | no | unassigned | 9a [#122](https://github.com/derekross/linux-omarchy-mobile/pull/122) (open); cheetah [BLUETOOTH-PLAN](../cheetah/BLUETOOTH-PLAN.md) | The controller is probably the combo chip that does Wi-Fi [I]; its UART, power and wake lines [I: not known to me] | Find the Bluetooth node in Google's tree; write `BLUETOOTH-PLAN.md` | -| Battery | testing (bus, gauge and MFD on kernel #163; the gauge's model through an overlay) | Lef | cheetah [POWER-PLAN](../cheetah/POWER-PLAN.md), [WIFI-BATTERY-PLAN](../cheetah/WIFI-BATTERY-PLAN.md); `gs201-cheetah.dts` has the same chip family. The 9a's [#119](https://github.com/derekross/linux-omarchy-mobile/pull/119) is the MAX77779 and does not apply as is | Stock overlay [V, same source as Display]: fuel gauge `maxim,max77759` @0x36, charger `max77759chrg` @0x69, Type-C `max77759tcpc` @0x25 and `max77729pmic` @0x66, all on `hsi2c_11`; also `nxp,pca9468` and the wireless charger `idt,p9412`. Zuma had no clock controller for that I2C block (CMU_PERIC, not in `clk-zuma.c`), no I2C or USI nodes, and `tools/phone-smoke` reported "no battery power supply" [V, until kernel #163] | Done on one phone, see [BATTERY-NOTES](BATTERY-NOTES.md): the PERIC1 clocks and the I2C nodes are kernel #163, the gauge works with Google's model loaded by an overlay. The pack ID is read (section 5.6: ATL). Next: the model, from the board file or the pack ID at runtime. **No hand writes to the PMIC or the gauge outside a reviewed tool** (AGENTS.md §1; the notes list the ones made, and why) | -| Charging, USB-C | testing (the MAX77759 charger driver in guarded runs; no USB-C yet) | Lef | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a: [#97](https://github.com/derekross/linux-omarchy-mobile/pull/97) is `tcpci_maxim` for the MAX77779 (merged), so check what husky's MAX77759 needs [I] | Same I2C bus as Battery; the USB data switch closes on unplug (AGENTS.md gotcha) | The charger ran under the dead-man tool at 500 and 900 mA and on a wall charger (slow net charging, plain 5 V), see [BATTERY-NOTES](BATTERY-NOTES.md). USB-C (`tcpci_maxim`) is not started; the replug rescue in the device package keeps the USB link until it is | -| Haptics, Torch | no | unassigned | 9a [#96](https://github.com/derekross/linux-omarchy-mobile/pull/96) (CS40L26 and LM3644, open); cheetah [HAPTICS-TORCH-PLAN](../cheetah/HAPTICS-TORCH-PLAN.md) | The parts on husky [I: not known to me] | Find them in Google's tree | -| GNSS | no | unassigned | cheetah [GNSS-PLAN](../cheetah/GNSS-PLAN.md); the 9a's is parked | Google's userspace in a chroot built from the owner's own factory image; the regulator rule (PMIC modules must load after about 30 s of late init) | After the display and battery rows | -| AoC, Speakers/mics, Sensors | no | unassigned | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [AUDIO-PLAN](../cheetah/AUDIO-PLAN.md); 9a WIP | The AoC starts only through Trusty; the amplifiers need the speaker-protection calibration; high risk (AGENTS.md gotchas) | Read AOC-PLAN to size it | -| Modem | no | Lef, once a SIM is found ([Brett asked](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6544100933)) | cheetah [MODEM-PLAN](../cheetah/MODEM-PLAN.md); 9a [MODEM-PLAN](../tegu/MODEM-PLAN.md) ("ONLINE with IPC, no SIM yet") | A SIM (a prepaid one is the plan; the phone's own SIM is a data-only eSIM); the baseband is `g5300i` [V: fastboot], the S5300 family like cheetah's [I]; the CP's PCIe link and the `cpif` driver; modem firmware from the owner's own factory image; the NV protections. **Lef has a private read-only backup of the modem and calibration partitions (checksummed, plus an encrypted second copy) [V: BUILD-SETUP log, not in this repository].** | Read cheetah's and the 9a's MODEM-PLAN M0 to M2 end to end. Stage 0 is read-only: partitions, and what a booted phone answers without starting the modem | -| NFC | no | unassigned | 9a [#105](https://github.com/derekross/linux-omarchy-mobile/pull/105), [#104](https://github.com/derekross/linux-omarchy-mobile/pull/104) (open) | The controller on husky [I: not known to me]; the 9a's NFC must not poll through s2idle (AGENTS.md) | After suspend | -| Cameras | no | unassigned | 9a [#103](https://github.com/derekross/linux-omarchy-mobile/pull/103) (open); cheetah [CAMERA-PLAN](../cheetah/CAMERA-PLAN.md) | The sensors, the MIPI receiver and the rest of the pipeline; large | After the rest | -| Suspend | no | unassigned | 9a [SLEEP-PLAN](../tegu/SLEEP-PLAN.md) (s2idle works, drain high); cheetah [SUSPEND-PLAN](../cheetah/SUSPEND-PLAN.md) | UFS hibern8 and system suspend ([UFS-PLAN](UFS-PLAN.md) U5 and U6); the ACPM and PMIC base from #153; the "UFS at `spm_lvl` 5", "only s2idle" and "regulators late" gotchas | UFS-PLAN U5 on the guarded initramfs boot | -| Thermal, CPU DVFS | no | unassigned | 9a [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) (open) | Zones and OPPs for zuma [I: not known to me]; needed before the GPU is enabled | Read Google's thermal and cpufreq nodes | -| USB host, Type-C | no | Lef (with Charging) | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a [#124](https://github.com/derekross/linux-omarchy-mobile/pull/124) (open) | The Type-C controller is the MAX77759 TCPC above | As Battery | -| Time, persistent storage | partly | unassigned | none yet | The clock starts wrong on first boot (omarchy-mobile #188); root is still behind the read-only guard, so everyday writes need a plan [I] | Write a short plan | -| Fingerprint | no | unassigned | cheetah [FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md); 9a [FINGERPRINT-PLAN](../tegu/FINGERPRINT-PLAN.md) | Trusty, `persist` and RPMB writes are irreversible and need the human's explicit go | Last, as a proposal | +| Wi-Fi | testing on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (draft) | [Brett](https://github.com/greenbrettmichael) | done | #156: zuma's PCIe PHY and the BCM4398 (NCI backplane) in brcmfmac, stacked on #153 (merged) and #143 (landed); firmware from the owner's image with [#214](https://github.com/derekross/omarchy-mobile/pull/214) (merged). On Lef's phone it joins 5 GHz at boot and held a 40 min run at 221 to 502 Mbit/s ([#156 comment](https://github.com/derekross/linux-omarchy-mobile/pull/156#issuecomment-6562550631)). Open: P2P, recovery after a firmware crash, the `PKTID` log lines after a failed join ([NOTES](NOTES.md), the #156 thread) | Test #156 on a second phone: `tools/extract-vendor-firmware -d husky -s `, then check the scan and a join | +| Bluetooth | testing on [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199) (open) | Lef | 9a [#122](https://github.com/derekross/linux-omarchy-mobile/pull/122); cheetah [BLUETOOTH-PLAN](../cheetah/BLUETOOTH-PLAN.md) | The BCM4398D0, the Bluetooth half of the Wi-Fi combo, on the APM's USI1 UART; BT_REG_ON, the wake lines and the REG_ON latch clock are in #199, with the CMU_APM UART clocks. Firmware is the stock `BCM.hcd` from the owner's own vendor image, never in a repository. Pairing and A2DP to headphones work on Lef's phone [V: #199]. Open: the board address from `/chosen` (an `omamobile-bt-addr` unit like cheetah's, not packaged yet), HFP, power | Review #199; then the bt-addr unit in the device package | +| Battery | testing (gauge, PMIC and pack EEPROM on kernel #163 and #175, merged; the buses and the gauge's model through overlays until kernel [#205](https://github.com/derekross/linux-omarchy-mobile/pull/205)) | Lef | cheetah [POWER-PLAN](../cheetah/POWER-PLAN.md), [WIFI-BATTERY-PLAN](../cheetah/WIFI-BATTERY-PLAN.md); `gs201-cheetah.dts` has the same chip family. The 9a's [#119](https://github.com/derekross/linux-omarchy-mobile/pull/119) is the MAX77779 and does not apply as is | Stock overlay [V, same source as Display]: fuel gauge `maxim,max77759` @0x36, charger `max77759chrg` @0x69, Type-C `max77759tcpc` @0x25 and `max77729pmic` @0x66, all on `hsi2c_11`; also `nxp,pca9468` and the wireless charger `idt,p9412` (what we found: at 0x3c on `hsi2c_9`, the pack EEPROM bus, with its enable and boost lines on the PMIC GPIO expanders; no mainline driver, read from the stock tree, not tested). The gauge-model overlays are generated from Google's published `zuma-husky-battery-data.dtsi` ([#279](https://github.com/derekross/omarchy-mobile/pull/279), merged). Open: the model in the board file (or picked by the pack ID at runtime), and the charger stopping at 92 % with the bootloader's 4.35 V float ([#272](https://github.com/derekross/omarchy-mobile/issues/272), baseline in [#452](https://github.com/derekross/omarchy-mobile/pull/452)) | Done on one phone, see [BATTERY-NOTES](BATTERY-NOTES.md). Next: kernel #205 (the bus on by default), then the model. **No hand writes to the PMIC or the gauge outside a reviewed tool** (AGENTS.md §1; the notes list the ones made, and why) | +| Charging, USB-C | testing (the MAX77759 charger and `tcpci_maxim` as a sink, both by hand in guarded runs) | Lef | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a: [#97](https://github.com/derekross/linux-omarchy-mobile/pull/97) is `tcpci_maxim` for the MAX77779 (merged) | Same I2C bus as Battery. With the Type-C driver loaded the port is a sink at 3 A, the charger follows TCPM's input limit (0x13 to 0x77), and the driver closes the USB data switch on replug itself; a 30 W PD charger with a C-to-C cable charges at the 1.485 A device-tree cap ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Not run: PD/PPS, host mode with VBUS out (the connector has no VBUS regulator; the external boost needs a `regulator-fixed` on the MAX77759's GPIO5 plus the TCPC's EXTBST_CTRL), dongles, DP alt mode | The host-mode runbook and the `b5-host` tool are in draft [#282](https://github.com/derekross/omarchy-mobile/pull/282); nothing that sources power runs before the maintainer's review of it and a USB-C meter (his rule on #272). The replug rescue in the device package ([#250](https://github.com/derekross/omarchy-mobile/pull/250), merged) keeps the USB link until the Type-C driver is on by default | +| Haptics, Torch | testing on [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200) (open) | Lef | 9a [#96](https://github.com/derekross/linux-omarchy-mobile/pull/96) (CS40L26 and LM3644); cheetah [HAPTICS-TORCH-PLAN](../cheetah/HAPTICS-TORCH-PLAN.md) | CS40L26A at 0x43 on PERIC1 USI0 (`hsi2c_0`) and the LM3644 at 0x63 on PERIC0 USI14 (`hsi2c_14`); #200 adds CMU_PERIC0 and the HSI1 pin controller for them. Lef felt the buzz and saw the LED; the torch is capped at 50 mA per LED like the 7 Pro's bring-up. Open: a gentle strength for UI taps (feedbackd), the shell's torch tile | Review #200 | +| GNSS | no (first steps in review: the bus clocks [#210](https://github.com/derekross/linux-omarchy-mobile/pull/210) and the PMIC rails [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211), both drafts; nothing runs yet) | Lef | cheetah [GNSS-PLAN](../cheetah/GNSS-PLAN.md); the 9a's is parked | What we found: a separate Broadcom BCM4775x on `spi_21` (HSI0 USI3, 26 MHz) with its own three S2MPG15 LDOs, as on the 7 Pro. The driver, the binding and the S2MPG15 regulators are already in the tree. The vendor image carries the Broadcom GNSS service, so this is the chip Android uses; the modem-GNSS channels in `cpif` are not the path. Missing: the pin controllers (in #156), the `gnss@0` node, and Google's `lhd` and `gpsd` in a chroot built from the owner's own factory image (the extract tool needs one line for husky); the regulator rule (PMIC modules after about 30 s of late init) | A bring-up overlay for the bus and the PMIC, read-only first; then the `gnss@0` node on #156's pin controllers | +| AoC, Speakers/mics | testing (AoC, both amplifiers, stereo speakers and one microphone through UCM2 and PipeWire, on a test tree: 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), plan [#450](https://github.com/derekross/omarchy-mobile/pull/450), all open) | Lef | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [AUDIO-PLAN](../cheetah/AUDIO-PLAN.md) | The AoC loads through the GSA and starts through Trusty (`trusty-ipc` before `trusty-virtio`); zuma's System MMU is v9, and the 7 Pro's v8 offsets reset the phone (#450). The amplifiers share one SPI controller, one on the native chip select and one on a GPIO one (#204). The speaker-protection firmware and `aoc.bin` come from the owner's own vendor image. Levels are capped (digital 737, analog 10, no `speaker_protection`), the microphone is one of three ids and which hole it is is not settled, the earpiece and headset paths are not done. Not PRs yet: the AoC core port to zuma and the System MMU v9 file (shape asked on #1) | Review #450 and #453; the AoC core and System MMU v9 patches once the maintainer picks the file shape | +| Sensors | no (read from the stock device tree, not tested) | unassigned | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [USF-PROTOCOL](../cheetah/USF-PROTOCOL.md) | What we found: the running AoC publishes the USF services (`com.google.usf`, its non-wake-up twin and the doorbell) and CHRE; the stock AoC node wants two sensor rails (S2MPG15 `L7S_SENSORS`, `L5S_PROX`) that our tree does not give it. Which physical sensors husky has is not known (the registry scripts are in the vendor partition). Needs the AoC char devices, Google's registry scripts loaded at boot, and the cheetah sensor proxy | After the AoC PRs: one read-only `RegistryGet` through the USF char device with the phone in hand (an AoC assert needs a reboot) | +| Modem | no | Lef, once a SIM is found ([Brett asked](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6544100933)) | cheetah [MODEM-PLAN](../cheetah/MODEM-PLAN.md); 9a [MODEM-PLAN](../tegu/MODEM-PLAN.md) ("ONLINE with IPC, no SIM yet") | A SIM (a prepaid one is the plan; the phone's own SIM is a data-only eSIM); the baseband is `g5300i` [V: fastboot], the S5300 family like cheetah's [I]; the CP's PCIe link and the `cpif` driver; modem firmware from the owner's own factory image; the NV protections. **Lef has a private read-only backup of the modem and calibration partitions (checksummed, plus an encrypted second copy) [V: not in this repository]; [#449](https://github.com/derekross/omarchy-mobile/pull/449) (open) gives husky's descriptor the `NV_PARTS` so `tools/nv-backup` takes and checks it.** | Read cheetah's and the 9a's MODEM-PLAN M0 to M2 end to end. Stage 0 is read-only: partitions, and what a booted phone answers without starting the modem | +| NFC | testing (a test kernel with the node switched on by an overlay: the chip answers and reads tags through `nxp-nci`; kernel [#208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209), both drafts) | Lef | 9a [#105](https://github.com/derekross/linux-omarchy-mobile/pull/105), [#104](https://github.com/derekross/linux-omarchy-mobile/pull/104) | What we found: an ST ST54L combo, its NCI controller at 0x08 on `hsi2c_0` (the haptics bus of #200) with its IRQ on gpa7, the chip's enable line on gph1-6 and a reference clock from the PMU's NFC pad (register 0x3e84); its secure element is on `spi_12` and is never to be touched. The driver is `nxp-nci` (as the 9a), not `st-nci`. On a test kernel the chip answered the NCI power-on, detected an ISO-DEP card, and read a Type 2 tag with one NDEF record; without the clock pad (#209) the same chip still powered on but found no tag in one run. Not tested: suspend, the secure element, the power cost of the pad clock, a second phone. The 9a's NFC must not poll through s2idle (AGENTS.md) | Merge #208 and #209, then s2idle with the driver bound and the clock's power cost | +| Cameras, video decode | no (read from the stock device tree, not tested) | unassigned | 9a [#103](https://github.com/derekross/linux-omarchy-mobile/pull/103); cheetah [CAMERA-PLAN](../cheetah/CAMERA-PLAN.md) | The sensors, the MIPI receiver and the rest of the pipeline; large. What we found for video: the SoC's codecs are Samsung's MFC (HEVC, VP9; firmware loaded behind the S2MPU through the GSA image loader) and Google's BigWave for AV1; neither has a driver in any tree we use, so there is no `/dev/video*` and Chromium decodes YouTube on the CPU, which heats the phone [V: Lef's phone] | After the rest; for video, a read of Google's MFC and BigWave trees first | +| Suspend | no (never run on husky) | unassigned | 9a [SLEEP-PLAN](../tegu/SLEEP-PLAN.md) (s2idle works, drain high); cheetah [SUSPEND-PLAN](../cheetah/SUSPEND-PLAN.md) | UFS hibern8 and system suspend ([UFS-PLAN](UFS-PLAN.md) U5 and U6); the "UFS at `spm_lvl` 5", "only s2idle" and "regulators late" gotchas. `/sys/power/mem_sleep` selects `deep` on the current kernels [V: Lef's phone], so a test must set `s2idle` first. Idle with the screen off draws about 0.5 A on Lef's phone, cause unknown; a CPU idle-state overlay and a power-domain overlay both reboot-looped the phone (recovered over fastboot), so neither is a safe next step [V: Lef's phone, test tree] | `pm_test=freezer` first, with the USB cable in; UFS-PLAN U5 on the guarded initramfs boot | +| Thermal, CPU DVFS | testing on [kernel #158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (open, stacked on #157) | Brett | 9a [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) | #158 adds the CPU levels from the ECT and the CPU thermal zones; until then every core runs at the bootloader's rate. On Lef's test tree cpufreq-dt runs three policies and the four ACPM TMU zones report; software video decode took the SoC to 86 C, so his phone runs lowered passive trips and CPU caps as a stopgap (local, not in a package) | Review #158; then a skin temperature source (the S2MPG15 ADC) and cpuidle, which needs the MCT timer first | +| USB host, Type-C | testing (role switch to host without VBUS, once) | Lef (with Charging) | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a [#124](https://github.com/derekross/linux-omarchy-mobile/pull/124) | The Type-C controller is the MAX77759 TCPC above. dwc3 switches to xHCI host and back with no VBUS ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)); VBUS out is the gated part (draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)) | As Charging | +| Time, persistent storage | partly | unassigned | none yet | No RTC: `systemd-timesyncd` sets the clock a few minutes after Wi-Fi is up, and the first-boot release-key problem is fixed (omarchy-mobile #188, closed). Root is on `userdata` behind the read-only guard; marking slot B successful is still undecided ([#252](https://github.com/derekross/omarchy-mobile/issues/252)) | Write a short plan | +| Fingerprint | no (read from the stock device tree, not tested) | unassigned | cheetah [FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md); 9a [FINGERPRINT-PLAN](../tegu/FINGERPRINT-PLAN.md) | What we found: a Goodix under-display sensor as a platform node (the secure world owns its SPI, as on the 7 Pro), IRQ on gpa7, reset on gpp1, its rail always on. Trusty, `persist` and RPMB writes are irreversible and need the human's explicit go | Last, as a proposal | ## Order I would take them in A proposal, not a verdict; Brett and Derek know the hardware better. -1. **Merge #148, #153, #154**, and write the missing plans (display, battery and USB-C, GPU) before any PMIC poking. -2. **Battery, charging and USB-C** (Lef, agreed on #1): today there is no battery power supply, which blocks daily use, and the phone should not be run flat unsupervised. -3. **Display driver** (Brett, next), because a render node alone still copies every frame through the simple framebuffer, and brightness, 120 Hz and power saving need it. -4. **GPU** (Brett, next): plan it in parallel, enable it after thermal zones and DVFS, and note that the zuma `clk-acpm` variant is missing. -5. **Suspend**, after UFS hibern8 and the regulators; then **Bluetooth** once the combo chip's firmware path is clear (it depends on the Wi-Fi work), then **audio, sensors, fingerprint**, each gated. -6. **Modem** once a SIM is found, after power, USB-C and the NV-protection steps in MODEM-PLAN. - -Wi-Fi works on a test kernel (#156); a second phone's test is the next step there. +1. ~~Merge #148, #153, #154~~ (done 2026-10-31 and 2026-11-01), and the battery base (#163, #175, done). Next to land: Brett's display, GPU, DVFS and Wi-Fi PRs (#160, #157, #158, #156), then #205 (the battery bus on by default), #199 and #200, the sound set (#203, #204, #450, #453). +2. **Battery, charging and USB-C** (Lef): the gauge and the charger work; the Type-C driver is a sink. Left: the model in the board file, the 92 % stop (#272), and host mode with VBUS out, which waits for the runbook review (#282) and a USB-C meter. +3. **Display driver** (Brett): works at 120 Hz on #160; it needs a second phone's test and review. +4. **GPU, DVFS and thermal** (Brett): #157 and #158; the zuma `clk-acpm` variant is in #157. +5. **Sound** (Lef): done on a test tree; the AoC core port and the System MMU v9 file need the maintainer's choice of file shape before they become PRs. Then the microphones (which id is which hole), the earpiece and headset paths, calibration. +6. **Idle power and suspend**: the phone draws about 0.5 A idle with the screen off, so an everyday battery life needs this before anything else; the idle-state and power-domain overlays tried so far reboot-looped the phone, so the next step is a measurement and a plan, not another overlay. +7. **Sensors, NFC, GNSS, fingerprint** in that order, each from the stage-0 facts in the table, each gated; **cameras and video decode** after them. +8. **Modem** once a SIM is found, after power, USB-C and the NV-protection steps in MODEM-PLAN. ## How to help without risking a phone @@ -67,15 +77,17 @@ Wi-Fi works on a test kernel (#156); a second phone's test is the next step ther ## Open questions -- Which Bluetooth, NFC and haptics parts does husky have, and which GPU generation? (The stock overlay already names the panel and the charger.) None is named in the husky files of this repository [V: searched `device/husky`]. -- Is husky's GPU the same Mali generation as the 9a's, so that its device tree can be adapted? [I] -- Is a zuma variant of `clk-acpm` planned? Kernel [#84](https://github.com/derekross/linux-omarchy-mobile/pull/84) is the pattern. -- Should husky's slot B ever be marked successful (a `devinfo` write)? On the 9a that is on hold; for husky it has not been decided. +- ~~Which Bluetooth, NFC and haptics parts does husky have, and which GPU generation?~~ Answered above: BCM4398D0 (#199), ST54L (stock tree), CS40L26A and LM3644 (#200), Mali-G715 on panthor (#157). The zuma `clk-acpm` variant is in #157. +- Which microphone id is which hole, and what do the earpiece and headset paths need (#450, #453)? +- Why does the phone draw about 0.5 A idle with the screen off, and why did the CPU idle-state and power-domain overlays reboot-loop it? Not known; no measurement plan yet. +- In which file shape should the zuma System MMU v9 code and the AoC core port go (asked on #1)? +- Should husky's slot B ever be marked successful (a `devinfo` write)? On the 9a that is on hold; for husky it is [#252](https://github.com/derekross/omarchy-mobile/issues/252), still open. Lef's phone sets the bit with a local unit after it ran out of retries once. +- Does touch survive a long idle with the screen off? One 12 h idle on 2026-11-04 left only Power working; not reproduced, not cause-checked. ## Credits and sources -- **Brett-Michael Green** ([@greenbrettmichael](https://github.com/greenbrettmichael)) brought the Pixel 8 Pro up: the zuma device tree, UFS, USB, the watchdog, buttons (#148), touch (#153), the ACPM and PMIC base, the test tags, and he is on Wi-Fi now. Most of "What works today" rests on that work. +- **Brett-Michael Green** ([@greenbrettmichael](https://github.com/greenbrettmichael)) brought the Pixel 8 Pro up: the zuma device tree, UFS, USB, the watchdog, buttons (#148), touch (#153), the ACPM and PMIC base, the test tags, and the open display (#160), GPU (#157), DVFS (#158) and Wi-Fi (#156) PRs that every test tree here is built on. Most of "What works today" rests on that work. - **W4HO** ([@W4HO-ham](https://github.com/W4HO-ham)) authored the 9a pull requests linked above (all but #143, which is Derek's, and #56, whose author I did not check). Others may have co-authored; the pull requests have the full record. - **Derek Ross** ([@derekross](https://github.com/derekross)) owns the project, the Pixel 7 Pro reference port and the cheetah `*-PLAN.md` files linked above, the kernel tree, the tools and the review lessons. -- **Lef** ([@Somnius](https://github.com/Somnius)) tested on a second unit (Kioxia UFS 4.0), traced the short keyboard to the wrong physical size and proposed the fix ([kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154), open), and wrote this page. +- **Lef** ([@Somnius](https://github.com/Somnius)) tested on a second unit (Kioxia UFS 4.0), traced the short keyboard to the wrong physical size and fixed it ([kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154), merged), did the battery buses and gauge (#163, #175), the charger and Type-C runs, Bluetooth (#199), haptics and torch (#200), the AoC and sound (#203, #204, #450, #453), the stage-0 reads of the stock tree for the rows marked "not tested", and wrote this page. - **Sources:** upstream Linux, Google's published GPL kernel trees (`android-gs-shusky-*`), and the plans and notes in this repository. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 5c30d696d..6bb7f9d9e 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 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, so frequency scaling and the GPU thermal zone count as in review, [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) in review, [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) in review; [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 once the modem is up, started by hand: a 30-minute session through the switch on 2026-11-01 (omamobile-gnss 0.2.5's start, the modem link left to cycle) ran clean, 1763 of 1765 GGA sentences fixed, first fix 37 s after a client connected; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150), merged, the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172) in review (without it the modem link hung the palmtop within minutes) and [#114](https://github.com/derekross/omarchy-mobile/pull/114); [plan](../device/tegu/MODEM-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)) | WIP (registered on LTE, mobile data over `rmnet0`, texts both ways and speakerphone calls in and out with `omamobile-modem-sit` ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#367](https://github.com/derekross/omarchy-mobile/pull/367)), on the owner's kernel and on in-tree drivers from the open kernel PRs ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187), [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162)); the package doesn't start the modem, the kernel PRs aren't merged, and calls have no echo cancellation or earpiece 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)) | testing (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key lights the lock screen on the first press ([#268](https://github.com/derekross/omarchy-mobile/pull/268), [#275](https://github.com/derekross/omarchy-mobile/pull/275)), and the RTC wakes it; on 2026-11-01 thirty attended 120 s sleeps ([plan](../device/tegu/SLEEP-PLAN.md) S1) and a day of real use with auto-sleep on ([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)) all woke, but six test sleeps since 10-28 did not (one in 21 on the clock-fix kernel on 11-01, and one in 127 in an overnight series of 120 s sleeps on 11-01 to 11-02), so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [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, not marked successful; 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)) | WIP (simple-framebuffer: console and Omarchy's lock screen) | no | testing (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); [NOTES](../device/husky/NOTES.md)) | testing (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); [NOTES](../device/husky/NOTES.md)) | testing (USB and SSH) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | no | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, on a test kernel, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver by hand under a dead-man tool, slow on plain 5 V, on a test kernel, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163); [notes](../device/husky/BATTERY-NOTES.md)) | no | no | no | no | no | no | no | no | no | no | no | +| Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B, not marked successful; 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)) | WIP (simple-framebuffer with the panel's size, [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154): console and Omarchy's lock screen; 120 Hz with brightness on a test kernel, [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)) | testing (panthor on the Mali-G715 on a test kernel, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157); [ROADMAP](../device/husky/ROADMAP.md)) | 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) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | testing (BCM4398D0 on the APM UART, pairing and A2DP, on a test kernel, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image; [ROADMAP](../device/husky/ROADMAP.md)) | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, pack EEPROM, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163) and [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175); the bus on by default waits for [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: 3 A from a Type-C source, 1.485 A into the battery from a PD charger; 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)) | testing (CS40L26 on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | testing (LM3644, 50 mA cap, on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | 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 [#450](https://github.com/derekross/omarchy-mobile/pull/450)) | 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 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; [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, in review, [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 | no | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; in review, [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); [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)) | no | no | no | no | no | no | no | no | 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) | no | | OnePlus 13 ([notes](../device/dodge/NOTES.md)) | dodge | sm8750 (Snapdragon 8 Elite) | testing (kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [BRINGUP](../device/dodge/BRINGUP-M1.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (msm/dpu; warm-boot drop fixed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (Adreno 830 / gpu2; Vulkan untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (CDC NCM + SSH; gadget stuck after replug until reboot; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (WCN7860 / ath12k; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (pairing; A2DP untested; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (gauge; charging path not claimed; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | no | no | - | testing (speakers, earpiece, mics; headset plug untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (accel, prox, compass; autorotate; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (LTE data; calls/SMS untested; opt-in flag; [modem](../device/dodge/modem/README.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | WIP (s2idle not default; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | | *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | | diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index 0cc10afac..62f66521b 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -159,7 +159,7 @@ The kernel package, the update path for slot B and the installer are designed to 6. **CI**: lint and package tests on every push; kernel, DTB validation and twice-built images per device on kernel tags; unsigned bundles on release. Pinned container and toolchain, so the maintainer can rebuild and compare before signing. 7. **Downloadable images**: build the per-device bundles and the shared root image in CI from a release tag, sign them, and host them (GitHub Releases or our own server) with the `install` script, so people flash a release without building anything. No Google file is ever in a download: the installer still extracts each user's firmware from their own factory image. 8. **Builds local by default**: every package (Mesa and Hyprland included) and every image builds on the builder's own machine from the repos alone (`tools/build-packages` in the arm64 container, ccache, native arm64 CI runners for speed). Building on a connected phone (`tools/repo-build`) stays an opt-in shortcut, never a requirement. -9. **Second device bring-up as the proof**: a second Pixel (a gs201 sibling first, or a gs101 phone to test the smaller boot image set) built, packaged and installed by the same tools with nothing but its descriptor, DTS, firmware map and device package added. Under way, all community work: the Pixel Fold (felix) boots to its cover screen with its keys and GPU, the Pixel 6 Pro (raven) runs Omarchy on our kernel (its package in review), the Pixel 8 Pro (husky, zuma) boots with USB and SSH and its UFS plan in review, the Pixel 9a (tegu, zumapro) reached first light, the Pixel 7a (lynx) boots to its initramfs, the Pixel 6 (oriole) has its descriptor from a retail phone, and the Pixel 4 (flame, Snapdragon) boots from RAM; board packages now come from each descriptor's `ROOTFS_PACKAGES`, so a non-cheetah image no longer pulls cheetah's. +9. **Second device bring-up as the proof**: a second Pixel (a gs201 sibling first, or a gs101 phone to test the smaller boot image set) built, packaged and installed by the same tools with nothing but its descriptor, DTS, firmware map and device package added. Under way, all community work: the Pixel Fold (felix) boots to its cover screen with its keys and GPU, the Pixel 6 Pro (raven) runs Omarchy on our kernel (its package in review), the Pixel 8 Pro (husky, zuma) boots to Omarchy's lock screen with touch, buttons and its UFS plan merged and more on test kernels, the Pixel 9a (tegu, zumapro) reached first light, the Pixel 7a (lynx) boots to its initramfs, the Pixel 6 (oriole) has its descriptor from a retail phone, and the Pixel 4 (flame, Snapdragon) boots from RAM; board packages now come from each descriptor's `ROOTFS_PACKAGES`, so a non-cheetah image no longer pulls cheetah's. Alongside every release, **keep linux-omarchy-mobile honest**: the release kernel is a tag on the published `omamobile` branch, so a curation pass moves what has passed on the phone out of the local `omamobile-int` into a release branch on `omamobile` before each release ([RELEASES](RELEASES.md) §8), and the gap between the phone's test kernel and the release shrinks release by release. From 1e740e384d29d62da6aaf08c1e63c7b0d4a4d76d Mon Sep 17 00:00:00 2001 From: Lef Date: Sat, 7 Nov 2026 15:52:28 +0200 Subject: [PATCH 2/3] device/husky: record the local boot-success unit as a dated note, charging wording, NOTES entries --- device/husky/NOTES.md | 11 +++++++++++ device/husky/ROADMAP.md | 16 ++++++++-------- docs/DEVICES.md | 2 +- 3 files changed, 20 insertions(+), 9 deletions(-) diff --git a/device/husky/NOTES.md b/device/husky/NOTES.md index 381a1eecc..36010a1fa 100644 --- a/device/husky/NOTES.md +++ b/device/husky/NOTES.md @@ -10,6 +10,15 @@ Sources: - `P/`: postmarketOS pmaports `device/testing` (2026-10-21). - `G/`: Google's GPL kernel for this phone, `android-gs-shusky-6.1-android16` ([source.android.com: Build Pixel kernels](https://source.android.com/docs/setup/build/building-pixel-kernels)). +## 2026-11-05: idle-state and power-domain overlays that reboot-looped the phone + +Lef's phone (Kioxia unit), slot B, while looking for the cause of a ~520 mA idle draw with the screen off. I tested two bring-up overlays; every kernel flashed with either of them reset the phone hard about 8 to 40 s after boot (no pstore, no panic text). My first note called the idle-state boot stable; it was not (the temperature log stopped after a minute and I had already flashed the next build). + +- **Kernels** [V]: `g65c974eb3063` (`power-c2-test`: the three `idle-states` from stock's DT switched on for all nine CPUs, `cpu-idle-states` on each), `g4ce060268fea` (plus `power-pd-test`: 13 power domains enabled for genpd), `g1f109674c767` (plus status-only nodes for g3d, embedded_g3d, dpub, dpuf0/1, aoc and hsi0/1). +- **Not established** [unknown]: which of the two overlays (or the PMU regmap range additions) caused the resets. Turning C2 off on all nine cores at runtime about 7 s after boot did not stop them. `pm_genpd_summary` readings are not usable here: the status bit the gs101 driver reads does not mean "powered" on zuma. +- **Recovery** [V]: I did not write to any partition while it was resetting. I held Volume Down + Power to reach fastboot (slot B current, successful yes, retry 2 left at that point, A unbootable), and `bin/omamobile flash` wrote boot, init_boot, vendor_boot, vendor_kernel_boot and dtbo to slot B with the original overlay set (without `power-c2-test` and `power-pd-test`; kernel `g1f109674c767`). It booted and stayed up. +- **Lessons**: wait at least 3 minutes and read `/proc/uptime` after every flash before trusting a boot; no more power-domain overlays without a plan (gs101 needs the DTZPC handling, as Derek said on [#472](https://github.com/derekross/omarchy-mobile/pull/472)). + ## 2026-10-31: Wi-Fi Wi-Fi works on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (a draft, stacked on #153, #143 and #56), at `f47c5bd34` on greenbrettmichael/linux-omarchy-mobile `omamobile-zuma-husky-wifi`, with the repository's husky config (`CONFIG_PHY_ZUMA_PCIE=m` is in #214), `modules-push` and the firmware from [#214](https://github.com/derekross/omarchy-mobile/pull/214). The phone joins its network at boot through NetworkManager. #156 has since been rebased to `717fba4f`; the only change is #143's join-parameter struct (`chanspec_list[1]` to `chanspec_list[]`). The phone joined at boot on that head too, as part of the display test kernel (tag `husky-test-20261031-d3`, which contains `717fba4f`), on 2026-10-31. @@ -71,6 +80,7 @@ Touch works on a test kernel, [kernel #153](https://github.com/derekross/linux-o - With stock's inversion, taps came in rotated 180°: a tap at the top-left read (1191, 2824). - Without it, a tap at the top-left reads (87, 144) of 1343 × 2991. - **In Omarchy** [V]: Hyprland lists the touchscreen (`salixp-touchscreen`). The lock screen's PIN pad takes the keys that are touched, and the phone unlocks by touch. A touch wakes the screen. +- **Which units ran it, on which tag** [V]: the first unit ran `husky-test-20261031-c5` (the orientation check above); the Kioxia unit (Lef's) ran `husky-test-20261031-c6` on 2026-10-31 (`salixp` lines, corner taps decoded from `/dev/input/event1`), and Brett's `salixp` lines and corners matched it. Not recorded here: a run of the merged `main` kernel on a stock tree by either unit (unknown; a boot of the current `main` tag with the corner-tap check would settle it). ## 2026-10-30: the buttons @@ -86,6 +96,7 @@ Power and volume work through `gpio-keys` on a test kernel, the U4 kernel plus [ - A short press of power locks and darkens the screen, and the next one wakes it (omamobile-keys). - Volume does nothing visible yet, since there is no sound card. - **The driver's `irq number not available`** [V]: once ALIVE was described, the zuma pinctrl data ran the GPIO EINT setup on ALIVE, whose banks are all wake-up EINTs, and it logged this line at every boot. #148 drops that setup from ALIVE, as gs101 does, and test `-b2` logs no such line. +- **Which units ran it, on which tag** [V]: the first unit ran `husky-test-20261030-b` and `-b2`; the Kioxia unit (Lef's) ran `husky-test-20261031-c6` on 2026-10-31 (volume up, volume down and power each logged a press and release on `/dev/input/event0`, in two rounds). Not recorded here: a run of the merged `main` kernel (unknown). ## 2026-10-21: stage 0, part 4: root capture, backup, and how ABL picks the DTB diff --git a/device/husky/ROADMAP.md b/device/husky/ROADMAP.md index fff79e4b8..87a0b6123 100644 --- a/device/husky/ROADMAP.md +++ b/device/husky/ROADMAP.md @@ -3,7 +3,7 @@ Written 2026-10-31 by Lef ([@Somnius](https://github.com/Somnius)). Last updated: 2026-11-07. The original roadmap for this port stops at "boots" ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1)), and that bar is met on the units tested so far: Omarchy runs from slot B and unlocks by touch. This page is the rest of it, one row per subsystem, in the order of the columns in [docs/DEVICES.md](../../docs/DEVICES.md). For each it says what works, who is on it, the closest finished work to copy from (the Pixel 9a, `tegu`, has a newer Tensor SoC (zumapro) than husky's zuma [I: neighbouring generations, so device-tree work should carry over in part], and the Pixel 7 Pro, `cheetah`, has a plan for almost everything), what is in the way, and a first step that is read-only (no flashing). Credits are at the end. -Facts are marked [V] (checked, with the source) or [I] (an inference, with what would settle it). Pull request states are as of 2026-11-07. "Merged" means on `main` of this repository or on `omamobile` of the kernel; everything else ran only on a test tree, and the table says which pull request it waits on. Where a boot of Lef's test tree is the evidence, the kernel release was `7.3.0-rc6-omamobile-push1-g50ef3c279021` for most rows and a later test tree, `7.3.0-rc6-omamobile-push1-ge98a7a38a3ef`, for NFC (the test branches and tags are on his fork and listed in [#450](https://github.com/derekross/omarchy-mobile/pull/450)). Nothing here asks anyone to skip the safety rules: read-only first, one change per boot, a read-only backup of the modem and calibration partitions before radio, PMIC, AoC or Trusty work ([AGENTS.md](../../AGENTS.md) §1, [CONTRIBUTING.md](../../CONTRIBUTING.md) §3). Kernel PR numbers are in [derekross/linux-omarchy-mobile](https://github.com/derekross/linux-omarchy-mobile), written `kernel #N`. +Facts are marked [V] (checked, with the source) or [I] (an inference, with what would settle it). Pull request states are as of 2026-11-07. "Merged" means on `main` of this repository or on `omamobile` of the kernel; everything else ran only on a test tree, and the table says which pull request it waits on. Where a boot of Lef's test tree is the evidence, the kernel release was `7.3.0-rc6-omamobile-push1-g50ef3c279021` for most rows and a later test tree, `7.3.0-rc6-omamobile-push1-ge98a7a38a3ef`, for NFC (the test branches and tags are on his fork and listed in [AOC-PLAN](AOC-PLAN.md)). Nothing here asks anyone to skip the safety rules: read-only first, one change per boot, a read-only backup of the modem and calibration partitions before radio, PMIC, AoC or Trusty work ([AGENTS.md](../../AGENTS.md) §1, [CONTRIBUTING.md](../../CONTRIBUTING.md) §3). Kernel PR numbers are in [derekross/linux-omarchy-mobile](https://github.com/derekross/linux-omarchy-mobile), written `kernel #N`. ## What works today @@ -11,19 +11,19 @@ Two units are in play: Brett's (Samsung 128 GB UFS 3.1) and Lef's (Kioxia 256 GB **On `main` (merged or landed):** boot, UFS, USB networking, the watchdog, the framebuffer display with its panel size (kernel #154), touch (kernel #153), buttons (kernel #148), the hsi2c_9 and hsi2c_11 buses with the gauge, the PMIC and the pack EEPROM (kernel #163, #175; the buses still need a bring-up overlay until kernel [#205](https://github.com/derekross/linux-omarchy-mobile/pull/205)), the `splash` command line ([#278](https://github.com/derekross/omarchy-mobile/pull/278)) and the device package's display start, USB replug rescue and retain-splash ([#228](https://github.com/derekross/omarchy-mobile/pull/228), [#250](https://github.com/derekross/omarchy-mobile/pull/250), [#285](https://github.com/derekross/omarchy-mobile/pull/285)). -**On test trees only (open PRs):** the DRM display at 120 Hz (kernel #160), the GPU (kernel #157), CPU DVFS and thermal zones (kernel #158), Wi-Fi (kernel #156), Bluetooth (kernel #199), haptics and torch (kernel #200), the AoC with speakers and microphone (kernel #203, #204, package #453, plan #450), the Type-C sink and the charger under a dead-man tool ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). +**On test trees only (open PRs):** the DRM display at 120 Hz (kernel #160), the GPU (kernel #157), CPU DVFS and thermal zones (kernel #158), Wi-Fi (kernel #156), Bluetooth (kernel #199), haptics and torch (kernel #200), the AoC with speakers and microphone (kernel #203, #204, package #453, [AOC-PLAN](AOC-PLAN.md)), the Type-C sink and the charger under a dead-man tool ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). -- **Boot** from slot B, with stock or GrapheneOS on slot A as the way back. Slot B is deliberately never marked successful, so ABL gives it three boots ([BRINGUP-M1](BRINGUP-M1.md), [UFS-PLAN](UFS-PLAN.md)). On 2026-11-01 Lef's phone ran out of retries and GrapheneOS wiped `userdata` on its next boot ([BATTERY-NOTES](BATTERY-NOTES.md) §9); he now sets the successful bit with a local unit that is not in any package. +- **Boot** from slot B, with stock or GrapheneOS on slot A as the way back. Slot B is deliberately not marked successful by any package, so ABL gives it three boots ([BRINGUP-M1](BRINGUP-M1.md), [UFS-PLAN](UFS-PLAN.md)). On 2026-11-01 Lef's phone ran out of retries and GrapheneOS wiped `userdata` on its next boot ([BATTERY-NOTES](BATTERY-NOTES.md) §9); from 2026-11-01 to 2026-11-07 a local unit marked slot B on this phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252). - **UFS** at HS-G4, two lanes, behind the read-only guard, on both device vendors ([UFS-PLAN](UFS-PLAN.md) U2 passed on the Kioxia unit). - **USB gadget** networking and SSH, and the watchdog driver (no 80 s reset). - **Display** as a simple framebuffer on `main`: console, lock screen and the shell at 1344x2992, with the panel's physical size (70x155 mm) since [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154) (merged 2026-11-01), so the on-screen keyboard has its proper height (196 px, 21% of the screen, instead of 105 px) [V: measured on the Kioxia unit]. On a test tree with [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (open): gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, started by the device package ([#228](https://github.com/derekross/omarchy-mobile/pull/228), merged); Lef's phone has run it since 2026-11-01. - **Touch** (STMicroelectronics SALIXP over SPI) and **buttons** (`gpio-keys`): raw events decoded in the right corners, swipe, PIN pad, app launching, wake by tap and by Power (both units). Merged 2026-10-31 as [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153) and [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148). - **Foundations those PRs added:** the ALIVE pin controller, the CMU_TOP and CMU_HSI0 clocks, the ACPM mailbox and protocol driver, the main PMIC (S2MPG14), USI2 and its SPI; then CMU_PERIC1, USI9 and USI11 with the battery buses ([kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163), [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175), merged 2026-11-01). -- **Battery and charging** on `main` plus an overlay: the gauge with Google's ATL model, the PMIC, the pack EEPROM; the charger driver by hand under a dead-man tool; the Type-C controller driver as a sink (3 A, replug survives) in the same guarded runs ([BATTERY-NOTES](BATTERY-NOTES.md), [issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Host mode with VBUS out waits for the runbook review ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). +- **Battery and charging** on `main` plus an overlay: the gauge with Google's ATL model, the PMIC, the pack EEPROM; the charger driver by hand under a dead-man tool; the Type-C controller driver as a sink (at the Type-C 3 A level, replug survives) in the same guarded runs ([BATTERY-NOTES](BATTERY-NOTES.md), [issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Host mode with VBUS out waits for the runbook review ([#272](https://github.com/derekross/omarchy-mobile/issues/272), draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)). - **Wi-Fi, GPU, CPU DVFS and thermal zones** on test trees with Brett's open kernel PRs [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156), [#157](https://github.com/derekross/linux-omarchy-mobile/pull/157) and [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158): on Lef's phone 5 GHz Wi-Fi, panthor on the Mali-G715 and cpufreq with the four ACPM TMU zones ([NOTES](NOTES.md) for Wi-Fi; the GPU and DVFS results are in those PRs, not re-measured here). - **Bluetooth** (BCM4398D0 on the APM UART): pairing and A2DP headphones, on [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199) (open); firmware from the owner's own vendor image. - **Haptics and torch** (CS40L26, LM3644): felt and seen, on [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200) (open). -- **Sound**: the AoC firmware loads and runs (GSA, Trusty, System MMU v9, mailboxes, 94 services), both CS35L41 amplifiers probe with the speaker-protection firmware from the owner's vendor image, and the AoC sound card plays stereo through the speakers and records from one microphone, through UCM2 and PipeWire. Test tree only: [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), plan and results [#450](https://github.com/derekross/omarchy-mobile/pull/450) (all open). The AoC core port and the System MMU v9 file are not PRs yet. +- **Sound**: the AoC firmware loads and runs (GSA, Trusty, System MMU v9, mailboxes, 94 services), both CS35L41 amplifiers probe with the speaker-protection firmware from the owner's vendor image, and the AoC sound card plays stereo through the speakers and records from one microphone, through UCM2 and PipeWire. Test tree only: [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), plan and results [AOC-PLAN](AOC-PLAN.md) (all open). The AoC core port and the System MMU v9 file are not PRs yet. Touch and Buttons are in `docs/DEVICES.md` with their merged PRs; the rest of this list is "testing" or "WIP" there, with the PR it waits on. @@ -41,10 +41,10 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists | Wi-Fi | testing on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (draft) | [Brett](https://github.com/greenbrettmichael) | done | #156: zuma's PCIe PHY and the BCM4398 (NCI backplane) in brcmfmac, stacked on #153 (merged) and #143 (landed); firmware from the owner's image with [#214](https://github.com/derekross/omarchy-mobile/pull/214) (merged). On Lef's phone it joins 5 GHz at boot and held a 40 min run at 221 to 502 Mbit/s ([#156 comment](https://github.com/derekross/linux-omarchy-mobile/pull/156#issuecomment-6562550631)). Open: P2P, recovery after a firmware crash, the `PKTID` log lines after a failed join ([NOTES](NOTES.md), the #156 thread) | Test #156 on a second phone: `tools/extract-vendor-firmware -d husky -s `, then check the scan and a join | | Bluetooth | testing on [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199) (open) | Lef | 9a [#122](https://github.com/derekross/linux-omarchy-mobile/pull/122); cheetah [BLUETOOTH-PLAN](../cheetah/BLUETOOTH-PLAN.md) | The BCM4398D0, the Bluetooth half of the Wi-Fi combo, on the APM's USI1 UART; BT_REG_ON, the wake lines and the REG_ON latch clock are in #199, with the CMU_APM UART clocks. Firmware is the stock `BCM.hcd` from the owner's own vendor image, never in a repository. Pairing and A2DP to headphones work on Lef's phone [V: #199]. Open: the board address from `/chosen` (an `omamobile-bt-addr` unit like cheetah's, not packaged yet), HFP, power | Review #199; then the bt-addr unit in the device package | | Battery | testing (gauge, PMIC and pack EEPROM on kernel #163 and #175, merged; the buses and the gauge's model through overlays until kernel [#205](https://github.com/derekross/linux-omarchy-mobile/pull/205)) | Lef | cheetah [POWER-PLAN](../cheetah/POWER-PLAN.md), [WIFI-BATTERY-PLAN](../cheetah/WIFI-BATTERY-PLAN.md); `gs201-cheetah.dts` has the same chip family. The 9a's [#119](https://github.com/derekross/linux-omarchy-mobile/pull/119) is the MAX77779 and does not apply as is | Stock overlay [V, same source as Display]: fuel gauge `maxim,max77759` @0x36, charger `max77759chrg` @0x69, Type-C `max77759tcpc` @0x25 and `max77729pmic` @0x66, all on `hsi2c_11`; also `nxp,pca9468` and the wireless charger `idt,p9412` (what we found: at 0x3c on `hsi2c_9`, the pack EEPROM bus, with its enable and boost lines on the PMIC GPIO expanders; no mainline driver, read from the stock tree, not tested). The gauge-model overlays are generated from Google's published `zuma-husky-battery-data.dtsi` ([#279](https://github.com/derekross/omarchy-mobile/pull/279), merged). Open: the model in the board file (or picked by the pack ID at runtime), and the charger stopping at 92 % with the bootloader's 4.35 V float ([#272](https://github.com/derekross/omarchy-mobile/issues/272), baseline in [#452](https://github.com/derekross/omarchy-mobile/pull/452)) | Done on one phone, see [BATTERY-NOTES](BATTERY-NOTES.md). Next: kernel #205 (the bus on by default), then the model. **No hand writes to the PMIC or the gauge outside a reviewed tool** (AGENTS.md §1; the notes list the ones made, and why) | -| Charging, USB-C | testing (the MAX77759 charger and `tcpci_maxim` as a sink, both by hand in guarded runs) | Lef | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a: [#97](https://github.com/derekross/linux-omarchy-mobile/pull/97) is `tcpci_maxim` for the MAX77779 (merged) | Same I2C bus as Battery. With the Type-C driver loaded the port is a sink at 3 A, the charger follows TCPM's input limit (0x13 to 0x77), and the driver closes the USB data switch on replug itself; a 30 W PD charger with a C-to-C cable charges at the 1.485 A device-tree cap ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Not run: PD/PPS, host mode with VBUS out (the connector has no VBUS regulator; the external boost needs a `regulator-fixed` on the MAX77759's GPIO5 plus the TCPC's EXTBST_CTRL), dongles, DP alt mode | The host-mode runbook and the `b5-host` tool are in draft [#282](https://github.com/derekross/omarchy-mobile/pull/282); nothing that sources power runs before the maintainer's review of it and a USB-C meter (his rule on #272). The replug rescue in the device package ([#250](https://github.com/derekross/omarchy-mobile/pull/250), merged) keeps the USB link until the Type-C driver is on by default | +| Charging, USB-C | testing (the MAX77759 charger and `tcpci_maxim` as a sink, both by hand in guarded runs) | Lef | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a: [#97](https://github.com/derekross/linux-omarchy-mobile/pull/97) is `tcpci_maxim` for the MAX77779 (merged) | Same I2C bus as Battery. With the Type-C driver loaded the port is a sink at the Type-C 3 A level and the charger input limit 0xc2 went 0x13 to 0x77 (the battery took +0.33 to +0.52 A, near full), and the driver closes the USB data switch on replug itself; in a separate run without the driver, a 30 W PD charger (no Type-C driver loaded, so no PD negotiation) gave +1.43 to +1.52 A into the battery (average +1.49 A) with 0xc2 unchanged at 0x13; 1.485 A is the device tree's cap, not a measurement ([REPORT-2026-11-01](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)). Not run: PD/PPS, host mode with VBUS out (the connector has no VBUS regulator; the external boost needs a `regulator-fixed` on the MAX77759's GPIO5 plus the TCPC's EXTBST_CTRL), dongles, DP alt mode | The host-mode runbook and the `b5-host` tool are in draft [#282](https://github.com/derekross/omarchy-mobile/pull/282); nothing that sources power runs before the maintainer's review of it and a USB-C meter (his rule on #272). The replug rescue in the device package ([#250](https://github.com/derekross/omarchy-mobile/pull/250), merged) keeps the USB link until the Type-C driver is on by default | | Haptics, Torch | testing on [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200) (open) | Lef | 9a [#96](https://github.com/derekross/linux-omarchy-mobile/pull/96) (CS40L26 and LM3644); cheetah [HAPTICS-TORCH-PLAN](../cheetah/HAPTICS-TORCH-PLAN.md) | CS40L26A at 0x43 on PERIC1 USI0 (`hsi2c_0`) and the LM3644 at 0x63 on PERIC0 USI14 (`hsi2c_14`); #200 adds CMU_PERIC0 and the HSI1 pin controller for them. Lef felt the buzz and saw the LED; the torch is capped at 50 mA per LED like the 7 Pro's bring-up. Open: a gentle strength for UI taps (feedbackd), the shell's torch tile | Review #200 | | GNSS | no (first steps in review: the bus clocks [#210](https://github.com/derekross/linux-omarchy-mobile/pull/210) and the PMIC rails [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211), both drafts; nothing runs yet) | Lef | cheetah [GNSS-PLAN](../cheetah/GNSS-PLAN.md); the 9a's is parked | What we found: a separate Broadcom BCM4775x on `spi_21` (HSI0 USI3, 26 MHz) with its own three S2MPG15 LDOs, as on the 7 Pro. The driver, the binding and the S2MPG15 regulators are already in the tree. The vendor image carries the Broadcom GNSS service, so this is the chip Android uses; the modem-GNSS channels in `cpif` are not the path. Missing: the pin controllers (in #156), the `gnss@0` node, and Google's `lhd` and `gpsd` in a chroot built from the owner's own factory image (the extract tool needs one line for husky); the regulator rule (PMIC modules after about 30 s of late init) | A bring-up overlay for the bus and the PMIC, read-only first; then the `gnss@0` node on #156's pin controllers | -| AoC, Speakers/mics | testing (AoC, both amplifiers, stereo speakers and one microphone through UCM2 and PipeWire, on a test tree: 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), plan [#450](https://github.com/derekross/omarchy-mobile/pull/450), all open) | Lef | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [AUDIO-PLAN](../cheetah/AUDIO-PLAN.md) | The AoC loads through the GSA and starts through Trusty (`trusty-ipc` before `trusty-virtio`); zuma's System MMU is v9, and the 7 Pro's v8 offsets reset the phone (#450). The amplifiers share one SPI controller, one on the native chip select and one on a GPIO one (#204). The speaker-protection firmware and `aoc.bin` come from the owner's own vendor image. Levels are capped (digital 737, analog 10, no `speaker_protection`), the microphone is one of three ids and which hole it is is not settled, the earpiece and headset paths are not done. Not PRs yet: the AoC core port to zuma and the System MMU v9 file (shape asked on #1) | Review #450 and #453; the AoC core and System MMU v9 patches once the maintainer picks the file shape | +| AoC, Speakers/mics | testing (AoC, both amplifiers, stereo speakers and one microphone through UCM2 and PipeWire, on a test tree: 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), plan [AOC-PLAN](AOC-PLAN.md), all open) | Lef | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [AUDIO-PLAN](../cheetah/AUDIO-PLAN.md) | The AoC loads through the GSA and starts through Trusty (`trusty-ipc` before `trusty-virtio`); zuma's System MMU is v9, and the 7 Pro's v8 offsets reset the phone (#450). The amplifiers share one SPI controller, one on the native chip select and one on a GPIO one (#204). The speaker-protection firmware and `aoc.bin` come from the owner's own vendor image. Levels are capped (digital 737, analog 10, no `speaker_protection`), the microphone is one of three ids and which hole it is is not settled, the earpiece and headset paths are not done. Not PRs yet: the AoC core port to zuma and the System MMU v9 file (shape asked on #1) | Review #450 and #453; the AoC core and System MMU v9 patches once the maintainer picks the file shape | | Sensors | no (read from the stock device tree, not tested) | unassigned | cheetah [AOC-PLAN](../cheetah/AOC-PLAN.md), [USF-PROTOCOL](../cheetah/USF-PROTOCOL.md) | What we found: the running AoC publishes the USF services (`com.google.usf`, its non-wake-up twin and the doorbell) and CHRE; the stock AoC node wants two sensor rails (S2MPG15 `L7S_SENSORS`, `L5S_PROX`) that our tree does not give it. Which physical sensors husky has is not known (the registry scripts are in the vendor partition). Needs the AoC char devices, Google's registry scripts loaded at boot, and the cheetah sensor proxy | After the AoC PRs: one read-only `RegistryGet` through the USF char device with the phone in hand (an AoC assert needs a reboot) | | Modem | no | Lef, once a SIM is found ([Brett asked](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6544100933)) | cheetah [MODEM-PLAN](../cheetah/MODEM-PLAN.md); 9a [MODEM-PLAN](../tegu/MODEM-PLAN.md) ("ONLINE with IPC, no SIM yet") | A SIM (a prepaid one is the plan; the phone's own SIM is a data-only eSIM); the baseband is `g5300i` [V: fastboot], the S5300 family like cheetah's [I]; the CP's PCIe link and the `cpif` driver; modem firmware from the owner's own factory image; the NV protections. **Lef has a private read-only backup of the modem and calibration partitions (checksummed, plus an encrypted second copy) [V: not in this repository]; [#449](https://github.com/derekross/omarchy-mobile/pull/449) (open) gives husky's descriptor the `NV_PARTS` so `tools/nv-backup` takes and checks it.** | Read cheetah's and the 9a's MODEM-PLAN M0 to M2 end to end. Stage 0 is read-only: partitions, and what a booted phone answers without starting the modem | | NFC | testing (a test kernel with the node switched on by an overlay: the chip answers and reads tags through `nxp-nci`; kernel [#208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209), both drafts) | Lef | 9a [#105](https://github.com/derekross/linux-omarchy-mobile/pull/105), [#104](https://github.com/derekross/linux-omarchy-mobile/pull/104) | What we found: an ST ST54L combo, its NCI controller at 0x08 on `hsi2c_0` (the haptics bus of #200) with its IRQ on gpa7, the chip's enable line on gph1-6 and a reference clock from the PMU's NFC pad (register 0x3e84); its secure element is on `spi_12` and is never to be touched. The driver is `nxp-nci` (as the 9a), not `st-nci`. On a test kernel the chip answered the NCI power-on, detected an ISO-DEP card, and read a Type 2 tag with one NDEF record; without the clock pad (#209) the same chip still powered on but found no tag in one run. Not tested: suspend, the secure element, the power cost of the pad clock, a second phone. The 9a's NFC must not poll through s2idle (AGENTS.md) | Merge #208 and #209, then s2idle with the driver bound and the clock's power cost | @@ -81,7 +81,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better. - Which microphone id is which hole, and what do the earpiece and headset paths need (#450, #453)? - Why does the phone draw about 0.5 A idle with the screen off, and why did the CPU idle-state and power-domain overlays reboot-loop it? Not known; no measurement plan yet. - In which file shape should the zuma System MMU v9 code and the AoC core port go (asked on #1)? -- Should husky's slot B ever be marked successful (a `devinfo` write)? On the 9a that is on hold; for husky it is [#252](https://github.com/derekross/omarchy-mobile/issues/252), still open. Lef's phone sets the bit with a local unit after it ran out of retries once. +- Should husky's slot B ever be marked successful (a `devinfo` write)? On the 9a that is on hold; for husky it is [#252](https://github.com/derekross/omarchy-mobile/issues/252), still open. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. - Does touch survive a long idle with the screen off? One 12 h idle on 2026-11-04 left only Power working; not reproduced, not cause-checked. ## Credits and sources diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 6bb7f9d9e..38524fb0d 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 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, so frequency scaling and the GPU thermal zone count as in review, [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) in review, [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) in review; [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 once the modem is up, started by hand: a 30-minute session through the switch on 2026-11-01 (omamobile-gnss 0.2.5's start, the modem link left to cycle) ran clean, 1763 of 1765 GGA sentences fixed, first fix 37 s after a client connected; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150), merged, the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172) in review (without it the modem link hung the palmtop within minutes) and [#114](https://github.com/derekross/omarchy-mobile/pull/114); [plan](../device/tegu/MODEM-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)) | WIP (registered on LTE, mobile data over `rmnet0`, texts both ways and speakerphone calls in and out with `omamobile-modem-sit` ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#367](https://github.com/derekross/omarchy-mobile/pull/367)), on the owner's kernel and on in-tree drivers from the open kernel PRs ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187), [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162)); the package doesn't start the modem, the kernel PRs aren't merged, and calls have no echo cancellation or earpiece 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)) | testing (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key lights the lock screen on the first press ([#268](https://github.com/derekross/omarchy-mobile/pull/268), [#275](https://github.com/derekross/omarchy-mobile/pull/275)), and the RTC wakes it; on 2026-11-01 thirty attended 120 s sleeps ([plan](../device/tegu/SLEEP-PLAN.md) S1) and a day of real use with auto-sleep on ([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)) all woke, but six test sleeps since 10-28 did not (one in 21 on the clock-fix kernel on 11-01, and one in 127 in an overnight series of 120 s sleeps on 11-01 to 11-02), so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [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, not marked successful; 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)) | WIP (simple-framebuffer with the panel's size, [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154): console and Omarchy's lock screen; 120 Hz with brightness on a test kernel, [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)) | testing (panthor on the Mali-G715 on a test kernel, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157); [ROADMAP](../device/husky/ROADMAP.md)) | 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) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | testing (BCM4398D0 on the APM UART, pairing and A2DP, on a test kernel, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image; [ROADMAP](../device/husky/ROADMAP.md)) | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, pack EEPROM, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163) and [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175); the bus on by default waits for [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: 3 A from a Type-C source, 1.485 A into the battery from a PD charger; 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)) | testing (CS40L26 on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | testing (LM3644, 50 mA cap, on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | 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 [#450](https://github.com/derekross/omarchy-mobile/pull/450)) | 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 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 this 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)) | WIP (simple-framebuffer with the panel's size, [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154): console and Omarchy's lock screen; 120 Hz with brightness on a test kernel, [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)) | testing (panthor on the Mali-G715 on a test kernel, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157); [ROADMAP](../device/husky/ROADMAP.md)) | 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) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | testing (BCM4398D0 on the APM UART, pairing and A2DP, on a test kernel, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image; [ROADMAP](../device/husky/ROADMAP.md)) | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, pack EEPROM, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163) and [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175); the bus on by default waits for [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205); [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)) | testing (CS40L26 on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | testing (LM3644, 50 mA cap, on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | 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 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; [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, in review, [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 | no | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; in review, [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); [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)) | no | no | no | no | no | no | no | no | 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) | no | | OnePlus 13 ([notes](../device/dodge/NOTES.md)) | dodge | sm8750 (Snapdragon 8 Elite) | testing (kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [BRINGUP](../device/dodge/BRINGUP-M1.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (msm/dpu; warm-boot drop fixed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (Adreno 830 / gpu2; Vulkan untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (CDC NCM + SSH; gadget stuck after replug until reboot; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (WCN7860 / ath12k; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (pairing; A2DP untested; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (gauge; charging path not claimed; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | no | no | - | testing (speakers, earpiece, mics; headset plug untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (accel, prox, compass; autorotate; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (LTE data; calls/SMS untested; opt-in flag; [modem](../device/dodge/modem/README.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | WIP (s2idle not default; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | | *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | | From c29fe910b8c078c631f4d873bbb06c7ada85aa79 Mon Sep 17 00:00:00 2001 From: Lef Date: Sat, 7 Nov 2026 17:55:21 +0200 Subject: [PATCH 3/3] device/husky: roadmap follows the ruling on #252 for marking slot B Line 55 and the open question now say what you decided on #252: marking is a manual, attended step, and nothing marks slot B on the 8 Pro until the boot LUN guard change and #483 are in. Line 55 also carries the same dated record as line 16 and the DEVICES Boot cell, as you asked. Signed-off-by: Lef --- device/husky/ROADMAP.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/device/husky/ROADMAP.md b/device/husky/ROADMAP.md index 87a0b6123..acbe4a867 100644 --- a/device/husky/ROADMAP.md +++ b/device/husky/ROADMAP.md @@ -52,7 +52,7 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists | Suspend | no (never run on husky) | unassigned | 9a [SLEEP-PLAN](../tegu/SLEEP-PLAN.md) (s2idle works, drain high); cheetah [SUSPEND-PLAN](../cheetah/SUSPEND-PLAN.md) | UFS hibern8 and system suspend ([UFS-PLAN](UFS-PLAN.md) U5 and U6); the "UFS at `spm_lvl` 5", "only s2idle" and "regulators late" gotchas. `/sys/power/mem_sleep` selects `deep` on the current kernels [V: Lef's phone], so a test must set `s2idle` first. Idle with the screen off draws about 0.5 A on Lef's phone, cause unknown; a CPU idle-state overlay and a power-domain overlay both reboot-looped the phone (recovered over fastboot), so neither is a safe next step [V: Lef's phone, test tree] | `pm_test=freezer` first, with the USB cable in; UFS-PLAN U5 on the guarded initramfs boot | | Thermal, CPU DVFS | testing on [kernel #158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (open, stacked on #157) | Brett | 9a [#87](https://github.com/derekross/linux-omarchy-mobile/pull/87) | #158 adds the CPU levels from the ECT and the CPU thermal zones; until then every core runs at the bootloader's rate. On Lef's test tree cpufreq-dt runs three policies and the four ACPM TMU zones report; software video decode took the SoC to 86 C, so his phone runs lowered passive trips and CPU caps as a stopgap (local, not in a package) | Review #158; then a skin temperature source (the S2MPG15 ADC) and cpuidle, which needs the MCT timer first | | USB host, Type-C | testing (role switch to host without VBUS, once) | Lef (with Charging) | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a [#124](https://github.com/derekross/linux-omarchy-mobile/pull/124) | The Type-C controller is the MAX77759 TCPC above. dwc3 switches to xHCI host and back with no VBUS ([issue #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)); VBUS out is the gated part (draft [#282](https://github.com/derekross/omarchy-mobile/pull/282)) | As Charging | -| Time, persistent storage | partly | unassigned | none yet | No RTC: `systemd-timesyncd` sets the clock a few minutes after Wi-Fi is up, and the first-boot release-key problem is fixed (omarchy-mobile #188, closed). Root is on `userdata` behind the read-only guard; marking slot B successful is still undecided ([#252](https://github.com/derekross/omarchy-mobile/issues/252)) | Write a short plan | +| Time, persistent storage | partly | unassigned | none yet | No RTC: `systemd-timesyncd` sets the clock a few minutes after Wi-Fi is up, and the first-boot release-key problem is fixed (omarchy-mobile #188, closed). Root is on `userdata` behind the read-only guard; marking slot B successful is a manual, attended step decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252); from 2026-11-01 to 2026-11-07 a local unit marked slot B on this phone; stopped pending #252, and nothing marks it on the 8 Pro until the boot-LUN guard change and the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)) are in | Write a short plan | | Fingerprint | no (read from the stock device tree, not tested) | unassigned | cheetah [FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md); 9a [FINGERPRINT-PLAN](../tegu/FINGERPRINT-PLAN.md) | What we found: a Goodix under-display sensor as a platform node (the secure world owns its SPI, as on the 7 Pro), IRQ on gpa7, reset on gpp1, its rail always on. Trusty, `persist` and RPMB writes are irreversible and need the human's explicit go | Last, as a proposal | ## Order I would take them in @@ -81,7 +81,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better. - Which microphone id is which hole, and what do the earpiece and headset paths need (#450, #453)? - Why does the phone draw about 0.5 A idle with the screen off, and why did the CPU idle-state and power-domain overlays reboot-loop it? Not known; no measurement plan yet. - In which file shape should the zuma System MMU v9 code and the AoC core port go (asked on #1)? -- Should husky's slot B ever be marked successful (a `devinfo` write)? On the 9a that is on hold; for husky it is [#252](https://github.com/derekross/omarchy-mobile/issues/252), still open. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. +- Marking slot B successful (a `devinfo` write): decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252) (2026-11-07). It is a manual, attended step, once per install of a smoke-tested image, never from a unit, with per-phone layout evidence first. The boot LUNs get the whole-disk node removed and each partition's own flag set first (its own PR, booted on the maintainer's Pixel 7 Pro), then the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)). Until both are in nothing marks slot B on the 8 Pro: flash a known-good set before the boot that would use B's last try, and count every deliberate reset as a boot. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. - Does touch survive a long idle with the screen off? One 12 h idle on 2026-11-04 left only Power working; not reproduced, not cause-checked. ## Credits and sources