From 0db66338c975177b613049ca8a64666680b0e16e Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Sun, 1 Nov 2026 09:29:11 -0800 Subject: [PATCH 1/3] DISPLAY-PLAN (panther): D3, gs-decon drives the screen Record D3's changes and runbook and its results on the phone: stage 0 and stage 1 (frame starts at 60.02 Hz), stage 2 first failing on Hyprland's padded 1080-pixel rows and then passing with the fix (1080x2400 at 60 Hz, smooth, no flip timeouts), and DPMS off/on with screen_off 0, 1 and 2, the last putting the panel to sleep and waking it through its cold init, also from the power key's lock. The Pixel 7 row's display cell names gs-decon and links linux-omarchy-mobile#181, which brings the kernel side. Co-Authored-By: Claude Opus 5.5 --- device/panther/DISPLAY-PLAN.md | 181 +++++++++++++++++++++++++++++++-- docs/DEVICES.md | 2 +- 2 files changed, 172 insertions(+), 11 deletions(-) diff --git a/device/panther/DISPLAY-PLAN.md b/device/panther/DISPLAY-PLAN.md index 1ab294d7e..61934c949 100644 --- a/device/panther/DISPLAY-PLAN.md +++ b/device/panther/DISPLAY-PLAN.md @@ -1,7 +1,7 @@ # Pixel 7 (panther) display: DCS brightness, then flip-only KMS -Status (2026-11-01): G1, D1 and D2 passed (kernel: [linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177), in review): the panel driver takes the panel over, and brightness and display off/on work over DCS, including from the shell's slider. device-panther 0.1.4 ships `allow_tx=1`, and at its boots `allow_tx` reads Y with no hand-written option. Next: D3 (flip-only KMS). +Status (2026-11-01): G1, D1, D2 and D3 passed. Brightness and display off/on work over DCS ([linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177), merged), and gs-decon drives the screen: Hyprland flips at 60 Hz, DPMS off stops the frames and puts the panel to sleep, and the panel's cold init wakes it ([linux-omarchy-mobile#181](https://github.com/derekross/linux-omarchy-mobile/pull/181), in review). device-panther 0.1.5 ships `screen_off=2`, and the bring-up file is gone. Next: D4 (90 Hz). Today the Pixel 7 shows the bootloader's framebuffer through simplefb and simpledrm: no brightness control, no screen off, no vsync. The Pixel 7 Pro @@ -121,16 +121,113 @@ shell's brightness slider drives the backlight. ### D3. Flip-only KMS (medium-high risk; staged) -`gs-decon` with the S6E3FC3 modes at 60 Hz, in three stages: -- **Stage 0:** log DECON and DPP0, read-only. -- **Stage 1:** count frame starts. The measured rate should be about 60 Hz. -- **Stage 2:** take the screen over from simpledrm, then test DPMS off/on - and the panel sleep (`screen_off=2`). +**The changes** ([linux-omarchy-mobile#181](https://github.com/derekross/linux-omarchy-mobile/pull/181)): +1. `drm/panel: samsung-s6e3fc3: support sleep and a cold restart from KMS`. + A panel taken over from the bootloader is marked prepared and enabled, + so gs-decon's `drm_panel_disable()`/`unprepare()` reach it. While the + panel is asleep, backlight changes are only recorded, and the panel's + lock covers every command sequence. This mirrors the S6E3HC4 change. +2. `drm: google: gs-dsim-cmd: recognise the Pixel 7's link`. The + bootloader's 60 Hz pair (UNDERRUN_CTRL 0x1cf8, CMD_TE_CTRL1 0x2a82306d, + read in D1) gets no second rate, so gs-decon gets the link and the panel + but never switches the rate. +3. `drm: google: gs-decon: pick the modes by the bootloader's scanout size`. + Each SoC gets a list of mode sets, one per panel, chosen by the size ABL + scans out. gs201 gains the S6E3FC3 P10 at 1080x2400, 60 Hz. +4. `drm: google: gs-decon: scan out padded rows on gs201 too`. It was found + in D3c: buffers allocated for 1080-pixel rows are padded to 64 bytes + (pitch 4352), and gs201 only took the boot pitch (4320). It comes before + the DECON0 enable, so that a bisect never lands on a frozen screen. +5. `arm64: dts: ... gs201-panther: enable DECON0 for gs-decon`. DECON0 + gets a `display_pool` (0x3800000, five 1080x2400 XRGB8888 buffers, below + 4 GiB, reusable) and the boot framebuffer. + +**Kernel D3** = D1 plus that branch. It is built +(`7.3.0-rc6-omamobile-push1-gdc3f0ce5e425`), and D1's image set is kept as +its rollback. + +Without a module option, gs-decon goes straight to stage 2 at boot. So the +first boot holds it at stage 0 with a bring-up file on the phone, +`/etc/modprobe.d/omamobile-display-bringup.conf`: +`options gs_decon stage=0`. That file is deleted once D3 passes (AGENTS.md §2). + +#### D3a. Stage 0, read-only (low risk) + +**Before the boot:** +1. Write the bring-up file. +2. `modules-push` D3. +3. Fastboot (Power + Volume Down), then flash D3. The flash puts slot B + back at 3 retries. -Each stage is its own boot or module reload. The plan gets its own -runbook before D3 starts, with a Rollback for each stage: D2's image set -by fastboot, and `gs_decon` blacklisted so that simpledrm keeps the -screen. +**Pass:** +- **0.1.4 at boot:** `allow_tx` reads Y with no hand-written option, and + the slider changes the brightness. +- `gs_decon` binds and logs DECON0 and DPP0 as ABL left them: command + mode, 1080x2400, DPP0 at 0xfac00000. It also logs "link timers for + 60 Hz" from gs-dsim-cmd. +- simpledrm still owns `card0`, and the screen looks as before. + +**Stop if:** "unexpected scanout size", "DPP0 scans …", or a DSIM error. +**Rollback:** stage 0 changes nothing, so keeping the bring-up file is +enough to go on with simpledrm; otherwise flash D1's set by fastboot. + +#### D3b. Stage 1, frame count (low risk) + +On the running D3 kernel: `rmmod gs_decon; modprobe gs_decon stage=1`. + +**Pass:** the frame start and frame done interrupts count at about 60 per +second (the driver's `stats` in sysfs and `/proc/interrupts`), with no +interrupt storm. The screen is unchanged. + +**Stop if:** a storm warning, or the count is far from 60. +**Rollback:** `rmmod gs_decon`. + +#### D3c. Stage 2, KMS (medium-high risk; the screen goes through gs-decon) + +Hyprland runs on simpledrm, and taking its device away at runtime would +end the session. So stage 2 comes with a reboot: +1. Change the bring-up file to `options gs_decon stage=2 screen_off=0`. +2. Push or reboot. Slot B goes from 2 retries to 1. + +**Pass:** +- gs-decon registers its DRM device, and simpledrm goes away (the aperture + is handed over). +- Hyprland and the Omarchy shell come up on gs-decon at 1080x2400, 60 Hz. +- Touch, the brightness slider and animations work, and vblank events + arrive (`modetest` or Hyprland's frame timing). +- There are no flip timeouts. + +**Stop if:** a black or frozen screen, flip timeouts, or Hyprland failing +to start. +**Rollback:** +- over SSH, set the bring-up file back to `stage=0` and reboot; +- or flash D1's set by fastboot. + +USB and SSH don't depend on the screen. + +#### D3d. Screen off (medium risk; the screen turns off and on) + +On D3c, with Hyprland's Lua dispatchers (AGENTS.md: `hl.dsp.dpms({ action += "disable" })`, then `"enable"`): +1. `screen_off=0`: DPMS off sends black frames, and DPMS on shows the + desktop again. +2. `screen_off=1`: DECON stops sending frames while dark. +3. `screen_off=2`: the panel goes to sleep (display off, sleep in, reset) + and wakes through the panel driver's cold init (reset, Google's init at + 60 Hz, TE2, DSC). **That cold init has never run before this step.** + +Announce each step before running it. On a pass of `screen_off=2`, +device-panther ships `options gs_decon screen_off=2`, and the bring-up file +goes. + +**Stop if:** +- the screen stays dark after DPMS on; +- the picture is scrambled after the cold init, which would point to the + DSC or PPS; +- a DSIM timeout. + +**Rollback:** `screen_off=0` (written at runtime) avoids the panel sleep. A +reboot restores ABL's state. ### D4. 90 Hz (medium risk) @@ -210,3 +307,67 @@ installed: - On a later boot, `ls /etc/modprobe.d` listed only `hid_apple.conf` (no hand-made `omamobile-display.conf` hiding the package's file), and `allow_tx` read `Y`. + +### 2026-11-01: D3 + +**D3a, stage 0.** Kernel `7.3.0-rc6-omamobile-push1-gdc3f0ce5e425` (D1 +plus the D3 branch's first four commits), flashed after its modules with +the bring-up file at `stage=0`: +- **0.1.4 at boot:** `allow_tx` read Y with no hand-written option, and the + slider worked. +- **gs-dsim-cmd** logged "link timers for 60 Hz". +- **gs-decon bound** (so the 1080x2400 mode set matched) and logged + GLOBAL_CON 0x133 (command mode), TRIG_CON 0x3061 (TE trigger on), + RDMA_IMG_SIZE and SRC_SIZE 0x09600438 (1080x2400), and DPP0 at + 0xfac00000. +- simpledrm kept `card0`, and the screen was unchanged. + +**D3b, stage 1.** After `rmmod gs_decon; modprobe gs_decon stage=1`: 601 +frame starts and 601 frame dones in 10.0 s, **60.02 Hz**, with no storm. MIF +was at 2028 MHz and DISP at 400 MHz. The screen was unchanged. + +**D3c, stage 2, first try.** The bring-up file was set to `stage=2 +screen_off=0`, then a reboot: +- gs-decon took the screen over: simpledrm went, `card2` is gs-decon, and + it reported "flip-only KMS on DECON0, 1080x2400, up to 60 Hz". +- **Every Hyprland modeset failed with -EINVAL**, and the screen froze on + the boot console's last line. DRM's debugfs showed why: Hyprland's + framebuffers had a pitch of 4352 (1080 pixels padded to 64 bytes), where + gs201's plane check took only the boot pitch, 4320. The Pixel 7 Pro's + 1440-pixel rows (5760 bytes) need no padding. +- **Fix:** gs-decon's fifth commit lets gs201 take padded rows, as G4 does. + DPP0's source width is the row length in pixels, and on gs201 the + source height shares that register. + +**D3c, stage 2, with the fix.** Kernel +`7.3.0-rc6-omamobile-push1-g53fab72d1489`, flashed after its modules: +- Hyprland's modesets all passed, and `hyprctl monitors` showed + 1080x2400@60.00000. +- **The desktop showed, and it was smooth.** In the first ~37 s there were + 162 flips with no timeouts and no late flips, and flip latency averaged + 12.2 ms (16.5 ms at most). Frame start ran at 59.96 Hz. +- 10 minutes later: 2624 flips, still no timeouts (8.9 ms on average). + +**D3d, screen off,** with Hyprland's DPMS dispatcher, each step seen on the +phone: + +| `screen_off` | While off | After DPMS on | +| --- | --- | --- | +| 0 | black frames (frames still counted) | desktop back | +| 1 | no frames (frame_start unchanged over 3 s), trigger masked | desktop back | +| 2 | no frames, trigger masked, **panel asleep** | **panel cold init**, desktop back with the picture correct | + +With `screen_off=2`, the power key's lock turned the screen off, a tap woke +it, and the PIN could be entered. There were no DSIM timeouts, no "cold +init failed" and no gs-decon errors (`dmesg` was cleared before the +`screen_off=2` step). + +**0.1.5 with no bring-up file.** device-panther 0.1.5 was installed on +the phone, the bring-up file deleted, and the phone rebooted on the same +kernel. After the reboot: +- `allow_tx`, `stage` and `screen_off` read Y, 2 and 2 from the package + alone, and gs-decon owned the screen. +- Hyprland ran at 1080x2400@60 (163 flips, no timeouts, frames at + 59.99 Hz), and the desktop was smooth. +- The slider worked. The power key's lock turned the screen off, a tap + turned it on, and the PIN could be entered. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index ab8e931f6..f50ef7112 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -27,7 +27,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | 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 (on the owner's kernel, 2026-11-02: registered on LTE, mobile data over `rmnet0` and texts both ways with `omamobile-modem-sit` 0.3.8 ([#356](https://github.com/derekross/omarchy-mobile/pull/356)); the package doesn't start the modem, CPIF isn't in the published kernel, and calls have no audio route; [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 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 | +| 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 (flip-only KMS through gs-decon at 1080x2400 and 60 Hz, with the panel asleep when the screen is off, on a test kernel, in review, [kernel #181](https://github.com/derekross/linux-omarchy-mobile/pull/181), with `screen_off` in device-panther 0.1.5; brightness and display off/on over DCS through the S6E3FC3 driver, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177), and device-panther 0.1.4; [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 21d9c85a8a1d62f2f062c7c4bae355407ac45f43 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Sun, 1 Nov 2026 09:33:29 -0800 Subject: [PATCH 2/3] device-panther 0.1.5: the screen sleeps with the display off Set gs_decon's screen_off to 2 in the display modprobe.d file, as the Pixel 7 Pro's package does: with the screen off, DECON stops sending frames and the panel goes to sleep, and DPMS on wakes it through the panel driver's cold init. DISPLAY-PLAN gate D3d proved it on the Pixel 7, from Hyprland's DPMS and from the power key's lock. Co-Authored-By: Claude Opus 5.5 --- packages/omamobile-device-panther/PKGBUILD | 2 +- packages/omamobile-device-panther/README.md | 2 +- packages/omamobile-device-panther/test/all | 2 ++ .../vendor/modprobe.d/omamobile-display.conf | 3 +++ 4 files changed, 7 insertions(+), 2 deletions(-) diff --git a/packages/omamobile-device-panther/PKGBUILD b/packages/omamobile-device-panther/PKGBUILD index ed30bf0c6..116b85210 100644 --- a/packages/omamobile-device-panther/PKGBUILD +++ b/packages/omamobile-device-panther/PKGBUILD @@ -3,7 +3,7 @@ pkgname=omamobile-device-panther pkgver=$(cat "${startdir:-.}/version") pkgrel=1 -pkgdesc="Omarchy Mobile support for the Google Pixel 7 (panther): storage guard, USB networking, GPU, haptics, suspend-to-idle, USB after a replug and display brightness" +pkgdesc="Omarchy Mobile support for the Google Pixel 7 (panther): storage guard, USB networking, GPU, haptics, suspend-to-idle, USB after a replug, and the display: brightness and screen off" arch=(aarch64) url="https://github.com/derekross/omarchy-mobile" license=(MIT) diff --git a/packages/omamobile-device-panther/README.md b/packages/omamobile-device-panther/README.md index e375aeaa0..bf758cfbf 100644 --- a/packages/omamobile-device-panther/README.md +++ b/packages/omamobile-device-panther/README.md @@ -10,7 +10,7 @@ Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panthe | `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover | | `bin/omamobile-usb-rescue`, `vendor/systemd/system/omamobile-usb-rescue.service` | `/usr/bin`, `/usr/lib/systemd/system` (enabled for `multi-user.target`) | Brings USB back after a replug: the MAX77759 opens its USB2 data switch on unplug, and with no Type-C driver nothing closes it. While VBUS is valid, puts the switch back to 0x09 on the chip's I2C bus (USI13, which the board file enables). Reads two registers and writes that one; stands aside once a Type-C driver owns the chip. Same script and unit as the Pixel 7 Pro; needs `i2c-tools` | | `vendor/systemd/logind.conf.d/10-omamobile-power-key.conf` | `/usr/lib/systemd/logind.conf.d` | A short power press does not power the phone off. Same drop-in as the Pixel 7 Pro. The long press stays the PMIC reset | -| `vendor/modprobe.d/omamobile-display.conf` | `/usr/lib/modprobe.d` | Lets `gs_dsim_cmd` send DCS packets to the panel (`allow_tx=1`), so the panel driver can set the brightness and turn the display off and on. The driver ships with sending off; brightness passed DISPLAY-PLAN gate D2 on the Pixel 7 | +| `vendor/modprobe.d/omamobile-display.conf` | `/usr/lib/modprobe.d` | Lets `gs_dsim_cmd` send DCS packets to the panel (`allow_tx=1`), so the panel driver can set the brightness and turn the display off and on; the driver ships with sending off. With the screen off, `gs_decon` stops DECON's frames and puts the panel to sleep (`screen_off=2`), and wakes it through the panel's cold init. DISPLAY-PLAN gates D2 and D3d on the Pixel 7 | | `vendor/systemd/sleep.conf.d/10-omamobile.conf` | `/usr/lib/systemd/sleep.conf.d` | Suspend means suspend-to-idle: the kernel offers `deep`, but Linux has no gs201 sleep sequence, and the phone doesn't wake from it. No hibernation. Same drop-in as the Pixel 7 Pro | | `vendor/NetworkManager/conf.d/10-omamobile-usb.conf` | `/usr/lib/NetworkManager/conf.d` | Keeps NetworkManager off that link | | `etc/omamobile-mirrorlist` | `/etc/pacman.d/omamobile-mirrorlist` | Where pacman finds the `[omamobile]` repository. Same file as the Pixel 7 Pro package | diff --git a/packages/omamobile-device-panther/test/all b/packages/omamobile-device-panther/test/all index 338880eb3..c106a69a3 100755 --- a/packages/omamobile-device-panther/test/all +++ b/packages/omamobile-device-panther/test/all @@ -112,6 +112,8 @@ grep -q '^MemorySleepMode=s2idle$' "$tmp/root/usr/lib/systemd/sleep.conf.d/10-om || fail "suspend must be s2idle: gs201 never wakes from deep" grep -qx 'options gs_dsim_cmd allow_tx=1' "$tmp/root/usr/lib/modprobe.d/omamobile-display.conf" \ || fail "the DSI command host may send to the panel (brightness)" +grep -qx 'options gs_decon screen_off=2' "$tmp/root/usr/lib/modprobe.d/omamobile-display.conf" \ + || fail "screen off stops DECON's frames and sleeps the panel" [[ -x $tmp/root/usr/bin/omamobile-usb-rescue ]] || fail "omamobile-usb-rescue is executable" [[ $(readlink "$tmp/root/usr/lib/systemd/system/multi-user.target.wants/omamobile-usb-rescue.service") == ../omamobile-usb-rescue.service ]] \ || fail "omamobile-usb-rescue starts at boot" diff --git a/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf index 0fbfc998d..c1a289b02 100644 --- a/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf +++ b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf @@ -3,3 +3,6 @@ # display off/on. Off by default in the driver; proven on the Pixel 7 in # device/panther/DISPLAY-PLAN.md gate D2. options gs_dsim_cmd allow_tx=1 +# Screen off sleeps the panel and stops DECON's frames (DISPLAY-PLAN D3d): +# no frames and no memory reads while dark, and the panel in sleep mode. +options gs_decon screen_off=2 From 6bd17467302bc05e608692c2125bf5714cc33d06 Mon Sep 17 00:00:00 2001 From: Alejandro Garcia Date: Tue, 3 Nov 2026 20:41:44 -0800 Subject: [PATCH 3/3] DISPLAY-PLAN (panther): D3 on a second Pixel 7, and device-panther 0.1.7 angelrenefm's unit passed every D3 step on linux-omarchy-mobile#181's head (issue #342), as derekross asked on #181: stage 0 found ABL's state as on the first unit, 60 Hz with no storm, 871 flips with no timeouts, and screen_off=2 six times out of six. The plan records it with his kernel release. The D3a paragraph now says its kernel lacked the padded-row commit, and D3c's that it had all five, for the series' new order. The package ships as 0.1.7: 0.1.6 is omarchy-mobile#396's AVB footers, which merges first. The results keep that the build tested was numbered 0.1.5. Co-Authored-By: Claude Opus 5.5 --- device/panther/DISPLAY-PLAN.md | 25 ++++++++++++++++++----- docs/DEVICES.md | 2 +- packages/omamobile-device-panther/version | 2 +- 3 files changed, 22 insertions(+), 7 deletions(-) diff --git a/device/panther/DISPLAY-PLAN.md b/device/panther/DISPLAY-PLAN.md index 61934c949..518e03e1a 100644 --- a/device/panther/DISPLAY-PLAN.md +++ b/device/panther/DISPLAY-PLAN.md @@ -1,7 +1,7 @@ # Pixel 7 (panther) display: DCS brightness, then flip-only KMS -Status (2026-11-01): G1, D1, D2 and D3 passed. Brightness and display off/on work over DCS ([linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177), merged), and gs-decon drives the screen: Hyprland flips at 60 Hz, DPMS off stops the frames and puts the panel to sleep, and the panel's cold init wakes it ([linux-omarchy-mobile#181](https://github.com/derekross/linux-omarchy-mobile/pull/181), in review). device-panther 0.1.5 ships `screen_off=2`, and the bring-up file is gone. Next: D4 (90 Hz). +Status (2026-11-01): G1, D1, D2 and D3 passed. Brightness and display off/on work over DCS ([linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177), merged), and gs-decon drives the screen: Hyprland flips at 60 Hz, DPMS off stops the frames and puts the panel to sleep, and the panel's cold init wakes it ([linux-omarchy-mobile#181](https://github.com/derekross/linux-omarchy-mobile/pull/181), in review). device-panther 0.1.7 ships `screen_off=2`, and the bring-up file is gone. A second Pixel 7 passed D3 too (2026-11-03). Next: D4 (90 Hz). Today the Pixel 7 shows the bootloader's framebuffer through simplefb and simpledrm: no brightness control, no screen off, no vsync. The Pixel 7 Pro @@ -311,7 +311,8 @@ installed: ### 2026-11-01: D3 **D3a, stage 0.** Kernel `7.3.0-rc6-omamobile-push1-gdc3f0ce5e425` (D1 -plus the D3 branch's first four commits), flashed after its modules with +plus the D3 branch without the padded-row commit, which came out of +D3c), flashed after its modules with the bring-up file at `stage=0`: - **0.1.4 at boot:** `allow_tx` read Y with no hand-written option, and the slider worked. @@ -340,7 +341,7 @@ screen_off=0`, then a reboot: source height shares that register. **D3c, stage 2, with the fix.** Kernel -`7.3.0-rc6-omamobile-push1-g53fab72d1489`, flashed after its modules: +`7.3.0-rc6-omamobile-push1-g53fab72d1489` (all five commits), flashed after its modules: - Hyprland's modesets all passed, and `hyprctl monitors` showed 1080x2400@60.00000. - **The desktop showed, and it was smooth.** In the first ~37 s there were @@ -362,8 +363,8 @@ it, and the PIN could be entered. There were no DSIM timeouts, no "cold init failed" and no gs-decon errors (`dmesg` was cleared before the `screen_off=2` step). -**0.1.5 with no bring-up file.** device-panther 0.1.5 was installed on -the phone, the bring-up file deleted, and the phone rebooted on the same +**The package with no bring-up file.** device-panther, built as 0.1.5 (it +ships as 0.1.7, after 0.1.6's AVB footers), was installed on the phone, the bring-up file deleted, and the phone rebooted on the same kernel. After the reboot: - `allow_tx`, `stage` and `screen_off` read Y, 2 and 2 from the package alone, and gs-decon owned the screen. @@ -371,3 +372,17 @@ kernel. After the reboot: 59.99 Hz), and the desktop was smooth. - The slider worked. The power key's lock turned the screen off, a tap turned it on, and the PIN could be entered. +### 2026-11-03: D3 on a second Pixel 7 + +angelrenefm's unit (issue #342: stock factory unit, `CP3A.261005.002.A1` on both slots), kernel `7.3.0-rc6-omamobile-push1-g0a132eb92793` (linux-omarchy-mobile#181's head), flashed with omarchy-mobile#396's AVB footers. Results from [linux-omarchy-mobile#181](https://github.com/derekross/linux-omarchy-mobile/pull/181): + +| Step | Result | +| --- | --- | +| D3a, stage 0 | pass: "link timers for 60 Hz"; DECON0 and DPP0 as ABL left them (1080x2400, RDMA 0xfac00000, TRIG_CON 0x3061); the panel taken over from the bootloader; simpledrm kept `card0`; `allow_tx` Y; no errors | +| D3b, stage 1 | pass: 601 frame starts and 601 frame dones in 10.01 s (60.1 Hz), no storm | +| D3c, stage 2 | pass: gs-decon on `card2`, simpledrm gone, Hyprland at 1080x2400@60. Over 10 minutes: 871 flips, no timeouts and no late flips, latency 9.0 ms on average (16.7 ms at most). No stripes or tearing | +| D3d, `screen_off` at runtime, DPMS through `hl.dsp.dpms` | 0: frames keep counting while dark. 1: frame start frozen, trigger masked. 2: `panel_asleep` 1 and the panel's TE count frozen while dark; after DPMS on, TE back at 60 Hz. Each time the desktop came back. `screen_off=2` six times out of six, with no DSIM timeouts, no "cold init failed" and nothing in `dmesg` | +| Boot with `stage=2 screen_off=2` from the bring-up file | gs-decon at 60.12 Hz, Hyprland up, no flip timeouts | + +Not checked there: the picture right after the runtime cold inits (that run measured over SSH: counters and `dmesg`). + diff --git a/docs/DEVICES.md b/docs/DEVICES.md index f50ef7112..88a616b88 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -27,7 +27,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | 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 (on the owner's kernel, 2026-11-02: registered on LTE, mobile data over `rmnet0` and texts both ways with `omamobile-modem-sit` 0.3.8 ([#356](https://github.com/derekross/omarchy-mobile/pull/356)); the package doesn't start the modem, CPIF isn't in the published kernel, and calls have no audio route; [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 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 (flip-only KMS through gs-decon at 1080x2400 and 60 Hz, with the panel asleep when the screen is off, on a test kernel, in review, [kernel #181](https://github.com/derekross/linux-omarchy-mobile/pull/181), with `screen_off` in device-panther 0.1.5; brightness and display off/on over DCS through the S6E3FC3 driver, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177), and device-panther 0.1.4; [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 | +| 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 (flip-only KMS through gs-decon at 1080x2400 and 60 Hz, with the panel asleep when the screen is off, on a test kernel, in review, [kernel #181](https://github.com/derekross/linux-omarchy-mobile/pull/181), with `screen_off` in device-panther 0.1.7; brightness and display off/on over DCS through the S6E3FC3 driver, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177), and device-panther 0.1.4; [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/packages/omamobile-device-panther/version b/packages/omamobile-device-panther/version index c946ee616..11808190d 100644 --- a/packages/omamobile-device-panther/version +++ b/packages/omamobile-device-panther/version @@ -1 +1 @@ -0.1.6 +0.1.7