Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/DEVICES.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
<!-- SPDX-License-Identifier: MIT -->
# Supported devices

The status of each device, as verified on real hardware. Rows in the matrix have merged notes behind them; ports still in review are listed under [Wanted](#wanted) with their issue or pull request. What's still missing and the order we plan to tackle it: [ROADMAP.md](ROADMAP.md). To add a device or update a cell, follow [CONTRIBUTING.md](../CONTRIBUTING.md) §6.4: only claim what you've run on your own phone, and link the notes entry that shows it. Status as of 2026-11-13.
The status of each device, as verified on real hardware. Rows in the matrix have merged notes behind them; ports still in review are listed under [Wanted](#wanted) with their issue or pull request. What's still missing and the order we plan to tackle it: [ROADMAP.md](ROADMAP.md). To add a device or update a cell, follow [CONTRIBUTING.md](../CONTRIBUTING.md) §6.4: only claim what you've run on your own phone, and link the notes entry that shows it. Status as of 2026-11-14.

**Legend:**

Expand All @@ -18,7 +18,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have

| Device | Codename | SoC | Boot | Storage | Display | GPU | Touch | Buttons | USB net | Wi-Fi | Bluetooth | Battery | Charging | Haptics | Torch | GNSS | AoC | Speakers/mics | Sensors | Modem | NFC | Cameras | Suspend | Fingerprint |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Pixel 7 Pro | cheetah | gs201 (Tensor G2) | works | works | works (120 Hz) | works (DVFS) | works | works | works | works | works (audio) | works | works | works | works | works | works | works | works | works (calls, texts and mobile data on a Verizon-network SIM, 2026-11-03; see below) | works | works (telephoto fixed-focus) | testing (s2idle and standby verified; auto-sleep off by default, and with the modem up the phone stays awake; see below) | works |
| Pixel 7 Pro | cheetah | gs201 (Tensor G2) | works | works | works (120 Hz) | works (DVFS) | works | works | works | works | works (audio) | works | works | works | works | works | works | works | works | works (calls, texts and mobile data on a Verizon-network SIM, 2026-11-03; see below) | works | works (telephoto fixed-focus) | partial (auto-sleep on by default, double tap wakes it, about 21 h of standby; with the modem up the phone stays awake until kernel #232 and #556 land; see below) | works |
| Pixel Fold | felix | gs201 (Tensor G2) | WIP ([#3](https://github.com/derekross/omarchy-mobile/issues/3)) | WIP (UFS behind the read-only guard, checked on the phone) | WIP (cover: simplefb console; inner: simpledrm output listed by Hyprland, its splash reserved by [kernel #72](https://github.com/derekross/linux-omarchy-mobile/pull/72); both panels' display triggers set by the descriptor, [#82](https://github.com/derekross/omarchy-mobile/pull/82)) | testing (Panthor; glmark2 on the cover, not up on every image yet; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | WIP (cover: chip id read, no touches yet; the driver's touch reports are merged, [kernel #48](https://github.com/derekross/linux-omarchy-mobile/pull/48), untested on the Fold; [notes](../device/felix/NOTES.md#2026-10-23-cover-touch-id)) | works (volume and power; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | works | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no |
| Pixel 6 Pro ([notes](../device/raven/NOTES.md)) | raven | gs101 (Tensor) | works ([#2](https://github.com/derekross/omarchy-mobile/issues/2)) | works | works (120 Hz through gs-decon and the S6E3HC3 driver; unpublished kernel, `omamobile-gs101-display`, in review as [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116), [plan](../device/raven/DISPLAY-PLAN.md)); the published kernel has the boot console only | partial (Panfrost; frequency scaling over 11 levels, 151 to 762 MHz, and GPU cooling through ACPM, merged, [kernel #189](https://github.com/derekross/linux-omarchy-mobile/pull/189), tested on 2026-11-04 on the published kernel plus [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116) and raven's USB override; [plan](../device/raven/GPU-PLAN.md)) | works ([kernel #8](https://github.com/derekross/linux-omarchy-mobile/pull/8)) | works | works (a NOT FOR MERGE DT change; [plan](../device/raven/USB-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-wifi`; [plan](../device/raven/WIFI-PLAN.md)) | partial ([kernel #6](https://github.com/derekross/linux-omarchy-mobile/pull/6); own address; pairing from the menu and A2DP audio work, crackling while Wi-Fi is busy; the chip came up silent after one of seven clean reboots on 2026-11-03, [#77](https://github.com/derekross/omarchy-mobile/issues/77); [plan](../device/raven/BLUETOOTH-PLAN.md)) | works (the gauge; unpublished kernel) | works (the MAX77759 charger at stock's limits with its temperature guard, loaded at boot by device-raven 0.1.26; a full charge to 100 %; the battery node is in the published kernel, [kernel #112](https://github.com/derekross/linux-omarchy-mobile/pull/112), tested on an unpublished kernel; [plan](../device/raven/USB-PLAN.md#4-charging-the-max77759-charger-ravens-b3-after-cheetahs)) | works (CS40L25A through feedbackd, device-raven 0.1.27, with the phone's own firmware from `tools/extract-vendor-firmware -d raven`; the driver and node are merged, [kernel #114](https://github.com/derekross/linux-omarchy-mobile/pull/114); [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (tested on `omamobile-gs101-torch`; the LED's node is now in the published kernel, [kernel #113](https://github.com/derekross/linux-omarchy-mobile/pull/113), not yet run from it; [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-gnss`; [plan](../device/raven/GNSS-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md)) | works (both speakers through raven's protection firmware with the phone's factory calibration, at cheetah's stage media (737/10), which R6 verified on raven; the microphones with them; unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md#r6-ravens-own-speaker-limits-2026-10-27-gb3d6253b0d61-omamobile-audio-044)) | works (accelerometer, light, proximity, compass through the AoC; unpublished kernel) | WIP (calls, texts and data on an unpublished kernel, `omamobile-gs101-cpif`; the package doesn't enable it; [plan](../device/raven/MODEM-PLAN.md)) | no | no | testing (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; Power wakes it, 3 of 3 on 2026-11-03 on an unpublished kernel (the published one plus [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116) and raven's USB override); UFS resumes clean with [kernel #188](https://github.com/derekross/linux-omarchy-mobile/pull/188), merged; with the modem up its sleep block holds; [plan](../device/raven/SUSPEND-PLAN.md)) | no |
| Pixel 7a ([notes](../device/lynx/NOTES.md)) | lynx | gs201 (Tensor G2) | WIP ([#36](https://github.com/derekross/omarchy-mobile/issues/36): Arch root on `userdata` from slot B, SSH; the device package marks the slot successful) | WIP (UFS behind the read-only guard, in the published kernel, [kernel #91](https://github.com/derekross/linux-omarchy-mobile/pull/91); [notes](../device/lynx/NOTES.md#2026-10-24-on-screen-console-and-ufs)) | WIP (simpledrm console only, [notes](../device/lynx/NOTES.md)) | no | WIP (GT9895 touches in the session, in the published kernel, [kernel #93](https://github.com/derekross/linux-omarchy-mobile/pull/93); [notes](../device/lynx/NOTES.md#2026-10-24-touchscreen-rtc-and-slot-retries)) | no | works | no (parked at the chip's boot ROM; [plan](../device/lynx/WIFI-PLAN.md)) | WIP (same chip as Wi-Fi; scans through its own UART; the device tree is merged, [kernel #98](https://github.com/derekross/linux-omarchy-mobile/pull/98), and the package side is in review, [#98](https://github.com/derekross/omarchy-mobile/pull/98); [plan](../device/lynx/WIFI-PLAN.md)) | no | no | no | no | no | no | no | no | no | no | no | no | no |
Expand Down Expand Up @@ -57,7 +57,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have
| Modem | works | Calls, texts and mobile data on Verizon's network since 2026-11-03 (a Tracfone SIM; VoLTE and SMS over IMS; registration 3 s after radio on; data as a fallback route behind Wi-Fi). What made it: stock's bearer order (IMS first on CID 2, the internet on CID 3, CID 1 left to the attach), and the earpiece through the protection service's earpiece mode; the carrier manifest turned out not to be needed. Today: the stack starts at boot by default (`omamobile-modem-boot.target`, enabled by `omamobile-device-cheetah` 0.1.43; the modem unit is skipped until `tools/phone-provision` has run, and a boot after a hang with the modem up leaves it off once, then holds until a clean reboot), the APNs and the bearer order come from the SIM's carrier (`omamobile-modem-sit` 0.3.29, #373, with a Mobile network settings page for anything else), the earpiece works at every speaker stage (since omamobile-audio 0.5.13 it takes the boost converter as the louder stage leaves it: clean by ear on a VoLTE call at stage `c9`, 2026-11-03), and suspend with the modem up is unqualified (the stack holds a sleep inhibitor). Phone and Messages use it through `omamobile-mmd`. Tested from the Pixel 7 Pro: an SMS each way, a VoLTE call answered on another phone, a call with the earpiece route to voicemail | [MODEM-PLAN](../device/cheetah/MODEM-PLAN.md), [IMS-SHANNON](../device/cheetah/IMS-SHANNON.md), [NOTES](../device/cheetah/NOTES.md#2026-11-03-ims-registered-and-an-sms-sent-on-a-verizon-network-sim-once-the-bearers-took-stocks-cids) |
| NFC | works | ST54J over I2C through st-nci with our plain-NCI link, loaded at boot; neard (patched for empty Type 4 tags) reads and writes tags, and tapping a tag with a web link opens it (`omamobile-nfc-open`): writing a tag and opening its link tested on the phone (N3). Card emulation and the secure element are not used | [RADIOS-CAMERA-PLAN](../device/cheetah/RADIOS-CAMERA-PLAN.md) §3 |
| Cameras | works (telephoto fixed-focus) | Ultrawide (Sony IMX386, D-PHY link 2): works end to end through our CSIS/WDMA driver and libcamera's software ISP (CAM5), basic quality (no Google ISP or tuning); a libcamera build with autofocus and low-light patches is installed, not yet evaluated (CAM5.3). Front (Samsung S5K3J1, D-PHY link 0): real images, raw and through libcamera (`cam -c1`, 30 fps, no WDMA errors; F.5-F.7, 2026-10-13). Main (Samsung S5KGN1, C-PHY link 1): 2016x1136 at 30 fps through libcamera with no WDMA errors. Telephoto (S5KGM5, C-PHY): 26 fps through libcamera, colour bars correct; its lens (SEM1215) isn't driven yet, so it stays at its resting focus: distant subjects are sharp (outdoors, 2026-10-26), close ones soft, and tap to focus does nothing. The CSIS write DMA (not the link) loses lines that arrive faster than about 400 MB/s within a line, so the sensors lengthen their lines to stay under `samsung,max-line-throughput` (360 in cheetah's DT for the main, telephoto and front cameras; the front's full 3840x2736 mode runs at 26 fps). The ultrawide (imx386) follows the same rule, so its full 4032x3016 mode streams (23 fps; one run in several still showed WDMA errors), and with 384 MiB of CMA `cam` without options runs every camera at full size (main 12 MP at 9.4 fps). The telephoto's lens (SEM1215) answers on a 950 kHz bus but holds the bus when driven longer, so the telephoto runs at fixed focus. Sensor and DC-PHY settings come from the user's own camera software (`tools/extract-camera-data`), never shipped. Since omamobile-device-cheetah 0.1.30 the camera modules load after boot (`omamobile-camera.timer`), the DMA-BUF heaps are open to the session (libcamera's software ISP), WirePlumber names them Main, Ultrawide, Telephoto and Front camera (0.1.31). The default camera app is omacam ("Camera", omamobile-apps 0.2.0; [CAMERA-APP-PLAN](CAMERA-APP-PLAN.md)): libcamera directly, zoom across the three back lenses, full-resolution photos. GNOME Snapshot is optional, named "Snapshot", for video until omacam records it; browsers and video calls use the cameras through PipeWire (`pipewire-libcamera`). Picture quality: libcamera 0.7.2-4.21 adds chroma noise reduction and defective pixel correction, and omacam 0.3.3 has Night mode and an HDR chip, bursts of raw frames aligned, merged and finished on the phone (Night: 12 frames in about 4.6 s, Q5.3 on 2026-10-21); single shots are still well below stock's | [CAMERA-PLAN](../device/cheetah/CAMERA-PLAN.md), [CAMERA-QUALITY-PLAN](CAMERA-QUALITY-PLAN.md) |
| Suspend | testing | **Verified on 2026-11-13** ([SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) P6-P8): a 10-hour night in one s2idle sleep with auto-sleep on and the modem off, about 228 mA, so roughly 22 h of standby, woken by Power; a day of use with auto-sleep on (the owner's report). Power off stays off, and an off phone on a charger starts a dark charging-only boot, both on a kernel with [kernel #233](https://github.com/derekross/linux-omarchy-mobile/pull/233) and [#554](https://github.com/derekross/omarchy-mobile/pull/554), not yet released (the release kernel restarts instead of powering off). Double tap wakes a sleeping phone on a kernel with [kernel #248](https://github.com/derekross/linux-omarchy-mobile/pull/248) and [#730](https://github.com/derekross/omarchy-mobile/pull/730), not yet released; on the release kernel only Power wakes it from sleep. **What keeps it from "works":** auto-sleep ships off (`omarchy-toggle omamobile-sleep on`); the fixes above aren't in a kernel release; and with the modem up the phone doesn't sleep at all: the modem holds a sleep inhibitor, because the first sleep test with it up ([kernel #232](https://github.com/derekross/linux-omarchy-mobile/pull/232), [#556](https://github.com/derekross/omarchy-mobile/pull/556), 2026-11-13) slept and woke twice but lost mobile data after a run of refused sleeps. Earlier results: s2idle works when asked for (`systemctl suspend`, `rtcwake`) and from the shell's auto-sleep (Power sleeps and wakes, no lock flash, fingerprint after a wake, alarms wake it); Wi-Fi stays connected across sleep (31 of 31 freezes, S5c), the AoC and sensors work across it (S6); NetworkManager drops Wi-Fi for each sleep and reconnects about 5 s after the wake; Wi-Fi traffic and a USB plug can't wake it; a few RTC cycles wake early on an unidentified PMIC interrupt. Deep sleep (SYS_SLEEP), which stock's standby needs, is research and not started | [SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) |
| Suspend | partial | **On by default since 2026-11-14 on the development channel** (omamobile-shell 0.2.129 turns auto-sleep on once where the device says so; omamobile-device-cheetah 0.1.55; kernel-2026.11.13): the phone sleeps (s2idle) 30 s after the screen goes off behind the lock, a double tap or Power wakes it, a touch that lights nothing lets it sleep again after 5 s. Verified on the reference phone ([SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md), 2026-11-13 and 2026-11-14): a night in one sleep and a day of use, about 230 mA asleep, roughly 21 h of standby; power off stays off (an off phone on a charger starts a dark charging boot); at 3 % battery it powers off cleanly. **The gap:** with the modem up the phone stays awake (the modem holds a sleep inhibitor). Sleep with the modem up passed every step on the reference phone on 2026-11-14 (sleeps, refused sleeps with data busy, a text and a call waking it, audio both ways) on [kernel #232](https://github.com/derekross/linux-omarchy-mobile/pull/232) with its analysis fix and [#556](https://github.com/derekross/omarchy-mobile/pull/556); the cell moves to "works" when both are merged and released. Also: Wi-Fi drops for each sleep and reconnects about 5 s after the wake; Wi-Fi traffic and a USB plug can't wake it; standby is far from stock's days, which needs the SoC's deep sleep (SYS_SLEEP, research, not started) | [SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) |
| Fingerprint | works (starts by default after provisioning; a fresh release install on 2026-11-03, provisioned, started it on its own, setup enrolled a finger and it unlocks) | Google's HAL in a chroot behind a bridge and Trusty's fingerprint TA on our kernel (F3-F9), fprintd with our libfprint driver: enrollment from the shell, and the lock screen unlocks with a finger alongside the PIN pad or password, with the keyboard usable over the lock (F16b). A verify stays open across system sleep, and an enrollment interrupted by sleep fails cleanly (libfprint 1.6, 2026-10-19). From omamobile-fingerprint 0.1.14 it starts by default after provisioning: the runner makes its read-only copies itself, refuses to start when the TDP copy changed, and runs one storage proxy per boot (F19, 2026-11-02; the fresh-install checks T1-T3 are pending) | [FINGERPRINT-PLAN](../device/cheetah/FINGERPRINT-PLAN.md), [FINGERPRINT-RESEARCH](../device/cheetah/FINGERPRINT-RESEARCH.md) |

## Wanted
Expand Down