From 8932755fbab92d06c5632b7b35bdc740a07d80b8 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Sat, 14 Nov 2026 23:57:03 -0500 Subject: [PATCH 1/2] AGENTS, DEVICES: sleep with the modem up is held on the 7 Pro again #791 described sleep with the modem up as on by default on the 7 Pro. #794 took the device's declaration back out after the twenty auto-sleeps on kernel-2026.11.15 lost mobile data, so the AGENTS entry goes back to its earlier wording, with one sentence on what passed and what didn't, and DEVICES' suspend cell and note say the gap is open again. The rule itself is the one from before #791: with the modem up nothing passes the inhibitor except the maintainer's attended test on the charger. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 4 ++-- docs/DEVICES.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 5ac221ce5..ee1b8bf43 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -196,8 +196,8 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **Some unattended RTC cycles wake early on the PMIC interrupt** (2 of 20 in S4, 4 of 31 in S5c, at 13-16 s instead of 30 s). Which PMIC event it is hasn't been read yet; count it, don't treat it as a failed cycle. [SUSPEND-PLAN](device/cheetah/SUSPEND-PLAN.md) S4, S5c - **Volume Up is the one key without an internal pull** (`PUD` 0x0, as on stock), and the first freeze woke 3 s in from it with nobody touching it. It didn't recur in the 51 RTC cycles of S4 and S5c, and it isn't proven to be a false edge; if spurious wakes recur, check gpa8-5's power-down pull before blaming the wake path. - **UFS ran its error handler around modem power changes** (PA LINERESET indications, recovered without a reset). Stock's DT shows no shared rail, clock or pin. M2.5 narrowed it down: power-on and a running link are clean, but every modem power-off is followed by one recovered UFS error-handler pass (a PA LINERESET, no I/O errors or resets). Stock powers the modem off only at shutdown, so the modem stays on once it is up (M2.6 is open), and a reboot with the modem up costs one such pass. Keep modem tests attended, don't power-cycle the modem, and check `dmesg | grep ufshcd_err_handler` after each step. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M2, M2.5, M2.6 -- **Suspend with the modem up is on by default on the 7 Pro, and unqualified on the 9a.** On the Pixel 7 Pro with a kernel carrying linux-omarchy-mobile#232 (kernel-2026.11.15 and later), `omamobile-modem` 0.1.26 and device-cheetah 0.1.57, the modem's sleep inhibitor is skipped and the phone sleeps with the modem up (verified on 2026-11-14: sleeps, refusals with data busy, a text and a call waking the phone). On an older kernel `omamobile-modem-sleep-policy` keeps the inhibitor, and the owner opts out with `/etc/omamobile/modem-suspend-disable`. On every other phone the rest of this entry stands unchanged. The 9a's one try (2026-10-27) also had NFC polling, which alone resets the 9a in s2idle, so the modem's part was unknown. With the sleep fixes (2026-11-09, both link drivers) it neither hung nor reset: CPIF refuses most sleeps (`suspend_cp: abort suspend`, -16, while the CP holds `cp2ap_wakeup`), and the three that were entered woke on the modem within seconds. But one sleep attempt, entered or refused, leaves CPIF unable to reach the CP (`Can't set D0 state`, its command register reading 0xffff) and the phone service timing out until a reboot, while `omamobile-sit status` goes on showing the last state read. So with the modem up nothing passes or goes round its sleep inhibitor (`systemctl suspend -i`, `rtcwake -m`, a write to `/sys/power/state`) except an attended test on the charger that ends in a reboot; on a 7 Pro whose inhibitor holds (an older kernel, the owner's opt-out) that test is the maintainer's. CPIF's PM paths are wake-armed in code; M6 has passed on the 7 Pro only. Keep modem tests on the charger, so upower's critical action doesn't suspend the phone mid-test. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) 6.3 and 7.5, [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) "Suspend with the modem on" -- **Never `systemctl restart omamobile-modem` (or stop and start it) to recover a crashed modem.** An in-place restart left raven's CP in BOOTING, and a bring-up that never reaches ONLINE sets a latch that makes the next boot skip the modem. Reboot instead. If a boot skipped it, remove the latch (`rm /var/lib/omamobile/modem-bringup-started`) and `systemctl start omamobile-modem`; `/usr/lib/omamobile-vendor/omamobile-modem-start --retry` also clears it, but run by hand it brings the modem up outside the unit (a stray `rfsd` in your shell's session). From `omamobile-modem` 0.1.13 there is a second marker, `/var/lib/omamobile/modem-up`, written at ONLINE and removed by the unit's clean stop: a boot that hung or reset with the modem up leaves it. The next boot logs "ended without a clean stop" and, from 0.1.19, starts the modem all the same (0.1.13 to 0.1.18 skipped it for that boot); a second unclean end in a row refuses "(held)" until the markers are removed the same way (cheetah [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6). On the 7 Pro the stack starts at boot by default since device-cheetah 0.1.43 ([MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6b); to keep it off from the next boot, `systemctl mask omamobile-modem-boot.target` (`unmask` turns it back on; `disable` doesn't remove device-cheetah's vendor wants link); it also holds a sleep inhibitor until the reboot, except where sleep with the modem up is on (the entry above). [raven MODEM-PLAN](device/raven/MODEM-PLAN.md) D4. The same on the 9a: after the modem profile has stopped, starting it again in the same boot reset the palmtop silently, a watchdog reset with nothing in pstore (the one try was in the rfsd stage). [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) G3. **From `omamobile-modem` 0.1.10, `omamobile-vendor-chroot modem check` refuses once the profile has started this boot** ("the modem profile already started this boot"), so it is no longer a post-install health check while the modem is up: it is read-only and safe to run, but a refusal means the profile ran, not that anything is wrong. After a reboot it says "preconditions met" again. +- **Suspend with the modem on is held on the 7 Pro, and unqualified on the 9a.** On the 7 Pro it passed M6's attended runbook on 2026-11-14 (kernel-2026.11.15), but twenty auto-sleeps that night lost mobile data from the first timer wake on and it stayed down awake until a reboot, so device-cheetah 0.1.59 no longer declares it verified and the modem's sleep inhibitor holds again ([SUSPEND-PLAN](device/cheetah/SUSPEND-PLAN.md)). The 9a's one try (2026-10-27) also had NFC polling, which alone resets the 9a in s2idle, so the modem's part was unknown. With the sleep fixes (2026-11-09, both link drivers) it neither hung nor reset: CPIF refuses most sleeps (`suspend_cp: abort suspend`, -16, while the CP holds `cp2ap_wakeup`), and the three that were entered woke on the modem within seconds. But one sleep attempt, entered or refused, leaves CPIF unable to reach the CP (`Can't set D0 state`, its command register reading 0xffff) and the phone service timing out until a reboot, while `omamobile-sit status` goes on showing the last state read. So with the modem up nothing passes or goes round its sleep inhibitor (`systemctl suspend -i`, `rtcwake -m`, a write to `/sys/power/state`) except an attended test on the charger that ends in a reboot; on the 7 Pro that test is the maintainer's. CPIF's PM paths are wake-armed in code; on the 7 Pro M6's runbook passed and its long check did not. Keep modem tests on the charger, so upower's critical action doesn't suspend the phone mid-test. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) 6.3, [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) "Suspend with the modem on" +- **Never `systemctl restart omamobile-modem` (or stop and start it) to recover a crashed modem.** An in-place restart left raven's CP in BOOTING, and a bring-up that never reaches ONLINE sets a latch that makes the next boot skip the modem. Reboot instead. If a boot skipped it, remove the latch (`rm /var/lib/omamobile/modem-bringup-started`) and `systemctl start omamobile-modem`; `/usr/lib/omamobile-vendor/omamobile-modem-start --retry` also clears it, but run by hand it brings the modem up outside the unit (a stray `rfsd` in your shell's session). From `omamobile-modem` 0.1.13 there is a second marker, `/var/lib/omamobile/modem-up`, written at ONLINE and removed by the unit's clean stop: a boot that hung or reset with the modem up leaves it. The next boot logs "ended without a clean stop" and, from 0.1.19, starts the modem all the same (0.1.13 to 0.1.18 skipped it for that boot); a second unclean end in a row refuses "(held)" until the markers are removed the same way (cheetah [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6). On the 7 Pro the stack starts at boot by default since device-cheetah 0.1.43 ([MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6b); to keep it off from the next boot, `systemctl mask omamobile-modem-boot.target` (`unmask` turns it back on; `disable` doesn't remove device-cheetah's vendor wants link); it also holds a sleep inhibitor until the reboot. [raven MODEM-PLAN](device/raven/MODEM-PLAN.md) D4. The same on the 9a: after the modem profile has stopped, starting it again in the same boot reset the palmtop silently, a watchdog reset with nothing in pstore (the one try was in the rfsd stage). [tegu MODEM-PLAN](device/tegu/MODEM-PLAN.md) G3. **From `omamobile-modem` 0.1.10, `omamobile-vendor-chroot modem check` refuses once the profile has started this boot** ("the modem profile already started this boot"), so it is no longer a post-install health check while the modem is up: it is read-only and safe to run, but a refusal means the profile ran, not that anything is wrong. After a reboot it says "preconditions met" again. - **Linux never writes the modem's NV partitions.** The modem chroot profile (cbd, rfsd) refuses to start unless the NV partitions read `ro=1` and none is mounted, and works on checksum-verified RAM copies only. What the modem writes is lost at stop, except its writes to `efs/nv_normal.bin` (expected to hold the carrier profile, network and IMS data; the runbook confirms it) when the NV overlay is on (section 1): those are captured every 30 minutes and at the unit's stop, after the CP is off, and laid over the verified copy at the next start. `reboot-to` (and `bin/omamobile push`) skips that stop, so stop the modem first (section 2) or run `omamobile-modem nv-overlay capture`. Don't give the chroot a real block device. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) "NV overlay" ### USB diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 6bdb4320b..f14afce2c 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -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) | 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-2026.11.15 and omamobile-modem 0.1.26 with device-cheetah 0.1.57 are released; 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: the long check of sleep with the modem up lost mobile data; 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 | WIP (one guarded AoC-first scan, association/DHCP and HTTPS test on a local kernel; startup remains manual; [notes](../device/lynx/NOTES.md#2026-11-13-aoc-first-wi-fi-scan-and-one-guarded-traffic-test)) | 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 | @@ -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 passed every step of MODEM-PLAN M6 on the reference phone on 2026-11-14 (sleeps, refused sleeps with data busy, a text and a call waking it): from `omamobile-modem` 0.1.26 and `omamobile-device-cheetah` 0.1.57 it is on by default on a kernel with [kernel #232](https://github.com/derekross/linux-omarchy-mobile/pull/232) (kernel-2026.11.15 and later; on an older kernel the stack keeps its sleep inhibitor, and `/etc/omamobile/modem-suspend-disable` keeps it by the owner's choice). 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 | 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 on the released kernel (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 early refusal, merged; the gap closes with kernel-2026.11.15 and omamobile-modem 0.1.26, omamobile-modem-sit 0.3.40 and omamobile-device-cheetah 0.1.57, which turn it on by default on a kernel with that refusal ([MODEM-PLAN](../device/cheetah/MODEM-PLAN.md) 7.5; the owner can opt out). The cell moves to "works" once those are released and checked on the phone after Updates. 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) | +| 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 on the released kernel (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 early refusal, merged; but twenty auto-sleeps that night on kernel-2026.11.15 with omamobile-modem 0.1.26 and device-cheetah 0.1.58 lost mobile data from the first timer wake on (it stayed down awake until a reboot), so device-cheetah 0.1.59 holds it again and the modem's inhibitor keeps the phone awake. The cause is open; the next check logs the routes and data after every wake. The cell moves to "works" once sleep with the modem up passes that check. 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 From f10740be47fc88d2604d08dc74915c1939c8b9bd Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Sat, 14 Nov 2026 23:58:34 -0500 Subject: [PATCH 2/2] DEVICES: the Modem row says the modem-up sleep is held again too Co-Authored-By: Claude Opus 5.5 --- docs/DEVICES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DEVICES.md b/docs/DEVICES.md index f14afce2c..03b3b8445 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -54,7 +54,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | AoC | works | The audio and sensor DSP starts at boot (`omamobile-aoc.service`) through the GSA and Trusty, with 82 services; sensors and the sound card use it | [AOC-PLAN](../device/cheetah/AOC-PLAN.md) | | Speakers/mics | works | Through the AoC sound card and PipeWire (`omamobile-audio`): "Built-in Audio Speaker" (both speakers in stereo, stock channel map) and "Built-in Audio Microphone", the volume keys and quick settings. The amplifiers run Google's speaker protection firmware with the phone's factory calibration, and a watchdog mutes them on any fault. Since C9j (2026-10-27, omamobile-audio 0.5.3-0.5.4) both speakers play clean and loud: the amplifiers' boost converter is off at the everyday level (stage `media`, digital 737, analog 10), which removed the static under music, and the speaker filter is flat with 6 dB of limiter drive, which brings streamed music up while the limiters hold peaks at -3 dBFS. Since omamobile-audio 0.5.8 (2026-10-31) the default is louder on a phone with verified protection: digital 817 on both, analog 14 bottom and 11 top, with the protection firmware measuring the coils as they play (3.5 minutes of loud music held both at 60-65 °C, under the 80 °C backstop). Stock's analog 17 on both still trips the coil temperature (C9d-3..6), so the maximum stays a little below stock's. The bottom speaker's static was a word-length bug, fixed in the kernel (C9d-6, 2026-10-13); stock's Waves processing on the AoC (`omamobile-speaker-tuning`, off by default) is research (T3b/T4) | [AOC-PLAN](../device/cheetah/AOC-PLAN.md) C7-C9, [AOC-TUNING-RESEARCH](../device/cheetah/AOC-TUNING-RESEARCH.md), [AUDIO-PLAN](../device/cheetah/AUDIO-PLAN.md) | | Sensors | works | `omamobile-sensors`: an iio-sensor-proxy D-Bus service from the AoC's USF, started at boot. Accelerometer, light, proximity and compass at every boot (the sensor rails are power-cycled before the AoC starts); auto-rotate, switched from the rotation lock tile | [AOC-PLAN](../device/cheetah/AOC-PLAN.md) C6, [USF-PROTOCOL](../device/cheetah/USF-PROTOCOL.md) | -| 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 passed every step of MODEM-PLAN M6 on the reference phone on 2026-11-14 (sleeps, refused sleeps with data busy, a text and a call waking it): from `omamobile-modem` 0.1.26 and `omamobile-device-cheetah` 0.1.57 it is on by default on a kernel with [kernel #232](https://github.com/derekross/linux-omarchy-mobile/pull/232) (kernel-2026.11.15 and later; on an older kernel the stack keeps its sleep inhibitor, and `/etc/omamobile/modem-suspend-disable` keeps it by the owner's choice). 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) | +| 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 passed every step of MODEM-PLAN M6 on the reference phone on 2026-11-14 (sleeps, refused sleeps with data busy, a text and a call waking it), but twenty auto-sleeps that night lost mobile data, so since `omamobile-device-cheetah` 0.1.59 the stack holds its sleep inhibitor again (see Suspend). 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 | 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 on the released kernel (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 early refusal, merged; but twenty auto-sleeps that night on kernel-2026.11.15 with omamobile-modem 0.1.26 and device-cheetah 0.1.58 lost mobile data from the first timer wake on (it stayed down awake until a reboot), so device-cheetah 0.1.59 holds it again and the modem's inhibitor keeps the phone awake. The cause is open; the next check logs the routes and data after every wake. The cell moves to "works" once sleep with the modem up passes that check. 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) |