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
2 changes: 1 addition & 1 deletion device/cheetah/FINGERPRINT-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ after. Before storageproxyd the runner makes the read-only copies of
or once the copy or `persist:/ss/0` differs from its recorded hash, and runs
one storage proxy per boot. The reference phone was reinstalled on
2026-11-02 and enrolled again by hand (F19 results, section 7). The
fresh-install checks (F19 T1-T3) haven't run yet.
fresh-install checks (F19 T1-T3) ran on 2026-11-03: a fresh 2026.11.02 install (`7.3.0-rc6-omamobile-g2219cc6cda77`), `tools/phone-provision` from the owner's factory image and a fresh NV backup, omamobile-fingerprint 0.1.15 (after #379's `diffutils` fix; 0.1.13 in the image refused with a false "differs" because `cmp` was missing) started on its own at boot, setup offered "Add a fingerprint", the owner enrolled one and the lock screen unlocks with it.

Earlier status (2026-10-19): **works, opt-in.** F3-F9 (the HAL) and the fprintd
stages through F16b passed on the phone (section 7): the lock screen
Expand Down
30 changes: 29 additions & 1 deletion device/cheetah/MODEM-PLAN.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,23 @@
<!-- SPDX-License-Identifier: MIT -->
# Modem plan (cheetah / gs201): S5300 on PCIe GEN4A_0

Status (2026-10-13): **IPC works: the CP serves SIT (M4.1h passed).**
Status (2026-11-03): **The modem works on the tested network, and the
stack is on by default.** On a Verizon-network SIM: VoLTE calls and texts
both ways through Phone and Messages (omatel-agent through
`omamobile-mmd`), mobile data behind Wi-Fi, IMS registered with the bearers
in stock's order (IMS first on CID 2, the internet on CID 3; #384) and no
carrier manifest, the APNs and the bearer order chosen from the SIM
(`omamobile-modem-sit` 0.3.29, #373), the earpiece at every speaker stage
(`omamobile-audio` 0.5.13, #402), and `omamobile-modem-boot.target` on by
default from `omamobile-device-cheetah` 0.1.43 (M4.6b, B6-B9b passed,
#398). Kernel `7.3.0-rc6-omamobile-g2219cc6cda77`, the release kernel.
Open: suspend with the modem up (section 6.3; the stack holds a sleep
inhibitor), other networks, cpif's `oem_ipc0` "is not opened" lines after
sitd starts (nothing opens the OEM IPC channel), and the UFS error-handler
pass at a modem power-off (M2.6). The day's evidence: [NOTES](NOTES.md),
2026-11-03.

Earlier status (2026-10-13): **IPC works: the CP serves SIT (M4.1h passed).**
The modem boots to ONLINE (M3.4.5b, M3.4.6) and, since M4.1h, answers
SIT requests (no SIM: "SIM card state 0 applications []", radio state 3
= POWER_OFF) and cycles its idle link as stock does, with no UFS handler
Expand Down Expand Up @@ -3005,6 +3021,18 @@ tools/phone-ssh 'sleep 120; systemctl is-active omamobile-modem; journalctl -b -
versions, pass/fail, the modem unit's journal lines (states only), the
tile's text in B8, the UFS handler count. Not the carrier, the number or
any identifier.

**B6-B9b passed (2026-11-03, `7.3.0-rc6-omamobile-g2219cc6cda77`,
`omamobile-modem` 0.1.16, `omamobile-device-cheetah` 0.1.43,
`omamobile-shell` 0.2.100):** the target on through the vendor wants link
only, `omamobile-modem` enabling nothing (B6); the chain up at boot with
no hand (B9: active x4, "CP ONLINE"); a planted stale marker refused once
("ended without a clean stop", the tile "Off after a hang or reset") and
its copy cleared at the next clean stop (B8, B9); a second unclean end
held ("the one automatic retry is used up", "(held)"), cleared by hand,
and the modem up on the boot after (B9b). `ufshcd_err_handler` count 0
in every one of those reboots. B10 and M4.7 aren't recorded here.

### NV overlay: the modem's own NV writes kept per phone (`omamobile-modem` 0.1.15, built offline 2026-11-02)

**Why.** Until 0.1.11 the modem ran on RAM copies of the backup and lost
Expand Down
41 changes: 41 additions & 0 deletions device/cheetah/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,47 @@

Findings from real hardware, newest first. `BRINGUP-M1.md` is the research map written before first boot.

## 2026-11-03: calls and texts through the apps, the SIM configures itself, the earpiece at the loud stage, the stack on by default

Kernel `7.3.0-rc6-omamobile-g2219cc6cda77` (the release kernel);
`omamobile-modem-sit` 0.3.29 (#373), `omamobile-modem` 0.1.16 and
`omamobile-device-cheetah` 0.1.43 (#398), `omamobile-audio` 0.5.13 (#402);
the same Verizon-network SIM as the entry below. The runbook:
[MODEM-PLAN](MODEM-PLAN.md) M4.6b.

- **Calls and texts through the apps** [V]: incoming and outgoing calls and
texts worked through Phone and Messages (omatel-agent through
`omamobile-mmd`), among them the first text from one Omarchy Mobile phone to
another: this 7 Pro to a Pixel 9a.
- **IMS registers with no carrier manifest** [V]: `carrier_manifest` empty,
the modem's 0x4602 unanswered, and IMS registered all the same. The
manifest isn't needed; the entry below still counted it among the things
tried.
- **The SIM configures itself** [V]: sitd 0.3.29 with every key on `auto`
read the SIM once, chose Verizon's values from its overrides (APN
VZWINTERNET, attach none, IMS first on CID 2, the internet on CID 3,
profiles 0/2/3/4) and registered IMS and data, with nothing typed into
`modem-sit.conf`.
- **The earpiece at the loud stage** [V]: stage `c9` with the boost converter
on (657/6 through ASP, the bottom amplifier muted,
`omamobile-earpiece@on.service`) was clean by ear on a VoLTE call, so
`omamobile-audio` 0.5.13 (#402) dropped the refusal that kept the earpiece
off at that stage.
- **The stack on by default** [V]: #398's runbook B6-B9b passed. The vendor
wants link alone turns `omamobile-modem-boot.target` on (`omamobile-modem`
enables nothing); the chain came up at boot; a planted stale marker was
refused once and cleared at the next clean stop; a second unclean end held
("held" in the tile) and was cleared by hand. No `ufshcd_err_handler` pass
in any of those reboots.
- **The Messages agent wasn't enabled on a fresh install.** Fixed: #394
enables it at login (`omamobile-shell` 0.2.97), and omamessages 0.2.2 and
omaphone 0.2.3 (#399) activate it over D-Bus.
- **Open:** the smoke report shows cpif `oem_ipc0` "is not opened" lines
minutes after sitd starts: the modem's OEM IPC channel, which nothing
opens. A follow-up.
- **Gotcha:** `omamobile-update` over ssh as root needs
`OMARCHY_PATH=/usr/share/omarchy` in its environment.

## 2026-11-03: IMS registered and an SMS sent on a Verizon-network SIM, once the bearers took stock's CIDs

Kernel `7.3.0-rc6-omamobile-g2219cc6cda77`, `omamobile-modem-sit` 0.3.24 (#384),
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have
| 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). 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 (starts by default after provisioning; the automatic path is being tested) | 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) |
| 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
Loading