diff --git a/device/husky/NOTES.md b/device/husky/NOTES.md index 703c9369b..495e30b70 100644 --- a/device/husky/NOTES.md +++ b/device/husky/NOTES.md @@ -10,6 +10,16 @@ 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-13: display, GPU and CPU DVFS on merged `omamobile` + +[Kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (merged 2026-11-10) and [#157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (merged 2026-11-13) booted from `omamobile` itself, at `82f31d3a7` (#158's last commit), on Brett's phone (Samsung UFS 3.1): `7.3.0-rc6-omamobile-push1-g82f31d3a7a35`, the repository's husky config, the pinned clang (`clang-r596125`), `modules-push`, slot B flashed with `bin/omamobile flash`. The initramfs was the one from the 2026-11-01 test set, unchanged (husky packs no modules into it), and `omamobile-device-husky` was 0.1.8, so the kernel was the only change on this boot. Before the flash, slot B's retry count read 2 after one boot, and entering fastboot with `reboot-to bootloader` didn't change it [V]. + +- **CPU DVFS** [V]: cpufreq-dt with schedutil on three policies: CPUs 0-3 up to 1704 MHz, 4-7 up to 1945 MHz and 8 up to 2294 MHz, the battery current limiter's caps, with boost off (the turbo levels unused). The energy model has its three perf domains (`cpu0`, `cpu4`, `cpu8`) and logs no `EM: invalid perf. state`. +- **Thermal** [V]: big 49, mid 50, little 49 and gpu 50 °C at 52 s, idle. +- **GPU** [V]: panthor renders the session; its devfreq idles at 150 MHz. +- **Display** [V]: gs-decon with the HK3 on DSIM0, `card2-DSI-1` connected at 1344x2992. The HK3's one refused brightness write before `allow_tx` (`sending dcs data 51 02 bc failed: -1`) is still there, as on the test trees. 120 Hz was measured on the test tree with the same code (`husky-test-20261109-t1`, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160#issuecomment-6748459836)), not again here. +- **The rest of the boot** [V]: the S2MPG14 RTC registers as `rtc0` ([kernel #243](https://github.com/derekross/linux-omarchy-mobile/pull/243)) and `/sys/power/mem_sleep` reads `[s2idle] deep` ([kernel #244](https://github.com/derekross/linux-omarchy-mobile/pull/244)). `tools/phone-smoke` passes every check: Wi-Fi joins (`wlp1s0`, brcmfmac), Bluetooth powers on, the battery charges. The test trees' `No PKTID available` and `exynos-clkout` probe lines are gone ([kernel #235](https://github.com/derekross/linux-omarchy-mobile/pull/235), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)). The new error-level lines it lists are the BCM4398's Bluetooth ID lines, brcmfmac's `TxCap blob found, loading` and the HK3 write above. + ## 2026-11-09: NFC on the 8 Pro: the pad clock and the controller, two boots on the head of kernel #209 My phone (the Kioxia unit), slot B. Kernel PR [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209) (the `exynos-clkout` match for zuma, plus the `nfc@8` node from #208) was tested at its head, `e9c3fa348` (a8087e225 plus the two optional edits Derek suggested, a DTS comment and a commit message line); the kernel is `7.3.0-rc6-omamobile-push1-ge9c3fa348c8a`, built with my test kernel's config. That head has no HK3 display driver and no PCIe PHY symbol, so these boots had a simple framebuffer, no Wi-Fi and no sound; the phone was driven over USB ssh. Each boot spent one slot B try; the count was refilled to 3 with `fastboot set_active b` before each flash. diff --git a/device/husky/ROADMAP.md b/device/husky/ROADMAP.md index 250187447..7c218f637 100644 --- a/device/husky/ROADMAP.md +++ b/device/husky/ROADMAP.md @@ -1,7 +1,7 @@ # Pixel 8 Pro (husky) roadmap: from "boots" to an everyday phone -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. +Written 2026-10-31 by Lef ([@Somnius](https://github.com/Somnius)). Last updated: 2026-11-13 (the display, GPU, DVFS and Wi-Fi rows; the rest as of 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 [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`. @@ -9,18 +9,18 @@ Facts are marked [V] (checked, with the source) or [I] (an inference, with what 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. -**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 `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)); Wi-Fi (landed 2026-11-09 through kernel #187); the DRM display at 120 Hz (kernel #160, merged 2026-11-10); the GPU, CPU DVFS and the thermal zones (kernel #157 and #158, merged 2026-11-13). Brett's phone booted merged `omamobile` with all of them on 2026-11-13 ([NOTES](NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)). -**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)). +**On test trees only (open PRs):** 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 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. +- **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]. With [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (merged 2026-11-10): 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 on test trees since 2026-11-01, and Brett's booted it from merged `omamobile` on 2026-11-13 ([NOTES](NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)). - **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 (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). +- **Wi-Fi, GPU, CPU DVFS and thermal zones**, merged: Wi-Fi through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) (Brett's [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156) commits), the GPU, DVFS and zones as [#157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#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 on test trees; on Brett's, the same from merged `omamobile` on 2026-11-13: three cpufreq-dt policies at the battery limiter's caps (1704, 1945 and 2294 MHz) with the energy model, the four zones at 49 to 50 °C idle ([NOTES](NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)). - **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 [AOC-PLAN](AOC-PLAN.md) (all open). The AoC core port and the System MMU v9 file are not PRs yet. @@ -33,12 +33,12 @@ 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 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 | +| Display (DRM driver) | works at 120 Hz on [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (merged 2026-11-10); simplefb with the panel size (kernel #154) before it | 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] | The black blink at the DRM master handover; the panel's reset and supplies (the driver runs the HK3 as the bootloader left it) | +| GPU | works on [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) (landed with #158, 2026-11-13) | 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) | 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 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 | +| Wi-Fi | partial: merged through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) (2026-11-09; #156 closed in its favour); no P2P | [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 (fixed by [kernel #235](https://github.com/derekross/linux-omarchy-mobile/pull/235)) ([NOTES](NOTES.md), the #156 thread) | P2P and recovery after a firmware crash ([NOTES](NOTES.md)) | | 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 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 | @@ -50,7 +50,7 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists | 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, and Colin's on `husky-test-20261109-t1`]; omamobile-device-husky 0.1.10 makes systemd's Suspend use `s2idle`, but a test that writes `/sys/power/state` itself must still 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 | +| Thermal, CPU DVFS | works on [kernel #158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (merged 2026-11-13) | 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; before it every core ran at the bootloader's rate. The turbo-mode marks are the 8 Pro's battery limiter caps, so only `zuma-husky.dts` points its CPUs at the tables (the 8a's caps are lower). 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) | 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 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 | @@ -59,10 +59,10 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists A proposal, not a verdict; Brett and Derek know the hardware better. -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). +1. ~~Merge #148, #153, #154~~ (done 2026-10-31 and 2026-11-01), and the battery base (#163, #175, done). Brett's display, GPU, DVFS and Wi-Fi PRs (#160, #157, #158, and #156 through #187) landed 2026-11-09 to 2026-11-13. Next: #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. +3. ~~**Display driver** (Brett)~~: #160 merged 2026-11-10. Open: the short black blink at the DRM master handover. +4. ~~**GPU, DVFS and thermal** (Brett)~~: #157 and #158 merged 2026-11-13. Next: a GPU load with the thermal zone watched, a skin temperature source and cpuidle. 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. @@ -86,7 +86,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better. ## 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 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. +- **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 display (#160), GPU (#157), DVFS (#158) and Wi-Fi (#156) PRs that every test tree here was built on, merged 2026-11-09 to 2026-11-13. 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 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. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 57a62bb42..254a738dd 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; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (Omarchy's Location switch serves fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up; `omamobile-device-tegu`'s boot unit, opt-in ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), starts gnssd with the modem: on 2026-11-03, after a reboot with nothing started by hand, a session through the switch's socket had 133 of 135 GGA sentences fixed, first fix 48 s after the client connected, 18 satellites; on 2026-11-09 the same from the in-tree drivers (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 (omamobile-gnss 0.2.5's start, by hand, the modem link left to cycle) had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); not on by default because the modem isn't (the Modem cell); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | testing (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | 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); two causes are known: dead storage after a wake (the UFS pads came back as plain inputs on about one wake in a hundred; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), in review, re-applies the pin state at resume), and a silent no-wake with C2 entered through s2idle's own path: with C2 disabled for the sleep (#96) or left to the ordinary idle path (#98) the RTC alarm woke the palmtop 300 of 300 times each, then 15 of 15 on the everyday path, twelve of them half-hour auto-sleeps (2026-11-07 and 11-08, [#409](https://github.com/derekross/omarchy-mobile/pull/409)); [#591](https://github.com/derekross/omarchy-mobile/pull/591) is the sleep hook for it; open: on the published kernel, which has no idle states, a sleep still fails to wake now and then: one in 22 on 2026-11-09 (a boot without modules), none in two re-runs of 36, and one in 213 overnight on 2026-11-10 on the newest tip with the fixes, where the console shows the kernel alive and CPU 7 not answering from just after the device suspend ([plan](../device/tegu/SLEEP-PLAN.md) S1, failure 3); the RTC alarm on the published kernel came with [kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10 (a kernel from before it has none, and a sleep there ends only on a key); works once that no-wake is found and fixed and kernel #224 is merged and has run from the published kernel; 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; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | 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 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | works (gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, merged, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (panthor on the Mali-G715 with the ACPM GPU clock and a thermal zone, merged, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | partial (BCM4398 on PCIe, merged through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); no P2P, and reloading after a firmware crash is untested, [NOTES](../device/husky/NOTES.md#2026-10-31-wi-fi)) | 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 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B boots Omarchy's root image from `userdata` with the session and the lock, and a second boot comes up clean, [BRINGUP-M2](../device/akita/BRINGUP-M2.md) gate (e), 2026-11-10; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md)) | testing (UFS at HS-G4 behind the storage guard, Omarchy's image on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206) and the device package and storage plan, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | testing (the GT9895 touchscreen: the PIN pad unlocks by touch, and the shell and on-screen keyboard work by hand, [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (g), 2026-11-11; merged, [kernel #241](https://github.com/derekross/linux-omarchy-mobile/pull/241)) | testing (Power wakes and locks, volume keys; [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (f); merged, [kernel #238](https://github.com/derekross/linux-omarchy-mobile/pull/238)) | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | | 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 |