Skip to content
Merged
Show file tree
Hide file tree
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: 5 additions & 1 deletion device/cheetah/SUSPEND-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -1617,7 +1617,11 @@ any wake.
- **h: the behaviour passed, but afterwards Hyprland ran neither power-key bind**
(the kernel saw every press; `omamobile-keys`' last-press stopped at the
second press) until `hyprctl reload`. A user would have no Power until a
reboot. Being traced in Hyprland's bind handling.
reboot. **Fixed (2026-11-01, omamobile-shell 0.2.75, #312):** the
on-screen keyboard's virtual keyboard reached the hardware-key binds; they
now exclude it. Derek installed #312 on the phone and re-ran the case
attended: the power key still works after a double press ("all tests
passed").
- **g** logged no "Stay awake is on" line on the power-key request; the
behaviour was right.
- **Wi-Fi drops for each sleep:** the driver stays loaded (the keep flag),
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have
| Modem | WIP (boots; needs a SIM) | S5300 on PCIe at Gen3 x2: the modem boots Google's firmware from RAM copies of its NV to ONLINE (M3.4.5b, M3.4.6), the CP serves the SIT IPC (SIM state, radio state, AT +CFUN; M4.1h) and idles its link as stock does, with NV unchanged across ten minutes of idle cycles (M4.1i). It needs the phone's own board id (`omamobile-modem` 0.1.4). A reboot with the modem up hung once (a DBI access while the PHY was isolated); the fix passed on the phone, and reboots with the modem up are clean (M4.1j, M4.1k, 2026-10-13). `omamobile-mmd` shows the modem to NetworkManager and the phone apps (T1). No SIM has been in the phone yet, so registration, SMS, data and calls (M4.2 on) are untested; the SIM runbook is ready. Open: each modem power-off (so each reboot with the modem up) causes one recovered UFS error-handler pass, so the modem stays on once up | [MODEM-PLAN](../device/cheetah/MODEM-PLAN.md), [MODEM-CLIENT](../device/cheetah/MODEM-CLIENT.md), [MODEM-SIT-RESEARCH](../device/cheetah/MODEM-SIT-RESEARCH.md) |
| 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 | WIP | s2idle works when asked for (`systemctl suspend`, `rtcwake`): `pm_test` dry runs, wakes on a volume key and on the RTC alarm, 20 of 20 unattended cycles (S3b, S4); UFS powers down in suspend by default (`spm_lvl` 5). Wi-Fi stays connected across sleep: 31 of 31 freezes with the D3 handshake (S5b-3, S5c, 2026-10-19), and the sleep hook keeps it loaded. The AoC and sensors work across sleep, and a running sensor stream doesn't wake the phone (S6, 2026-10-19). Screen off, with Wi-Fi up, it draws 434 mA awake and 312 mA in s2idle: about 16 h of standby on the 4986 mAh battery (S7, 2026-10-19), against 32-50 mA in stock's deep sleep. Auto-sleep is in the packages and off by default ([#64](https://github.com/derekross/omarchy-mobile/pull/64), omamobile-shell 0.2.29): with the `omamobile-sleep` toggle on, the phone sleeps 30 s after the screen goes off behind a secure lock and at once on Power, and Power wakes it to the PIN pad; 13 cycles in one boot with 0 failures (P0-P5, 2026-10-26). The toggle stays off until a day of use (P6) and a power-off from Linux (P7) have run; P5 stopped on a speaker trip that turned out not to come from sleep ([NOTES](../device/cheetah/NOTES.md#2026-10-27-the-muted-speakers-were-the-open-loop-coil-estimate-not-sleep-the-static-was-the-boost-converter-the-earpiece-is-the-top-speaker)). Wi-Fi traffic and a USB plug can't wake it, a few RTC cycles wake early on a PMIC interrupt not yet identified, and the modem has never run across a suspend. Deep sleep (SYS_SLEEP), which stock's standby numbers need, is research and not started | [SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) |
| Suspend | WIP | s2idle works when asked for (`systemctl suspend`, `rtcwake`): `pm_test` dry runs, wakes on a volume key and on the RTC alarm, 20 of 20 unattended cycles (S3b, S4); UFS powers down in suspend by default (`spm_lvl` 5). Wi-Fi stays connected across sleep: 31 of 31 freezes with the D3 handshake (S5b-3, S5c, 2026-10-19), and the sleep hook keeps it loaded. The AoC and sensors work across sleep, and a running sensor stream doesn't wake the phone (S6, 2026-10-19). Screen off, with Wi-Fi up, it draws 434 mA awake and 312 mA in s2idle: about 16 h of standby on the 4986 mAh battery (S7, 2026-10-19), against 32-50 mA in stock's deep sleep. Auto-sleep is in the packages and off by default ([#64](https://github.com/derekross/omarchy-mobile/pull/64), omamobile-shell 0.2.29): with the `omamobile-sleep` toggle on, the phone sleeps 30 s after the screen goes off behind a secure lock and at once on Power, and Power wakes it to the PIN pad; 13 cycles in one boot with 0 failures (P0-P5, 2026-10-26). P5 stopped that day on a speaker trip that turned out not to come from sleep ([NOTES](../device/cheetah/NOTES.md#2026-10-27-the-muted-speakers-were-the-open-loop-coil-estimate-not-sleep-the-static-was-the-boost-converter-the-earpiece-is-the-top-speaker)); resumed on 2026-11-01, it passed with 11 suspends and 0 failures, the speakers fine across each sleep. After its power-key test Hyprland ran neither power-key bind until `hyprctl reload`; the on-screen keyboard's virtual keyboard was reaching the hardware-key binds, which now ignore it ([#312](https://github.com/derekross/omarchy-mobile/pull/312), omamobile-shell 0.2.75; re-tested on the phone 2026-11-01, [SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) P5 test h). Still open: NetworkManager drops Wi-Fi for each sleep and reconnects about 5 s after the wake. The toggle stays off by default until a day of use (P6) and a power-off from Linux (P7) have run. Wi-Fi traffic and a USB plug can't wake it, a few RTC cycles wake early on a PMIC interrupt not yet identified, and the modem has never run across a suspend. Deep sleep (SYS_SLEEP), which stock's standby numbers need, is research and not started | [SUSPEND-PLAN](../device/cheetah/SUSPEND-PLAN.md) |
| Fingerprint | works (opt-in) | 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). Opt-in: `omamobile-fp.service` ships disabled, because its first run writes Trusty's secure storage | [FINGERPRINT-PLAN](../device/cheetah/FINGERPRINT-PLAN.md), [FINGERPRINT-RESEARCH](../device/cheetah/FINGERPRINT-RESEARCH.md) |

## Wanted
Expand Down