From 50b1faaf78b1b4819cc246be4723e030c04982ce Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Tue, 3 Nov 2026 10:41:35 -0500 Subject: [PATCH 1/2] release notes 2026.11.03, device/cheetah NOTES, MODEM-PLAN: the first release's notes, and the day the modem worked through the apps docs/release-notes/2026.11.03.md is the draft made final for the 2026.11.03 release (kernel-2026.11.01, uname -r 7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install): the header comment gone, every 2026.MM.DD replaced, the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP), and the install paragraph's `` and `` renamed to BACKUP-DIR and FACTORY-IMAGE.zip, which `tools/release tag` would otherwise refuse as placeholders. The modem bullet under "New in the last weeks" now says what works (calls, texts and data on the tested network, the APNs chosen from the SIM), and "Phones already running a development build" says that a provisioned phone's modem stack starts at boot once it has omamobile-device-cheetah 0.1.43, and how to keep it off (systemctl mask omamobile-modem-boot.target). The draft stays for the next release, as its own header says and tools/release expects. device/cheetah/NOTES.md records 2026-11-03 on the reference phone: calls and texts both ways through Phone and Messages (the first text between two Omarchy Mobile phones), IMS registered with no carrier manifest, sitd 0.3.29 choosing the SIM's values on its own, the earpiece clean at stage c9 with the boost converter on, #398's B6-B9b runbook passed with no UFS error-handler pass, the Messages agent fix (#394, #399), the open cpif oem_ipc0 lines, and the OMARCHY_PATH gotcha for omamobile-update over ssh. MODEM-PLAN's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as history, and M4.6b has its result. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --- device/cheetah/MODEM-PLAN.md | 30 ++++++++++- device/cheetah/NOTES.md | 41 +++++++++++++++ docs/release-notes/2026.11.03.md | 87 ++++++++++++++++++++++++++++++++ 3 files changed, 157 insertions(+), 1 deletion(-) create mode 100644 docs/release-notes/2026.11.03.md diff --git a/device/cheetah/MODEM-PLAN.md b/device/cheetah/MODEM-PLAN.md index c6a4e44e5..a5fc61f6f 100644 --- a/device/cheetah/MODEM-PLAN.md +++ b/device/cheetah/MODEM-PLAN.md @@ -1,7 +1,23 @@ # 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 @@ -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 diff --git a/device/cheetah/NOTES.md b/device/cheetah/NOTES.md index 425d74b32..21c4f00d1 100644 --- a/device/cheetah/NOTES.md +++ b/device/cheetah/NOTES.md @@ -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), diff --git a/docs/release-notes/2026.11.03.md b/docs/release-notes/2026.11.03.md new file mode 100644 index 000000000..877b93cbb --- /dev/null +++ b/docs/release-notes/2026.11.03.md @@ -0,0 +1,87 @@ + +# Omarchy Mobile 2026.11.03 (developer preview) + +The first release of Omarchy Mobile: native Omarchy (Arch Linux ARM, Hyprland and Omarchy's own packages) on the Google Pixel 7 Pro, with a mainline Linux kernel and no Android underneath. This is a **developer preview**: it installs and runs as an everyday Linux phone for people comfortable with fastboot, but some hardware is still being worked on (below), installing erases the phone's data, and stock Android stays on slot A as the way back. + +Omarchy Mobile is a community project built on [Omarchy](https://omarchy.org). It is not an official Omarchy or Basecamp product, and it is not affiliated with or endorsed by Google. + +## What's in it + +- **Device:** Google Pixel 7 Pro (`cheetah`, Tensor G2 / gs201). No other phone is part of this release. +- **Kernel:** `kernel-2026.11.01`, linux-omarchy-mobile's `omamobile` branch at `2219cc6cda77` (Linux 7.3-rc6 plus our drivers); `uname -r` is `7.3.0-rc6-omamobile-g2219cc6cda77`. The source is public at that tag before any binary ships. +- **Userspace:** Arch Linux ARM, Omarchy from its stable channel with our pending patches (re-applied after every Omarchy upgrade), and the signed `[omamobile]` repository (pkgs.omamobile.org, stable channel) for the phone shell, Mesa for the Mali-G710, Hyprland, libcamera and the device support packages. +- **Updates:** `omarchy update` on the phone, from the stable channel, kernel included: the kernel is the `linux-omamobile` package, and `omamobile-boot-update`'s pacman hook writes a new one to slot B (it never reboots by itself; the update sheet asks for a restart). Both are in this release's root image, and the release was tested with a kernel update through them before it shipped. + +### Hardware on the Pixel 7 Pro + +From [docs/DEVICES.md](../DEVICES.md) on the release day: + +| Works | Notes | +| --- | --- | +| Boot, storage | Slot B with stock Android kept on slot A; the Arch root on `userdata` behind a read-only guard for every other partition | +| Display | 120 Hz, brightness, the panel sleeps with the screen off | +| GPU | Mali-G710 on Panthor with Mesa, frequency scaling | +| Touch, buttons, haptics, torch | Touchscreen, power and volume keys, vibration through feedbackd, the torch tile | +| Wi-Fi, Bluetooth | Wi-Fi (stays connected across sleep); Bluetooth pairing and A2DP audio (headset calls not yet) | +| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM (#373) (known issues) | +| Battery, charging | Fuel gauge with the stock battery model; charging with a temperature guard | +| Speakers, microphones | Both speakers in stereo under Google's speaker-protection firmware with the phone's own calibration, plus the microphones; at the louder level, a little below stock's maximum volume, on a phone whose speaker firmware is the verified one (today: the factory image cp2a.260705.006); other phones start at a quieter everyday level until their firmware is verified | +| Sensors | Accelerometer (auto-rotate), light, proximity and compass | +| GNSS | Location through GeoClue, with a quick-settings tile | +| NFC | Reads and writes tags; a tag with a link opens it | +| Cameras | Main, ultrawide and front through libcamera; the telephoto at fixed focus | +| Fingerprint | Starts automatically after provisioning: enrollment offered at setup, unlock on the lock screen | +| CPU | Frequency scaling and thermal zones | + +### New in the last weeks + +- **Phone, Contacts and Messages** come in the image: Omarchy Mobile's own apps for the dialpad, call log, favorites and contacts (with import and export), and SMS conversations with drafts and search. With the modem up they place and take calls and send and receive texts (below); without it a call is refused with "No modem is available" and a text you send is kept, marked "Not sent", to retry later. +- **The modem, on by default: calls, texts and mobile data work on the tested network.** Once `tools/phone-provision` has put Google's modem files, your backup's checksums and the phone's board id on the phone, the modem stack starts at every boot on its own (`omamobile-modem-boot.target`: the modem, the radio service, the data fallback and the bridge the apps use). The APNs and the bearer order are chosen from the SIM, read once at boot, so there is nothing to type for a SIM the carrier database knows; a Verizon-network SIM is the one tested end to end (VoLTE calls both ways, texts over IMS, data behind Wi-Fi; known issues below). Nothing starts before provisioning, and the Mobile data tile says why the modem is off when it is (a boot after a hang, a phone not provisioned). +- **Voice input, ready out of the box:** a voice bar on the keyboard with live words as you speak, on-device speech recognition, and a setting for the longest recording. Voxtype and its English speech model (Whisper base.en) come in the image, so dictation works from the first login with no setup step and no download, offline too. +- **Media controls** with album art in the notification shade and on the lock screen. +- **Lock screen:** a glance view (time, date, weather, notifications), the battery level, and a clock that follows the bar's 12/24-hour setting. +- **Fluid home and drawer gestures**, pill gestures, and hiding or showing the keyboard from the home pill. +- **Keyboard:** themed, with an action row in every layout and a language sheet from the globe key. +- **Updates** entry in the app drawer, with an update sheet that shows what's new and the phone's patches. +- **Louder speakers** under the protection firmware, and an earpiece mode for calls. +- **The louder speaker level from the first start, on phones with the verified firmware:** if the speaker-protection firmware `tools/phone-provision` copies from your factory image is the one verified on the reference phone (today that is factory image cp2a.260705.006; Google's files, byte for byte), the speakers run at the louder level right after the install, with no verification step on your phone. The watchdog still checks your phone at its first song (the protection running on your phone's own calibration, plausible coil temperatures) and falls back to the quieter level if anything looks wrong. Phones on other factory images start at the quieter everyday level until their firmware is verified. `omamobile-speaker-protection status` says which. +- **Files** opens folders with a single tap; the file chooser no longer stalls at login. +- **Fingerprint unlock after provisioning:** the phone makes its read-only copies of the calibration and `persist:/ss` itself, and setup offers "Add a fingerprint" after the PIN. +- **Screenshots and images:** tapping a screenshot's notification opens it in a touch image viewer (pinch and double-tap to zoom, swipe to the next, copy, share or delete), which is also the default for every image. + +## Known issues + +- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13). With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot leaves the modem off once (the Mobile data tile says "Off after a hang or reset"; `journalctl -b -1 -u omamobile-modem` has that boot's line) and the boot after starts it again; if that boot ends the same way, the modem stays off (the tile adds "(held)") until `sudo omamobile-modem-start --retry`, and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way). +- **Suspend: works when asked for, auto-sleep off by default.** `systemctl suspend` sleeps and wakes reliably (on a key or the RTC), Wi-Fi stays connected across it, and standby lasts about 16 hours, well short of stock's. Auto-sleep after the screen goes off ships **off**; it can be turned on with `omarchy-toggle omamobile-sleep on`, but it hasn't finished a day-long test. With the modem up the phone doesn't sleep at all (above). Wi-Fi traffic and a USB plug can't wake the phone. +- **Cameras:** basic image quality (no Google ISP or tuning); the telephoto doesn't focus. +- **Bluetooth:** headset calls (HFP) don't work yet. +- **USB-C:** the phone is a USB device only (no host mode or role switch yet); after a replug, `omamobile-usb-rescue` reconnects it. +- **Fingerprint starts once per boot by design:** if it stops, restart the phone. Its first start writes the phone's secure storage (Trusty's area in the RPMB, the same kind of write as an Android factory reset); `persist` and `mfg_data` are only read. Fingers are enrolled again after a reinstall. To keep it off, `sudo systemctl mask omamobile-fp`. +- **Google's firmware is not included** and never will be: after installing, the bundle's `tools/phone-provision` extracts it from your own factory image for your phone (Wi-Fi, Bluetooth, haptics, speakers, cameras). + +## Phones already running a development build + +A phone installed before this release (from the repository, not this bundle) needs two things once before `omarchy update` works again: + +- **The new keyring.** Packages are now signed with the Omarchy Mobile release key, which keyrings before `omamobile-keyring` 20261026 don't know. Until it's installed, pacman refuses the `[omamobile]` repository ("key DDBA4581E0178D33DB69973F7F1041BF47291504 is unknown"). Install it as a local file, which pacman takes without the key: download `omamobile-keyring-20261026-1-any.pkg.tar.zst` from `https://pkgs.omamobile.org/stable/aarch64/` and run `sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -U` on it (Omarchy's update guard otherwise asks you to use `omarchy update`). Then check that `pacman-key --list-keys DDBA4581E0178D33DB69973F7F1041BF47291504` names the Omarchy Mobile Release Key, under the fingerprint at the end of these notes. +- **Hyprland 0.57 together with its libraries.** Arch Linux ARM moved to new Hyprland libraries on 2026-11-02, and the older Hyprland can't be installed next to them. `omarchy update` brings `hyprland` 0.57.0-3.1 (our build, with the DPMS fix) and `omamobile-shell` 0.2.79 in the same update; take both, then restart the phone. Without shell 0.2.79, Hyprland 0.57 draws the shell's transparent layers black (a black home screen). + +The kernel stays as it is: on a development install, `omamobile-boot-update` is off unless `/etc/omamobile/boot-update.conf` says `AUTO_WRITE=yes`, so slot B is still written by `bin/omamobile push`. + +Two things change on their own with the update. **The modem stack now starts at boot:** once the update brings `omamobile-device-cheetah` 0.1.43, a phone that is provisioned (Google's modem files, the backup's checksums and the board id in place) brings the modem, the radio service, the data fallback and the apps' bridge up at every start, as a fresh install does; a phone that isn't provisioned leaves it off. To keep it off, `sudo systemctl mask omamobile-modem-boot.target` (and `unmask` to turn it back on); `disable` doesn't remove the package's link. **Fingerprint starts at boot** too, after provisioning (known issues above); `sudo systemctl mask omamobile-fp` keeps it off. + +## Installing + +Follow [docs/INSTALL.md](../INSTALL.md), step by step. In short: a Pixel 7 Pro with an **unlocked bootloader**, a Linux computer with `fastboot` and the tools INSTALL.md lists, and Google's factory image for `cheetah`. Download the one file `omamobile-cheetah-2026.11.03.tar` with its `.tar.sha256` (and `.tar.sha256.sig`, to check the signature) from `https://pkgs.omamobile.org/releases/cheetah/2026.11.03/`, check it with `sha256sum -c`, unpack it with `tar -xf`, then run `bash install --dry-run` and `bash install` in the unpacked folder. After the first start, back up the phone's radio partitions with the bundle's `bash tools/nv-backup BACKUP-DIR` (INSTALL.md step 6; read-only, keep the backup folder private: it holds your IMEI), then add Google's firmware with `bash tools/phone-provision --nv-backup BACKUP-DIR FACTORY-IMAGE.zip` (INSTALL.md step 7). + +If the installer stops about the bootloader slots, don't work around it: [open an issue](https://github.com/derekross/omarchy-mobile/issues). + +What it writes: slot B's `boot`, `init_boot`, `vendor_boot`, `vendor_kernel_boot` and `dtbo`, and `userdata` (**erased**). It never touches slot A, the bootloader, radio, `persist`, `efs`, `modem`, `devinfo` or `vbmeta`. + +## Going back to stock Android + +Stock Android is still on slot A. In fastboot: `fastboot --set-active=a`, then `fastboot reboot`, and factory-reset Android when it asks (its data was erased by the install). Or flash Google's factory image for `cheetah`. Before you first boot stock again, note that stock's modem stack rewrites `efs`, `persist` and `modem_userdata`; keep your read-only backup of them. + +## Checksums and signatures + +The bundle's `SHA256SUMS` is signed with the Omarchy Mobile release key (`2056 7593 566E EEE2 DD88 6460 8632 C807 5EB9 4673`); its `MANIFEST` and `manifest.json` name the root image and its SHA-256, so the installer checks the root image against the signed record before it contacts the phone. From ad4af5e112794d48da23bf045373641ae4dcd387 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Tue, 3 Nov 2026 10:51:31 -0500 Subject: [PATCH 2/2] release notes 2026.11.03, DEVICES, FINGERPRINT-PLAN: the user-facing recovery, and the fresh-install fingerprint record The notes told a user to run omamobile-modem-start --retry, which isn't on PATH and by hand brings the modem up outside its unit; the recovery is the runbook's (clear the markers, restart). The draft's placeholders take the forms the tag stage accepts. The fingerprint cell records today's fresh-install run (T1-T3) instead of "being tested". Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --- device/cheetah/FINGERPRINT-PLAN.md | 2 +- docs/DEVICES.md | 2 +- docs/release-notes/2026-11-DRAFT.md | 6 +++--- docs/release-notes/2026.11.03.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/device/cheetah/FINGERPRINT-PLAN.md b/device/cheetah/FINGERPRINT-PLAN.md index 4c946241a..224616995 100644 --- a/device/cheetah/FINGERPRINT-PLAN.md +++ b/device/cheetah/FINGERPRINT-PLAN.md @@ -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 diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 2bb09797b..bf8ed50ab 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -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 diff --git a/docs/release-notes/2026-11-DRAFT.md b/docs/release-notes/2026-11-DRAFT.md index 8c4b36be5..47b12c7f3 100644 --- a/docs/release-notes/2026-11-DRAFT.md +++ b/docs/release-notes/2026-11-DRAFT.md @@ -31,7 +31,7 @@ From [docs/DEVICES.md](../DEVICES.md) on the release day: | GPU | Mali-G710 on Panthor with Mesa, frequency scaling | | Touch, buttons, haptics, torch | Touchscreen, power and volume keys, vibration through feedbackd, the torch tile | | Wi-Fi, Bluetooth | Wi-Fi (stays connected across sleep); Bluetooth pairing and A2DP audio (headset calls not yet) | -| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM (#373) (known issues) | +| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM (#373; see Known issues) | | Battery, charging | Fuel gauge with the stock battery model; charging with a temperature guard | | Speakers, microphones | Both speakers in stereo under Google's speaker-protection firmware with the phone's own calibration, plus the microphones; at the louder level, a little below stock's maximum volume, on a phone whose speaker firmware is the verified one (today: the factory image cp2a.260705.006); other phones start at a quieter everyday level until their firmware is verified | | Sensors | Accelerometer (auto-rotate), light, proximity and compass | @@ -59,7 +59,7 @@ From [docs/DEVICES.md](../DEVICES.md) on the release day: ## Known issues -- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13). With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot leaves the modem off once (the Mobile data tile says "Off after a hang or reset"; `journalctl -b -1 -u omamobile-modem` has that boot's line) and the boot after starts it again; if that boot ends the same way, the modem stays off (the tile adds "(held)") until `sudo omamobile-modem-start --retry`, and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way). +- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13). With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot leaves the modem off once (the Mobile data tile says "Off after a hang or reset"; `journalctl -b -1 -u omamobile-modem` has that boot's line) and the boot after starts it again; if that boot ends the same way, the modem stays off (the tile adds "(held)") until the markers are cleared by hand (`sudo rm -f /var/lib/omamobile/modem-up /var/lib/omamobile/modem-up.refused-*`, then restart the phone), and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way). - **Suspend: works when asked for, auto-sleep off by default.** `systemctl suspend` sleeps and wakes reliably (on a key or the RTC), Wi-Fi stays connected across it, and standby lasts about 16 hours, well short of stock's. Auto-sleep after the screen goes off ships **off**; it can be turned on with `omarchy-toggle omamobile-sleep on`, but it hasn't finished a day-long test. With the modem up the phone doesn't sleep at all (above). Wi-Fi traffic and a USB plug can't wake the phone. - **Cameras:** basic image quality (no Google ISP or tuning); the telephoto doesn't focus. - **Bluetooth:** headset calls (HFP) don't work yet. @@ -78,7 +78,7 @@ The kernel stays as it is: on a development install, `omamobile-boot-update` is ## Installing -Follow [docs/INSTALL.md](../INSTALL.md), step by step. In short: a Pixel 7 Pro with an **unlocked bootloader**, a Linux computer with `fastboot` and the tools INSTALL.md lists, and Google's factory image for `cheetah`. Download the one file `omamobile-cheetah-2026.MM.DD.tar` with its `.tar.sha256` (and `.tar.sha256.sig`, to check the signature) from `https://pkgs.omamobile.org/releases/cheetah/2026.MM.DD/`, check it with `sha256sum -c`, unpack it with `tar -xf`, then run `bash install --dry-run` and `bash install` in the unpacked folder. After the first start, back up the phone's radio partitions with the bundle's `bash tools/nv-backup ` (INSTALL.md step 6; read-only, keep the folder private: it holds your IMEI), then add Google's firmware with `bash tools/phone-provision --nv-backup ` (INSTALL.md step 7). +Follow [docs/INSTALL.md](../INSTALL.md), step by step. In short: a Pixel 7 Pro with an **unlocked bootloader**, a Linux computer with `fastboot` and the tools INSTALL.md lists, and Google's factory image for `cheetah`. Download the one file `omamobile-cheetah-2026.MM.DD.tar` with its `.tar.sha256` (and `.tar.sha256.sig`, to check the signature) from `https://pkgs.omamobile.org/releases/cheetah/2026.MM.DD/`, check it with `sha256sum -c`, unpack it with `tar -xf`, then run `bash install --dry-run` and `bash install` in the unpacked folder. After the first start, back up the phone's radio partitions with the bundle's `bash tools/nv-backup BACKUP-DIR` (INSTALL.md step 6; read-only, keep the folder private: it holds your IMEI), then add Google's firmware with `bash tools/phone-provision --nv-backup BACKUP-DIR FACTORY-IMAGE.zip` (INSTALL.md step 7). If the installer stops about the bootloader slots, don't work around it: [open an issue](https://github.com/derekross/omarchy-mobile/issues). diff --git a/docs/release-notes/2026.11.03.md b/docs/release-notes/2026.11.03.md index 877b93cbb..73d69406e 100644 --- a/docs/release-notes/2026.11.03.md +++ b/docs/release-notes/2026.11.03.md @@ -23,7 +23,7 @@ From [docs/DEVICES.md](../DEVICES.md) on the release day: | GPU | Mali-G710 on Panthor with Mesa, frequency scaling | | Touch, buttons, haptics, torch | Touchscreen, power and volume keys, vibration through feedbackd, the torch tile | | Wi-Fi, Bluetooth | Wi-Fi (stays connected across sleep); Bluetooth pairing and A2DP audio (headset calls not yet) | -| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM (#373) (known issues) | +| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM (#373; see Known issues) | | Battery, charging | Fuel gauge with the stock battery model; charging with a temperature guard | | Speakers, microphones | Both speakers in stereo under Google's speaker-protection firmware with the phone's own calibration, plus the microphones; at the louder level, a little below stock's maximum volume, on a phone whose speaker firmware is the verified one (today: the factory image cp2a.260705.006); other phones start at a quieter everyday level until their firmware is verified | | Sensors | Accelerometer (auto-rotate), light, proximity and compass | @@ -51,7 +51,7 @@ From [docs/DEVICES.md](../DEVICES.md) on the release day: ## Known issues -- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13). With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot leaves the modem off once (the Mobile data tile says "Off after a hang or reset"; `journalctl -b -1 -u omamobile-modem` has that boot's line) and the boot after starts it again; if that boot ends the same way, the modem stays off (the tile adds "(held)") until `sudo omamobile-modem-start --retry`, and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way). +- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13). With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot leaves the modem off once (the Mobile data tile says "Off after a hang or reset"; `journalctl -b -1 -u omamobile-modem` has that boot's line) and the boot after starts it again; if that boot ends the same way, the modem stays off (the tile adds "(held)") until the markers are cleared by hand (`sudo rm -f /var/lib/omamobile/modem-up /var/lib/omamobile/modem-up.refused-*`, then restart the phone), and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way). - **Suspend: works when asked for, auto-sleep off by default.** `systemctl suspend` sleeps and wakes reliably (on a key or the RTC), Wi-Fi stays connected across it, and standby lasts about 16 hours, well short of stock's. Auto-sleep after the screen goes off ships **off**; it can be turned on with `omarchy-toggle omamobile-sleep on`, but it hasn't finished a day-long test. With the modem up the phone doesn't sleep at all (above). Wi-Fi traffic and a USB plug can't wake the phone. - **Cameras:** basic image quality (no Google ISP or tuning); the telephoto doesn't focus. - **Bluetooth:** headset calls (HFP) don't work yet.