diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml index 405ef3d6d..4c783e778 100644 --- a/.github/workflows/checks.yml +++ b/.github/workflows/checks.yml @@ -45,9 +45,9 @@ jobs: steps: - name: Packages the tests use run: | - pacman -Syu --noconfirm --needed git base-devel e2fsprogs zstd openssl \ + pacman -Syu --noconfirm --needed git base-devel e2fsprogs zstd lz4 openssl \ python python-dbus python-gobject dbus nodejs dtc cpio file jq busybox \ - xz gzip qt6-declarative shellcheck rsync + xz gzip qt6-declarative qt6-svg shellcheck rsync android-tools # Arch's nodejs can lag a simdjson soname bump: on 2026-10-29 # simdjson 5.0.8 dropped the libsimdjson.so.34 that nodejs still # linked, and node no longer started. Only while node can't start, diff --git a/AGENTS.md b/AGENTS.md index 498c43883..a024081fc 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -58,6 +58,7 @@ Omarchy Mobile runs native Omarchy (Arch Linux ARM, Hyprland, Omarchy's packages This leaves other people's staged and unstaged changes alone. - **Moving a feature from bring-up into a package:** bump the package `version`, enable nothing that isn't hang-safe, and delete the bring-up files from `/etc/modprobe.d` on the phone (`omamobile-*-bringup.conf`, and any hand-copied package file). A file in `/etc/modprobe.d` replaces the package's `/usr/lib/modprobe.d` file of the same name, so a stale `omamobile-aoc.conf` there hid the package's new blacklist. - **Kernel releases change with every push** (`7.3.0-rc6-omamobile-push1-NNNNN-g`). `bin/omamobile push` runs `modules-push` when the tarball's checksum differs. Without its modules a new kernel boots without its drivers, the GPU among them. `modules-push` replaces `/usr/lib/modules/` as a whole; on the 9a that once took a hand-installed panel driver with it, and the display stayed on the boot logo. It now refuses when the folder holds modules added or swapped by hand since the last push (it records what each push installed in `.omamobile-modules.sha256`), and `OMAMOBILE_MODULES_REPLACE=1` overrides that, wiping them. Pin a daily release whose folder carries hand-installed modules (`/usr/lib/modules/.omamobile-pinned`), and keep a copy before overriding (`tar -C /usr/lib/modules -cf … `). +- **Stop the modem before a `push` or a `reboot-to`.** `push` ends in `reboot-to`, a raw reboot syscall that stops no unit, so `omamobile-modem.service` never runs its clean stop and its `modem-up` marker stays. On the 7 Pro, where the modem starts at boot (device-cheetah 0.1.43+), the next boot then skips the modem once ("ended without a clean stop: a hang or a reset"), and a second such end before a clean stop holds it off until `omamobile-modem-start --retry`. This happened on 2026-11-08 after a `reboot-to bootloader` taken to charge a flat battery. So run `systemctl stop omamobile-modem` first, as part of the reboot the human said yes to; a reboot that needs no reason can be `systemctl reboot` instead, which stops it. The stop powers the CP off (one recovered UFS error-handler pass, as any reboot with the modem up costs) and, with the NV overlay on, captures its writes. For now it takes about 40 s and ends as "failed", with the CP's power-off logged as a crash; the marker is still removed ([#532](https://github.com/derekross/omarchy-mobile/issues/532)). This is not the restart the modem notes below forbid: nothing starts the modem again before the reboot. [#403](https://github.com/derekross/omarchy-mobile/pull/403), still open, would let the next boot start the modem after a `reboot-to`; the CP's ordered power-off and the NV capture would still come only from the unit's stop. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6b ## 3. How the tools fit together @@ -125,7 +126,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **ABL picks the base DTB by `soc_id`:** `bin/omamobile images` ships both silicon revisions. It also needs an empty `/ect` node and `/chosen/bootargs`, and applies a DPM overlay that needs label stubs (build with `-@`). - **Pixel 7 Pro: once slot B has booted with AVB footers, it needs them.** A stock install's `vbmeta_b` chains `boot` and `init_boot`. After one boot of #104's footer-carrying images, ABL refused footer-less ones (images built by any tool from before #104, or a saved older image set): it stopped in fastboot or used up B's tries and fell back to stock, whose recovery offered "Try again" or "Factory data reset". Build every image with the current `bin/omamobile`, keep rollback sets built the same way, and on that recovery screen choose neither: hold Volume Down + Power about 20 s for fastboot. A stock boot rewrites `efs`, `persist` and `modem_userdata`, so take a fresh read-only backup after one. [NOTES](device/cheetah/NOTES.md#2026-10-30-the-charger-reads-offline-at-full-and-slot-b-now-needs-its-avb-footers) - **Pixel 9a: a fallback to slot A costs the Linux root.** `fastboot --set-active=b` (which `bin/omamobile flash` runs) clears B's successful flag and gives B three ABL tries. A fastboot flash of slot B's images without `--set-active` clears the flag too: on 2026-10-31, `slot-successful:b` read `yes` before five suffixed flashes and `no` after, and the next boot started with `retry-count` 2 ([tegu NOTES](device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)). Every boot uses one try, and the initramfs USB safety net (no USB host in about 65 s: panic) uses them fast. At zero ABL boots stock on slot A, and stock overwrote `userdata` on 10-28, and most likely on 10-26, before anyone could choose anything in recovery. So: `flash` only a known-good image set, and on the 9a ask the maintainer before any `flash` or fastboot write to slot B, because it unmarks B. Marking B successful is a `devinfo` write, and on the 9a it is on hold until the maintainer decides how it's done: don't mark B, and don't run `omamobile-bootctl` or anything that makes `devinfo` writable. With B marked, try new images with `push`, which doesn't call `--set-active` and leaves the mark alone; ABL then no longer falls back, so a broken pushed image means fastboot by the buttons, and the fastboot recovery leaves B unmarked: from then on every boot spends a try, so keep reboots few and ask the maintainer before marking B. With B unmarked, every boot spends one of the three tries: keep reboots few and don't test new images. [tegu NOTES](device/tegu/NOTES.md#2026-10-26-and-2026-10-28-slot-a-fallbacks-that-cost-userdata); the operation approved on 2026-10-22, now on hold: [NOTES](device/tegu/NOTES.md#approved-b-success-operation-after-layout-review-2026-10-22). -- **`reboot -f` and busybox `reboot` hang:** use `reboot-to ` (`LINUX_REBOOT_CMD_RESTART2`). ABL often ignores the `bootloader` reason anyway. +- **`reboot -f` and busybox `reboot` hang:** use `reboot-to ` (`LINUX_REBOOT_CMD_RESTART2`). ABL often ignores the `bootloader` reason anyway. It stops no unit, so stop the modem first (section 2). - **Reserved memory on gs201 is `#address-cells = <2>`, `#size-cells = <1>`,** so each `reg`/`alloc-ranges` entry is 12 bytes. A 16-byte value is silently ignored, and the pool lands anywhere. The display pool's `alignment` must be two cells too, or `of_reserved_mem` rejects it. `/proc/device-tree` shows the raw property, so it *looks* right. [WIFI-BATTERY-PLAN](device/cheetah/WIFI-BATTERY-PLAN.md) 9.x, [NOTES](device/cheetah/NOTES.md) - **Check every stock `reserved-memory` region against `/proc/iomem`:** five were plain System RAM in our kernel, and firmware writes into them at runtime. - **Don't make a driver depend on device-tree node order.** The AoC sound card numbered its PCMs in DAI link order, and the PCM number is the AoC entry point ID. Rewriting the overlay's node order changed nothing on the phone (`fdtoverlay` in our tree kept the source order), so the card driver now sorts its links by link id itself. [AOC-PLAN](device/cheetah/AOC-PLAN.md) C7d-5 @@ -193,8 +194,8 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **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 on has never run on the 7 Pro, and is unqualified on the 9a**: its one try (2026-10-27) also had NFC polling, which alone resets the 9a in s2idle, so the modem's part is unknown. CPIF's PM paths are wake-armed in code, but M6 is design only and no SIM test has happened (M4.2). 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, and the next boot refuses with "ended without a clean stop" until it is removed the same way (cheetah [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) M4.6). On the 7 Pro the stack at boot is `systemctl enable omamobile-modem-boot.target`, opt-in; 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`) stops no unit, so run `omamobile-modem nv-overlay capture` first, or use `systemctl reboot`. Don't give the chroot a real block device. [MODEM-PLAN](device/cheetah/MODEM-PLAN.md) "NV overlay" +- **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, and the next boot refuses with "ended without a clean stop" until it is 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 @@ -207,6 +208,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **`grep -q` under `set -o pipefail`:** `grep -q` exits early, SIGPIPEs the writer, and the pipeline fails on large input. Use `grep -c … >/dev/null`. - **Omarchy's Chromium launcher splits each line of `chromium-flags.conf` on spaces:** quote a flag whose value has spaces (`"--user-agent=…"`). - **Chromium needs `--force-device-scale-factor` on the phone,** even with the mobile user agent: its window layout won't go below about 500 px and the panel is 480 px wide in logical pixels, so without it the window runs off the right edge. Sites get phone layouts from the user agent. +- **Grok Bot needs it too** (`~/.config/grok-bot-flags.conf`, read by its launcher): it won't lay out narrower than 512 px. `omamobile-setup-user` picks the factor from the panel's mode so the layout is about 578 px wide (0.83 on the 7 Pro, 0.70 on the 9a). - **The screensaver runs in a terminal, so focusing it pops up the on-screen keyboard:** `patches/omarchy/0006-*` turns `org.gnome.desktop.a11y.applications screen-keyboard-enabled` off for the screensaver and back on afterwards (from an EXIT trap in the launcher, since omamobile-omarchy 0.1.9), and `omamobile-osk-guard` (omamobile-shell 0.2.19) turns it back on whenever it is off with no screensaver running. If the keyboard stops appearing, check that key first. - **Vendor chroots:** bootstrap binaries such as `servicemanager` use `/system/bin/bootstrap/linker64` as their interpreter. `extract-vendor-chroot` links it to the runtime APEX linker. Run the chroot by path, without `env chroot`. - **If a shell change doesn't show on a phone, check that `omamobile-setup-user.service` runs at login and that its marker exists.** The user unit re-links every `omamobile.*` plugin into `~/.config/omarchy/plugins/` at each login, so a package update reaches the user; it runs only if `~/.local/state/omarchy/done/omamobile-shell-profile` exists, which firstboot creates. On the 9a, whose user was set up during bring-up, the marker was missing, so the unit was skipped at every login, and two plugin links still pointed at hand copies (`omamobile.quicksettings` at a 2026-10-17 copy with no notification shade, `omamobile.switcher` at a 2026-10-22 copy) while four plugins weren't linked at all. Check with `systemctl --user status omamobile-setup-user` and `ls ~/.local/state/omarchy/done/`. Relink with the script's loop (`for p in /usr/share/omamobile/shell/plugins/omamobile.*; do ln -sfn "$p" ~/.config/omarchy/plugins/"${p##*/}"; done`), not the script: without its markers it would copy the package's `shell.json` over the user's and repeat every other once-only step, such as appending the cursor and keyboard lines to the Hyprland files again. [tegu NOTES](device/tegu/NOTES.md#2026-10-31-and-11-01-leftovers-on-the-palmtop-from-bring-up) @@ -215,7 +217,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - pointer handlers declared directly on a window get no events, so put them on an Item inside it; - Qt 6.12's `QtQuick/Color` shadows Omarchy's `Commons.Color`, so import `qs.Commons as Commons`. - **pacman.conf order on aarch64:** `[omamobile]`, then `[omarchy]`, then Arch Linux ARM's repositories, so our Mesa and Omarchy's builds win. Use `omarchy update`, not `pacman -Syu`: on the phone it hands over to `omamobile-update` (patch 0012), which refuses a wrong order, low battery, another kernel or a bootloader package (`linux-omamobile` passes only when `omamobile-boot-update preflight` does), skips Snapper, the AUR and gum prompts, and holds boot-related migrations ([RELEASES](docs/RELEASES.md) §5.4). -- **Omarchy upgrades overwrite our Omarchy patches;** `omamobile-omarchy`'s pacman hook puts them back (all or nothing, from Omarchy's own files). Edit the series in `packages/omamobile-omarchy/patches` (`patches/omarchy` links there), bump that package's version, and make every patch apply with `--fuzz=0` on the Omarchy the phone runs: `packages/omamobile-omarchy/test/all` applies it to the real aarch64 package. A patch Omarchy has absorbed is reported as upstream: drop it. +- **Omarchy upgrades overwrite our Omarchy patches;** `omamobile-omarchy`'s pacman hook puts them back (all or nothing, from Omarchy's own files). Two families are selected by the installed Omarchy version: today's 4.0.6 phones use `packages/omamobile-omarchy/legacy-4.0.6/`; 4.5 uses `packages/omamobile-omarchy/patches/` (`patches/omarchy` links only to that family). Fixes for today's phones go in `legacy-4.0.6/`, and in `patches/` too when applicable to 4.5. Bump the package version and make the selected family apply with `--fuzz=0` on the Omarchy the phone runs: `packages/omamobile-omarchy/test/all` applies it to the real aarch64 package. A patch Omarchy has absorbed is reported as upstream: drop it. - **`environment.d` can't unset a variable:** `VAR=` with an empty value is a syntax error, and the generator skips the line silently, so the old value stays. Set an explicit value instead (`omamobile-shell` uses `none`). - **GeoClue answers no client until an authorization agent is registered for the caller's user,** and queues the call with no timeout, so every client just times out. `omamobile-gnss` runs GeoClue's demo agent as a user unit; app allow-list entries skip only the agent's question, not the agent. - **Firewall changes** (ufw is on): arm `systemd-run --on-active=90 /usr/bin/ufw disable` first, then check with a fresh SSH connection (`tools/phone-ssh --fresh`). @@ -231,7 +233,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link | `kernel/configs/omamobile.config` | Config fragment on top of arm64 `defconfig`, commented by plan | | `packages/omamobile-device-cheetah` | Boot-success marker, Wi-Fi and AoC start scripts, udev, modprobe and systemd policy | | `packages/omamobile-shell`, `-sensors`, `-gnss`, `-audio`, `-remote` (opt-in, with `wlrctl`), `-fingerprint`, `-modem` (chroot profile), `libfprint`, `neard`, `mesa`, `hyprland`, `omamobile-keyring` | Userspace packages | -| `packages/omamobile-omarchy/patches/` (`patches/omarchy/` links there) | Omarchy changes waiting to land upstream, re-applied after every Omarchy upgrade | +| `packages/omamobile-omarchy/{legacy-4.0.6,patches}/` | Version-selected Omarchy families: current 4.0.6 phone fixes belong in `legacy-4.0.6/`, and also in the 4.5 `patches/` family when applicable; `patches/omarchy/` links only to 4.5 | | `docs/DEVICES.md` | Supported-devices matrix | | `~/omamobile-kernel/linux`, `wt-*`, `out-*` | The kernel clone, its worktrees and build outputs (outside the repo; `~/android/mainline` on older setups) | | `~/android/reference/` | Stock captures and partition backups: private, never committed | diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 43d63d13d..c41462101 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -73,6 +73,12 @@ Keeping stock on slot A is how we avoid bricking phones during development, not - **The initramfs's no-USB-host panic needs a review for the phone.** On an A/B phone it hands over to stock on slot A; on a single-slot phone it would restart into the same image. The device's descriptor and plan say what happens instead (stay up with the screen lit, or reboot into fastboot) before the first boot. - **Everything else in this section still applies:** never relock with a non-stock image, never flash an older factory image, the backup rules, the hang safety nets. +Phones with an entry: + +| Device | Boot partition the installer may write | Fastboot by buttons | Forced restart | +| --- | --- | --- | --- | +| Xiaomi Mi 8 (`dipper`) | `boot` only; stock `dtbo` stays untouched | Power off, then hold Volume Down + Power until FASTBOOT appears. | Hold Power alone for 10 seconds; confirmed to restart into Android under the Omarchy Mobile kernel. | + ### 3.2 The read-only storage guard UFS holds the per-device calibration. The initramfs ([`initramfs/init`](initramfs/init)) guards it before anything else runs: diff --git a/README.md b/README.md index ea6f21975..6719e8692 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ The kernel and boot images come from `bin/omamobile kernel`, `modules`, `initram | `tools/build-packages`, `tools/build-rootfs`, `tools/install-phone`, `tools/phone-provision`, `tools/make-bundle` | The installer: aarch64 packages and the root image built on the laptop, the narrow fastboot installer, per-phone provisioning, release bundles (`rootfs/` holds the image's package lists; `tests/` their tests) | | `tools/` | Staged bring-up and capture tools, on-phone probes, firmware extraction from the user's factory image, package and repository helpers | | `packages/` | pacman packages: `omamobile-shell` (the phone profile for Omarchy's shell), `omamobile-apps` (the mobile apps desktop Omarchy lacks: Camera, Maps, NFC), `omacam` (the camera app, built from its own repository), `omamobile-device-cheetah` (Pixel 7 Pro support), `omamobile-device-felix` (Pixel Fold), `omamobile-sensors` (sensors and auto-rotate through the AoC), `omamobile-gnss` (location on demand), `omamobile-mirror` (the phone's screen and input on a computer over USB, VNC), `omamobile-remote` and a click-patched `wlrctl` (use the phone over ssh from a script or an agent; opt-in, [docs/REMOTE-TESTING.md](docs/REMOTE-TESTING.md)), `omamobile-audio` (PipeWire and speaker protection), `omamobile-speaker-tuning` (stock's speaker tuning, off by default), `omamobile-fingerprint` with a patched `libfprint`, `omamobile-modem` (the modem's vendor chroot profile), `omamobile-modem-sit` (the SIT client daemon; talks to the modem, registration untested), `omamobile-mmd` (ModemManager's D-Bus API in front of it, for GNOME Calls, Chatty and NetworkManager), `neard`, `omamobile-keyring` (the `[omamobile]` repository's signing key), patched `mesa` and `hyprland`. `tools/phone-install-package` builds one on the phone and installs it | -| `patches/omarchy/` | Changes to Omarchy for touch devices, to send upstream (`bridge-*` ones are stopgaps for the phone's older Omarchy); a link to `packages/omamobile-omarchy/patches`, whose pacman hook re-applies them after every Omarchy upgrade | +| `patches/omarchy/` | Changes to Omarchy for touch devices, to send upstream (`bridge-*` stopgaps are retained only in the legacy 4.0.6 family); a link to the 4.5 family in `packages/omamobile-omarchy/patches/`. The installed Omarchy version selects the family: today's 4.0.6 phones use `legacy-4.0.6/`, so fixes go there and also in `patches/` when applicable to 4.5; the pacman hook re-applies the selected family after upgrades | | `bin/lineage-ref` | Builds LineageOS for the phone. Used as a rooted reference Android (M0) and, later, for Waydroid images | | `kernel/configs/` | Our kernel config fragment, merged on top of arm64 `defconfig` | | `device/cheetah/` | Pixel 7 Pro bring-up notes, one plan per subsystem, overlays, the initramfs and the device descriptor (`device.conf`) | diff --git a/bin/omamobile b/bin/omamobile index b43e609ad..16802719c 100755 --- a/bin/omamobile +++ b/bin/omamobile @@ -123,8 +123,8 @@ load_device() { fi done < "$file" case $DEV_BOOT_METHOD in - android-v4|qcom-abl) ;; - *) die "$file: unsupported BOOT_METHOD=$DEV_BOOT_METHOD; this command supports android-v4 and qcom-abl" ;; + android-v4|android-v0|qcom-abl) ;; + *) die "$file: unsupported BOOT_METHOD=$DEV_BOOT_METHOD; this command supports android-v4, android-v0 and qcom-abl" ;; esac [[ $DEV_CODENAME == "$DEVICE" ]] || die "$file: CODENAME=$DEV_CODENAME, expected $DEVICE" # Safety: the guard's allowlist may name slot B's boot images and userdata @@ -142,8 +142,31 @@ load_device() { seen_rw+="$p " done [[ $seen_rw == *" userdata "* ]] || die "$file: UFS_RW must include userdata" + # Optional: LUNs besides sda that hold UFS_RW partitions; the init guards + # each as it guards sda (whole-disk node removed, partitions one by one) + if [[ -n ${DEV_UFS_RW_LUNS:-} && ! $DEV_UFS_RW_LUNS =~ ^sd[b-z]( sd[b-z])*$ ]]; then + die "$file: UFS_RW_LUNS may hold only disk names sdb to sdz separated by spaces" + fi - if [[ $DEV_BOOT_METHOD == qcom-abl ]]; then + if [[ $DEV_BOOT_METHOD == android-v0 ]]; then + # One header-v0 boot.img: a gzip kernel with the board DTB appended, the + # shared initramfs and CMDLINE, at the load offsets the descriptor gives + # (enchilada). No dtbo, no vendor_boot, no device package needed yet: + # images makes it for `fastboot boot`; flash, push, fastboot and the + # installer refuse it until a slot-B install has a CONTRIBUTING.md §3.1 + # entry. + for key in CODENAME SOC DTB BOOT_IMAGES UFS_RW INITRAMFS_INIT PANEL_SIZE; do + p="DEV_$key" + [[ -n ${!p:-} ]] || die "$file: $key is missing" + done + for key in PAGESIZE BASE KERNEL_OFFSET RAMDISK_OFFSET SECOND_OFFSET TAGS_OFFSET; do + p="DEV_$key" + [[ ${!p:-} =~ ^(0x[0-9a-f]+|[0-9]+)$ ]] || die "$file: $key is missing or not a number" + done + [[ $DEV_PAGESIZE =~ ^(2048|4096|8192|16384)$ ]] || die "$file: PAGESIZE must be 2048, 4096, 8192 or 16384" + [[ $DEV_BOOT_IMAGES == boot ]] || die "$file: android-v0 BOOT_IMAGES may hold only boot" + slot_b_allowed boot || die "$file: boot_b is not in UFS_RW" + elif [[ $DEV_BOOT_METHOD == qcom-abl ]]; then for key in CODENAME SOC PACKAGE DTB BOOT_IMAGES UFS_RW INITRAMFS_INIT PANEL_SIZE; do p="DEV_$key" [[ -n ${!p:-} ]] || die "$file: $key is missing" @@ -540,6 +563,9 @@ initramfs_config() { # The storage guard's allowlist. Without this file the init leaves every # partition read-only. printf '%s\n' "${rw[*]}" > "$etc/omamobile-ufs-rw" + if [[ -n ${DEV_UFS_RW_LUNS:-} ]]; then + printf '%s\n' "$DEV_UFS_RW_LUNS" > "$etc/omamobile-ufs-rw-luns" + fi if [[ -n $product ]]; then printf '%s\n' "$product" > "$etc/omamobile-usb-product" fi @@ -611,10 +637,14 @@ cmd_initramfs() { say "Staging initramfs in $stage" rm -rf "$stage" && mkdir -p "$stage" tar -xzf "$dl/$tarball" -C "$stage" - local apk + # Each package list is read whole before it is used: `for apk in $(…)` + # loses alpine-fetch.py's exit status and unpacks what it printed + local apk apks # e2fsprogs-extra: resize2fs and dumpe2fs, to grow a freshly flashed root # to the whole userdata partition on its first boot (init, boot_arch) - for apk in $(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" dropbear kexec-tools e2fsprogs e2fsprogs-extra); do + apks=$(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" dropbear kexec-tools e2fsprogs e2fsprogs-extra) || + die "tools/alpine-fetch.py failed for the initramfs's packages" + for apk in $apks; do tar -xzf "$apk" -C "$stage" --exclude='.PKGINFO' --exclude='.SIGN.*' --exclude='.*.sh' 2>/dev/null || true done # INITRAMFS_I2C_TOOLS=1: i2cget and i2cset (and their libi2c) for a device @@ -623,7 +653,9 @@ cmd_initramfs() { if [[ ${DEV_INITRAMFS_I2C_TOOLS:-} == 1 ]]; then local i2c f i2c=$(mktemp -d) - for apk in $(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" i2c-tools); do + apks=$(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" i2c-tools) || + { rm -rf "$i2c"; die "INITRAMFS_I2C_TOOLS: tools/alpine-fetch.py failed for i2c-tools"; } + for apk in $apks; do tar -xzf "$apk" -C "$i2c" --exclude='.PKGINFO' --exclude='.SIGN.*' --exclude='.*.sh' 2>/dev/null || true done for f in usr/sbin/i2cget usr/sbin/i2cset; do @@ -686,11 +718,13 @@ cmd_initramfs() { # sysroot is already in use, otherwise the host clang against the same # musl sysroot. A first-light device has no bootctl. alpine_sysroot() { - local sysroot="$WORK/downloads/alpine/sysroot" apk + local sysroot="$WORK/downloads/alpine/sysroot" apk apks if [[ ! -f $sysroot/usr/lib/crt1.o ]]; then mkdir -p "$sysroot" tar -xzf "$dl/$tarball" -C "$sysroot" - for apk in $(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" musl-dev); do + apks=$(python3 -I "$ROOT/tools/alpine-fetch.py" "$ver" "$dl/apks" musl-dev) || + die "tools/alpine-fetch.py failed for the musl sysroot's musl-dev" + for apk in $apks; do tar -xzf "$apk" -C "$sysroot" 2>/dev/null || true done fi @@ -781,6 +815,8 @@ cmd_images() { if [[ $DEV_BOOT_METHOD != qcom-abl ]]; then [[ -f $tools/mkbootimg.py ]] || die "no mkbootimg.py in $tools: run tools/fetch-toolchain, or set SRC_DIR to an Android checkout (or MKBOOTIMG_DIR)" + fi + if [[ $DEV_BOOT_METHOD == android-v4 ]]; then [[ -f $MKDTBOIMG ]] || die "no mkdtboimg.py at $MKDTBOIMG: run tools/fetch-toolchain, or set SRC_DIR to an Android checkout (or MKDTBOIMG)" fi @@ -803,6 +839,26 @@ cmd_images() { dtb="$img/$DEV_CODENAME-overlaid.dtb" fi + if [[ $DEV_BOOT_METHOD == android-v0 ]]; then + # This ABL gunzips the kernel and takes the DTB appended to it; the + # ramdisk is the shared initramfs. gzip -n keeps no name or time, so + # the bytes depend only on the inputs. + say "Boot image (header v0, DTB appended to the gzip kernel): $DEV_DTB" + gzip -9 -n -c "$boot/Image" > "$img/Image.gz" + cat "$img/Image.gz" "$dtb" > "$img/Image.gz-dtb" + python3 "$tools/mkbootimg.py" --header_version 0 \ + --kernel "$img/Image.gz-dtb" --ramdisk "$KERNEL_OUT/initramfs.cpio.lz4" \ + --cmdline "${DEV_CMDLINE:-}" --pagesize "$DEV_PAGESIZE" --base "$DEV_BASE" \ + --kernel_offset "$DEV_KERNEL_OFFSET" --ramdisk_offset "$DEV_RAMDISK_OFFSET" \ + --second_offset "$DEV_SECOND_OFFSET" --tags_offset "$DEV_TAGS_OFFSET" \ + --output "$img/boot.img" || die "mkbootimg failed" + rm -f "$img/Image.gz" + printf '%s\n' "$DEV_CODENAME" > "$img/DEVICE" + ls -lh "$img"/*.img + sha256sum "$img/boot.img" + return 0 + fi + say "Kernel: Image.lz4" lz4 -l -9 -f -q "$boot/Image" "$img/Image.lz4" @@ -1058,11 +1114,15 @@ cmd_fastboot() { # Qualcomm ABL panic path is uncharacterized on dodge (sysrq-c fallthrough # when reboot-to bootloader is ignored). Refuse before any phone I/O; use # the buttons instead (see device/$DEVICE/BRINGUP-M1.md). + # android-v0 (enchilada): no slot-B install yet, so a crash here would + # land on whatever the phone's other slot holds; use the buttons. + [[ $DEV_BOOT_METHOD != android-v0 ]] || + die "fastboot refuses BOOT_METHOD=android-v0 (RAM-only: reach fastboot by the buttons, see device/$DEVICE/NOTES.md)" [[ $DEV_BOOT_METHOD != qcom-abl ]] || die "fastboot refuses BOOT_METHOD=qcom-abl (panic path uncharacterized on this ABL; use the buttons — see device/$DEVICE/BRINGUP-M1.md)" in_fastboot && { say "Already in fastboot"; return 0; } for i in $(seq 1 12); do - if adb get-state 2>/dev/null | grep -q device; then + if adb get-state 2>/dev/null | grep -c device >/dev/null; then say "Stock Android: adb reboot bootloader" adb reboot bootloader elif "$ssh" true 2>/dev/null; then @@ -1078,7 +1138,7 @@ cmd_fastboot() { local t for t in $(seq 1 40); do in_fastboot && { say "In fastboot"; return 0; } - adb get-state 2>/dev/null | grep -q device && break + adb get-state 2>/dev/null | grep -c device >/dev/null && break "$ssh" true 2>/dev/null && break sleep 2 done @@ -1093,6 +1153,9 @@ cmd_flash() { # successful and refill retries; the bit-54 mark has no §3.1 entry yet. # Refuse here; day-2 updates use push once that path is viable, and the # installer PR can reopen flash with the rest. + # android-v0: RAM-only until a slot-B install has its §3.1 entry + [[ $DEV_BOOT_METHOD != android-v0 ]] || + die "flash refuses BOOT_METHOD=android-v0 (RAM-only: fastboot boot \$KERNEL_OUT/images/boot.img)" [[ $DEV_BOOT_METHOD != qcom-abl ]] || die "flash refuses BOOT_METHOD=qcom-abl (no in-tree day-2 update path yet; see device/$DEVICE/BRINGUP-M1.md)" images_for_device "$img" @@ -1130,6 +1193,8 @@ cmd_push() { # Same class of refusal as flash: boot_b is on sde here, and there is no # in-tree day-2 rewrite path for qcom-abl yet. Refuse before any phone I/O # (modules-push would otherwise rewrite the running root's modules). + [[ $DEV_BOOT_METHOD != android-v0 ]] || + die "push refuses BOOT_METHOD=android-v0 (RAM-only: fastboot boot \$KERNEL_OUT/images/boot.img)" [[ $DEV_BOOT_METHOD != qcom-abl ]] || die "push refuses BOOT_METHOD=qcom-abl (no in-tree day-2 update path yet; see device/$DEVICE/BRINGUP-M1.md)" images_for_device "$img" diff --git a/device/akita/BRINGUP-M2.md b/device/akita/BRINGUP-M2.md index 555d430f7..4063d509e 100644 --- a/device/akita/BRINGUP-M2.md +++ b/device/akita/BRINGUP-M2.md @@ -1,7 +1,7 @@ # akita M2: storage (UFS behind the guard, then the Arch root) -**Status (2026-11-07):** M2.1-M2.6 are done; M2.7 waits for the signed package. M1 is complete and merged ([BRINGUP-M1](BRINGUP-M1.md)): +**Status (2026-11-08):** M2.1-M2.6 are done and merged (#456); M2.7 waits for the signed package. M1 is complete and merged ([BRINGUP-M1](BRINGUP-M1.md)): - derekross/linux-omarchy-mobile#192 was rebase-merged on 2026-11-05, so its three commits are on `omamobile` under new ids, with the same patches: `cb2cd5e4b` (binding), `c7eb44543` (first light) and `0e2739a92` (framebuffer). - #414 was squash-merged as `905aa91`. @@ -64,7 +64,7 @@ As in [BRINGUP-M1](BRINGUP-M1.md): `R/` is the private stock capture, `L/` our k 2. **The first UFS boot is read-only and stays in the initramfs.** A bring-up overlay, `device/akita/overlays/ufs-probe.dtso`, sets the board's `bootargs` plus `omamobile.ufs-probe omamobile.initramfs`. That gives the probe listing and no hand-over to Arch, so nothing runs on `userdata`. `DTB_OVERLAYS="ufs-probe"` goes in `device.conf` for that build only, and comes out again afterwards. 3. **Nothing writes before the guard.** UFS is built in, so the disks appear before PID 1. In M2.3 they attached at 0.26 s, and `/init` started at 0.28 s. The init's first job is the guard, which flagged every partition by 0.61 s and removed `/dev/sda`. In between, the kernel only reads the partition tables, and nothing is mounted. `UFS_RW` is unchanged since stage 0. 4. **The fresh backup comes from our kernel.** - - `NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b"` and `NV_BACKUP_EXTRA="devinfo"` go in the descriptor, cheetah's values. Then `tools/nv-backup -d akita` copies the radio and calibration partitions read-only over SSH, and its `--check` can later show that nothing on Linux changed them. + - `NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b"` (cheetah's) and `NV_BACKUP_EXTRA="devinfo trusty_persist trusty_userdata"` (husky's since #449) go in the descriptor. M2.4 ran with `devinfo` alone; Trusty's two partitions joined after #456's review. Then `tools/nv-backup -d akita` copies the radio and calibration partitions read-only over SSH. Its `--check` can later show that nothing on Linux changed them, and report when Android has written the extras. - The rest of the stage-0 set is copied the same way, with each partition hashed on the phone and on the laptop. 5. **The device package comes first, in its own PR.** `omamobile-device-akita` starts with husky's generic first set: - the storage rule; @@ -189,7 +189,9 @@ The install needs the human's go, since it erases `userdata` again. - the guard's flags hold; - `reboot-to bootloader` works; - `tools/phone-smoke`'s report goes to the pull request, naming what doesn't apply yet (no GPU or touch driver). -- **Watch for:** the clock. With no RTC driver and no network time, the clock starts early, and gpg can skip a new release key as "created in the future" (husky's U4 finding). Set it from the laptop over ssh before `pacman-key --populate`. +- **Watch for:** + - **The clock.** With no RTC driver and no network time, the clock starts early, and gpg can skip a new release key as "created in the future" (husky's U4 finding). Set it from the laptop over ssh before `pacman-key --populate`. + - **Suspend.** Don't use it in M2.7. The package's drop-in makes Suspend mean s2idle, and that has never run on Tensor G3. It waits for the Pixel 8 Pro's U6, so the session test doesn't turn into a suspend test. - **Risk:** low for the hardware. The trap is the fallback to stock after three boots (above). ## Risks @@ -272,7 +274,7 @@ The UFS change went out as linux-omarchy-mobile#206, signed off by the owner, an ### 2026-11-06: Arch on `userdata`, test image (M2.6, gate d) -- **Kernel:** `7.3.0-rc6-omamobile-push1-g31d8b229d0d0`: #206's head before it merged (`31d8b229d`), built clean with no overlay. Its DTS is blob `bfa8b6f54e0e`, as merged in `75b9c0b73`. +- **Kernel:** `7.3.0-rc6-omamobile-push1-g31d8b229d0d0`: linux-omarchy-mobile#206's head before it merged (`31d8b229d`), built clean with no overlay. Its DTS is blob `bfa8b6f54e0e`, as merged in `75b9c0b73`. - **The test root:** built by `device/akita/build-u3-root` from the Arch Linux ARM base (sha256 `42a4eeaa…`), `omamobile-device-akita` 0.1.0 and this kernel's modules. Its MANIFEST names repository commit `93de3d963c6d`. - **The install:** `tools/install-phone --device akita --rootfs … --bootloader-slots-match akita-17.0-15681527 --reinstall`, run by the owner after a dry run. @@ -283,6 +285,7 @@ The UFS change went out as linux-omarchy-mobile#206, signed off by the owner, an | 15 | The guard under Arch | 62 partitions, exactly `UFS_RW` writable; `sdb`-`sdd` `ro`; no `/dev/sda`. Only `sda34` is mounted (ext4, 107.9 G). The kernel log has no UFS or ext4 error | The guard's flags hold after `switch_root` | | 16 | `bin/omamobile fastboot` from Arch, 282 s into the first boot | `reboot-to bootloader` reached fastboot in 25 s. `getvar`: slot B `slot-successful:no` with 2 tries, slot A unchanged | The reboot mode works from Arch too. `reboot-to` syncs before it resets | | 17 | `fastboot --set-active=b` (B back to 3 tries), then `fastboot reboot` | SSH at 28 s, with systemd `running` 9 s into boot. `systemd-analyze`: 2.0 s kernel and initramfs plus 2.2 s userspace. As before: no failed units, 27 running, the guard's flags, `usb0`, the same four journal lines. ext4 mounted cleanly with no journal replay, and the root wasn't grown again | **Gate (d) passed:** a second boot comes up the same | +| 18 | `tools/phone-smoke` from the laptop, 42 h into that boot (2026-11-08; the report's own date is the phone's clock, July) | Required rows: boot, storage guard (62 partitions, only `UFS_RW` writable), root (ext4 on `userdata`), kernel health (no oops or BUG, 0 WARN), systemd units, USB gadget, all ok; session not ok. Evidence: the display ok (1080x2400 on simpledrm); GPU, lock and touch not ok; buttons, radios, battery, sound, sensors and cameras skip. Its "new dmesg errors" are the two `exynos-clkout` lines, which husky's log has too (H/), but which the tool's known list (the 7 Pro's) doesn't name | As expected for the test root: everything below the session works, and the session rows wait for M2.7's image | Findings: diff --git a/device/akita/NOTES.md b/device/akita/NOTES.md index 614fdbee4..80f355d1f 100644 --- a/device/akita/NOTES.md +++ b/device/akita/NOTES.md @@ -20,10 +20,10 @@ UFS with the storage guard (gate c) and Arch on `userdata` (gate d). The steps a - **The kernel's default sleep is `deep`** [V]: `/sys/power/mem_sleep` reads `s2idle [deep]` under Arch. Linux has no zuma SoC sleep sequence, so `omamobile-device-akita` makes Suspend use `s2idle`, as the Pixel 7 Pro's package does. - **`NV_PARTS` names the radio's partitions only** (the Pixel 7 Pro's list, all present on akita). Other per-phone partitions it doesn't name: - `mfg_data`: factory data, which the Pixel 7 Pro's fingerprint stack reads a copy of ([cheetah's FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md)); - - `trusty_persist`: Trusty's persistent storage ([tegu's FINGERPRINT-PLAN](../tegu/FINGERPRINT-PLAN.md)); + - `trusty_persist` and `trusty_userdata`: Trusty's persistent storage ([tegu's FINGERPRINT-PLAN](../tegu/FINGERPRINT-PLAN.md)); - `pinfo`, `fips` and `blenv`, whose contents haven't been read [I]. - None is on `UFS_RW`, so the guard keeps them read-only, and all are in M2.4's full backup. Since stage 0's clean backup, `mfg_data`, `pinfo`, `fips` and `blenv` are unchanged, and `trusty_persist` changed (stock ran) [V]. + None is on `UFS_RW`, so the guard keeps them read-only, and all are in M2.4's full backup. Since stage 0's clean backup, `mfg_data`, `pinfo`, `fips`, `blenv` and `trusty_userdata` are unchanged, and `trusty_persist` changed (stock ran) [V]. The two Trusty partitions are now in `NV_BACKUP_EXTRA`, as on the Pixel 8 Pro, so `tools/nv-backup --check` shows when Android has written Trusty's storage. - **A second retail 8a passed M2.3, M2.4 and M2.6** on the same branch, with the same link, partition map and guard results ([#456](https://github.com/derekross/omarchy-mobile/pull/456)). ## 2026-11-03: first light (M1.3) and the console (M1.4) @@ -126,7 +126,7 @@ The descriptor carries no comments; this table is its provenance. | `VENDOR_PAGESIZE` | 0x800 | [V] | F/ `vendor_boot` and `vendor_kernel_boot` headers | | `OS_VERSION`, `OS_PATCH_LEVEL` | 17.0.0, 2026-10 | [V] | F/ `init_boot` header; the build on both slots (R/) | | `BOOT_IMAGES`, `UFS_RW` | the five boot images; their `_b` names and `userdata` | [V] | R/ `/dev/block/by-name`; F/ | -| `NV_PARTS`, `NV_BACKUP_EXTRA` | `efs efs_backup modem_userdata persist modem_a modem_b`; `devinfo` | [V] | R/ `/dev/block/by-name` has all seven, none on `UFS_RW`. They are cheetah's values: the partitions of AGENTS.md §1's checksum check, plus `devinfo`, whose slot flags change with every flash. They let `tools/nv-backup` back them up read-only from our own kernel ([BRINGUP-M2](BRINGUP-M2.md), M2.4) | +| `NV_PARTS`, `NV_BACKUP_EXTRA` | `efs efs_backup modem_userdata persist modem_a modem_b`; `devinfo trusty_persist trusty_userdata` | [V] | R/ `/dev/block/by-name` has all nine, none on `UFS_RW`. `NV_PARTS` is cheetah's: the partitions of AGENTS.md §1's checksum check. `NV_BACKUP_EXTRA` is husky's (#449): `devinfo`, whose slot flags change with every flash, and Trusty's two partitions, which Android writes (`trusty_persist` changed while stock ran, M2.4). Together they let `tools/nv-backup` back them up read-only from our own kernel ([BRINGUP-M2](BRINGUP-M2.md), M2.4), and `--check` report the extras' changes | | `INITRAMFS_INIT` | the shared init | [V] | as husky | | `PANEL_SIZE` | 1080x2400 | [V] | R/ `dumpsys display`; G/ `zuma-akita-display.dtsi` | | `SIMPLEFB_TRIG_CON` | `0x19470030 0x3061` | [V] | DECON0 `TRIG_CON` read 0x3070 at handover on a booted 8a (2026-11-03, above); 0x3061 unmasks the trigger as on husky (H/), and with it the console reaches the panel (M1.4, above) | diff --git a/device/akita/device.conf b/device/akita/device.conf index 66aa7c5db..d672f94f9 100644 --- a/device/akita/device.conf +++ b/device/akita/device.conf @@ -20,7 +20,7 @@ OS_PATCH_LEVEL=2026-10 BOOT_IMAGES="boot init_boot vendor_boot vendor_kernel_boot dtbo" UFS_RW="boot_b init_boot_b vendor_boot_b vendor_kernel_boot_b dtbo_b userdata" NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b" -NV_BACKUP_EXTRA="devinfo" +NV_BACKUP_EXTRA="devinfo trusty_persist trusty_userdata" INITRAMFS_INIT=/initramfs/init SIMPLEFB_TRIG_CON="0x19470030 0x3061" PANEL_SIZE=1080x2400 diff --git a/device/akita/overlays/ufs-probe.dtso b/device/akita/overlays/ufs-probe.dtso index ef6a9614a..2b34d9817 100644 --- a/device/akita/overlays/ufs-probe.dtso +++ b/device/akita/overlays/ufs-probe.dtso @@ -9,8 +9,9 @@ * * An overlay replaces bootargs whole, so these are a copy: zuma-akita.dts's * bootargs as of linux-omarchy-mobile#206 (omamobile 75b9c0b73), unchanged - * since the first-light board file (#192). If the board file's change, - * copy them again before reusing this, or the overlay silently reverts them. + * since the first-light board file (#192). If the board file's bootargs + * change, copy them again before reusing this, or the overlay silently + * reverts them. */ /dts-v1/; /plugin/; diff --git a/device/cheetah/FINGERPRINT-PLAN.md b/device/cheetah/FINGERPRINT-PLAN.md index 3a2e3209d..99fb84d0d 100644 --- a/device/cheetah/FINGERPRINT-PLAN.md +++ b/device/cheetah/FINGERPRINT-PLAN.md @@ -232,6 +232,8 @@ export KERNEL_DIR=~/android/mainline/wt-int KERNEL_OUT=$O # OVL = the overlays the phone boots with today; it must include aoc-core-test # (Trusty) and gnss-pmic-test (pmic-2), e.g. OVL="gnss-pmic-test gnss-test aoc-core-test audio-amps-test aoc-sound-test" +# B = the newest off-repo backup tools/nv-backup made +B=~/android/reference/cheetah-nv-backup-20261102 ``` ### FB: backups (read-only, before anything else; risk none) @@ -239,15 +241,13 @@ OVL="gnss-pmic-test gnss-test aoc-core-test audio-amps-test aoc-sound-test" FB1, the M0.1 check against the latest off-repo backup: ```sh -tools/phone-ssh 'for p in efs efs_backup modem_userdata persist modem_a modem_b; do - d=$(grep -lx "PARTNAME=$p" /sys/class/block/*/uevent | head -1 | cut -d/ -f5) - printf "%s %s.img\n" "$(sha256sum < /dev/$d | cut -d" " -f1)" "$p"; done' > logs/fb-partitions.sha256 -sort -k2 ~/android/reference/cheetah-partition-backup-20261012-radio/SHA256SUMS | grep -E ' (efs|efs_backup|modem_userdata|persist|modem_a|modem_b)\.img$' | - diff - <(sort -k2 logs/fb-partitions.sha256) +tools/nv-backup --check "$B" ``` -Pass: no diff (or a diff explained by a stock boot since, then a fresh -read-only backup first). **Stop** if there is no backup. +Pass: `nv-backup` exits 0, every NV partition `SAME`. A difference +explained by a stock boot since: a fresh read-only backup into a new +directory first, then FB1 against it. **Stop** if there is no backup, if +`nv-backup` refuses, or on any other difference. FB2, LDO15S as it is now, on the kernel the phone runs (pmic-2 bound by `gnss-pmic-test`; register `0x3a` is `L15S_CTRL`): @@ -360,21 +360,40 @@ root has no `/dev/disk/by-partlabel`. F3 passed on 2026-10-13 from an > where storageproxyd has never run (F19.1); once it has, Trusty is using > that copy. +**Stop** before anything else if storageproxyd already ran on this install +(F19.1's checks): Trusty is using `/var/lib/omamobile-fp` then. + ```sh tools/phone-ssh 'modprobe sg; for d in /sys/class/scsi_generic/sg*; do echo "$d $(basename $(readlink -f $d/device))"; done' # the copies on the phone: F19.3's commands +# the laptop copy of mfg_data (read-only dd, found by PARTNAME): created +# private (umask 077) as $F.part, renamed to $F only if the copy succeeds +F=~/android/reference/cheetah-mfg_data-"$(date +%F)".img +if (umask 077; tools/phone-ssh 'set -e; M=$(grep -lx "PARTNAME=mfg_data" /sys/class/block/*/uevent | head -1 | cut -d/ -f5) + test "$(cat /sys/class/block/$M/ro)" = 1; dd if=/dev/$M bs=1M status=none' > "$F.part") && + mv -T "$F.part" "$F" +then sha256sum "$F" | cut -c1-16 +else rm -f "$F.part"; echo "mfg_data copy refused or failed; no file kept" +fi # the laptop backup of persist and the radio partitions (into a new directory) tools/nv-backup ~/android/reference/cheetah-nv-backup-"$(date +%Y%m%d)" tools/phone-ssh 'modprobe -r sg' ``` Expect one sg node at `0:0:0:49476` (the RPMB well-known LUN), F19.3's -output, then `nv-backup`'s verified copies. `mfg_data` isn't one of -`nv-backup`'s partitions: F19.3 compares the phone's copy with the laptop's -2026-10-13 one. Pass: F19.3's Pass and `nv-backup` exits 0. **Stop** on -F19.3's stops, if `nv-backup` refuses, or if the storage guard complains. -Rollback: `modprobe -r sg`, then F19.3's (nothing is written to `persist` -or `mfg_data`). +output, the laptop copy's hash, then `nv-backup`'s verified copies. +`mfg_data` isn't one of `nv-backup`'s partitions, so it gets its own copy. +A refused or failed copy prints its message and keeps no file (only an +interrupted one leaves a `.part`). F19.3 compares the phone's copy with the +laptop's 2026-10-13 one; a phone without that copy compares with this one. +Pass: F19.3's Pass, the laptop copy's hash equal to F19.3's `mfg_data.img` +hash, and `nv-backup` exits 0. **Stop** on F19.3's stops, if the laptop copy +is refused, fails or is empty, if its hash differs, if `nv-backup` refuses, +or if the storage guard complains. Rollback: +`modprobe -r sg`, then remove only what F3 wrote on the phone, never the +whole directory (it holds Trusty's TD once storageproxyd has run): +`rm -rf /var/lib/omamobile-fp/persist-ss /var/lib/omamobile-fp/mfg_data.img`. +Nothing is written to `persist` or `mfg_data`. ### F4: secure storage (IRREVERSIBLE: the first RPMB write from Linux) @@ -968,20 +987,17 @@ the last TD. Three facts decide the runbook: `persist:/ss/0` hashed to `e0e1990d…` in the 10-12, 10-30 and 11-02 persist backups and in both fingerprint backup tars. -Variables: `B=~/android/reference/cheetah-nv-backup-20261102`. +Variables: section 6's (`B`, the newest backup). **F19.0 Backups match (read-only; risk none).** ```sh -tools/phone-ssh 'for p in efs efs_backup modem_userdata persist modem_a modem_b; do - d=$(grep -lx "PARTNAME=$p" /sys/class/block/*/uevent | head -1 | cut -d/ -f5) - printf "%s %s.img\n" "$(sha256sum < /dev/$d | cut -d" " -f1)" "$p"; done' > logs/f19-partitions.sha256 -grep -E ' (efs|efs_backup|modem_userdata|persist|modem_a|modem_b)\.img$' "$B/SHA256SUMS" | sort -k2 | - diff - <(sort -k2 logs/f19-partitions.sha256) && echo SAME +tools/nv-backup --check "$B" ``` -Pass: `SAME`. **Stop** on any difference: take a fresh read-only backup and -find out why first. +Pass: `nv-backup` exits 0, every NV partition `SAME`. **Stop** if it +refuses or on any difference: take a fresh read-only backup and find out +why first. **F19.1 Nothing has run yet (read-only; risk none).** `uname -r`, the package versions, `systemctl is-enabled omamobile-fp` (disabled), diff --git a/device/cheetah/MODEM-PLAN.md b/device/cheetah/MODEM-PLAN.md index 0b9f05962..3299dbfa2 100644 --- a/device/cheetah/MODEM-PLAN.md +++ b/device/cheetah/MODEM-PLAN.md @@ -342,7 +342,8 @@ Same checks as below: full build exits 0 (`logs/kernel-modem7.log`), ```sh # M0.1 partitions unchanged against the 2026-10-11 backup (reads ~430 MB) tools/phone-ssh 'for p in efs efs_backup modem_userdata persist modem_a modem_b; do - printf "%s %s.img\n" "$(sha256sum < /dev/disk/by-partlabel/$p | cut -d" " -f1)" "$p"; done' \ + d=$(grep -lx "PARTNAME=$p" /sys/class/block/*/uevent | head -1 | cut -d/ -f5) + printf "%s %s.img\n" "$(sha256sum < /dev/$d | cut -d" " -f1)" "$p"; done' \ > logs/m0-partitions.sha256 grep -E ' (efs|efs_backup|modem_userdata|persist|modem_a|modem_b)\.img$' \ ~/android/reference/cheetah-partition-backup-20261011/SHA256SUMS | sort -k2 | diff - <(sort -k2 logs/m0-partitions.sha256) @@ -378,7 +379,8 @@ tools/phone-ssh 'cat > /etc/udev/rules.d/60-omamobile-modem-nv-ro.rules' <<'EOF' SUBSYSTEM=="block", ENV{ID_PART_ENTRY_NAME}=="efs|efs_backup|modem_userdata|modem_a|modem_b", RUN+="/usr/bin/blockdev --setro $devnode" EOF tools/phone-ssh 'udevadm control --reload; udevadm trigger -s block -c change; - for p in efs efs_backup modem_userdata modem_a modem_b; do echo $p $(blockdev --getro /dev/disk/by-partlabel/$p); done' + for p in efs efs_backup modem_userdata modem_a modem_b; do + d=$(grep -lx "PARTNAME=$p" /sys/class/block/*/uevent | head -1 | cut -d/ -f5); echo $p $(blockdev --getro /dev/$d); done' # pass: all 1. (persist stays writable for the fingerprint work's own plan; nothing here writes it.) ``` @@ -2800,13 +2802,16 @@ tools/phone-ssh 'nmcli -f DEVICE,TYPE,STATE device | grep -c gsm; omamobile-sit # rollback: as B2 # B4 the second reboot: the clean stop clears the modem-up marker, and the next boot starts again -# (asks the human; risk: medium: one UFS pass) -tools/phone-ssh 'sync; (sleep 1; reboot-to omamobile) >/dev/null 2>&1 &' +# (asks the human; risk: medium: one UFS pass). Through systemd: `reboot-to` stops no unit, so the stop +# hook wouldn't run (AGENTS.md section 2) +tools/phone-ssh 'systemctl reboot' +# once the phone is back on USB (the modem's stop takes about 40 s, #532): tools/phone-ssh 'sleep 240; journalctl -b -1 -u omamobile-modem -o cat | grep -E "CP OFFLINE|stopped|removed|kept" | tail -3; systemctl is-active omamobile-modem omamobile-sitd omamobile-sit-data omamobile-mmd; omamobile-sit status | head -3; ls -l /var/lib/omamobile/modem-* 2>&1; dmesg | grep -c ufshcd_err_handler' -# pass: the previous boot's journal ends with "CP OFFLINE" and "modem stopped (success): ... modem-up -# removed"; active x4 and registered again; only this boot's modem-up; err_handler 0 on this boot +# pass: the previous boot's journal has "CP OFFLINE" and ends with "modem stopped (): ... modem-up +# removed" (the result is "timeout" until #532 is fixed; the removal is what counts); active x4 and +# registered again; only this boot's modem-up; err_handler 0 on this boot # stop: the modem unit refused with "ended without a clean stop" (the stop hook didn't run or ran on # another boot's marker: the -1 journal says which; the fix is in the package, not on the phone: # `systemctl disable omamobile-modem-boot.target`, remove the marker, and reboot); "never reached @@ -2953,7 +2958,7 @@ tools/phone-ssh 'sleep 240; systemctl list-units --no-pager "omamobile-modem*" o # keeps a marker that isn't this boot's (--stopped), so the next boot finds a stale one, refuses once, # moves it aside, and the boot after starts the modem again. No forced reset needed. tools/phone-ssh 'cat /var/lib/omamobile/modem-up; printf "%s boot %s\n" "$(date -Is)" 00000000-0000-0000-0000-000000000000 > /var/lib/omamobile/modem-up; sync; cat /var/lib/omamobile/modem-up' -tools/phone-ssh 'sync; (sleep 1; reboot-to omamobile) >/dev/null 2>&1 &' +tools/phone-ssh 'systemctl reboot' # through systemd, so the stop hook runs (B4); after it, once back on USB: tools/phone-ssh 'sleep 120; journalctl -b -1 -u omamobile-modem -o cat | tail -3; systemctl is-active omamobile-modem omamobile-sitd omamobile-sit-data omamobile-mmd; journalctl -b -u omamobile-modem -o cat; ls -l /var/lib/omamobile/modem-* 2>&1; cat /run/omamobile/modem-refused; systemd-inhibit --list --no-legend | grep -c omamobile-modem; dmesg | grep -c ufshcd_err_handler' @@ -2987,7 +2992,7 @@ tools/phone-ssh 'sleep 240; systemctl is-active omamobile-modem omamobile-sitd o # another boot's id again. The reboot's stop hook keeps the planted marker and the copy (not this boot's), # so the next boot finds both: the one automatic retry is used up, and it holds. tools/phone-ssh 'ls -l /var/lib/omamobile/modem-*; printf "%s boot %s\n" "$(date -Is)" 00000000-0000-0000-0000-000000000000 > /var/lib/omamobile/modem-up; sync' -tools/phone-ssh 'sync; (sleep 1; reboot-to omamobile) >/dev/null 2>&1 &' +tools/phone-ssh 'systemctl reboot' # through systemd, so the stop hook runs (B4); after it, once back on USB: tools/phone-ssh 'sleep 120; systemctl is-active omamobile-modem omamobile-sitd omamobile-sit-data omamobile-mmd; journalctl -b -u omamobile-modem -o cat | grep -E "clean stop|used up|moved"; ls -l /var/lib/omamobile/modem-* 2>&1; cat /run/omamobile/modem-refused; systemd-inhibit --list --no-legend | grep -c omamobile-modem; dmesg | grep -c ufshcd_err_handler' @@ -2999,9 +3004,9 @@ tools/phone-ssh 'sleep 120; systemctl is-active omamobile-modem omamobile-sitd o # -1 journal and the ls before the plant); the modem started (the planted marker was removed) # then: rm -f /var/lib/omamobile/modem-up*; reboot (asks the human); after 240 s: as B9's pass (active x4, # "CP ONLINE", this boot's modem-up, no refused copy, no modem-refused) -# then: one more clean reboot (asks the human; one UFS pass): the modem starts, this boot's modem-up, -# and ls /var/lib/omamobile/modem-up.refused-* finds nothing (the streak reset by --stopped at the -# reboot before: the copies are removed with this boot's marker) +# then: one more clean reboot, `systemctl reboot` (asks the human; one UFS pass): the modem starts, this +# boot's modem-up, and ls /var/lib/omamobile/modem-up.refused-* finds nothing (the streak reset by +# --stopped at the reboot before: the copies are removed with this boot's marker) # stop: a refused copy after the clean reboot (--stopped didn't remove them: journalctl -b -1 -u # omamobile-modem, "modem stopped"); refused on either boot # rollback: as B8 diff --git a/device/cheetah/NOTES.md b/device/cheetah/NOTES.md index 0861b2479..515269d1b 100644 --- a/device/cheetah/NOTES.md +++ b/device/cheetah/NOTES.md @@ -2,6 +2,107 @@ Findings from real hardware, newest first. `BRINGUP-M1.md` is the research map written before first boot. +## 2026-11-09: the 2026.11.08 test install, and an update run as root + +The release's signed bundle, `omamobile-cheetah-2026.11.08`, installed on the +reference phone with `bash install --reinstall --bootloader-slots-match +cloudripper-17.0-15199429` (slot A's bootloader version in the stock +capture, the same as slot B's), after `--dry-run`. The phone booted +`7.3.0-rc6-omamobile-g1a9d1d4e9289` with `omamobile-device-cheetah` 0.1.47, +`omamobile-shell` 0.2.107, `omamobile-omarchy` 0.1.37 and Omarchy 4.0.6. + +- **Provisioning, by hand** (`tools/phone-provision --nv-backup`, the + owner's CP2A factory image and the 2026-11-03 radio backup, whose + checksums still matched): after the reboot Wi-Fi, the AoC and the + fingerprint stack were up, and the modem came up at boot and registered + IMS by itself. No unit failed. `tools/phone-smoke`: 18 ok, the modem's + usual "not opened" lines, the camera check skipped. The fingerprint + sensor reads ready with no finger enrolled. +- **The package hook, on a reinstall:** at 00:42 a reinstall of the + release's own `linux-omamobile` (`pacman -U`, the same + `7.3.0rc6.r704.g1a9d1d4e9289-1`) ran `omamobile-boot-update`'s hook + (the install's `AUTO_WRITE=yes`). It rebuilt slot B's five images and + wrote `vendor_kernel_boot_b`, read it back ("written and verified"), left the + other four images ("already there"), saved the previous set and did not + reboot. The reboot into it worked. The one image differed because the + hook appends the owner's `authorized_keys` to the initramfs and the + bundle's image carries none: the saved slot-B copy equals the bundle's + byte for byte, and the new one has a vendor ramdisk 171 bytes longer + (6847295 against 6847124), so a fresh install's initramfs SSH has no + owner key until the first hook run (RELEASES §11.4 expects the same + bytes). An update to a newer kernel hasn't run on this release yet. +- **`omarchy update` as root over SSH**, with `OMARCHY_PATH` set by hand + (the command we gave the owner; without it the run stops before + updating anything), ran Omarchy's migrations again as root: Omarchy records them per user, and + root's record was empty, so 59 ran. One swapped `quickshell` for an older + `quickshell-git` (Omarchy's later migration back counted as done), others + wrote configs into `/root`, restarted systemd-oomd and left + `/tmp/omarchy-update.log` owned by root, after which the Updates app + stopped at once ("script: cannot open /tmp/omarchy-update.log: Permission + denied"). Nothing else in `/etc` changed, and no package moved apart + from that swap (with `vulkan-headers`, which it pulled in) and the + normal updates. + Put back by hand: `quickshell` reinstalled, `vulkan-headers` removed, root's + Omarchy state and configs and the log deleted. `omamobile-omarchy` 0.1.38 + (#548) refuses an update as root. +- **The update as the user** (the Updates app, 11:06): "Updated", one + package (`inotify-tools`, from Arch Linux ARM), Omarchy still 4.0.6, + nothing held, no restart asked for; patches "already applied". The + "local is newer than omamobile" warnings are the stable channel still + holding the previous release until the promote. + +Recorded with `tools/release --version 2026.11.08 test-install --passed +7.3.0-rc6-omamobile-g1a9d1d4e9289`. + +## 2026-11-08: the release kernel for 2026.11.08, a flat battery, the reboot reason + +Kernel `7.3.0-rc6-omamobile-g1a9d1d4e9289`, `omamobile` at `1a9d1d4e9289` +(the planned `kernel-2026.11.08`), built with the release `LOCALVERSION` and +the development initramfs and pushed to slot B; `omamobile-device-cheetah` +0.1.43, `omamobile-shell` 0.2.107 and `omamobile-omarchy` 0.1.37 (#420's test +build), Omarchy 4.0.6. + +- **The release kernel boots** [V]: `uname -r` reads + `7.3.0-rc6-omamobile-g1a9d1d4e9289`. Touch probed as before (`S3908GA1B0-15.0, + TouchComm v1, build 4104960, message CRC off`), the charger's guard had its + battery reading at probe (4.67 s, mode 5), the sound card registered all 18 + playback PCMs, Wi-Fi connected, and the modem came up at boot: IMS + registered (`state 2 (VoLTE registered)`) about 100 s after boot. + `tools/phone-smoke`: 18 ok, cameras skipped (no libcamera tools); its one + "not ok" is the modem's `rx_demux … is not opened` drops, at the rate of + every modem-up boot today. +- **This tree, piece by piece** [V], each on its own test kernel, `-push1` + builds of the PR merged onto `omamobile`, and posted on the PR: + linux-omarchy-mobile#194 (touch: both probe lines unchanged, no fallback, + no desync after a minute of touch), #201 (S2MPG12 RTC: reads 0 s off, a + wake alarm awake, 10 RTC-woken s2idle cycles with the modem off, none woken + early), #191 with #187 (Wi-Fi scans, a 300 MB download at about 130 Mbit/s + with no `No PKTID`; the modem: an SMS, an answered call, 10 minutes idle), + #176 (the reboot reason: with `nvmem_max77759` loaded by hand, `reboot-to + bootloader` reached fastboot without the buttons, about 4 s; device-cheetah + 0.1.47, #534, stops blacklisting it) and #162 (the AoC series: the same + PCMs, both amplifiers' protection firmware, a -20 dBFS tone clean from both + speakers, the three sensors). +- **A flat battery** [V] (issue #169): after five days unplugged the phone + booted Linux at 3.14 V, the gauge's model load failed (`-110`) and the + charger logged `charging inhibited`; the battery read -706 mA on the + laptop's port. About 20 minutes in fastboot on the cable took it from 3.40 + to 3.91 V, and the next boot loaded the model and charged at 1.43 A. On that + boot the charger still probed before the gauge answered and charged only + from its guard's next period, 31 s later. The fix (`omamobile` 01ba2e2119ed, + 28bab7f602ca, 1a9d1d4e9289) re-checks a missing reading every 2 s and at the + gauge's first report: unloading and reloading the gauge, charging resumed + 10 ms after it came back. The model-load retry itself waits for the next + real flat battery. +- **A modem marker left by `reboot-to`** [V]: the `reboot-to bootloader` that + took the flat phone to fastboot stopped no unit, so `/var/lib/omamobile/modem-up` + stayed and the next boot skipped the modem once ("ended without a clean + stop"), as designed. Stop the modem first (`systemctl stop + omamobile-modem`) before a `reboot-to` or a `bin/omamobile push`; that stop + takes 40 s and ends "failed" with a recorded crash, issue #532. To keep the + modem off for a boot (a suspend test), `systemctl mask + omamobile-modem-boot.target`, not `/etc/omamobile/modem-hold`. + ## 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); @@ -44,7 +145,9 @@ the same Verizon-network SIM as the entry below. The runbook: 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. + `OMARCHY_PATH=/usr/share/omarchy` in its environment. **Don't (2026-11-09):** + an update as root runs Omarchy's migrations again as root; run + `omarchy update` on the phone as its user (above, 2026-11-09). ## 2026-11-03: IMS registered and an SMS sent on a Verizon-network SIM, once the bearers took stock's CIDs diff --git a/device/cheetah/RADIOS-CAMERA-PLAN.md b/device/cheetah/RADIOS-CAMERA-PLAN.md index 8a02e595c..c27f4b6c1 100644 --- a/device/cheetah/RADIOS-CAMERA-PLAN.md +++ b/device/cheetah/RADIOS-CAMERA-PLAN.md @@ -273,16 +273,18 @@ From the omamobile repo, phone in Arch over USB. # M0.1 the modem's NV and firmware partitions are untouched: checksums match the backup. # Reads only. ~430 MB from UFS, a minute or two. tools/phone-ssh 'for p in efs efs_backup modem_userdata persist modem_a modem_b; do - printf "%s %s.img\n" "$(sha256sum < /dev/disk/by-partlabel/$p | cut -d" " -f1)" "$p"; done' \ + d=$(grep -lx "PARTNAME=$p" /sys/class/block/*/uevent | head -1 | cut -d/ -f5) + printf "%s %s.img\n" "$(sha256sum < /dev/$d | cut -d" " -f1)" "$p"; done' \ > logs/m0-partitions.sha256 grep -E ' (efs|efs_backup|modem_userdata|persist|modem_a|modem_b)\.img$' \ ~/android/reference/cheetah-partition-backup-20261011/SHA256SUMS | sort -k2 | diff - <(sort -k2 logs/m0-partitions.sha256) # pass: no diff for efs, efs_backup, modem_a, modem_b. persist and modem_userdata # may differ if stock Android ran after 2026-10-11; then take a fresh backup -# before M2 (same dd as the original backup, to the laptop). +# before M2 into a new directory on the laptop (tools/nv-backup DIR). # also: nothing mounts them -tools/phone-ssh 'grep -E "sda(1|5|6|7|19|29) " /proc/mounts; ls -l /dev/disk/by-partlabel/ | grep -E " (efs|efs_backup|modem_userdata|persist|modem_a|modem_b) "' -# pass: no mount lines. +tools/phone-ssh 'grep -E "sda(1|5|6|7|19|29) " /proc/mounts + grep -xE "PARTNAME=(efs|efs_backup|modem_userdata|persist|modem_a|modem_b)" /sys/class/block/*/uevent' +# pass: no mount lines. The PARTNAME lines give each partition's sdaN. # M0.2 memory map: the CP regions must not be System RAM in use. tools/phone-ssh 'grep -iE "e8000000|ea400000|f6200000|reserved" /proc/iomem | head -20' diff --git a/device/cheetah/WAYDROID-PLAN.md b/device/cheetah/WAYDROID-PLAN.md index c6cb16d4b..387e7548f 100644 --- a/device/cheetah/WAYDROID-PLAN.md +++ b/device/cheetah/WAYDROID-PLAN.md @@ -178,8 +178,25 @@ Waydroid 1.6.3 does three things that are wrong on this phone: - `config` (`ExecStartPre` of `waydroid-container.service`, through our drop-in) drops any such lines from the generated `config_nodes` and appends `lxc.include = /usr/share/omamobile-waydroid/lxc-omamobile.conf`, - whose one rule is `lxc.cgroup2.devices.deny = b *:* rwm`: no block - device at all, whoever makes the node. + which allows the character devices Android uses (`c 1:3` for `/dev/null`, + the standard nodes, the binderfs nodes by path) and denies every block device with + `lxc.cgroup2.devices.deny = b *:* rwm`, whoever makes the node. With LXC 7 + the filter starts in "block everything" mode and leaves deny rules out of + the device program, so a list with only the deny rule allows nothing and + `lxc-start` dies with `Can't open /dev/null`. Block devices are refused + because no rule allows a `b` device, and the order of the lines does not + matter. The deny line covers one case: an `lxc.cgroup2.devices.allow = a` + placed before our include (a hand-edit) switches LXC to "allow everything", + and the `b *:*` deny keeps block devices out. An `allow = a` placed after + the include would clear every rule before it and open everything, so + `test/all` fails if the file has one. binderfs's major is assigned at boot + (507 on cheetah), so `binder`, `vndbinder` and `hwbinder` are allowed by + path (`lxc.cgroup2.devices.allow = /dev/binderfs/binder rwm`): LXC reads + each node's major and minor with `stat()` when the container starts, after + Waydroid has mounted binderfs, and `lxc-start` fails if a node is missing. + `binder-control` is not allowed. `omamobile-waydroid-check` wants the + three lines, and that the Panthor render node's `major:minor` (from + sysfs) is the one the file allows (`c 226:128`), before every start. - `verify` (`ExecStartPre` too) refuses to start the container unless all of it is in place. `waydroid upgrade` regenerates the config, so this runs before every start. @@ -263,7 +280,7 @@ Android, or Android posts "Configure physical keyboard". | `lib/omamobile-waydroid-check` | `/usr/lib/omamobile-waydroid` | Read-only: kernel options (`/proc/config.gz` or `CONFIG_FILE=`), binderfs, PSI, the Panthor render node, cgroup2 | | `lib/omamobile-waydroid-harden` | same | Section 5 | | `lib/omamobile-waydroid-mesa` | same | Section 3 | -| `lib/lxc-omamobile.conf` | `/usr/share/omamobile-waydroid` | The block-device deny rule | +| `lib/lxc-omamobile.conf` | `/usr/share/omamobile-waydroid` | The device rules: allow list, then the block-device deny | | `systemd/waydroid-container-omamobile.conf` | `waydroid-container.service.d/omamobile.conf` | `ExecStartPre`: check, harden config, harden verify | | `libalpm/90-omamobile-waydroid.hook` | `/usr/share/libalpm/hooks` | `harden patch` after `waydroid` installs or upgrades | | `etc/omamobile/waydroid.conf` | `/etc/omamobile` (backup) | `SYSTEM_TYPE`, `LCD_DENSITY`, `MULTI_WINDOWS` | @@ -355,17 +372,22 @@ Stream the kernel log first: `tools/phone-ssh 'dmesg -w' | tee logs/waydroid-w4. tools/phone-ssh 'systemctl start waydroid-container; sleep 5; systemctl --no-pager status waydroid-container | head -5; \ ls -l /dev/binderfs; waydroid status' # Block devices must be unreachable from inside (loop0 is harmless to read): +# lxc-attach gives Android's shell no PATH: without the export every command +# is "inaccessible or not found" (rc=127), which looks like a refusal. tools/phone-ssh 'lxc-attach -P /var/lib/waydroid/lxc -n waydroid -- /system/bin/sh -c \ - "mknod /dev/omtest b 7 0; head -c 1 /dev/omtest > /dev/null; echo rc=\$?; rm -f /dev/omtest"' -tools/phone-ssh 'lxc-attach -P /var/lib/waydroid/lxc -n waydroid -- /system/bin/ls /sys/kernel/debug /dev | head' + "export PATH=/system/bin:\$PATH; toybox mknod /dev/omtest b 7 0; echo mknod_rc=\$?; toybox head -c 1 /dev/omtest > /dev/null; echo head_rc=\$?; toybox rm -f /dev/omtest"' +tools/phone-ssh 'lxc-attach -P /var/lib/waydroid/lxc -n waydroid -- /system/bin/sh -c \ + "export PATH=/system/bin:\$PATH; toybox ls /sys/kernel/debug /dev | toybox head"' ``` The `lxc-attach` lines need a running container; if the container only starts with a session, run them after W5's session start instead. - **Expect:** the service is active (its three `ExecStartPre` lines passed); - `binder`, `vndbinder`, `hwbinder` in `/dev/binderfs`; the `head` read - fails with "Operation not permitted"; `/sys/kernel/debug` empty or + `binder`, `vndbinder`, `hwbinder` in `/dev/binderfs`; `toybox mknod` + prints `mknod: /dev/omtest: Operation not permitted` (that line is the pass + condition, not a nonzero rc: a missing command also gives one); + `/sys/kernel/debug` empty or missing inside; no `video*` or `fb*` in the container's `/dev`. - **Stop:** the block read succeeds (stop the container at once and fix the device rule before anything else); any oops; any diff --git a/device/dodge/initramfs/reboot-to.c b/device/dodge/initramfs/reboot-to.c index f663f18e4..4d98a95dd 100644 --- a/device/dodge/initramfs/reboot-to.c +++ b/device/dodge/initramfs/reboot-to.c @@ -7,6 +7,7 @@ // // aarch64 Linux entry: sp points at argc, then the argv pointers. +#define __NR_write 64 #define __NR_sync 81 #define __NR_reboot 142 #define __NR_exit_group 94 @@ -40,6 +41,16 @@ __attribute__((naked)) void _start(void) "b go\n"); } +static const char usage[] = "usage: reboot-to [REASON]\n" + "Reboot with REASON (default: bootloader), e.g. bootloader or recovery.\n"; + +static int same(const char *a, const char *b) +{ + while (*a && *a == *b) + a++, b++; + return *a == *b; +} + void go(long argc, char **argv) { const char *reason = "bootloader"; @@ -47,6 +58,12 @@ void go(long argc, char **argv) if (argc > 1 && argv[1] && argv[1][0]) reason = argv[1]; + /* An option is never a reason: don't reboot on "--help" or a typo */ + if (reason[0] == '-') { + scall(__NR_write, 1, (long)usage, sizeof(usage) - 1, 0); + scall(__NR_exit_group, same(reason, "-h") || same(reason, "--help") ? 0 : 2, 0, 0, 0); + } + scall(__NR_sync, 0, 0, 0, 0); scall(__NR_reboot, LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2, LINUX_REBOOT_CMD_RESTART2, (long)reason); diff --git a/device/enchilada/NOTES.md b/device/enchilada/NOTES.md index 5e9723616..a3b456784 100644 --- a/device/enchilada/NOTES.md +++ b/device/enchilada/NOTES.md @@ -29,8 +29,8 @@ tried yet; it is next. **Slot A does not hold stock Android.** This is a §3.1 event, recorded here as the maintainer asked on #432. Putting stock back on slot A is -outside the project: this tree only writes slot B and `userdata`, and -never `vbmeta`. If it is done, it is the owner's own step, with +outside the project ([the maintainer's decision on #432](https://github.com/derekross/omarchy-mobile/issues/432#issuecomment-6708103355)): +this tree only writes slot B and `userdata`, and never `vbmeta`. If it is done, it is the owner's own step, with OnePlus's own images, and it is recorded on #432 (slot flags before and after, what was flashed and from which image, then a fresh read-only radio backup). The owner has decided not to restore it, so @@ -66,30 +66,27 @@ three steps of 2026-11-05: that reply was posted at 16:13 (21:13 UTC), and `flash boot_b` (netfilter kernel), `--set-active=a` and the package install into `userdata` ran from 16:15 to about 16:20, before I had read it. Since then the only commands sent to the phone have been the read-only -backup, one `fastboot boot` (2026-11-05 16:35) and `getvar` (below). No +backup, one `fastboot boot` (2026-11-05 16:35), `getvar` and one rescue +boot to read the slot flags again (below). No slot flag is written again until this phone has a per-device entry in CONTRIBUTING.md. -**Slot flags** (`fastboot getvar all`, read-only): +**Slot flags** (read-only; `fastboot getvar all`, except the last row): | Read | `current-slot` | A: successful / unbootable / retry-count | B: successful / unbootable / retry-count | | --- | --- | --- | --- | | 2026-11-04, before any write of this port | a | no / no / 6 | yes / no / 7 | -| 2026-11-07, now | a | no / no / 5 | no / no / 7 | +| 2026-11-07 | a | no / no / 5 | no / no / 7 | +| 2026-11-07, after one more rescue boot, read in the rescue from `sde`'s GPT attributes (`sfdisk --dump`) | a | no / no / 5 | no / no / 7 | Between the two reads, B lost its successful mark (left by the third-party build; `--set-active=b` clears it and nothing of this port marks a slot) and A's retry count went from 6 to 5. Neither slot is marked unbootable. -Slot A is not marked successful, so each boot of the rescue may spend one -of its tries. If ABL works as on other Qualcomm phones, `--set-active=a` -on 2026-11-05 reset A's count to 7, and the rescue boots since (including -the reboot after a `fastboot boot` panics with no USB host) took it to 5. -At 0 ABL would switch to slot B and run B's tries down too, and since -nothing here may mark a slot, the phone would then stop in fastboot and -need a `--set-active` to come back. This is not confirmed yet: one more -`getvar` after the next rescue boot will tell. Until then, rescue boots -are kept few. +Slot A is not marked successful, but a rescue boot does not spend one of +its tries here: after one more rescue boot A was still at 5 and B at 7 +([#432](https://github.com/derekross/omarchy-mobile/issues/432#issuecomment-6716747930)). What took A from 6 to 5 between the first two reads is not +known. Neither slot is near 0. **The slot-A rescue.** It is not the shared init and has no initramfs (an empty ramdisk): the kernel mounts `system_a` from the `root=` that ABL @@ -104,6 +101,20 @@ tree and goes away if stock is restored. 20 s and panics, and `panic=10` reboots the phone. ABL then starts the active slot, A, which is the rescue. +## 2026-11-08: the LUN-aware guard, booted RAM-only + +`fastboot boot` of an initramfs built from commit 2331a85 (the +`UFS_RW_LUNS` pull request, with `UFS_RW_LUNS=sde` in this descriptor), +the first-light kernel (`7.1.0-rc1-sdm845`); nothing written. From the +init's log and `/sys/block`: + +- allowlist `boot_b userdata`; LUNs with allowlisted partitions `sda sde`; +- `/dev/sda` and `/dev/sde` removed; +- only `sda17` (`userdata`) and `sde39` (`boot_b`) writable; the other + 71 `sde` partitions `ro=1`; +- `sdb`, `sdc`, `sdd` and `sdf` read-only at the disk level; +- no UFS errors in the kernel log. + ## 2026-11-05: complete backup Taken from the slot-A rescue (`boot_a`, `system_a`), read-only. Every @@ -169,8 +180,9 @@ wrote nothing. nothing mounted. - **`boot_b` is on LUN `sde`, not `sda`.** The shared guard's `UFS_RW` only looks at `sda`, so `boot_b` and `dtbo_b` stay read-only (seen - live). This is the same split as dodge; a LUN-aware `UFS_RW` will be its - own shared pull request. + live). This is the same split as dodge. The guard can now open a second + LUN (`UFS_RW_LUNS`, #530); enchilada's `UFS_RW_LUNS=sde` comes with the + slot-B install, which gives `boot_b` on `sde` a writer. - msm DRM came up (`fb0` is `msmdrmfb`). - ABL appends `root=PARTUUID= skip_initramfs ro init=/init` to the command line even on `fastboot boot`. The shared init runs as PID 1 diff --git a/device/enchilada/device.conf b/device/enchilada/device.conf index 40d415f20..a9e0e4d0c 100644 --- a/device/enchilada/device.conf +++ b/device/enchilada/device.conf @@ -4,12 +4,11 @@ # # RAM-only bring-up: this ABL boots an Android boot image header v0 holding # a gzip kernel with the DTB appended (no dtbo, no vendor_boot), booted with -# `fastboot boot`, so nothing is written. No packer in this tree makes that -# image yet, so images, flash, push and the installer all refuse -# BOOT_METHOD=android-v0 before touching a phone (tests/boot-method). The -# header-v0 packer is a separate change; flash, push and the installer keep -# refusing it until the slot-B install and its CONTRIBUTING.md §3.1 entry -# are agreed. +# `fastboot boot`, so nothing is written. `omamobile images` packs that +# boot.img from the header fields below (tests/images-layout); fastboot, +# flash, push and the installer refuse BOOT_METHOD=android-v0 before +# touching a phone (tests/boot-method), and keep refusing it until the +# slot-B install and its CONTRIBUTING.md §3.1 entry are agreed. # # Storage: userdata is on sda, but boot_* sit on LUN sde, so the shared # init's sda-only guard keeps boot_b read-only (the same split as dodge). diff --git a/device/husky/MODEM-PLAN.md b/device/husky/MODEM-PLAN.md new file mode 100644 index 000000000..309283d4a --- /dev/null +++ b/device/husky/MODEM-PLAN.md @@ -0,0 +1,447 @@ + +# Pixel 8 Pro modem plan (husky, Samsung S5300) + +Status (2026-11-08): on hold. Stages S1 to S5e have been run; none of them +hung, oopsed or raised a UFS error (S5c stopped on its own current abort, +see below). No modem step and no power-line step has been run since S5e +ended at 2026-11-07 21:21 UTC (23:21 here), and I take none on the 8 Pro +until derekross answers the question on omarchy-mobile#472 +(https://github.com/derekross/omarchy-mobile/pull/472#issuecomment-6711065625; +see "Current state: on hold" below). + +I asked that question on 2026-11-07 at 18:04 UTC and wrote that I would not +run the first hardware step until I heard back. I then ran S3 (19:14:50 UTC) +and after it S4, S5a, S5b, S5c, S5d and S5e, all before any answer. That was +my mistake: I should have waited. S1 and S2 (18:47 and 18:52 UTC) came after +the question too, but they only read: S1 reads the PMU register (the module +probes with `allow_hw=0`) and S2 reads the eleven modem lines as the +bootloader left them, with no direction or level change. + +Times: this file gives Athens time (EET, UTC+2) unless a time is marked UTC. +Subtract 2 h for UTC. +This file is the record of S1 to S5e: what each step does, its gates, its +stop conditions, the dated result with the kernel release, and what the +result does not prove. + +[V] = read in source, stock DT or my captures on the phone. [I] = inferred; +each [I] names the step that would settle it. + +Stock references are Google's tree `kernel/google-modules/radio/samsung/s5300`, +branch `android-gs-shusky-6.1-android16` (the stock CPIF, `modem_ctrl_s5100.c`, +`s5300` node). The line numbers below are the ones derekross checked in that +tree on omarchy-mobile#514; my own copy was the `soc-gs` tree, where the same +functions sit at different lines (`gpio_power_off_cp()` at 874, for example). +The PCIe side is `pcie-gs201-cp` from W4HO's stack in +linux-omarchy-mobile#187. + +## Test kernels + +All steps ran from slot B on a test kernel built from my husky e1 branch +plus the #187 stack and the husky device tree, with the modem nodes +disabled unless the step enables them. + +| Set | `uname -r` | Used for | +| --- | --- | --- | +| images-plain, images-s1, images-s2 | `7.3.0-rc6-omamobile-push1-gc5b6ae8f4dc2` | boot 1 (plain), S1, S2, S3 (images-s1 again) | +| images-s4 | `7.3.0-rc6-omamobile-push1-g6a203e4b8a67` | S4, S5a to S5e | + +Between stages the phone went back to the normal NFC set (release +`...ge98a7`), so a test boot is never the running system for long. +Where a log did not print `uname -r` itself, the table says which image set +was flashed; the lines below say so for each stage. + +## Safety (all stages) + +Gates, all of which must hold before any stage: + +- First of all: `tools/nv-backup --check` matches the 2026-11-01 backup for + `efs`, `efs_backup`, `modem_userdata`, `persist` and `modem_a`/`modem_b` + (read-only; `devinfo` is expected to differ). I did not run this before + S1 to S5e. I ran it afterwards, on 2026-11-08, and every partition matched + (see "Current state"). From now on it is the first gate of every stage. +- I am at the phone with the USB cable in. The charger is in too, except in + S5d and S5e, which are battery-only on purpose: a current reading cannot be + taken with a charger feeding the rail. The battery was at 92 % and each run + lasted a few minutes. On this phone 92 % is "full": the charger chip + finishes at 4350 mV and the gauge stays at 92 %, even after 12 hours plugged + in (`BATTERY-NOTES.md` section 10a, #452). +- Nothing armed or fed a watchdog during S3 to S5. Every step was attended, + with the buttons as the way back. On the 8 Pro a hung kernel needs Power + + Volume Up held for 15 to 30 s; the power button alone is not enough. +- Battery 50 % or more; battery temperature under 40 C at the start; SoC at + or under 62 C (idle SoC is about 53 C). A `THERMAL-PAUSE` file blocks the + step. +- A current backup of the images and the config is on the desktop + (`backup-pre-s3-20261107`, five slot-B images as flashed, `/etc` and user + config, SHA256). +- Retry count read in fastboot: 3 after `set_active b`. Every boot of a + flashed slot B spends a retry (devinfo byte 0x35 went 06 to 04 at the + first flash), and at 0 GrapheneOS wipes userdata, so I count boots and + never run more than two boots of one flash. +- No process holds `/dev/umts_boot0`; no cbd, rfsd or ModemManager runs; no + suspend. +- Each hardware step (S3, S5a, S5b, S5c, S5d, S5e) needs my explicit go in + that turn. + +Never, in any stage: cbd, rfsd, any firmware or ROM image, +`IOCTL_POWER_ON` or the boot ioctls (they write CP DRAM and there is no way +back), writes to `umts_boot0`, `allow_poweroff=1`, the `cp_on`, `cp_off` +and `atu` debugfs files, the SIM, stock slot A (its first boot can wipe +userdata), and the `efs`, `efs_backup`, `modem_userdata`, `persist`, +`modem_a` and `modem_b` partitions (read-only checks only). + +General stop rules: a hang, USB loss, an oops or an rcu stall; any UFS +counter going up or a `ufshcd_err_handler started` line that does not +recover in seconds; a pin or line reading different from what the previous +log said; battery temperature over 45 C. Never reboot with the modem lines +high: `gpio_off` first, reboot only after an all-0 read. A phone that ends +with a dead screen is not woken or rebooted; I run the dead-screen kit +first. The kit is a read-only script for a phone whose screen is off while ssh +still answers (touch and power key dead): it records while I touch and press +power in a 12 s window, and only then do I wake the screen +(`omamobile-remote wake`) and read the uptime, the DRM state and +`hyprctl monitors -j`, and ask whether the panel is lit; the case is +linux-omarchy-mobile#215. + +## S1: PCIe controller and PHY loaded, no hardware access (2026-11-07 20:47) + +What it does: boots the test kernel with `pcie_0` and its PHY enabled in the +device tree and runs `modprobe pcie-gs201-cp` with `allow_hw=0`. The module +probes and registers; it does not touch the link. + +Gates: the general ones; boot 1 of the flash checked first (plain boot up, +Wi-Fi and NFC working, no modem module loaded, 7 fixed regulators, the modem +pins at their baseline: gph1-2 an output at 0, gph1-1 and gph1-7 inputs at +0). + +Stop: the general rules; any modem pin changing. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-gc5b6ae8f4dc2`: PASS. Probe +rc 0, PMU 0x3ec4 = 0xc0 (the same as on the 9a), PHY 0/0, link 0, IRQ +counts 0, pins unchanged. + +Does not prove: that the PHY or the link work (nothing was read from them); +anything about the modem. + +## S2: modem node enabled, driver not loaded (2026-11-07 20:52) + +What it does: the same kernel with the `modem` node enabled in the device +tree. No cpif module loaded. Reads the seven AP2CP and four CP2AP lines. + +Gates and stop: as S1. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-gc5b6ae8f4dc2` (image set +images-s2; I did not copy `uname -r` into the S2 log, the set shares the +S1 build): PASS. All 7 AP2CP and 4 CP2AP lines read 0, pins equal baseline, +PMU 0xc0, clean shutdown. After it the phone went back to the NFC set. + +Does not prove: anything beyond "the node enabled changes nothing on the +pins before a driver loads". + +## S3: one PCIe link attempt with the modem off (2026-11-07 21:15, my go) + +What it does: `allow_hw=1`, PHY trace every 100 ms, exactly one +`link_up 1` try. The stock module tries three times; for this step I +rebuilt the module with `CP_LINK_TRIES` 3 to 1 (same vermagic, test only, +not committed; the original module stayed on the phone as +`/root/pcie-gs201-cp.ko.tries3`). The modem is off, so no endpoint is +expected. + +Gates: the general ones, plus the backup above, plus a review of the S1/S2 +evidence. SoC had peaked at 62 C during backups and builds, so the step +waited for every zone at 62 C or less. + +Stop: a hang; an oops; no progress in the PHY trace. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-gc5b6ae8f4dc2` (image set +images-s1, flashed again for this step; the kernel is in the S3 dmesg log): +no hang. Trace: PMU bit 0 set (SMC), first PMA read, PLL on, PMA and PCS +tables, external PLL lock 1, PLL lock 1, CDR lock 1, offset calibration +done 1, PMU bit 10 set, DBI ID 0xa5a5144d; then `no L0, LTSSM 0x0` and +`link_up 1: -110` (no endpoint). After: PMU 0x3ec4 = 0x4c1, PHY 1/0, link +0, `link_down` rc 0, 53 C, no oops, Wi-Fi up. The PCIe "active" pinctrl +state changed the function of gph0-0 (PERST, now output 0), gph0-1 +(CLKREQ), gpa0-1 (output 0 to input), gpa0-2 (input to output 0), gpa6-5 +and gpa7-0; all DAT 0; gph1-1, gph1-2 and gph1-7 untouched. +It also answered one open question: HSI1 and its PHY/controller are +reachable with only the PMU 0x3ec4 bit 0 SMC before the first access (stock +source does the same). + +Does not prove: that the PCIe link works. The AP side starts, the link +itself has never been tested, because the modem was off. Not settled: who +powers the modem, what gpa0-1 drives, the S2MPU windows for CP memory. + +## S4: cpif loaded, modem stays OFFLINE (2026-11-07 22:10) + +What it does: flashes the S4 set (cpif enabled, overlay `modem-s4-cpif`), +then `modprobe pcie-gs201-cp` (`allow_hw=0`), `modprobe shm_ipc`, +`modprobe cpif`. cpif probe sets the seven AP2CP lines as outputs at 0. +No power-on, no link, no firmware. + +Gates: the general ones, plus before the load: gph1-2 an output at 0, the +six other lines inputs at DAT 0 with PUD 0x1 (pull-down); UFS stats all 0 +and no `ufshcd_err_handler started`; no modem module, no `umts` node; 56 C. + +Stop: the general rules; any `poweron`, `link up` or phone_state line in +dmesg (the two `link up` lines at boot are the Wi-Fi's HSI2 link). + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67`: PASS. All +seven AP2CP lines are outputs at 0 (CON 0x1), the CP2AP inputs unchanged, +`modem_state` OFFLINE, PMU 0xc0, PHY 0/0, link 0, UFS counters 0 before and +60 s after, no oops, Wi-Fi up, 57 C. `shm_ipc` mapped the three reserved +regions (`cp-rmem@ea400000`, `cp-msi@f6200000`, `cp-rmem1@e8000000`) with +no fault. The probe log matches stock's values: `mif_off_during_volte:1`, +`num_iodevs:54`, `link_attrs:0x000037c8`, `PCIe Channel Number:0`, +`s5300 is created`. `cpif_probe: Failed to register logbuffer!` appears; +it is debug-log registration only and I did not look into it. The reboot +to bootloader ran cpif's shutdown path with the modem OFFLINE. + +Does not prove: who powers the modem or in what order; any way to power it +down (stock cpif has none once the modem is on); anything about firmware or +the SIM. + +## S5: power lines, in five parts + +The hook (test only, not for merge): `modem_ctrl_s5100.c` gets a debugfs +directory `cpif_test/`, created only when cpif is loaded with +`cpif_test_gpio=1`. Files: `lines` (read, the 11 line levels and +`phone_state`), `gpio_off` and `gpio_on` (any write fires them; they call +only the stock `gpio_power_off_cp` and `gpio_power_offon_cp`), and from S5c a +`pda_active` file. `gpio_on` is refused with -EBUSY unless six AP2CP lines +read 0: `cp_pwr`, `nreset`, `wakeup`, `dump_noti`, `cp_wrst_n` and +`pm_wrst_n`. `ap2cp-pda-active` is left out of that check because stock +`power_on_cp` sets it before the power-on, and S5e's E3 needs it high. No +state change, no CP memory write (`clear_boot_stage` and `init_ctrl_msg` are +skipped on purpose), no PCIe, no PMU, no ioctl. cpif has no module_exit, so +it cannot be unloaded. + +Builds: S5a and S5b ran an earlier build of the same code without the +`pda_active` file, the module kept on the phone as `/root/cpif.ko.s5a` +(sha256 `4ee11e7d01764522c5eebca5f6378439d2fc45db4decf17e1e883add0855d972`). +S5c to S5e ran the build that has it (sha256 +`f1e3173f55a07cb70685d611abfa05b004266dbfb23ed1aa0718ed57de7bbe11`). + +Edges [V] (the code is in my `soc-gs` copy; the line numbers are derekross's +from Google's s5300 tree: stock `modem_ctrl_s5100.c`, `gpio_power_off_cp()` +at 906-918 and `gpio_power_offon_cp()` at 921-933, non-`CP_WRESET_WA` branch, +confirmed compiled; `CP_WRESET_WA`, `CP_LCD_NOTIFIER` and +`LINK_DEVICE_PCIE_GPIO_WA` are not set in this build): + +- `gpio_off` from the all-0 state: one 10 ms pulse of `ap2cp-wakeup`; + `nreset`, `cp_wrst`, `cp_pwr` and `pm_wrst` are rewritten to 0 (no + change). +- `gpio_on` from all-0: that pulse, then `pm_wrst` 1, `cp_pwr` 1, `nreset` + 1, `cp_wrst` 1, 10 ms apart, about 130 ms in all. +- `gpio_off` with the lines high: wakeup pulse, `nreset` 0, `cp_wrst` 0, + `cp_pwr` 0 (30 ms), `pm_wrst` 0 (50 ms). + +Setup for each S5 stage: push the new `cpif.ko` (the S4 original kept as +`/root/cpif.ko.s4-original`), write `/etc/modprobe.d/modem-test.conf` (the +blacklist lines), flash images-s4, count 3, stream `dmesg -w` to the desktop, +repeat the S4 pre-checks, then `modprobe pcie-gs201-cp`, `shm_ipc`, +`cpif cpif_test_gpio=1`. + +Extra stop rules for S5b to S5e: `gpio_on` returning -EBUSY or -EINVAL (do +not retry, read `lines`, stop); any `IOCTL_`, `poweron`, `link up` or +`SET GPIO ... not valid` line; the modem lines on for more than 60 s in one +cycle; battery down more than 3 % in the stage; if a CP2AP line stays high +after `gpio_off`: do not write `gpio_off` again, do not write +`pda_active` = 0, do not reboot, read `lines` every 10 s for 2 minutes and +stop. + +### S5-0: read only (2026-11-07 22:25) + +`cat cpif_test/lines`: all 11 lines read 0, `phone_state` 0. No write. +Kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67` (`modem-s5-pre.txt`; this +read did not print `uname -r` again). That checks the read path and the +module parameter. It does not show that a later power-on is safe. + +### S5a: gpio_off from the all-0 state (2026-11-07 22:25:50, my go) + +This is the hook run (one write to `gpio_off` from the all-0 state). The +earlier note that S5a was NO-GO meant the pre-hook plan: cpif has no +software power-off, and `IOCTL_POWER_ON` writes CP DRAM. That plan was not +run. This result is only the hook's `gpio_off`. + +What it does: one write to `gpio_off` with everything at 0, to see whether the +way down runs from the all-0 state and leaves the lines at 0. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67`: PASS. The +log shows the 10 ms wakeup pulse and `nreset`, `cp_wrst`, `cp_pwr` and +`pm_wrst` rewritten to 0 as duplicates; "after" all 0; 60 s later all 0, +OFFLINE, UFS counters 0, no error handler start, no oops, Wi-Fi up, 57 C, +battery 92 %. + +Does not prove: that `gpio_off` is safe with the modem on (that is only +shown in S5b). + +### S5b: first power-on of the lines (2026-11-07 22:34:12, separate go, charger in) + +What it does: `/root/s5b.sh` on the phone: one `gpio_on`, one sample per +second of `lines` for 55 s, then `gpio_off`, then samples. `pda_active` +stays at 0 (the hook cannot set it yet). + +Stop: the general rules and the S5 rules; `gpio_off` at 55 s whatever +happened. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67` (S4 image set; +the S5b log itself does not print `uname -r`): the edges came in stock +order, 10 ms apart. For the 55 s the four AP2CP power lines read 1 and all +four CP2AP lines (`ps_hold`, `wakeup`, `cp_active`, `cp_wrst`) stayed 0; +`phone_state` OFFLINE; UFS 0 before, during and after; battery 92 %, +battery 35.8 to 36.1 C; no oops, no hang. After `gpio_off` all 11 lines 0, +57 C, Wi-Fi up. (My sleeps were shorter than the labels in the script +output; the tail covered about 20 s, and a check at 22:37 read all 0.) + +Does not prove: that the modem has no power. Stock `power_on_cp` sets +`ap2cp-pda-active` to 1 and `dump-noti` to 0 right before the power-on and +clears the shared-memory control blocks (stock `modem_ctrl_s5100.c`: +`clear_boot_stage()` called at 1000, and the `ap2cp-pda-active`/`dump-noti` +pair and the two `init_ctrl_msg()` calls in `power_on_cp()` at 1022-1027); +S5b did neither. Current was not measured. + +### S5c: S5b again with pda_active = 1 and current sampling (2026-11-07 22:44, my go) + +What it does: `/root/s5c.sh` (hook with the `pda_active` file): 30 s +baseline of lines, UFS, battery `current_now`, `current_avg` and voltage; +`pda_active` = 1; one `gpio_on`; 1 s samples; `gpio_off`; `pda_active` = 0 +only if all four CP2AP lines read 0. Built-in aborts to `gpio_off`: any UFS +counter or error handler start, battery over 45 C, `current_now` more than +300 mA below the baseline. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67`: ended by its +own abort after 24 s (one `current_now` sample at -303 mA against a 117 mA +baseline mean); `gpio_off`, `pda_active` = 0. All four CP2AP lines read 0 +in every sample; UFS 0 throughout; no oops; clean end state. A no-write +control run with the same music playing and the charger in showed the same +kind of slide (`current_avg` from +170 mA to about 0, one -377 mA sample), +so the current figures of S5b and S5c are inconclusive. + +Does not prove: anything about the modem's current draw. The charger +(holding 92 %) can feed the rail, and music was playing. From here on the +abort rule uses a median of 5 or more samples and the current runs are +battery-only. + +### S5d: battery-only current around the power-on (2026-11-07 22:58:17, my go) + +What it does: `/root/s5d.sh`, USB cable out, music off, screen off, ssh +over Wi-Fi after an identity check (model and exact test kernel). Phase A +150 s with no writes; phase B `pda_active` = 1 then one `gpio_on` +(23:00:51), 60 s, median-of-5 abort (UFS error, battery over 45 C, or a +5-sample median more than 300 mA below the baseline median); `gpio_off`, +`pda_active` = 0 if the CP2AP lines are 0; phase C 120 s no writes; phase D +120 s no-write control. Battery 92 % at 38.1 C, SoC 59 C. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67` (S4 image set; +the identity check before the run read it, but the S5d log itself does not +print `uname -r`): ran the full 60 s (no abort). Median `current_now` per phase: A -550.6 mA, B -615.9 mA, +C -556.3 mA, D -554.7 mA (negative = discharge). The three no-write phases +agree within about 10 mA; the power-on phase is about 60 to 65 mA deeper (62 against the mean of A, C +and D), with a +sharp start at the `gpio_on` write and a sharp return after `gpio_off`. All +four CP2AP lines 0 in every sample; UFS 0; battery 38.1 to 37.1 C. + +Does not prove: that the load is the modem. `pda_active` = 1 was written +immediately before `gpio_on` (back-to-back writes in the script, no timing +recorded), so the two cannot be split; it is one run; +the CP2AP lines never moved. `s5d.sh` has no signal trap, so a killed +script would not have switched the lines off by itself. + +### S5e: pda_active separated from gpio_on (2026-11-07 23:12:35, battery only) + +What it does: `/root/s5e.sh` (v3, with INT, TERM and HUP trapped into a +safe off, started with `nohup setsid`), USB out, screen off. Phases: A +baseline 90 s | E1 `pda_active` = 1 alone 30 s | B base 60 s | E2 `gpio_on` +with `pda_active` low 60 s | C base | E3 `pda_active` = 1 then `gpio_on` +60 s | D base | E1b replicate of E1 30 s | E base. The script had a +simulated four-case test before the run. + +Result [V], kernel `7.3.0-rc6-omamobile-push1-g6a203e4b8a67` (S4 image +set; the log does not print `uname -r`): no phase hit a stop; UFS 0 and all +four CP2AP lines 0 in every sample; clean end state. Median `current_now` (as printed by the script): +A -556.6 mA, E1 -541.3, B -561.3, E2 -607.2, C -550.9, E3 -611.6, D -560.6, +E1b -546.9, E -548.1. `pda_active` alone does not change the current (E1 +is about 18 mA less discharge than the mean of A and B and E1b about 8 mA +less than the mean of D and E: noise). `gpio_on` draws about 51 mA extra with `pda_active` low (E2 against +the mean of B and C) and about 56 mA with it high (E3 against C and D); S5d +measured about 60 to 65 mA. The step starts one sample after each `gpio_on` write +and ends one sample after `gpio_off`, all three times. Medians only: the +screen woke during two baseline phases (about 9 s in B, about 11 s in D right +after the E3 `gpio_off`; S5d had the same shape once in C), which makes the +means unreliable but sits against the effect, not for it. + +Does not prove: that the load is the S5300. It could be another load on the +same rail, a power stage or level shifters with no modem core behind them, +or the ROM idling. The CP ROM gave no sign of life on any CP2AP line. +Two battery-only runs, three power-on phases, one phone and one gauge. + +## Current state: on hold + +- S3, S4, S5a, S5b, S5c, S5d and S5e ran after my question on + omarchy-mobile#472 (2026-11-07 18:04 UTC) and before any answer to it. + So the hold now covers S6 and any repeat, but it came too late for S3 to + S5e, which should have waited as well. +- No further modem step and no power-line step on the 8 Pro until derekross + answers the question on omarchy-mobile#472 + (https://github.com/derekross/omarchy-mobile/pull/472#issuecomment-6711065625); + his instruction to wait is on linux-omarchy-mobile#187. +- The hook is on the branch `husky-modem-cpif-test-hook` of + Somnius/linux-omarchy-mobile (commit 058a439b3). It is test only and not + for merge. +- `tools/nv-backup --check` on 2026-11-08: `efs`, `efs_backup`, + `modem_userdata`, `persist`, `modem_a`, `modem_b`, `trusty_persist` and + `trusty_userdata` are SAME as the 2026-11-01 10:01 backup. `devinfo` is + different, as expected (the retry bit and boot counts change with every + flash). +- Leftovers on the phone (checked 2026-11-08 at 21:40 local): `/etc/modprobe.d/` + has no `modem-test.conf`; the folder holds only `hid_apple.conf` and + `omamobile-aoc-blacklist.conf`, neither from the modem tests (the AoC one + is dated 2026-11-05 and does not shadow a packaged file). The test + `cpif.ko` is still inside the two test module trees (`...gc5b6ae8f4dc2` + and `...g6a203e4b8a67`) and as `/root/cpif.ko.s5a` and + `/root/cpif.ko.s4-original`; the normal NFC set's tree has none, so a + normal boot loads none of it. +- What ran is in this folder: the overlays `overlays/modem-s1-link.dtso` + (`pcie_0` and `pcie_0_phy` on), `overlays/modem-s2-lines.dtso` (S1 plus the + `modem` child of `pcie_0`) and `overlays/modem-s4-cpif.dtso` (the controller + on, its `modem` child off, and `/cp-shmem` and `/cpif` on), and the scripts + `bringup/s5b.sh`, `s5c.sh`, `s5c-control.sh`, `s5d.sh` and `s5e.sh`, as they + ran (two comment lines were added at the top of each: an SPDX line and a note). The headers of the overlays now point at this file; nothing else in them changed. `bringup/s5e.sh` is the version the S5e result + above describes, with INT, TERM and HUP trapped into a safe off (its own + header still says v2). The S3 module change was one line: `CP_LINK_TRIES` from 3 + to 1 in `pcie-gs201-cp`, test only, not committed. +- The phone is on the normal NFC image set. The first revert boot on + 2026-11-07 had no drivers because a clean-up timer had deleted the + module folder; I fixed it by hand between 23:26 and 23:35 and checked the module + tree before every revert since. +- Not run, and not to be run before the answer: S6 (the same power-on plus + one `link_up` try with the modem powered), a PMIC power-meter reading of + the modem channel, repeats of the S5 power-ons for more statistics. +- When S6 comes, each step gets an Expect line, a rollback and a risk level + as well as its stop rules, and the NV check runs first. + +## Unknowns + +- Whether the 50 to 65 mA is the modem [I]. A control that would split it: + not available without a way to see the CP side (S6 or the power meter). +- Which rail the lines switch. The stock husky DT has no regulator or + consumer named cp, modem, rfic, rf, lte, 5g, sub6, vdd_cp or qlink [V]; + `cp_pwr_on` and `pm_wrst_n` are plain pinctrl there, so the rail is + unknown. The only modem-named items are PMIC power-meter sense channels + (`VSYS_PWR_MODEM`, `VSYS_PWR_RFFE`, `VSYS_PWR_MMWAVE`), which suggests the + modem runs from VSYS [I, from the DT only]. The PCIe0 rails are S2MPG14 + LDO16M and LDO18M, which our driver does not cover. +- Whether the CP ROM waits for the shared-memory control blocks or for the + PCIe link before any CP2AP line moves [I]. Stock `power_on_cp` writes + `clear_boot_stage` and `init_ctrl_msg` before the lines; the hook skips + that on purpose. `cp2ap_cp_wrst_n` (gpa0-1) is high while the CP is alive + in stock logic and stayed 0 here; whether it rises before PCIe training + is unknown. Source reading, then S6, would settle it. +- What the bootloader does with the modem lines on a forced reboot or a + hang. Nothing in my notes covers it. A hung kernel needs Power + Volume Up + held for 15 to 30 s, and the debugfs hook exists only while the test + module is loaded. +- Whether a power-off edge triggers the UFS error pass on husky (it did on + cheetah). S5b, S5c, S5d and S5e saw none. +- The husky modem image and partition mapping, the BAR and doorbell layout, + and who sets up the S2MPU windows for CP memory. diff --git a/device/husky/NOTES.md b/device/husky/NOTES.md index 36010a1fa..24e28abff 100644 --- a/device/husky/NOTES.md +++ b/device/husky/NOTES.md @@ -10,6 +10,20 @@ Sources: - `P/`: postmarketOS pmaports `device/testing` (2026-10-21). - `G/`: Google's GPL kernel for this phone, `android-gs-shusky-6.1-android16` ([source.android.com: Build Pixel kernels](https://source.android.com/docs/setup/build/building-pixel-kernels)). +## 2026-11-08: a third phone: Samsung 128 GB, UFS 3.1, still locked + +A third retail Pixel 8 Pro, offered in [#1](https://github.com/derekross/omarchy-mobile/issues/1). `R3/` below means read-only queries of this phone (`adb shell getprop` while booted, `fastboot getvar all` on the locked bootloader), facts only, no serial, IMEI or MACs. Nothing has been unlocked, flashed or booted on it yet. + +- **Identity** [V] (R3/): `husky`, `hw-revision` `MP1.0`, SKU G1MNW, `ro.boot.dtbo_idx` 8, `secure-boot:PRODUCTION`. The SKU and the storage vendor and size are the first phone's. +- **Storage** [V] (R3/ getvar): `storage-vendor:SAMSUNG`, `storage-model:KLUDG4UHGC-B0E1`, `storage-capacity:128 GB`, `storage-protocol:3.1`, `storage-rev:3203`, `storage-power-mode:lanes=2 gear=4 mode=FAST hs_series=SERIES_B`. +- **Starting state** [V] (R3/): GrapheneOS `2026110201`, the security preview of `2026110200` (`CP3A.261005.005`, security patch 2026-11-01), bootloader locked with its own verified boot key (`verifiedbootstate` yellow). Current slot a with `slot-successful:a:yes`, and `slot-unbootable:b:yes`, `slot-fastboot-ok:b:no`, retry count 2 on both: the second phone's starting state with the slots swapped. That is probably what GrapheneOS's 2026-11-06 update left behind (Virtual A/B, once the update merged) [I]. Its updater reported "Device is up-to-date" before the reboot to the bootloader. +- **Patch level** [V] (R3/, `device.conf`): GrapheneOS's security patch, 2026-11-01, is newer than the 2026-10-05 our husky images carry (`AVB_SECURITY_PATCH=2026-10-05`, `OS_PATCH_LEVEL=2026-10`). The second phone started at 2026-10-05, the same as our images, so it didn't meet this. Whether booting the older patch level on slot B matters to the bootloader or Trusty once unlocked is not known [I]. +- **Bootloader and modem** [V] (R3/ getvar): `ripcurrent-17.0-15681527` and baseband `g5300i-260604-260807-B-16036236`, both as on the second phone; anti-rollback `ap-ar-ns`, `ap-ar-s`, `gsa-bl1-ar` and `gsa-fw-ar` all 3; `unlocked:no`, `off-mode-charge:1`. +- **Partitions** [V] (R3/ getvar): `boot`, `vendor_boot` and `vendor_kernel_boot` 64 MiB, `init_boot` 8 MiB, `dtbo` 16 MiB, `modem` 200 MiB, `efs` 64 MiB, `persist` 128 MiB, `super` 7.95 GiB and `userdata` 117,744,685,056 bytes, all as on the first phone. +- **OEM unlocking** [V]: allowed in Developer options (switched on, not greyed out). No SIM (`gsm.sim.state` `ABSENT`). +- **GrapheneOS cuts USB data while the phone is locked** [V]: after `fastboot reboot`, no USB device showed up on the host until the phone was unlocked with its PIN; adb was back at once after that. Expect to unlock it after each reboot into GrapheneOS. Which of its USB-C port settings does this was not checked [I]. +- **fastbootd** [V]: `fastboot reboot fastboot` on the locked phone reached fastbootd (`is-userspace:yes`), and `fastboot reboot` from there went back to GrapheneOS on slot a. + ## 2026-11-05: idle-state and power-domain overlays that reboot-looped the phone Lef's phone (Kioxia unit), slot B, while looking for the cause of a ~520 mA idle draw with the screen off. I tested two bring-up overlays; every kernel flashed with either of them reset the phone hard about 8 to 40 s after boot (no pstore, no panic text). My first note called the idle-state boot stable; it was not (the temperature log stopped after a minute and I had already flashed the next build). diff --git a/device/husky/ROADMAP.md b/device/husky/ROADMAP.md index acbe4a867..93e86a9b4 100644 --- a/device/husky/ROADMAP.md +++ b/device/husky/ROADMAP.md @@ -81,7 +81,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better. - Which microphone id is which hole, and what do the earpiece and headset paths need (#450, #453)? - Why does the phone draw about 0.5 A idle with the screen off, and why did the CPU idle-state and power-domain overlays reboot-loop it? Not known; no measurement plan yet. - In which file shape should the zuma System MMU v9 code and the AoC core port go (asked on #1)? -- Marking slot B successful (a `devinfo` write): decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252) (2026-11-07). It is a manual, attended step, once per install of a smoke-tested image, never from a unit, with per-phone layout evidence first. The boot LUNs get the whole-disk node removed and each partition's own flag set first (its own PR, booted on the maintainer's Pixel 7 Pro), then the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)). Until both are in nothing marks slot B on the 8 Pro: flash a known-good set before the boot that would use B's last try, and count every deliberate reset as a boot. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. +- Marking slot B successful (a `devinfo` write): decided on [#252](https://github.com/derekross/omarchy-mobile/issues/252) (2026-11-07). It is a manual, attended step, once per install of a smoke-tested image, never from a unit, with per-phone layout evidence first. The boot LUNs get the whole-disk node removed and each partition's own flag set first (its own PR, booted on the maintainer's Pixel 7 Pro), then the marking tool ([#483](https://github.com/derekross/omarchy-mobile/pull/483)). Until both are in nothing marks slot B on the 8 Pro: flash a known-good set before the boot that would use B's last try, and count every deliberate reset as a boot. On Lef's phone a local unit marked it from 2026-11-01 to 2026-11-07, after it ran out of retries once; stopped pending #252. On Lef's phone slot B stayed marked (`devinfo` byte 0x35 read `06`) from the unit's last write until the first flash after the unit was masked on 2026-11-07, when it read `04`. Since then, about a dozen flashes on 2026-11-07 (each followed by `fastboot set_active b`; a `flash`, which also sets B active, clears the bit) have read `slot-retry-count:b` as 3 after `set_active` and 2 after one boot, so a boot spends one of B's tries and the flash-before-the-last-try routine above applies. `slot-successful:b` was not read after those flashes, so "cleared" rests on the retry count and byte 0x35, not on the bootloader's own answer. The bit is not cleared by hand: that would be a `devinfo` write too. - Does touch survive a long idle with the screen off? One 12 h idle on 2026-11-04 left only Power working; not reproduced, not cause-checked. ## Credits and sources diff --git a/device/husky/bringup/s5b.sh b/device/husky/bringup/s5b.sh new file mode 100755 index 000000000..25bc84de6 --- /dev/null +++ b/device/husky/bringup/s5b.sh @@ -0,0 +1,18 @@ +#!/bin/sh +# SPDX-License-Identifier: MIT +# Test only, as run on the 8 Pro on 2026-11-07 (see device/husky/MODEM-PLAN.md); this note and the SPDX line are the only changes. +L=/sys/kernel/debug/cpif_test; U=/sys/kernel/debug/ufshcd/13200000.ufs/stats; O=/root/s5b.log +: > $O +snap() { echo "$(date +%T.%N | cut -c1-12) $1 $(awk '{printf "%s=%s ",$1,$2}' $L/lines) ufs=$(grep -vc ': 0$' $U) errh=$(dmesg | grep -c 'ufshcd_err_handler started') bat=$(cat /sys/class/power_supply/*battery*/capacity)% bt=$(cat /sys/class/power_supply/*battery*/temp)" >> $O; } +snap pre +echo 1 > $L/gpio_on; echo "gpio_on rc=$?" >> $O +i=0 +while [ $i -lt 55 ]; do + sleep 1; i=$((i+1)); snap "on+$i" + if [ "$(grep -vc ': 0$' $U)" != 0 ]; then echo "STOP-UFS-COUNTER" >> $O; break; fi +done +echo 1 > $L/gpio_off; echo "gpio_off rc=$?" >> $O +for t in 1 5 10 30 60; do + sleep $([ $t = 1 ] && echo 1 || echo 5); snap "off+$t" +done +echo DONE >> $O diff --git a/device/husky/bringup/s5c-control.sh b/device/husky/bringup/s5c-control.sh new file mode 100755 index 000000000..272b973fc --- /dev/null +++ b/device/husky/bringup/s5c-control.sh @@ -0,0 +1,14 @@ +#!/bin/sh +# SPDX-License-Identifier: MIT +# Test only, as run on the 8 Pro on 2026-11-07 (see device/husky/MODEM-PLAN.md); this note and the SPDX line are the only changes. +# CONTROL for S5c: the same 30 s + 55 s + 30 s sampling, NO writes to any modem line. Log: /root/s5c-control.log +L=/sys/kernel/debug/cpif_test; U=/sys/kernel/debug/ufshcd/13200000.ufs/stats; O=/root/s5c-control.log +B=/sys/class/power_supply/max170xx_battery +: > $O +snap() { echo "$(date +%T.%N | cut -c1-12) $1 cur=$(cat $B/current_now) avg=$(cat $B/current_avg) v=$(cat $B/voltage_now) bat=$(cat $B/capacity)% bt=$(cat $B/temp) ufs=$(grep -vc ': 0$' $U) lines=$(awk '{s+=$2} END {print s+0}' $L/lines)" >> $O; } +i=0; while [ $i -lt 30 ]; do snap "base-$i"; sleep 1; i=$((i+1)); done +snap "pda1(none)" +i=0; while [ $i -lt 55 ]; do sleep 1; i=$((i+1)); snap "on+$i(none)"; done +sleep 2; snap "off+2(none)" +for t in 3 8 13 18 23 28; do sleep 5; snap "post+$t(none)"; done +echo DONE >> $O diff --git a/device/husky/bringup/s5c.sh b/device/husky/bringup/s5c.sh new file mode 100755 index 000000000..fd15e7eee --- /dev/null +++ b/device/husky/bringup/s5c.sh @@ -0,0 +1,37 @@ +#!/bin/sh +# SPDX-License-Identifier: MIT +# Test only, as run on the 8 Pro on 2026-11-07 (see device/husky/MODEM-PLAN.md); this note and the SPDX line are the only changes. +# S5c (TEST ONLY): pda_active=1, then gpio_on once, 55 s of 1 s samples, gpio_off, pda_active=0 only if the CP side is quiet. +# Runs ON the phone so the power-off happens even if ssh drops. Log: /root/s5c.log +L=/sys/kernel/debug/cpif_test; U=/sys/kernel/debug/ufshcd/13200000.ufs/stats; O=/root/s5c.log +B=$(ls -d /sys/class/power_supply/*battery* | head -1) +: > $O +cp2ap() { awk '/^CP2AP_/ {s+=$2} END {print s+0}' $L/lines; } +ufsbad() { [ "$(grep -vc ': 0$' $U)" != 0 ] || [ "$(dmesg | grep -c 'ufshcd_err_handler started')" != 0 ]; } +snap() { echo "$(date +%T.%N | cut -c1-12) $1 $(awk '{printf "%s=%s ",$1,$2}' $L/lines | sed 's/AP2CP_//g;s/CP2AP_/c2a_/g') ufs=$(grep -vc ': 0$' $U) cur=$(cat $B/current_now) avg=$(cat $B/current_avg 2>/dev/null) v=$(cat $B/voltage_now) bat=$(cat $B/capacity)% bt=$(cat $B/temp)" >> $O; } +# 30 s baseline at the same cadence +i=0; while [ $i -lt 30 ]; do snap "base-$i"; sleep 1; i=$((i+1)); done +BASE=$(awk '/ base-/ {for(i=1;i<=NF;i++) if ($i ~ /^cur=/) {sub("cur=","",$i); s+=$i; n++}} END {printf "%d", s/n}' $O) +echo "baseline cur=$BASE uA" >> $O +echo 1 > $L/pda_active; echo "pda_active=1 rc=$?" >> $O; snap "pda1" +echo 1 > $L/gpio_on; RC=$?; echo "gpio_on rc=$RC" >> $O +STOP="" +if [ $RC = 0 ]; then + i=0 + while [ $i -lt 55 ]; do + sleep 1; i=$((i+1)); snap "on+$i" + ufsbad && { STOP="UFS"; break; } + BT=$(cat $B/temp); [ "$BT" -gt 450 ] && { STOP="BATTEMP"; break; } + CUR=$(cat $B/current_now); [ $((BASE - CUR)) -gt 300000 ] && { STOP="CURRENT"; break; } + done +fi +echo "STOPREASON=${STOP:-none-at-55s}" >> $O +echo 1 > $L/gpio_off; echo "gpio_off rc=$?" >> $O +sleep 2; snap "off+2" +if [ "$(cp2ap)" = 0 ]; then + echo 0 > $L/pda_active; echo "pda_active=0 rc=$?" >> $O +else + echo "CP2AP STILL HIGH after gpio_off: pda_active NOT lowered, do not reboot" >> $O +fi +for t in 3 8 13 18 23 28; do sleep 5; snap "post+$t"; done +echo DONE >> $O diff --git a/device/husky/bringup/s5d.sh b/device/husky/bringup/s5d.sh new file mode 100755 index 000000000..f7ff5759c --- /dev/null +++ b/device/husky/bringup/s5d.sh @@ -0,0 +1,35 @@ +#!/bin/sh +# SPDX-License-Identifier: MIT +# Test only, as run on the 8 Pro on 2026-11-07 (see device/husky/MODEM-PLAN.md); this note and the SPDX line are the only changes. +# S5d (TEST ONLY): battery-only current measurement around the modem power-on. Runs ON the phone; log /root/s5d.log. +# Phases: A baseline 150 s (no writes) -> B pda_active=1 + gpio_on, 60 s (median-of-5 abort) -> gpio_off, pda_active=0 if CP2AP quiet +# -> C post 120 s -> D control 120 s (no writes). 1 s samples of current_now/current_avg/voltage. +L=/sys/kernel/debug/cpif_test; U=/sys/kernel/debug/ufshcd/13200000.ufs/stats; O=/root/s5d.log; B=/sys/class/power_supply/max170xx_battery +: > $O +cp2ap() { awk '/^CP2AP_/ {s+=$2} END {print s+0}' $L/lines; } +ufsbad() { [ "$(grep -vc ': 0$' $U)" != 0 ] || [ "$(dmesg | grep -c 'ufshcd_err_handler started')" != 0 ]; } +snap() { echo "$(date +%T) $1 cur=$(cat $B/current_now) avg=$(cat $B/current_avg) v=$(cat $B/voltage_now) bt=$(cat $B/temp) c2a=$(cp2ap) ufs=$(grep -vc ': 0$' $U)" >> $O; } +med5() { tail -5 $O | sed 's/.* cur=\([-0-9]*\) .*/\1/' | sort -n | sed -n 3p; } +phase() { n=$1; tag=$2; i=0; while [ $i -lt $n ]; do snap "$tag-$i"; sleep 1; i=$((i+1)); done; } +phase 150 A +BASEMED=$(sed -n '/ A-/p' $O | tail -60 | sed 's/.* cur=\([-0-9]*\) .*/\1/' | sort -n | awk '{a[NR]=$1} END {print a[int((NR+1)/2)]}') +echo "BASELINE_MEDIAN_cur=$BASEMED uA" >> $O +echo 1 > $L/pda_active; echo "pda_active=1 rc=$?" >> $O +echo 1 > $L/gpio_on; RC=$?; echo "gpio_on rc=$RC" >> $O +STOP="" +if [ $RC = 0 ]; then + i=0 + while [ $i -lt 60 ]; do + sleep 1; i=$((i+1)); snap "B-$i" + ufsbad && { STOP="UFS"; break; } + [ "$(cat $B/temp)" -gt 450 ] && { STOP="BATTEMP"; break; } + if [ $i -ge 5 ]; then M=$(med5); [ $((BASEMED - M)) -gt 300000 ] && { STOP="CURRENT_MEDIAN"; break; }; fi + done +fi +echo "STOPREASON=${STOP:-none-at-60s}" >> $O +echo 1 > $L/gpio_off; echo "gpio_off rc=$?" >> $O +sleep 2; snap "off+2" +if [ "$(cp2ap)" = 0 ]; then echo 0 > $L/pda_active; echo "pda_active=0 rc=$?" >> $O; else echo "CP2AP STILL HIGH: pda_active NOT lowered, do not reboot" >> $O; fi +phase 120 C +phase 120 D +echo DONE >> $O diff --git a/device/husky/bringup/s5e.sh b/device/husky/bringup/s5e.sh new file mode 100755 index 000000000..70c82cb2c --- /dev/null +++ b/device/husky/bringup/s5e.sh @@ -0,0 +1,71 @@ +#!/bin/sh +# SPDX-License-Identifier: MIT +# Test only, as run on the 8 Pro on 2026-11-07 (see device/husky/MODEM-PLAN.md); this note and the SPDX line are the only changes. +# S5e v2 (TEST ONLY): battery-only current, isolating pda_active from gpio_on. Run as: nohup setsid sh /root/s5e.sh & Log: /root/s5e.log +# A 90 s base | E1 pda_active ALONE 30 s | B 60 s | E2 gpio_on, pda LOW 60 s | C 60 s | E3 pda=1 then gpio_on 60 s | D 60 s | E1b (replicate) 30 s | E 60 s +# Fixes after review: trap (safe_off on INT/TERM/HUP), abort ends the run, CP2AP-high stops, pda verified low before powered steps, +# UFS error count compared to the count at start, tighter E1 rule (150 mA), screen state in every sample, per-phase medians at the end. +L=/sys/kernel/debug/cpif_test; U=/sys/kernel/debug/ufshcd/13200000.ufs/stats; O=/root/s5e.log; B=/sys/class/power_supply/max170xx_battery +: > $O +N0=$(dmesg | grep -c 'ufshcd_err_handler started') +ABORT="" +hw() { echo "$2" > $L/$1; } +cp2ap() { awk '/^CP2AP_/ {s+=$2} END {print s+0}' $L/lines; } +ap2cp() { awk '/^AP2CP_/ {s+=$2} END {print s+0}' $L/lines; } +pda() { awk '/^AP2CP_AP_ACTIVE/ {print $2}' $L/lines; } +ufsbad() { [ "$(grep -vc ': 0$' $U)" != 0 ] || [ "$(dmesg | grep -c 'ufshcd_err_handler started')" != "$N0" ]; } +snap() { echo "$(date +%T) $1 cur=$(cat $B/current_now) avg=$(cat $B/current_avg) v=$(cat $B/voltage_now) bt=$(cat $B/temp) c2a=$(cp2ap) a2c=$(ap2cp) pda=$(pda) ufs=$(grep -vc ': 0$' $U) bl=$(cat /sys/class/backlight/*/bl_power | head -1)" >> $O; } +med5() { tail -5 $O | sed 's/.* cur=\([-0-9]*\) .*/\1/' | sort -n | sed -n 3p; } +phase() { n=$1; tag=$2; i=0; while [ $i -lt $n ]; do snap "$tag-$i"; sleep 1; i=$((i+1)); done; } +safe_off() { + hw gpio_off 1; echo "gpio_off rc=$?" >> $O; sleep 2; snap "off+2" + if [ "$(cp2ap)" = 0 ]; then hw pda_active 0; echo "pda_active=0 rc=$?" >> $O + else echo "CP2AP STILL HIGH: pda_active NOT lowered, do not reboot" >> $O; ABORT="CP2AP_HIGH"; fi + [ "$(pda)" = 0 ] || [ "$ABORT" = "CP2AP_HIGH" ] || ABORT="PDA_NOT_LOW" +} +trap 'echo TRAP >> $O; safe_off; echo ABORTED-BY-SIGNAL >> $O; exit 1' INT TERM HUP +# powered TAG SECONDS THRESHOLD_uA : the enabling write(s) were done by the caller +powered() { tag=$1; n=$2; th=$3; STOP=""; i=0 + while [ $i -lt $n ]; do sleep 1; i=$((i+1)); snap "$tag-$i" + ufsbad && { STOP=UFS; break; } + [ "$(cat $B/temp)" -gt 450 ] && { STOP=BATTEMP; break; } + if [ $i -ge 5 ]; then M=$(med5); [ $((BASEMED - M)) -gt $th ] && { STOP=CURRENT_MEDIAN; break; }; fi + done + echo "STOPREASON($tag)=${STOP:-none-at-${n}s}" >> $O; [ -n "$STOP" ] && ABORT="$tag:$STOP"; } +finish() { phase 30 Z; echo "ABORTED=$ABORT" >> $O; summary; echo DONE >> $O; exit 1; } +summary() { echo "--- per-phase median cur (uA) and n" >> $O + for ph in A E1 B E2 C E3 D E1b E; do grep -E "^[0-9:]+ $ph-[0-9]+ " $O | sed 's/.* cur=\([-0-9]*\) .*/\1/' | sort -n | awk -v ph=$ph '{a[NR]=$1} END { if (NR) printf "%s median=%d n=%d\n", ph, a[int((NR+1)/2)], NR }' >> $O; done; } +echo "start: bl=$(cat /sys/class/backlight/*/bl_power | head -1) N0=$N0 status=$(cat $B/status)" >> $O +[ "$(cat $B/status)" = "Discharging" ] || { echo "NOT DISCHARGING: refusing" >> $O; ABORT=START_STATUS; finish; } +[ "$(cat $B/temp)" -le 450 ] || { echo "BATTERY HOT: refusing" >> $O; ABORT=START_TEMP; finish; } +[ "$(ap2cp)$(cp2ap)" = "00" ] || { echo "LINES NOT ALL 0: refusing" >> $O; ABORT=START_LINES; finish; } +ufsbad && { echo "UFS NOT CLEAN: refusing" >> $O; ABORT=START_UFS; finish; } +phase 90 A +BASEMED=$(sed -n '/ A-/p' $O | tail -60 | sed 's/.* cur=\([-0-9]*\) .*/\1/' | sort -n | awk '{a[NR]=$1} END {print a[int((NR+1)/2)]}') +echo "BASELINE_MEDIAN_cur=$BASEMED uA" >> $O +[ "$(pda)" = 0 ] || { echo "pda not low at start" >> $O; ABORT=START; finish; } +# E1: pda_active alone (tight rule 150 mA) +hw pda_active 1; echo "E1 pda_active=1 rc=$?" >> $O +if [ "$(pda)" = 1 ] && [ "$(ap2cp)" = 1 ]; then powered E1 30 150000; else echo "E1 READBACK MISMATCH" >> $O; ABORT="E1:READBACK"; fi +hw pda_active 0; echo "E1 pda_active=0 rc=$?" >> $O; [ -z "$ABORT" ] || finish +[ "$(pda)" = 0 ] || { ABORT="PDA_NOT_LOW_AFTER_E1"; finish; } +phase 60 B +# E2: gpio_on with pda low +[ "$(pda)" = 0 ] || { ABORT="PDA_NOT_LOW_BEFORE_E2"; finish; } +hw gpio_on 1; RC=$?; echo "E2 gpio_on(pda low) rc=$RC" >> $O +if [ "$(ap2cp)" = 4 ] && [ "$(pda)" = 0 ]; then powered E2 60 400000; else echo "E2 READBACK MISMATCH (ap2cp=$(ap2cp) pda=$(pda))" >> $O; ABORT="E2:READBACK"; fi +safe_off; [ -z "$ABORT" ] || finish +phase 60 C +# E3: pda_active then gpio_on (the S5d order) +hw pda_active 1; echo "E3 pda_active=1 rc=$?" >> $O +hw gpio_on 1; RC=$?; echo "E3 gpio_on rc=$RC" >> $O +if [ "$(ap2cp)" = 5 ] && [ "$(pda)" = 1 ]; then powered E3 60 400000; else echo "E3 READBACK MISMATCH (ap2cp=$(ap2cp) pda=$(pda))" >> $O; ABORT="E3:READBACK"; fi +safe_off; [ -z "$ABORT" ] || finish +phase 60 D +# E1b: replicate of E1 +hw pda_active 1; echo "E1b pda_active=1 rc=$?" >> $O +if [ "$(pda)" = 1 ] && [ "$(ap2cp)" = 1 ]; then powered E1b 30 150000; else echo "E1b READBACK MISMATCH" >> $O; ABORT="E1b:READBACK"; fi +hw pda_active 0; echo "E1b pda_active=0 rc=$?" >> $O; [ -z "$ABORT" ] || finish +phase 60 E +summary +echo DONE >> $O diff --git a/device/husky/overlays/modem-s1-link.dtso b/device/husky/overlays/modem-s1-link.dtso new file mode 100644 index 000000000..52ddf557e --- /dev/null +++ b/device/husky/overlays/modem-s1-link.dtso @@ -0,0 +1,21 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* + * Modem link bring-up, stage S1, never default (device/husky/ + * MODEM-PLAN.md): turns on the modem PCIe controller node + * (pcie_0, ch0) and its PHY (pcie_0_phy) and nothing else. The `modem` + * child stays disabled, so the controller driver takes no modem line, and + * the pins are not touched (pcie_0 has only an "active" pinctrl state, which + * only link_up selects). Both drivers only map their registers at probe. + * The controller module is blacklisted and loaded by hand after the boot. + * The modem power lines are not described as enabled anywhere in this file. + */ +/dts-v1/; +/plugin/; + +&pcie_0_phy { + status = "okay"; +}; + +&pcie_0 { + status = "okay"; +}; diff --git a/device/husky/overlays/modem-s2-lines.dtso b/device/husky/overlays/modem-s2-lines.dtso new file mode 100644 index 000000000..d91aa0586 --- /dev/null +++ b/device/husky/overlays/modem-s2-lines.dtso @@ -0,0 +1,24 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* + * Modem link bring-up, stage S2, never default (device/husky/ + * MODEM-PLAN.md): S1 (pcie_0 and pcie_0_phy) plus the `modem` + * child of pcie_0, so the controller driver requests the eleven modem lines + * as the bootloader left them (GPIOD_ASIS: no direction or level change at + * probe). Only the debugfs `status` file reads them. There is no cpif node + * (samsung,exynos-cp) in the tree, so cpif and shm_ipc cannot bind and must + * not be loaded. No pin state is selected and no line is driven by hand. + */ +/dts-v1/; +/plugin/; + +&pcie_0_phy { + status = "okay"; +}; + +&pcie_0 { + status = "okay"; + + modem { + status = "okay"; + }; +}; diff --git a/device/husky/overlays/modem-s4-cpif.dtso b/device/husky/overlays/modem-s4-cpif.dtso new file mode 100644 index 000000000..9e0581d3d --- /dev/null +++ b/device/husky/overlays/modem-s4-cpif.dtso @@ -0,0 +1,31 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* + * Modem link test, stage S4, never default (device/husky/ + * MODEM-PLAN.md): the controller (pcie_0_phy, pcie_0) + * is on, but its `modem` child is OFF so the lines are free for CPIF, and + * /cp-shmem and /cpif (disabled in the base dtb, kernel branch + * husky-e1-modem-cpif) are switched on. cpif probe forces the seven AP2CP + * outputs low; nothing powers the modem or starts PCIe. + */ +/dts-v1/; +/plugin/; + +&pcie_0_phy { + status = "okay"; +}; + +&pcie_0 { + status = "okay"; + + modem { + status = "disabled"; + }; +}; + +&{/cp-shmem} { + status = "okay"; +}; + +&{/cpif} { + status = "okay"; +}; diff --git a/device/kodiak/BRINGUP-NOTES.md b/device/kodiak/BRINGUP-NOTES.md index e1c1343a7..3e94bd0ed 100644 --- a/device/kodiak/BRINGUP-NOTES.md +++ b/device/kodiak/BRINGUP-NOTES.md @@ -5,17 +5,22 @@ Tracking: https://github.com/derekross/omarchy-mobile/pull/231 ## Current state - Bootloader unlocked -- Stock CD1A.260905.001.B1 on slot B (factory flash-all.sh) +- Stock CD1A.260905.001.B1 on slot B (factory flash-all.sh). On 2026-11-01 OrangeFox’s recovery replaced slot B’s vendor_boot (stock copy saved by the installer at backup/20261101-151204/vendor_boot_b before the rebuild). +- Stock recovery did not provide adb root, so OrangeFox was installed on slot B to take the read-only calibration backup. - Slot A is the safety slot (do not flash) - device.conf has partition sizes, AVB values, and confirmed board id/rev - Critical calibration partitions backed up off-device with SHA-256 checksums (persist, modem_a/b, nvdata, nvram, devinfo, trusty_userdata). - Taken from OrangeFox recovery (read-only `dd` of the by-name nodes, pulled off-device). - Images and SHA256SUMS live in a local `kodiak-critical/` directory (not in the repository). - No classic efs*/modem_userdata nodes exist on this device. +- Calibration backup taken from OrangeFox recovery (read-only `dd` of the by-name nodes, pulled off-device, contents at that time; recovery may have mounted persist/metadata). Not a clean stock baseline. +- OrangeFox was installed via the AIO installer (`install-desktop.sh`) after the factory flash and OTA sideload, and before the calibration backup. +- The installer replaced only the recovery part of `vendor_boot` on slot B. Slot A remains stock. +- It did not write `vbmeta`, `boot`, or `init_boot`. +- No plan to restore stock `vendor_boot` on slot A (it was never changed). +- Images and SHA256SUMS live in a local `kodiak-critical/` directory (not in the repository). +- No classic efs*/modem_userdata nodes exist on this device. ## Still needed -- [x] Slot-B backup of stock boot images +- [x] Slot-B backup of stock boot images (taken before OrangeFox install; stock vendor_boot_b also saved by the installer at backup/20261101-151204/vendor_boot_b) - [x] Calibration partition backup (see above) - [ ] First Omarchy build / flash to slot B @@ -29,3 +34,4 @@ Tracking: https://github.com/derekross/omarchy-mobile/pull/231 - DTB lives in vendor_kernel_boot.img - DTBO entry 37: id=0x80406 rev=0x10000 - Bootloader: spacecraft-17.4-16238327 (both slots) +- Partition mapping (from recovery sysfs/by-name): all on sda — boot_b (sda23), init_boot_b (sda24), vendor_boot_b (sda25), vendor_kernel_boot_b (sda26), dtbo_b (sda27), userdata (sda42). diff --git a/device/kodiak/NOTES.md b/device/kodiak/NOTES.md index 2f919309c..e62cc3434 100644 --- a/device/kodiak/NOTES.md +++ b/device/kodiak/NOTES.md @@ -26,15 +26,25 @@ Tracking issue: https://github.com/derekross/omarchy-mobile/issues/199 - Display: Verisilicon DC9x00 DPU + MIPI DSI2 (stock DTB) - dtbo_idx: 37 (`adb shell getprop ro.boot.dtbo_idx`) - DTBO entry 37: id=0x80406 rev=0x10000 (`mkdtboimg dump` on factory `dtbo.img`) +- AVB values: `avbtool info_image` on the factory `vbmeta.img` (from the official factory image for CD1A.260905.001.B1), plus `boot.img` and `init_boot.img`. Rollback index and security patch match the factory image; vbmeta chains boot (loc 2) and init_boot (loc 4). Same values present on slot B after the factory flash. - Bootloader unlocked: yes - Current confirmed bootable slots: both (factory flash + full OTA sideload) - ABL still appends `console=null` (`adb shell cat /proc/cmdline`) +## Slots + +- OrangeFox was installed via the AIO installer (`install-desktop.sh`) after the factory flash and OTA sideload, and before the calibration backup. +- Flash output not kept; the installer was set to slot b only. +- The installer replaced only the recovery part of `vendor_boot` on slot B. Slot A remains stock. +- The installer dropped the AVB footer from slot B’s vendor_boot (grown ramdisk + old footer would overflow the partition). Slot B’s vendor_boot currently has no AVB footer. +- It did not write `vbmeta`, `boot`, or `init_boot`. +- No plan to restore stock `vendor_boot` on slot A (it was never changed). + ## Partition and AVB sources - Partition sizes: `fastboot getvar partition-size:boot_b`, `partition-size:init_boot_b`, etc. - Partition names and by-name → block mapping: from recovery (sysfs/by-name) -- AVB values: `avbtool info_image` on stock `vbmeta_b`, `boot`, and `init_boot` (rollback index, security patch, chaining) +- AVB values: see Stock facts above (factory `vbmeta.img`) ## Hardware from stock DTB (vendor_kernel_boot) @@ -61,6 +71,8 @@ Tracking issue: https://github.com/derekross/omarchy-mobile/issues/199 ## Status -Stock facts collected and both slots restored to factory. +Stock facts collected and both slots restored to factory. On 2026-11-01 OrangeFox’s recovery replaced slot B’s vendor_boot (stock copy saved by the installer at backup/20261101-151204/vendor_boot_b before the rebuild). Device descriptor added in `device/kodiak/device.conf`. -Critical calibration partitions backed up off-device with SHA-256 checksums (persist, modem_a/b, nvdata, nvram, devinfo, trusty_userdata). Taken from OrangeFox recovery (read-only `dd` of the by-name nodes, pulled off-device). +Critical calibration partitions backed up off-device with SHA-256 checksums (persist, modem_a/b, nvdata, nvram, devinfo, trusty_userdata). Taken from OrangeFox recovery on slot B (contents at that time; recovery may have mounted persist/metadata). Not a clean stock baseline. + +Next calibration backup will be taken from the Omarchy initramfs on first slot B boot (read-only dd). Checksums and file/folder timestamps will be compared with the OrangeFox backup to see if persist or other calibration partitions changed. diff --git a/device/tegu/NOTES.md b/device/tegu/NOTES.md index 2d9ae83cd..b37172659 100644 --- a/device/tegu/NOTES.md +++ b/device/tegu/NOTES.md @@ -13,6 +13,126 @@ hash/build ID; this dirty release is not a published kernel package. `[V]` marks verified observations; `[I]` marks an inference still to test. Raw captures, recordings, backups and vendor files remain off repository. +## 2026-11-08: swap on zram + +Kernel `7.3.0-rc6-omamobile-push1-ge8d722982099`, a local build, with the +zram options of `kernel/configs/omamobile.config` (set in the device's +`kernel.config` for the test). They build only modules, so `zram.ko` and +`zsmalloc.ko` went onto the running release with `bin/omamobile +modules-push`, without a new boot image. Omarchy 4.0.6 on the phone. + +- [V] **Before:** no swap (`CONFIG_ZRAM` not set; Omarchy 4.0.6 ships no + zram-generator on aarch64). A `cargo build` of squeekboard on the phone, + next to Brave and the shell, left 177 MB available: memory PSI `full` + about 50 %, load 13, the session stuttering and SSH timing out in the + banner exchange. The OOM killer ended `rustc` (1.2 GB anonymous), and + systemd stopped the app scope it ran in, the terminal with it. +- [V] **Setup**, as a newer Omarchy does it on aarch64 (Omarchy v4.5.0): + `zram-generator` 1.2.1 from Arch, Omarchy's `90-omarchy.conf` (zstd, + `swap-priority = 100`) and the `vm.*` lines of its + `99-omarchy-sysctl.conf` (`swappiness=150`, `vfs_cache_pressure=50`, + `page-cluster=0`, the watermark and dirty settings). zram-generator + loads the module itself. +- [V] **`zram-size = ram / 2` (3.6 GB), 5 GB more allocated** on top of + about 4 GB in use: no OOM kill, PSI `full` peaked at 32 % and fell below + 10 %, and SSH answered throughout. zram held 3.2 GB in 1.7 GB; the test + data compresses about 2:1, ordinary app memory closer to 3:1. +- [V] **`zram-size = ram` (Omarchy's default, 7.3 GB), 6 GB more + allocated:** the phone stopped answering, ping included, and came back + after a restart about six minutes later. The journal has no oops or + panic and no OOM kill for this run; its last lines are the CP's PCIe + link going down and brcmfmac failing to allocate RX buffers. [I] RAM ran + out before zram filled, and reclaim spun instead of killing. Not a + like-for-like comparison (5 GB against 6 GB), so this says only that a + RAM-sized zram is not a safe default here yet. +- [V] **Stock Android on the 9a** (BP3A.250905.014 vendor image): + `vendor.zram.size=50p` selects `fstab.zram.50p` (`zramsize=50%`, plus a + 1 GB `zram_backingdev_size` writeback file for idle pages), started at + `sys.boot_completed` by `init.zumapro.board.rc` with `page-cluster 0`; + no swap partition. +- [V] **After the hang:** `tools/nv-backup -d tegu --check`: every NV + partition the same. `omamobile-tegu-modem-boot` refused to start (its + latch for a boot that didn't shut down cleanly), as designed; the modem + came up ONLINE once the logs were read and the latch removed. +- **By hand, until the image ships it:** build with the options, install + `zram-generator`, put `[zram0]` with `zram-size = ram / 2`, + `compression-algorithm = zstd` and `swap-priority = 100` in + `/etc/systemd/zram-generator.conf`, then `systemctl daemon-reload` and + `systemctl start systemd-zram-setup@zram0.service`. `zramctl` and + `swapon --show` show it. Resize only while it is empty: stopping the unit + removes `/dev/zram0`, and `cat /sys/class/zram-control/hot_add` brings + it back. + +## 2026-11-07: the main camera's autofocus (LC898129) + +Kernel `7.3.0-rc6-omamobile-push1-gd00d9fd2272f`, a local build: `omamobile` +with kernel #178, #103 and #164's camera device tree merged, the lc898129 +driver ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213)) and a lens node for it (below). + +- [V] **The controller:** the main module's focus and OIS controller is an + onsemi LC898129 at `0x24` on the main camera's bus (`hsi2c_5`, i2c-3), + stock's `act-nessie` / `ois-nessie`. 16-bit register addresses, 32-bit + big-endian values. It shares the sensor's supplies and reset and NACKs + unless the sensor is powered (a read while the camera is stopped gives + ENXIO or a timeout). +- [V] **Where the register map comes from:** no public datasheet or driver + for the part. The register numbers and the form of a move came from + disassembling the LC898129 actuator code in Google's camera HAL, + `liblyric_hwl.so` in the `com.google.pixel.camera.hal` APEX on the vendor + partition of factory image BP3A.250905.014: it reads `0xf010` and + `0x0548` and writes `0xf01a` as `0x0002` in the upper half and the + target in the lower. No code was copied. What the registers do, the + usable range and the direction below were measured on the phone. +- [V] **What was written while working it out:** only `0xf01a`, always + `0x0002` in the upper half, with lower halves from 0 to 32000 (those + above 4095 are the tries with the upper bits set). Every other access + was a register read (the two-byte address, then a 4-byte read): + `0x0000`, `0xf010`, `0xf01a`, `0xf01f`, `0xe00d`, `0xf000`, `0xf001`, + `0xf008`, `0xf00a`, `0xf100`, `0x0538` and `0x0548`. Finding the + address took only read probes: `i2cdetect -r` on the bus and a read of + `0x0000` at four other candidate addresses. The module's calibration + EEPROM, which stock puts at the same address, was never written, and + the driver writes only `0xf01a`. +- [V] **Its focus registers:** after power-up it reads `0xf010` = 7 (servo + on) and `0xf01a` = `0x00000fff` (focus target). Writing `0x0002xxxx` to + `0xf01a` moves the lens. The corrected Hall position at `0x0548` (upper + 16 bits, signed) is `0xc005 + 8 * (target & 0xfff)`: linear from -16379 + at 0 to 16381 at 4095, the same up and down. Targets with bits above the + low 12 also changed the framing and sharpness in ways that don't follow + the Hall position, so the driver never sets them. +- [V] **Direction:** sweeping 0-4095 with a can at about 25 cm, sharpness + rose steadily towards 0 and fell towards 4095; the picture before the + first write matched 4095. So 0 is the near end and 4095 the far end + [I: the far end not yet checked on a distant scene]. +- [V] **The driver:** `lc898129` ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213)) is a V4L2 lens subdev, + `V4L2_CID_FOCUS_ABSOLUTE` 0-4095 with higher values closer (it writes + 4095 minus the value). The `s5kgn1` driver powers it through + `lens-focus` while streaming, as for the 7 Pro's SEM1215SA. The node: + + ```dts + main_lens: lens@24 { + compatible = "onnn,lc898129"; + reg = <0x24>; + vio-supply = <&cam_1v8>; + }; + ``` + + with `lens-focus = <&main_lens>;` in `cam_main`. It isn't in #164; it + can go there or follow it. +- [V] **Autofocus in omacam:** the phone ran libcamera 0.7.2-4.22 with the + `Af` lines added by hand to its S5KGN8 tuning file, the same lines + 0.7.2-4.23's 0057 adds. libcamera's contrast autofocus scans and settles + on the can in a little over a second, and a full-size photo (3000x3992) + is sharp on it. +- [V] **2026-11-08, the driver as reviewed** (supplies `vio`, `vm`, + `vdda`; kernel `7.3.0-rc6-omamobile-push1-ge8d722982099`, `lc898129.c` + blob `50cce3a5f4c0`, the kernel #213 head): while the main camera + streams, `focus_absolute` 0, 1024, 2048, 3072, 4095, 2048, 0 settles at + Hall 16371, 8179, -7, -8197, -16383, -4, 16369, and the lens is + runtime-suspended after the stream. libcamera's autofocus (still + 4.22 with the lines by hand) sweeps 8 coarse steps over the range, + then finely around the peak, and settles there. + ## 2026-11-03: the radio backup check with tools/nv-backup - [V] **NV partitions unchanged (`7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`):** diff --git a/device/tegu/TELEPHONY-APPS-PLAN.md b/device/tegu/TELEPHONY-APPS-PLAN.md new file mode 100644 index 000000000..074335381 --- /dev/null +++ b/device/tegu/TELEPHONY-APPS-PLAN.md @@ -0,0 +1,202 @@ + +# Pixel 9a: connect Phone and Messages to sitd + +Status (2026-11-03): Phone and Messages ran on the palmtop on 2026-11-02 +through this path (results at the end). The optional +`omamobile-telephony-tegu` package installs mmd, the agent, an active-RIL +bridge policy and `omamobile-tegu-mmd-attach --check|--attach`, and enables +nothing. sitd's unit gets its modem dependency from a device-owned drop-in: +tegu uses Requisite on its already running starter, while cheetah and raven +keep Requires on their modem unit, and the virtual `omamobile-sitd-policy` +makes the drop-ins come along with a RIL upgrade. It builds on #363 (the +device modem policy). [Package/runbook](../../packages/omamobile-telephony-tegu/README.md). + +Two ways start the bridge, each for its own case: at boot, #372's opt-in +`omamobile-tegu-modem-boot` starts the modem, sitd and mmd once the CP is +ONLINE (daily use); and `omamobile-tegu-mmd-attach --attach` attaches mmd +and the agent to a modem and sitd already started by hand (bring-up and +tests, where nothing should start the modem for you). The helper refuses +when sitd isn't running and never starts the modem itself. + +Offline: the seven affected package suites pass, the attach package has 21 +tests (including systemd verification of all three device policies), and +the architecture-independent package builds with makepkg. One bridge API +comparison skips when ModemManager's reference XML is missing. + +The sections below are the investigation this started from, on `origin/main` +at `31fbcf9`, before #363 and the attach package. The owner then had texts +both ways and calls through `omamobile-sit`; this was the plan for the apps +on top. + +The app protocol already exists. The immediate missing layer in the +recorded tegu setup is `omamobile-mmd`, installed and running. A normal +package install is blocked by the cheetah-only dependency still on main; +sitd's packaged modem-unit dependency also needs the tegu startup work. +Those are existing, separate changes. Do not duplicate them or install +with dependency checks disabled. The first app test can use an already +running, attended sitd; it need not wait for modem startup at boot. + +## The existing path + +```text +Phone / Messages + | session bus: org.omamobile.Phone1, org.omamobile.Messages1 +omatel-agent (the logged-in user's service) + | system bus: org.freedesktop.ModemManager1 +omamobile-mmd (root, ModemManager-compatible API) + | /run/omamobile-sit/socket: JSON requests and status subscription +omamobile-sitd (the only owner of the modem channels) + | SIT / AT +modem +``` + +| Layer | What the repository already supplies | +| --- | --- | +| Apps | `omamobile-apps` depends on `omaphone` and `omamessages`; both pull in `omatel-agent`. Contacts is supplied with Phone and does not need a modem. #361 puts all three packages in the image. | +| Agent | `packages/omatel` packages the agent, its user unit and both session-bus activation files. Its session-bus activation files are meant to start it when an app opens; on the palmtop that didn't happen (results below), and the user unit had to be started and enabled. The disabled user unit is intentional; no root agent and no generic enablement change are needed. | +| Bridge | `packages/omamobile-mmd` owns the system-bus name normally used by ModemManager, exports modem/call/SMS objects, and checks polkit for operations. It conflicts with the real `modemmanager`; installing both is not the solution. | +| Commands | `Voice.CreateCall` plus `Call.Start` maps to sitd `dial`; `Accept`, `Hangup` and `SendDtmf` map to sitd requests. `Messaging.Create` plus `Sms.Send` maps to `sms-send` with a durable request ID. | +| Incoming events | The bridge subscribes to sitd, exports calls, reads `sms-list`, and maps deletion to `sms-delete`. The agent stores SMS before deleting them from the bridge and handles notifications and call history. | +| Privileges | Apps and agent use D-Bus. Only the bridge needs sitd's private socket. Keep socket permissions and the current polkit policy; no wheel-group workaround is needed for app access. | + +Sources: [app package](../../packages/omamobile-apps/PKGBUILD), +[agent packaging and activation](../../packages/omatel/README.md), +[bridge mappings](../../packages/omamobile-mmd/lib/bridge.py), +[socket subscription](../../packages/omamobile-mmd/lib/sitd_link.py), and +[the shared telephony plan](../../docs/TELEPHONY-APPS-PLAN.md), especially +sections 1.5 and 10.1b. + +Contacts uses the shared local vCard address book; it does not need a modem +or an additional cellular service. + +## What tegu is missing + +1. **A dependency-correct install.** `omamobile-mmd` depends on + `omamobile-modem-sit`, which depends on `omamobile-modem`, which still + depends on `omamobile-device-cheetah`. That conflicts with tegu's device + package. #363 (merged) replaces that last dependency with the virtual + `omamobile-modem-policy` and adds tegu's provider. +2. **The bridge package and its start.** The common rootfs list deliberately + omits mmd and modem-sit. Tegu's `ROOTFS_PACKAGES` does not include them. + `omamobile-mmd.service` ships disabled, has no D-Bus activation file, + and its installer creates no wants link. Merely opening an app cannot + start it. The recorded SIM runbook says mmd was not installed; current + hardware state must be checked by the human rather than inferred here. +3. **The right modem service for later automatic integration.** The shipped + `omamobile-sitd.service` requires `omamobile-modem.service`; the recorded + tegu run uses its own starter and an `/etc` copy of sitd's unit that + removes this dependency. A bridge-only test must retain the already + qualified, running stack. Do not start or restart the stock sitd unit + to attach the bridge. Package tegu's starter/order separately before + making this an image default. +4. **The tested tegu RIL and release safety.** Main still carries the older + RIL; use the independently reviewed tegu SIM fixes and safe unconfirmed + call-release behavior. Do not replace a running test RIL as part of + installing the bridge. An unconfirmed hang-up must not stop the tegu + modem in place. Call audio remains its separate route/qualification. + +There is no evidence that SMS needs an mmd APN, a tegu-specific socket +path, an extra bridge SMS transport, or a second modem daemon. The bridge +forwards SMS through sitd; sitd chooses the transport. Its modem state is +based on SIM/radio/registration and can be REGISTERED without a data bearer. +The hard-coded MM model string `Exynos Modem 5300` is misleading on tegu, +but is display metadata, not a routing selector or a reason to block SMS. + +## The smallest durable changes after the prerequisites + +- Keep `omamobile-apps` modem-independent, as #361 intends. Do not make all + images depend on the modem stack to get Phone or Contacts. +- After tegu's packaged modem start is qualified, add mmd and modem-sit to + tegu's board package list (and its packaged descriptor copy), with a + test that the descriptors agree and resolve against tegu's policy + provider without installing the cheetah device package. +- Enable only the bridge's existing relationship to sitd: + `systemctl enable omamobile-mmd.service` creates + `omamobile-sitd.service.wants/omamobile-mmd.service`. This follows a sitd + start without enabling sitd or starting the CP. Tegu's setup can do this + conditionally when mmd is installed; it need not use `--now`. +- Preserve mmd's one-way relationship: `After=omamobile-sitd.service`, no + `Requires=`, `Wants=` or activation path from the bridge to sitd or the + CP. An app opening or a bridge restart must never power the modem on. +- Test the conditional enablement with a fake systemctl, absent-package + handling, and a scratch unit root. Starting the bridge alone must not + request a CP start; starting qualified sitd must pull in the bridge. + +For the already running palmtop, the manual steps below are enough once +package dependencies are correct. The durable boot/image changes are not +prerequisites for that test. + +## Attended first test (ran on 2026-11-02) + +Keep the existing modem sleep inhibitor throughout; suspend with the CP on +is not qualified by this work. Keep the existing once-per-boot start and +NV checks. No step below starts, stops or restarts the CP or sitd. +Run user commands in the existing graphical user's terminal, root commands +in the attended administrative session. + +| Step / risk | Commands or action | Expect / pass | Stop condition | Rollback | +| --- | --- | --- | --- | --- | +| 1. Read-only / none | `uname -r`; `pacman -Q omaphone omamessages omatel-agent omamobile-mmd omamobile-modem-sit omamobile-modem`; `systemctl is-active omamobile-sitd omamobile-mmd ModemManager`; `systemctl cat omamobile-sitd`; `systemd-inhibit --list` | Record kernel/package versions, actual sitd unit, active inhibitor and existing running sitd. Missing bridge is expected initially. | No confirmed running sitd, wrong starter, competing ModemManager, or no inhibitor. | None; end this session without starting the modem. | +| 2. Install bridge / low | First review `pacman -Sp --print-format '%n %v' omamobile-mmd`. After the dependency fix is available, `pacman -S omamobile-mmd`, only if the transaction adds the bridge/dependencies without changing the running RIL, modem or device package. | No cheetah package, no tegu removal, no modem/RIL upgrade, and nothing starts the CP. | Resolver conflict or any unexpected upgrade/removal. Never use `-dd`. | Cancel before accepting the transaction; if installed, remove only the bridge after stopping it. | +| 3. Start bridge / low | Root: `systemctl start omamobile-mmd.service`; `busctl --system list --no-pager org.freedesktop.ModemManager1`; use `packages/omamobile-mmd/test/libmm-status.py` for states only. | Bus name owned by mmd, a modem object with SIM ready and expected registration; sitd/CP remain the same running instances. | Bridge cannot own the name/connect; sitd exits; hardware warning. | `systemctl stop omamobile-mmd.service`. Do not restart sitd or stop the modem. | +| 4. Agent and apps / low, screen changes | Announce first, then open Phone and Messages as the session user. `systemctl --user is-active omatel-agent`; `busctl --user list --no-pager org.omamobile.Phone1 org.omamobile.Messages1`. | Agent activates, apps see the modem instead of no-modem; Contacts opens without requiring a live modem. | Activation or authorization error. Do not weaken polkit/socket permissions. | Close apps; stop the user agent if it was started only for this test; stop mmd. | +| 5. SMS / carrier charge possible | Human sends one agreed test text in Messages, then sends one back from the other device; reopen the conversation. | One send, one received message, preserved after closing/reopening; no duplicate send on retry/reconnect. | Duplicate, uncertain delivery, or missing inbound text. Do not retry an uncertain send automatically. | Stop testing and stop the bridge; keep private message stores for diagnosis. | +| 6. Calls / medium, screen and sound | Only after the separate safe-release and call-audio checks: announce, place one ordinary agreed call from Phone, receive one, answer/decline and hang up. | UI state follows the call, release is confirmed, and the approved audio route behaves as qualified separately. | Unconfirmed release, unexpected audio level, CP/AoC/UFS fault. No emergency-number test. | Follow the attended safe-release runbook; no modem stop or second start. A reboot needs separate approval. | +| 7. Optional persistence / low | After passing, root: `systemctl enable omamobile-mmd.service` without `--now`. Inspect the resulting sitd wants link. | Bridge follows future *approved* sitd starts; sitd and modem remain disabled at boot. | Any change enabling the modem or sitd itself. | Disable only mmd if this step enabled it, then stop mmd if ending the test. | + +SMS/call numbers, contents, operator identities and object dumps remain +private. Record only states, counts, errors and test outcomes in this plan. +The read-only libmm status helper deliberately prints states and counts. + +A session that has never opened either app needs an additional activation +check before claiming always-on incoming notifications. The shell's call +watcher checks whether the agent owns its name and does not itself start +it. For this first test, open an app before arranging incoming traffic. +Keep #361's app-triggered activation policy until cold-session reception +has a separate test and an explicit decision about login activation. + +App mute/speaker controls are also separate: the shared plan records that +the agent uses callaudiod for those, while sitd owns its own voice PCMs. +A successful dial through mmd does not prove those controls affect tegu's +route. MMS and mobile-data control through ModemManager are outside this +SMS/basic-call integration; keep the existing sitd data ownership. + +## Offline evidence + +`packages/omamobile-mmd/test/all` passed on this base with private D-Bus +and local simulator sockets. This covers API/bridge/libmm clients, the +real sitd-to-sit-sim call and SMS chain, and staged unit checks. One test +was skipped because ModemManager's reference introspection XML is absent. +The suite verifies that the bridge has no unit dependency that pulls in +the modem and no system-bus activation file. + +`packages/omamobile-apps/test/all` also passed all 12 checks, including +Phone/Messages dependencies and the absence of a common modem dependency. + +This does not run the packaged Rust agent or either GUI, does not test +tegu hardware or the current private carrier configuration, and does not +qualify polkit for the actual graphical session. The earlier full agent +chain result is recorded in the shared plan; it was not rerun here. + +## Results on the palmtop, 2026-11-02 + +The daily kernel (`7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`), +the modem started by hand and sitd running (built from this stack, 0.3.12 +at the time), `omamobile-mmd` 0.1.0 started with `systemctl start`. + +- Steps 1 to 3 passed: the bridge owned `org.freedesktop.ModemManager1` + and exported the modem with the SIM ready; sitd and the CP stayed the + same running instances. +- Step 4: opening Messages did *not* start the agent, and it showed + "service isn't running" until `systemctl --user enable --now + omatel-agent`. After that both apps saw the modem. Cold-session + activation stays open, as above. +- Step 5: texts both ways from Messages, with no duplicate. +- Step 6: calls out from Phone and in, with speakerphone audio (#367), + released cleanly. +- The status bar showed airplane mode until sitd mapped radio state 10 to + on (now on main with #381). + +A `tools/phone-smoke` report from the palmtop is still to come, with the +next run. + diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 6deb59bec..446d6c59e 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -25,12 +25,12 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); native test image on one phone; slot B marked successful and `vbmeta_b` verification turned off, both without project approval; see notes) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); guarded `userdata` root on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); connected output on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); Panfrost render node present) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); touchscreen detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); gpio-keys detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); USB network and SSH on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); link up; traffic not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); controller powered; pairing not checked) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charge and temperature reported) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | | Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - | | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | -| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (Omarchy's Location switch serves fixes from GPS, Galileo, BeiDou and GLONASS once the modem is up, started by hand: a 30-minute session through the switch on 2026-11-01 (omamobile-gnss 0.2.5's start, the modem link left to cycle) ran clean, 1763 of 1765 GGA sentences fixed, first fix 37 s after a client connected; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150), merged, the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), merged (without it the modem link hung the palmtop within minutes), and [#114](https://github.com/derekross/omarchy-mobile/pull/114), merged, from whose package build a session in a moving car fixed 145 of 153 times; the GNSS link driver is merged, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), loaded by hand with the modem off, and a session through it waits on the modem link; [plan](../device/tegu/MODEM-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | WIP (registered on LTE, mobile data over `rmnet0`, texts both ways and speakerphone calls in and out with `omamobile-modem-sit` ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#367](https://github.com/derekross/omarchy-mobile/pull/367)), on the owner's kernel and on in-tree drivers from the open kernel PRs ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187), [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162)); the package doesn't start the modem, the kernel PRs aren't merged, and calls have no echo cancellation or earpiece yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | testing (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key lights the lock screen on the first press ([#268](https://github.com/derekross/omarchy-mobile/pull/268), [#275](https://github.com/derekross/omarchy-mobile/pull/275)), and the RTC wakes it; on 2026-11-01 thirty attended 120 s sleeps ([plan](../device/tegu/SLEEP-PLAN.md) S1) and a day of real use with auto-sleep on ([record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) all woke, but six test sleeps since 10-28 did not (one in 21 on the clock-fix kernel on 11-01, and one in 127 in an overnight series of 120 s sleeps on 11-01 to 11-02), so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | -| Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on this phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | WIP (simple-framebuffer with the panel's size, [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154): console and Omarchy's lock screen; 120 Hz with brightness on a test kernel, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228)) | testing (panthor on the Mali-G715 on a test kernel, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157); [ROADMAP](../device/husky/ROADMAP.md)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | testing (BCM4398D0 on the APM UART, pairing and A2DP, on a test kernel, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image; [ROADMAP](../device/husky/ROADMAP.md)) | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, pack EEPROM, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163) and [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175); the bus on by default waits for [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: sink at the Type-C 3 A level (input limit 0xc2 0x13 to 0x77); +1.5 A measured from a 30 W charger without the driver (1.485 A is the device-tree cap); no host mode, [#282](https://github.com/derekross/omarchy-mobile/pull/282); [notes](../device/husky/BATTERY-NOTES.md), [#1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)) | testing (CS40L26 on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | testing (LM3644, 50 mA cap, on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | no (first steps as drafts: [kernel #210](https://github.com/derekross/linux-omarchy-mobile/pull/210), [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211)) | testing (loads and runs through the GSA and Trusty on a test kernel; plan and results [AOC-PLAN](../device/husky/AOC-PLAN.md)) | testing (stereo speakers and one microphone through UCM2 and PipeWire on a test kernel, [kernel #203](https://github.com/derekross/linux-omarchy-mobile/pull/203), [#204](https://github.com/derekross/linux-omarchy-mobile/pull/204), package [#453](https://github.com/derekross/omarchy-mobile/pull/453)) | no | no | testing (a test kernel reads tags; [kernel #208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)) | no | no | no | +| Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (Omarchy's Location switch serves fixes from GPS, Galileo, BeiDou and GLONASS once the modem is up, started by hand: a 30-minute session through the switch on 2026-11-01 (omamobile-gnss 0.2.5's start, the modem link left to cycle) ran clean, 1763 of 1765 GGA sentences fixed, first fix 37 s after a client connected; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150), merged, the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), merged (without it the modem link hung the palmtop within minutes), and [#114](https://github.com/derekross/omarchy-mobile/pull/114), merged, from whose package build a session in a moving car fixed 145 of 153 times; the GNSS link driver is merged, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), loaded by hand with the modem off, and a session through it waits on the modem link; [plan](../device/tegu/MODEM-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | WIP (registered on LTE, mobile data over `rmnet0`, texts both ways and speakerphone calls in and out with `omamobile-modem-sit` ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#367](https://github.com/derekross/omarchy-mobile/pull/367)), on the owner's kernel and on in-tree drivers from the open kernel PRs ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187), [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162)); the package doesn't start the modem, the kernel PRs aren't merged, and calls have no echo cancellation or earpiece yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | testing (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key lights the lock screen on the first press ([#268](https://github.com/derekross/omarchy-mobile/pull/268), [#275](https://github.com/derekross/omarchy-mobile/pull/275)), and the RTC wakes it; on 2026-11-01 thirty attended 120 s sleeps ([plan](../device/tegu/SLEEP-PLAN.md) S1) and a day of real use with auto-sleep on ([record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) all woke, but six test sleeps since 10-28 did not (one in 21 on the clock-fix kernel on 11-01, and one in 127 in an overnight series of 120 s sleeps on 11-01 to 11-02), so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | +| Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | WIP (simple-framebuffer with the panel's size, [kernel #154](https://github.com/derekross/linux-omarchy-mobile/pull/154): console and Omarchy's lock screen; 120 Hz with brightness on a test kernel, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228)) | testing (panthor on the Mali-G715 on a test kernel, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157); [ROADMAP](../device/husky/ROADMAP.md)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | testing (BCM4398D0 on the APM UART, pairing and A2DP, on a test kernel, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image; [ROADMAP](../device/husky/ROADMAP.md)) | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, pack EEPROM, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163) and [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175); the bus on by default waits for [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: sink at the Type-C 3 A level (input limit 0xc2 0x13 to 0x77); +1.5 A measured from a 30 W charger without the driver (1.485 A is the device-tree cap); no host mode, [#282](https://github.com/derekross/omarchy-mobile/pull/282); [notes](../device/husky/BATTERY-NOTES.md), [#1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)) | testing (CS40L26 on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | testing (LM3644, 50 mA cap, on a test kernel, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200)) | no (first steps as drafts: [kernel #210](https://github.com/derekross/linux-omarchy-mobile/pull/210), [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211)) | testing (loads and runs through the GSA and Trusty on a test kernel; plan and results [AOC-PLAN](../device/husky/AOC-PLAN.md)) | testing (stereo speakers and one microphone through UCM2 and PipeWire on a test kernel, [kernel #203](https://github.com/derekross/linux-omarchy-mobile/pull/203), [#204](https://github.com/derekross/linux-omarchy-mobile/pull/204), package [#453](https://github.com/derekross/omarchy-mobile/pull/453)) | no | no | testing (a test kernel reads tags; [kernel #208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)) | no | no | no | | Pixel 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B into the initramfs with USB and SSH, no Arch root yet; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md), [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | WIP (UFS at HS-G4 behind the read-only guard, from the initramfs only, nothing run on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206); the device package and storage plan are in review, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | no | no | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | | OnePlus 13 ([notes](../device/dodge/NOTES.md)) | dodge | sm8750 (Snapdragon 8 Elite) | testing (kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [BRINGUP](../device/dodge/BRINGUP-M1.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (msm/dpu; warm-boot drop fixed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (Adreno 830 / gpu2; Vulkan untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (CDC NCM + SSH; gadget stuck after replug until reboot; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (WCN7860 / ath12k; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (pairing; A2DP untested; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (gauge; charging path not claimed; kernel [mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | no | no | - | testing (speakers, earpiece, mics; headset plug untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (accel, prox, compass; autorotate; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (LTE data; calls/SMS untested; opt-in flag; [modem](../device/dodge/modem/README.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | WIP (s2idle not default; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | -| OnePlus 6 ([notes](../device/enchilada/NOTES.md)) | enchilada | SDM845 (Snapdragon 845) | WIP (RAM-only `fastboot boot` of a header-v0 image; kernel: Linux 7.1-rc1 from the sdm845-mainline tree, not linux-omarchy-mobile; the firewall and GPU results booted the Arch root on `userdata`; stock is not on slot A, a §3.1 event: [notes](../device/enchilada/NOTES.md#slots-and-what-is-on-them-contributingmd-31); [#432](https://github.com/derekross/omarchy-mobile/issues/432)) | WIP (UFS behind the read-only guard; `boot_b` is on LUN `sde` and stays read-only; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | WIP (msm DRM framebuffer console; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (needs the phone's own zap shader; [notes](../device/enchilada/NOTES.md#2026-11-05-adreno-630-needs-this-phones-zap-shader)) | no | no | testing (NCM + ACM + SSH; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (modem/rmtfs plan first) | no | no | no | no | no | no | - | no | no | no | no | no | no | no | +| OnePlus 6 ([notes](../device/enchilada/NOTES.md)) | enchilada | SDM845 (Snapdragon 845) | WIP (RAM-only `fastboot boot` of a header-v0 image; kernel: Linux 7.1-rc1 from the sdm845-mainline tree, not linux-omarchy-mobile; the firewall failure booted from `boot_b` after `--set-active=b`, the firewall fix and GPU results were `fastboot boot`s, all three with the Arch root on `userdata`; stock is not on slot A, a §3.1 event: [notes](../device/enchilada/NOTES.md#slots-and-what-is-on-them-contributingmd-31); [#432](https://github.com/derekross/omarchy-mobile/issues/432)) | WIP (UFS behind the read-only guard; `boot_b` is on LUN `sde` and stays read-only; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | WIP (msm DRM framebuffer console; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (needs the phone's own zap shader; [notes](../device/enchilada/NOTES.md#2026-11-05-adreno-630-needs-this-phones-zap-shader)) | no | no | testing (NCM + ACM + SSH; [notes](../device/enchilada/NOTES.md#2026-11-04-ram-only-first-light)) | no (modem/rmtfs plan first) | no | no | no | no | no | no | - | no | no | no | no | no | no | no | | *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | | ## cheetah (Pixel 7 Pro) in detail @@ -80,5 +80,5 @@ Devices we'd like to support, with the closest starting point. Open an issue to | Pixel 4 XL | coral | SM8150 (Snapdragon 855) | **WIP, community port**, in the matrix above: bring-up notes merged ([#52](https://github.com/derekross/omarchy-mobile/pull/52): [BRINGUP-M1](../device/coral/BRINGUP-M1.md), [NOTES](../device/coral/NOTES.md)), with companion kernel/userspace sources ([omarchy-mobile-coral v0.2.3](https://github.com/HemangKumawat/omarchy-mobile-coral/tree/v0.2.3)); slot-B installer and `CONTRIBUTING.md` §3.1 entry still to land | | POCO F3 | alioth | SM8250 (Snapdragon 870) | the first non-Pixel port: a guarded installer and root image in review ([#25](https://github.com/derekross/omarchy-mobile/pull/25)) | | OnePlus 13 | dodge | SM8750 (Snapdragon 8 Elite) | **WIP, community port**, in the matrix above: device files, notes and the qcom-abl boot images merged ([#111](https://github.com/derekross/omarchy-mobile/pull/111)); its kernel stays in the contributor's fork ([mrlund/linux-omarchy-mobile `dodge-v3-20261101`](https://github.com/mrlund/linux-omarchy-mobile/tree/dodge-v3-20261101); [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed: the SoC series is out of this tree's scope); the guarded installer follows in a later pull request | -| OnePlus 6 | enchilada | SDM845 (Snapdragon 845) | **WIP, community port: [#432](https://github.com/derekross/omarchy-mobile/issues/432)**, in the matrix above: descriptor and notes; RAM-only (`fastboot boot`) until the slot-B install and its CONTRIBUTING.md §3.1 entry are agreed; the header-v0 packer and a LUN-aware `UFS_RW` follow in their own pull requests | +| OnePlus 6 | enchilada | SDM845 (Snapdragon 845) | **WIP, community port: [#432](https://github.com/derekross/omarchy-mobile/issues/432)**, in the matrix above: descriptor and notes; RAM-only (`fastboot boot`) until the slot-B install and its CONTRIBUTING.md §3.1 entry are agreed; `omamobile images` packs its header-v0 boot image, and its `UFS_RW_LUNS=sde` (the guard's second-LUN list, #530) comes with the slot-B install | | PinePhone Pro | pinephone-pro | Rockchip RK3399S | No port in this tree yet; mainline's `rk3399-pinephone-pro.dts` is already in our kernel. Prior art: [Omarchy on the PinePhone Pro](https://github.com/FlorencioJP/omarchy-mobile-pinephone-pro) | diff --git a/docs/INSTALL.md b/docs/INSTALL.md index 60e5d35b7..6193f8f80 100644 --- a/docs/INSTALL.md +++ b/docs/INSTALL.md @@ -20,10 +20,10 @@ Today these steps are manual. Where the install is going, one guided step from a - **A Pixel 7 Pro** whose bootloader can be unlocked. Phones sold locked to a carrier often can't be. In Android, go to Settings > About phone and tap Build number seven times to turn on Developer options, then check that Settings > System > Developer options > **OEM unlocking** can be switched on. If it's greyed out, the phone can't be unlocked. - **A computer running Linux** (Omarchy, Arch Linux or another distribution), and a USB-C cable that carries data. The installer is a shell script for Linux; installing from a web page or a desktop app is planned. -- **These programs on the computer:** `fastboot` and `adb` (Android platform tools), `e2fsprogs`, `zstd`, `openssl`, `gnupg`, `python3`, `unzip`, and `binutils`. On Omarchy or Arch Linux: +- **These programs on the computer:** `fastboot` and `adb` (Android platform tools), `e2fsprogs`, `zstd`, `lz4`, `cpio`, `openssl`, `gnupg`, `python3`, `unzip`, and `binutils`. On Omarchy or Arch Linux: ```sh - sudo pacman -S --needed android-tools e2fsprogs zstd openssl gnupg python unzip binutils erofs-utils + sudo pacman -S --needed android-tools e2fsprogs zstd lz4 cpio openssl gnupg python unzip binutils erofs-utils ``` On other distributions, install the packages with the same names (Android's tools are often split into `fastboot`, `adb` and a "libsparse" package for `img2simg` and `simg2img`). diff --git a/docs/RELEASES.md b/docs/RELEASES.md index 27941295c..54d9f93d3 100644 --- a/docs/RELEASES.md +++ b/docs/RELEASES.md @@ -34,7 +34,7 @@ The audit behind this design (2026-10-13). "Step" names the roadmap step that re | `bin/omamobile initramfs` | the splash size comes from `PANEL_SIZE`; C sources from the device package when it has them. The init path and the trigger write come from the descriptor | 1 (done) | | `bin/omamobile capture` | the default capture name `cheetah-` | 1 (done) | | `bin/omamobile push`, `flash` | the partition lookup assumes the main LUN is `sda` | 1 (allowlist check and `BOOT_IMAGES` layouts done; the Pixel 6 has no `init_boot` or `vendor_kernel_boot`, [oriole NOTES](../device/oriole/NOTES.md)), 3 | -| `initramfs/init` | `probe()` when `BRINGUP_PROBE=1` and the board matches `COMPATIBLE` (watchdog and DPP reads); the main LUN `sda`. The TRIG_CON write is `SIMPLEFB_TRIG_CON`, the storage-guard allowlist `UFS_RW` and the USB product string `USB_PRODUCT`, all packed from the descriptor into that device's initramfs only | 2 (trigger, allowlist and USB name done; the rest still step 2) | +| `initramfs/init` | `probe()` when `BRINGUP_PROBE=1` and the board matches `COMPATIBLE` (watchdog and DPP reads); the main LUN `sda`. The TRIG_CON write is `SIMPLEFB_TRIG_CON`, the storage-guard allowlist `UFS_RW` (and `UFS_RW_LUNS`) and the USB product string `USB_PRODUCT`, all packed from the descriptor into that device's initramfs only | 2 (trigger, allowlist and USB name done; the rest still step 2) | | `bin/omamobile initramfs` | the developer's `~/.ssh/*.pub` baked in as `authorized_keys` (fine for development, never for a release); `--release` leaves them out, and `tools/make-bundle` refuses to sign an initramfs that has them | 2 (done) | | `tools/extract-vendor-firmware` | `BOARD="google,gs201-cheetah"`, `DEVICE="cheetah"`, the firmware `MAP` | 4 | | `tools/extract-vendor-chroot`, `extract-fingerprint-vendor` | `DEVICE="cheetah"`, cheetah's file lists | 4 | @@ -76,9 +76,11 @@ Bring-up tools (`*-stage`, `display-hz`, `usbc-deadman`) stay per plan: they pok | `OS_VERSION`, `OS_PATCH_LEVEL` | `17.0.0`, `2026-07` | The `init_boot` header values (the `boot` header's, on a device without `init_boot`) | | `AVB_FOOTERS` | (zuma, the Pixel 7a and the Pixel 7 Pro: `boot:0x4000000 init_boot:0x800000`) | Optional. For a phone whose `vbmeta_b` chains these partitions, as stock's does: libavb takes a chained partition with no AVB footer as invalid metadata, which an unlocked bootloader doesn't let through (zuma; the Pixel 7a; the Pixel 7 Pro, device/cheetah/NOTES.md 2026-10-28). A `vbmeta_b` that lists them as hash descriptors, or has verification disabled, never reads the footers. `image:partition_size`, each a `BOOT_IMAGES` entry, once; the size is the slot's partition size in bytes (stock's footer, `avbtool info_image`, or `fastboot getvar partition-size:_b`), a multiple of 4096. `images` adds a hash footer to each, padding it to that size, signed with AOSP's test key (an unlocked bootloader accepts any key); needs `external/avb` under `SRC_DIR` (or `AVBTOOL`, `AVB_KEY`) and `openssl` | | `AVB_ROLLBACK_INDEX`, `AVB_SECURITY_PATCH` | `1791158400`, `2026-10-05` | Required with `AVB_FOOTERS`, refused without it: stock's rollback index and `com.android.build..security_patch` from its footers. Never set the index above stock's: an index the bootloader stores locks stock's own images out of slot A. The `os_version` property is `OS_VERSION`'s major | -| `BOOT_METHOD` | `android-v4` (default when omitted) | Generic images, flash, push and installer accept only `android-v4`; other methods are refused before phone access. `ram-only` marks a probe with no persistent install support | +| `BOOT_METHOD` | `android-v4` (default when omitted) | Generic images, flash, push and installer accept only `android-v4`; other methods are refused before phone access. `ram-only` marks a probe with no persistent install support. `android-v0` (enchilada) is a header-v0 phone: `images` packs one `boot.img` for `fastboot boot`, and fastboot, flash, push and the installer refuse it | +| `PAGESIZE`, `BASE`, `KERNEL_OFFSET`, `RAMDISK_OFFSET`, `SECOND_OFFSET`, `TAGS_OFFSET` | (enchilada: `4096`, `0x00000000`, `0x00008000`, `0x01000000`, `0x00f00000`, `0x00000100`) | `android-v0` only, all required: the header-v0 page size and load offsets, numbers in decimal or lower-case hex. `images` packs the gzip `Image` with the `DTB` appended as the kernel, the initramfs as the ramdisk and `CMDLINE` as the command line. `BOOT_IMAGES` is `boot` alone and `boot_b` must be on `UFS_RW` | | `BOOT_IMAGES` | `boot init_boot vendor_boot vendor_kernel_boot dtbo` | The images written to slot B (the `_b` suffix is added by the tools and is not configurable). `boot`, `vendor_boot` and `dtbo` are always there. Without `init_boot`, `boot` carries the empty generic ramdisk and the OS version; without `vendor_kernel_boot`, `vendor_boot` carries the DTB and the initramfs (the Pixel 6: `boot vendor_boot dtbo`) | | `UFS_RW` | `boot_b … dtbo_b userdata` | The storage guard's allowlist, packed into the initramfs as `/etc/omamobile-ufs-rw`. Only slot B's boot images (`boot_b`, `init_boot_b`, `vendor_boot_b`, `vendor_kernel_boot_b`, `dtbo_b`) and `userdata` are accepted, `userdata` and every `BOOT_IMAGES` entry must be on it, and each name only once. The init fails closed: a missing, empty or malformed file, or any other name in it, leaves every partition read-only | +| `UFS_RW_LUNS` | (unset) | Optional. The LUNs besides `sda` that hold `UFS_RW` partitions, as disk names `sdb` to `sdz`, packed as `/etc/omamobile-ufs-rw-luns`. The init guards each as it guards `sda`: the whole-disk node removed, the disk left writable, and only its `UFS_RW` partitions left writable. Absent (every descriptor so far), malformed, or with a closed allowlist: every LUN but `sda` stays read-only at the disk level. Boot-image writers on the phone (`omamobile-boot-update`) still look only on `sda` | | `INITRAMFS_INIT` | `/initramfs/init` | The init script. A leading `/` is relative to the repo root, so devices share one script. Any other value is relative to the descriptor | | `INITRAMFS_MODULES` | (unset) | Optional: kernel modules the initramfs carries in `/lib/modules/omamobile/`, listed in load order in `/lib/modules/omamobile/order`, from this kernel build's `lib/modules/$(kernel_release)` (`omamobile modules` first). The shared init loads them before any other step, and only on a board whose first compatible is `COMPATIBLE`. For drivers the boot needs before the Arch root, such as the PMIC rails a `simple-framebuffer` waits for; `images` refuses an initramfs whose modules come from another build | | `INITRAMFS_I2C_TOOLS` | (unset) | `1`: `i2cget` and `i2cset` (and `libi2c`) from Alpine's i2c-tools in the initramfs, for an init that talks to a chip before any driver runs (raven closes the MAX77759 USB switch). Nothing else from the package | @@ -122,7 +124,7 @@ What `bin/omamobile` checks, so a wrong descriptor fails the build rather than t - the descriptor's format, required keys and `CODENAME`; - `UFS_RW` holds only slot B's boot images and `userdata`, each once, includes `userdata`, and covers every `BOOT_IMAGES` entry; - `BOOT_IMAGES` names only `boot`, `init_boot`, `vendor_boot`, `vendor_kernel_boot` and `dtbo`, each once, and includes `boot`, `vendor_boot` and `dtbo`; -- `initramfs` packs the checked `UFS_RW` into the image (`/etc/omamobile-ufs-rw`), so the init's allowlist is the descriptor's; +- `initramfs` packs the checked `UFS_RW` into the image (`/etc/omamobile-ufs-rw`), so the init's allowlist is the descriptor's, and `UFS_RW_LUNS`, when set, holds only disk names `sdb` to `sdz` (`/etc/omamobile-ufs-rw-luns`); - the DTB really is built with the first `SOC_IDS` value, and each rewrite took; - with `SOC_COMPATIBLE` instead, the DTB has a `/soc_compatible` node holding exactly its entries (one child each, labelled or not), and a descriptor never names both keys; - `AVB_FOOTERS` names only the device's boot images, once each, with block-aligned partition sizes, and comes with its rollback index and security patch; the footers are deterministic (the salt is the image's own hash) for a given avbtool: the footer records avbtool's version, which `images` prints, so another `external/avb` checkout gives other bytes; @@ -181,7 +183,7 @@ As built (§5.5), the tool and the hook are their own package, `omamobile-boot-u The same Alpine-based initramfs, with release differences: -- **No developer keys.** It ships without `authorized_keys`: `bin/omamobile initramfs --release` builds it that way, and `tools/make-bundle` refuses to sign a bundle whose initramfs still holds SSH keys. The hook appends a second, tiny cpio to the ramdisk that holds the phone's own `/root/.ssh/authorized_keys` (the kernel unpacks concatenated cpio archives in order), so SSH into the initramfs keeps working for the phone's owner and nobody else. +- **No developer keys.** It ships without `authorized_keys`: `bin/omamobile initramfs --release` builds it that way, and `tools/make-bundle` refuses to sign a bundle whose initramfs still holds SSH keys. The hook appends a second, tiny cpio to the ramdisk that holds the phone's own `/root/.ssh/authorized_keys` (the kernel unpacks concatenated cpio archives in order), so SSH into the initramfs keeps working for the phone's owner and nobody else. `tools/install-phone` appends the same cpio, with the same commands, to a copy of the bundle's ramdisk image (`vendor_kernel_boot`, or `vendor_boot` on a phone without one) before flashing it, so the initramfs takes the owner's key from the first boot and the hook's first run finds the image it would build already on slot B (`tests/install-phone-initramfs`). A device with `INITRAMFS_MODULES` (raven) is the exception: the hook's cpio also carries those modules, so its first run rewrites the image once. - **No bring-up probes.** `probe()` and `omamobile.debug` stay in development builds only. - **Quirks from the descriptor.** The trigger write is already per device: `bin/omamobile initramfs` packs `SIMPLEFB_TRIG_CON` into `/etc/omamobile-simplefb-trig` and `COMPATIBLE` beside it. The init writes the pair only when the board's first compatible string matches. A device without the trigger key gets no register write. The storage guard's allowlist is packed the same way, from `UFS_RW` into `/etc/omamobile-ufs-rw`, and the init leaves every partition read-only without a valid one. So is the USB product string (`USB_PRODUCT`, else `NAME`). Step 2 still turns the remaining quirk (`MAIN_LUN`) into a generated `/etc/omamobile/device.conf` the shared init reads at boot. That remaining step changes what boots, so it gets its own runbook and a test boot from `bin/omamobile push`; it is not a refactor. - **Reproducible:** fixed mtimes (`SOURCE_DATE_EPOCH`), sorted file list, `cpio --reproducible`. @@ -204,7 +206,7 @@ The same Alpine-based initramfs, with release differences: `omamobile-omarchy` (in every image built from 2026-10-13 on, and a dependency of `omamobile-shell`, so `omarchy update` brings it to older phones) owns both halves; the details are in the headers of its `bin/omamobile-update` and `bin/omamobile-omarchy-patches`. -**The patches survive upgrades.** The series lives in `packages/omamobile-omarchy/patches` (`patches/omarchy` links there) and ships in the package. Its pacman hook (`95-omamobile-omarchy-patches.hook`, PostTransaction on `omarchy`, `omarchy-dev` and itself) re-applies it after every transaction that replaces Omarchy's files, and `rootfs/build-inside` runs the same tool, so image builds and upgrades take one code path. Every run starts from Omarchy's own files (checked against the package's mtree), applies the series in a scratch tree with `--fuzz=0`, verifies it by reversing it back to Omarchy's files, and only then swaps the files in. A patch whose reverse applies is already in Omarchy (a backport that landed): it is skipped and reported, and should be dropped from the series. Any other failure leaves Omarchy's files exactly as shipped, logs to `/var/log/omamobile/omarchy-patches.log` and notifies the user (the lock's PIN pad may be missing until a fixed series ships). A file that matches neither Omarchy's copy nor the last patched one was changed by something else and is never overwritten. +**The patches survive upgrades.** Two series families ship in the package, selected by the installed Omarchy version: `packages/omamobile-omarchy/legacy-4.0.6/` for today's 4.0.6 phones, and `packages/omamobile-omarchy/patches/` for 4.5 (`patches/omarchy` links only to the latter). Fixes for today's phones must go in `legacy-4.0.6/`, and also in `patches/` when applicable to 4.5. Its pacman hook (`95-omamobile-omarchy-patches.hook`, PostTransaction on `omarchy`, `omarchy-dev` and itself) re-applies it after every transaction that replaces Omarchy's files, and `rootfs/build-inside` runs the same tool, so image builds and upgrades take one code path. Every run starts from Omarchy's own files (checked against the package's mtree), applies the series in a scratch tree with `--fuzz=0`, verifies it by reversing it back to Omarchy's files, and only then swaps the files in. A patch whose reverse applies is already in Omarchy (a backport that landed): it is skipped and reported, and should be dropped from the series. Any other failure leaves Omarchy's files exactly as shipped, logs to `/var/log/omamobile/omarchy-patches.log` and notifies the user (the lock's PIN pad may be missing until a fixed series ships). A file that matches neither Omarchy's copy nor the last patched one was changed by something else and is never overwritten. **The update takes the phone's path.** Patch 0012 hands `omarchy update` to `omamobile-update`, which runs Omarchy's own `omarchy-update -y` unchanged, with stand-ins first on `PATH` for the steps that don't belong on a phone. Step by step: @@ -230,7 +232,7 @@ The same Alpine-based initramfs, with release differences: **The phone follows Omarchy's stable channel.** Phones installed before 2026-10-20 take `[omarchy]` from edge, which then carried 4.5.0rc1, a release candidate the phone's patches don't apply to. Switch before the next update, because the update would fetch the candidate in the same transaction as the fixed patches: `sudo sed -i 's|pkgs.omarchy.org/edge/|pkgs.omarchy.org/stable/|' /etc/pacman.conf && sudo rm -f /var/lib/pacman/sync/omarchy.db* /tmp/checkup-db-*/sync/omarchy.db*`. Removing edge's cached database matters: it is newer than stable's, so pacman's refresh keeps it and still offers the candidate. `omamobile-omarchy` 0.1.3's `omamobile-update` refuses an edge or rc `[omarchy]` and prints that line. Don't use Omarchy's own `omarchy-channel-set` or `omarchy-refresh-pacman` on the phone: they copy Omarchy's x86 `pacman.conf` and mirrorlist over the phone's (no `[omamobile]`, no Arch Linux ARM) and then upgrade everything. -**`[omamobile]` can hold Omarchy at a version the patches support.** `rootfs/packages.pinned` lists upstream package files by SHA-256 and URL (upstream's first, then our published copy, for when upstream prunes it); `tools/build-packages` adds them to `out/repo` unchanged, signed with the release key, so the daily publish carries them too; it refuses a pin with the name of a package we build, and `tools/release`'s packages stage refuses an index without every pin. `[omamobile]` comes first, so its copy wins over the newer one in `[omarchy]`: `omarchy update` (and `checkupdates`, behind the update toast) offers no newer Omarchy, and images install the pinned one. Since 2026-11-06 it holds `omarchy` and `omarchy-settings` at 4.0.6, because the series doesn't apply to 4.5 and 4.5's migrations install packages that replace ours (#433, #434). When a series for the new Omarchy ships, its line comes out and phones move on at their next update. A phone that already took the newer Omarchy keeps it: pacman doesn't downgrade on `-Syu`. +**`[omamobile]` can hold Omarchy at a version the patches support.** `rootfs/packages.pinned` lists upstream package files by SHA-256 and URL (upstream's first, then our published copy, for when upstream prunes it); `tools/build-packages` adds them to `out/repo` unchanged, signed with the release key, so the daily publish carries them too; it refuses a pin with the name of a package we build, and `tools/release`'s packages stage refuses an index without every pin. `[omamobile]` comes first, so its copy wins over the newer one in `[omarchy]`: `omarchy update` (and `checkupdates`, behind the update toast) offers no newer Omarchy, and images install the pinned one. Since 2026-11-06 it holds `omarchy` and `omarchy-settings` at 4.0.6, while the 4.5 companion changes and update validation remain pending (#433, #434); 4.5's migrations can install packages that replace ours. Once the new series and its companions are accepted, the maintainer moves the pins to the reviewed package versions and phones move on at their next update. A phone that already took the newer Omarchy keeps it: pacman doesn't downgrade on `-Syu`. **Recovering a phone that took Omarchy 4.0.6 with `omamobile-omarchy` 0.1.0.** Its migration 1791403252 ran: `[omarchy]` sits above `[omamobile]`, Omarchy's Hyprland replaced the phone's, and no phone patch applies (no PIN pad on the lock screen, `omarchy update` no longer handed over). `omamobile-update` then refuses on the repository order, so the fix goes in by hand, over SSH or in a terminal on the phone: @@ -279,7 +281,7 @@ For a first install, or to recover a phone that won't boot. One bundle per devic | Piece | Where | Notes | | --- | --- | --- | | aarch64 packages without a phone | `tools/build-packages` | makepkg in an Arch Linux ARM container (the official tarball, MD5 and signature checked against the pinned build key, `tools/lib/alarm.sh`) under the laptop's qemu-user; signs with `keys/` into `out/repo/aarch64`. Mesa, Hyprland and libcamera take hours this way, so they're built only when named, once per version | -| The device's root image | `tools/build-rootfs`, `rootfs/` | pacstrap in that container: `rootfs/packages.base`, then Omarchy's own `install/omarchy-base.packages` (minus `rootfs/packages.omarchy-skip` and what isn't built for aarch64), then `rootfs/packages.omamobile`, the device package and the board's `ROOTFS_PACKAGES`, the `[omamobile]` repository itself, the kernel modules of the current build, and `patches/omarchy`. Output `out/omamobile-rootfs---aarch64.img.zst`, `.sha256` and a `MANIFEST` with every package version (also inside, `/usr/share/omamobile/rootfs/MANIFEST`) | +| The device's root image | `tools/build-rootfs`, `rootfs/` | pacstrap in that container: `rootfs/packages.base`, then Omarchy's own `install/omarchy-base.packages` (minus `rootfs/packages.omarchy-skip` and what isn't built for aarch64), then `rootfs/packages.omamobile`, the device package and the board's `ROOTFS_PACKAGES`, the `[omamobile]` repository itself, the kernel modules of the current build, and `omamobile-omarchy`'s version-selected patch family. Output `out/omamobile-rootfs---aarch64.img.zst`, `.sha256` and a `MANIFEST` with every package version (also inside, `/usr/share/omamobile/rootfs/MANIFEST`) | | First boot | `packages/omamobile-firstboot` | reads `/etc/omamobile/firstboot.conf` (data, never sourced), creates the user, SSH keys, ufw with SSH on `usb0`, runs Omarchy's own setup leaves (skipping four that don't fit a phone), SDDM autologin and the lock, Omarchy's and our user setup, then deletes the file | | Growing the root | `initramfs/init` (`grow_root`) | `resize2fs` before mounting, only for a file system labelled `omamobile-root` smaller than its partition; `omamobile.noresize` skips it | | The installer | `tools/install-phone` (the bundle's `install`) | as described below, steps 1, 3-5; the factory-image step (2) is `tools/phone-provision` after the first boot instead | @@ -321,9 +323,9 @@ The bundle's signed `SHA256SUMS` covers its `MANIFEST`, which names the exact ro 1. Checks the bundle's signature and checksums, and that `fastboot getvar product` is this bundle's codename, the bootloader is unlocked, and both slots carry the same bootloader version. Any doubt stops it. 2. Asks for the user's factory zip, checks its `board=`, and runs the device's firmware and chroot extraction on the laptop. -3. Makes a **local copy** of the root image and writes into it, with `debugfs -w` (no root needed): the extracted firmware, the user's SSH public key, `/etc/omamobile/boot-update.conf` with `AUTO_WRITE=yes`, and a first-boot marker naming the device package to install. Nothing extracted leaves the laptop except into the user's own phone. +3. Makes a **local copy** of the root image and writes into it, with `debugfs -w` (no root needed): the extracted firmware, the user's SSH public key, `/etc/omamobile/boot-update.conf` with `AUTO_WRITE=yes`, and a first-boot marker naming the device package to install. The same key goes into a local copy of the ramdisk image's initramfs, as the boot hook appends it (§5.2), and that copy is what step 5 flashes. Nothing extracted leaves the laptop except into the user's own phone. 4. Shows exactly what it will write (`BOOT_IMAGES` with `_b`, and `userdata`), says that `userdata` is erased (stock Android needs a factory reset if it is ever booted again), and waits for the user to type the codename. -5. Runs only `fastboot flash _b images/.img` for each `BOOT_IMAGES` entry, `fastboot flash userdata `, `fastboot --set-active=b` and `fastboot reboot`. The partition names come from the descriptor and are checked against its `UFS_RW` again; the script has no code path for any other partition, no `-w`, no `--slot`, no `flashing` command. +5. Runs only `fastboot flash _b images/.img` for each `BOOT_IMAGES` entry (the ramdisk image from its copy, step 3), `fastboot flash userdata `, `fastboot --set-active=b` and `fastboot reboot`. The partition names come from the descriptor and are checked against its `UFS_RW` again; the script has no code path for any other partition, no `-w`, no `--slot`, no `flashing` command. 6. On first boot, `omamobile-setup-system` installs the device package named by the marker (from the package cache, offline) and reminds the user to take the read-only backup of `efs`, `efs_backup`, `modem_userdata`, `persist` and `modem_a/b` ([MODEM-PLAN](../device/cheetah/MODEM-PLAN.md) M0.1) before any radio work. `tools/nv-backup DIR` (in the bundle's `tools/`) takes it over USB SSH: the partitions from the descriptor's `NV_PARTS` and `NV_BACKUP_EXTRA`, found by `PARTNAME`, refused unless every one is found once, read-only and unmounted, each copied with `dd`, read again on the phone and compared, into a directory of mode 700 with files of mode 600; `--check DIR` compares the phone with it later. `bin/omamobile flash` stays the developer's tool; `install` is for everyone else and is deliberately narrower. diff --git a/docs/REMOTE-TESTING.md b/docs/REMOTE-TESTING.md index 5b3a32454..03153019a 100644 --- a/docs/REMOTE-TESTING.md +++ b/docs/REMOTE-TESTING.md @@ -5,7 +5,7 @@ Most of bringing up a phone is trying things on it: does the speaker play, does ![An agent or script on a computer drives the phone over ssh](screenshots/remote/remote-overview.png) -It is opt-in. `omamobile-remote` and the patched `wlrctl` are in `packages/`, no image installs them, and installing them enables nothing: no service, no udev rule, and nothing listens.. See [Security](#security). +It is opt-in. `omamobile-remote` and the patched `wlrctl` are in `packages/`, no image installs them, and installing them enables nothing: no service, no udev rule, and nothing listens. See [Security](#security). `omamobile-mirror` is the other way in: a VNC window on your computer, with your own mouse and keyboard driving the phone, for demos and for typing. This is for scripts and agents: nothing to watch, no viewer, no open port, and every action and screenshot is a command with an exit code. @@ -14,7 +14,7 @@ It is opt-in. `omamobile-remote` and the patched `wlrctl` are in `packages/`, no On the phone, from the repository built by `tools/build-packages`: ``` -pacman -U wlrctl-0.2.2-1-aarch64.pkg.tar.* omamobile-remote-0.1.0-1-any.pkg.tar.* +pacman -U wlrctl-0.2.2-1-aarch64.pkg.tar.* omamobile-remote-0.1.2-1-any.pkg.tar.* ``` From your computer, an ssh key to the phone's user (USB networking is the easy way: `ssh user@172.16.42.1` on the images that have it). Every command below is run as that user: diff --git a/docs/TELEPHONY-APPS-PLAN.md b/docs/TELEPHONY-APPS-PLAN.md index 164c0305d..1e4011606 100644 --- a/docs/TELEPHONY-APPS-PLAN.md +++ b/docs/TELEPHONY-APPS-PLAN.md @@ -134,7 +134,7 @@ shell status / quick settings ──────────────── └─ AoC voice PCMs (EP5/EP4), rmnet0 ``` -- **Why a separate process.** `omamobile-sitd` holds the safety model: the allow-list, the do-not-send list, durable SMS sends that never repeat, and power-off when a hangup isn't confirmed. Keeping D-Bus out of it keeps that code small and keeps its tests (`tools/sit-sim`) as they are. A crash in the bridge can't drop a call, and the bridge can restart freely, which the RIL can't (a second start-up on the same CP isn't supported). +- **Why a separate process.** `omamobile-sitd` holds the safety model: the allow-list, the do-not-send list, durable SMS sends that never repeat, and radio-off recovery for unconfirmed call release. Keeping D-Bus out of it keeps that code small and keeps its tests (`tools/sit-sim`) as they are. A crash in the bridge can't drop a call, and the bridge can restart freely, which the RIL can't (a second start-up on the same CP isn't supported). - **Why Python, with dbus-fast.** This differs from the apps, and it is Q3. The RIL is Python, and ofono2mm shows that Python with dbus-fast carries MM's whole API. The bridge is a translation layer with no performance load, and the same team reads both sides. Read Droidian's BSD-3-Clause original for structure (compatible with our MIT tree), and FuriLabs' GPL-2.0 fork for reference only. Rust with zbus is the alternative if the owner wants one language for everything new. It would add a toolchain to the system side, and the apps wouldn't share code with it anyway, since they use MM's public API. - **Changes to `omamobile-sitd`'s socket API** (T0, offline, against `tools/sit-sim`): - `subscribe`: a long-lived connection that receives one JSON event per change, with call, SMS, registration, signal and SIM events. The bridge then doesn't poll `state.json`. @@ -143,7 +143,8 @@ shell status / quick settings ──────────────── - Received SMS handed over by ID: the bridge exports each one as an `Sms` object, and a client's `Messaging.Delete` deletes it in sitd's store. That is Chatty's pattern: it copies each message into its own database and deletes it from the modem. - **Packaging, as built (T1, `packages/omamobile-mmd` 0.1.0; [MODEM-PLAN](../device/cheetah/MODEM-PLAN.md) "T0/T1: the ModemManager bridge"):** - Its own package, `omamobile-mmd`, with `conflicts=(modemmanager)` and **no `provides=`**: nothing in Arch or Arch Linux ARM hard-depends on `modemmanager` (gnome-calls, chatty, networkmanager and geoclue need only libmm-glib; mmsd-tng is AUR-only and also needs only libmm-glib). - - It ships `omamobile-mmd.service`, not `ModemManager.service`, with no `dbus-org.freedesktop.ModemManager1.service` alias: `Type=dbus`, `BusName=org.freedesktop.ModemManager1`, `Conflicts=ModemManager.service`, `WantedBy=omamobile-sitd.service`, and not enabled by the package. It also ships the D-Bus bus policy (only root owns the name) and MM's polkit actions. + - It ships `omamobile-mmd.service`, not `ModemManager.service`, with no `dbus-org.freedesktop.ModemManager1.service` alias: `Type=dbus`, `BusName=org.freedesktop.ModemManager1`, `WantedBy=omamobile-sitd.service`, and not enabled by the package (up to mmd 0.1.2 it also had `Conflicts=ModemManager.service`). It also ships the D-Bus bus policy (only root owns the name) and MM's polkit actions. + - From mmd 0.1.3 (#371), the unit has no `Conflicts=ModemManager.service`: starting the bridge must not stop another modem daemon. Package conflicts and exclusive D-Bus name ownership still provide exclusion. The optional tegu integration adds Requisite on an already active sitd, a read-only service check, and an attended attachment helper; it enables neither modem nor RIL. - **No D-Bus activation file**, so no client can start the bridge. Enabled, it starts with `omamobile-sitd`. - No `mmcli` and no CLI of our own. Phone runbooks read the modem through libmm-glib with `test/libmm-status.py`; mmcli runs only in the conformance container (`test/conformance`). - **Packaging, superseded (the design before T1, kept for history; not built):** a package named `omamobile-mm` with `provides=(modemmanager)` and `conflicts=(modemmanager)`, shipping `ModemManager.service` aliased `dbus-org.freedesktop.ModemManager1.service`, the bus policy, a D-Bus activation file, and `mmcli` or a small `omamobile-mm-cli`. T1 dropped `provides=` (no package needs it), the activation file (so no client can start the bridge) and the takeover of ModemManager's unit name. diff --git a/docs/release-notes/2026.11.08.md b/docs/release-notes/2026.11.08.md new file mode 100644 index 000000000..7fe58138d --- /dev/null +++ b/docs/release-notes/2026.11.08.md @@ -0,0 +1,100 @@ + +# Omarchy Mobile 2026.11.08 (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.08`, linux-omarchy-mobile's `omamobile` branch at `1a9d1d4e9289` (Linux 7.3-rc6 plus our drivers); `uname -r` is `7.3.0-rc6-omamobile-g1a9d1d4e9289`. The source is public at that tag before any binary ships. +- **Userspace:** Arch Linux ARM, Omarchy 4.0.6 (held at that version in `[omamobile]` until our patches are ported to 4.5) 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. On the test install of this release, a reinstall of its `linux-omamobile` ran the hook: it rebuilt slot B's five images, left the four that matched, wrote `vendor_kernel_boot` (its initramfs gains the owner's SSH key, which the bundle's doesn't carry), read it back, and the phone booted it. An update to a newer kernel hasn't run on 2026.11.08 yet; the same `omamobile-boot-update` 0.1.0 wrote and rolled back one on 2026-11-02. + +### 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](https://github.com/derekross/omarchy-mobile/pull/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 | +| 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 + +- **Double tap to wake:** a double tap on the dark screen wakes the lock screen, and a single touch, a pocket or a brush of the palm leaves it dark. Covered by a hand or a pocket (the proximity sensor reads near), a double tap is ignored too. +- **`reboot-to bootloader` reaches fastboot by itself:** the kernel writes the bootloader reason where Google's driver does, so no button combination is needed. +- **A low battery starts charging sooner:** the charger looks again every 2 s for the battery reading instead of waiting 30 s with charging off, and the battery gauge retries a failed model load. The retry hasn't met a really flat battery yet ([#169](https://github.com/derekross/omarchy-mobile/issues/169)); if the phone keeps restarting on the cable, see Known issues. +- **Touch, Wi-Fi and the clock:** a touchscreen variant that sends no identify report now probes; Wi-Fi skips scan results on bands the chip can't use; the clock (the power chip's RTC) reads correctly, and every RTC-timed sleep wakes on time in our tests (10 of 10). +- **Recent apps** stay on the card you were on when another window closes. +- **The battery's reported state** (charging, full, not charging) in the shell. +- **The Hotspot tile** brings the DHCP server it needs (dnsmasq). +- **The Greek keyboard** has a row of accented vowels, and Omarchy's About window fits the screen. +- **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), on by default (`omamobile-modem-sit` 0.3.30 with `omamobile-device-cheetah` 0.1.44). A development install whose `/etc/omamobile/modem-sit.conf` was edited (the Mobile network page writes it) keeps its `card = none` line: delete it for call audio. 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. +- **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, and installing it is still a separate step: after the first start, run the bundle's `tools/phone-provision` with your own factory image for your phone (Wi-Fi, Bluetooth, haptics, speakers, sensors, the modem, cameras and the fingerprint sensor), then restart the phone. Until then Wi-Fi, sound, the modem and fingerprint don't work, and the setup can't offer a fingerprint. A guided installer that does this on its own is the next release's goal. +- **Run `omarchy update` as yourself, never as root:** from the phone's terminal or the Updates entry. As root over SSH it stops before updating anything, with "OMARCHY_PATH: unbound variable"; set by hand, the variable lets it continue, and Omarchy then runs every one of its migrations again as root (it keeps their record per user), which swaps the shell's quickshell for an older build. `omamobile-omarchy` 0.1.38 refuses a root update and says why ([#548](https://github.com/derekross/omarchy-mobile/pull/548)); it reaches the development channel first. +- **A completely flat battery:** if the phone keeps restarting on the cable, hold Volume Down + Power for fastboot and leave it there on the charger for 20-30 minutes (`fastboot getvar battery-voltage` should pass 3.8 V), then choose Start ([#169](https://github.com/derekross/omarchy-mobile/issues/169)). +- **Stopping the modem** (`systemctl stop omamobile-modem`) takes 40 s and is logged as a crash ([#532](https://github.com/derekross/omarchy-mobile/issues/532)), though it stops cleanly; to get the modem back, restart the phone rather than starting it again. +- **Omarchy 4.5:** this release is built for Omarchy 4.0.6. A phone that already took Omarchy 4.5 before the hold isn't supported by this release's patches yet. +- **`systemd-firstboot` fails once** on the first start (the phone has no console); Omarchy Mobile's own first-boot setup does its job. + +## 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.2 or later (our build, with the DPMS fix) and `omamobile-shell` 0.2.79 or later 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.08.tar` with its `.tar.sha256` (and `.tar.sha256.sig`, to check the signature) from `https://pkgs.omamobile.org/releases/cheetah/2026.11.08/`, 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. diff --git a/docs/review/LESSONS.md b/docs/review/LESSONS.md index abcf566f3..d872bd088 100644 --- a/docs/review/LESSONS.md +++ b/docs/review/LESSONS.md @@ -468,6 +468,122 @@ never change, so reviews can cite them. 12 to 17). *Check:* grep the author's comments on the device issue since that date and diff the extent (levels, durations, parts). Extends L-435. *From:* #450, round 42, 2026-11-07. +- **L-531. An isolation check we suggest never reads the node it makes.** + Drafting W5's character-side check for #493 nearly suggested `head -c1` on a + `c 1:1` node, which, if the rule failed, reads physical address 0 through + `/dev/mem`. *Check:* every suggested proof of a device refusal stops at + `mknod` or `open` of a harmless device; `/dev/mem`, `/dev/port` and + register-backed nodes are tested by `mknod` only. Extends AGENTS.md section + 1 and L-454. *From:* #493, round 44 (a near miss in drafting); 2026-11-08. +- **L-532. A measuring tool we name for another phone is read for hard-coded + register addresses first.** `tools/display-hz` `devmem`-reads cheetah's + DECON at `0x1c24xxxx`; suggested for a 9a rate-switch check on kernel #212, + it would have read an unknown zumapro block. *Check:* `grep -n + 'devmem\|0x[0-9a-f]\{8\}' tools/` before a draft names it for a phone + that isn't cheetah; name a log line or a compositor query instead. Extends + L-295 and L-276. *From:* kernel #212, round 44 (a near miss in drafting); + 2026-11-08. + Again in round 45, the right way round: kernel #212's author counted the + DECON frame-start interrupt in `/proc/interrupts` under a redrawing terminal + (120/60/121 per second), read-only and device-neutral; name that (`grep -i + decon /proc/interrupts` twice, a second apart) when asking another phone for + a rate. +- **L-533. A lens or OIS controller at the same I2C address as the module's + calibration EEPROM is a calibration part.** Stock's tegu DT puts + `eeprom-nessie`, `act-nessie` and `ois-nessie` all at 0x24: the LC898129 + holds the module's calibration. *Check:* grep the device's `*-camera.dtsi` + for nodes sharing the actuator's `i2c-addr`; if one is an EEPROM, the driver + writes only the registers it names, and the notes list every register + written during bring-up. Extends L-90 and L-108. *From:* kernel #213, round + 44, 2026-11-08. +- **L-562. A custom recovery or installer in a contributor's record is a slot + question first.** Kodiak's notes said a step was "taken from" a third-party + recovery and sat merged through two rounds; the answer, "installed to + `vendor_boot` on both slots, may have mounted persist", means slot A was + written, the fallback recovery is no longer stock's, and the calibration + backup and slot B's rollback set may not be stock's either. *Check:* + whenever a third-party recovery, root tool or installer appears, ask which + partitions on which slots it wrote (`vbmeta` flags included), when relative + to each backup, and what it mounted; record a slot A write as a §3.1 event + and downgrade any backup taken under it (L-198). Extends L-186, L-198 and + L-35. *From:* #511 with #489 and #231, round 45, 2026-11-08. +- **L-563. A locally administered MAC that a PR makes persistent is an + identifier, and `tools/pr-check` exempts it and reads no commit message or + PR body.** #510 saves a random address pair per phone, so the contributor's + example in the body and commit now names their phone to every host it meets. + *Check:* for a PR that stores generated addresses or IDs, grep the body, + every commit message and the thread for them (the L-324 pattern without the + locally-administered exemption), and ask for placeholders and a rotation. + Extends L-324 and L-145. *From:* #510, round 45, 2026-11-08. +- **L-564. `reboot-to` (and `bin/omamobile push`) stops no unit, so with the + modem up it leaves `/var/lib/omamobile/modem-up` behind and the next boot + skips the modem once.** *Check:* a runbook or test plan that reboots a phone + with the modem up stops it first (`systemctl stop omamobile-modem`; it takes + about 40 s and ends as "failed" for now, issue #532), or uses `systemctl + reboot`. To keep the modem off for a boot it is `systemctl mask + omamobile-modem-boot.target`, not `/etc/omamobile/modem-hold`, which matters + only after an unclean end. *From:* the 2026-11-08 7 Pro session, issue #532. +- **L-598. A code change that enables a protected-partition write waits until + its evidence is called verified, not provisional.** #436 marked its 3.11 + table "provisional, not a same-state row" in the same push that kept the + build flag enabling 3.11 writes at every boot. *Check:* for a PR that widens + a `devinfo`, GPT or calibration write, grep its notes for "provisional", "not + yet confirmed" and "still needs"; if one applies to the layout, ask for the + enabling switch to come out (or a split) until it goes. Extends L-2, L-36 and + L-527. *From:* #436, round 46, 2026-11-09. +- **L-599. (Provisional: from ABL's documented retry behaviour on 3.15, not + yet seen on 3.11.) A same-state row for slot metadata has no slot boot + between its two reads.** ABL spends a retry when it boots an unmarked slot, + so `getvar` before a boot and Linux's bytes after it disagree on a correct + layout. *Check:* when a row's retry byte is one below `getvar`, ask in which + order the reads were taken, and prescribe the Linux read, then fastboot by + the buttons, then `getvar`. Extends L-36 and L-527. *From:* #436, round 46, + 2026-11-09. +- **L-600. A "read-only check" a contributor reports is also read for what the + phone is running now.** #330's check showed a live session of an unpublished + image with `/sys/block/sda/ro` 0 on a single-slot phone. *Check:* for any + reported `ro` values, read the whole-disk lines first, then ask what booted, + how and since when, before reading the partition lines as a guard result. + Extends L-321 and L-562. *From:* #330, round 46, 2026-11-09. +- **L-601. A guard change that makes a partition writable is checked for a + writer in the same tree.** #530 opened enchilada's `boot_b` on `sde`, while + `flash` and `push` refuse `android-v0`, `push` and `omamobile-boot-update` + look on `sda` only, and a fastboot install never runs the guard, so the only + possible writer was a hand `dd`. *Check:* for each partition a guard or + allowlist change opens, grep `cmd_push`, `cmd_flash`, `omamobile-boot-update` + and `tools/install-phone` for how they find it; if no tool reaches it, the + opt-in waits for the writer's PR, and the mechanism can land inert. Extends + L-321 and L-422. *From:* #530, round 46, 2026-11-09. +- **L-602. A contributor's note that a documented recovery path didn't work on + their phone is checked against what the PR changes before it lands in the + device's notes.** #554's NOTES said Volume Down + Power "ended in a normal + boot", and kernel #233's fix, which runs only at power off, can't touch that + path. *Check:* name the mechanism the fix changes and the one the claim + uses; if they differ, ask for the hold, the starting state and the result, + and keep AGENTS' instruction until it is re-run. Extends L-29 and L-91. + *From:* #554 with kernel #233, round 46, 2026-11-09. +- **L-603. A boot that replaces `multi-user.target` as the default loses + everything wanted only there:** `omamobile-boot-success`, ufw, logind (#554's + off-mode charging target). *Check:* `grep -l 'WantedBy=multi-user'` over the + image's units (Omarchy's included) and each device package's + `multi-user.target.wants/`, and say for each whether the new boot needs it. + *From:* #554, round 46, 2026-11-09. +- **L-604. A PR that touches AGENTS.md or CONTRIBUTING.md is word-diffed in + full against its own parent, not only read where its topic is.** #409's + 9a-sleep commit replaced the whole AGENTS.md with what looks like a local + copy: the first safety rule became "Reboots and pushes do not need advance + approval", and three maintainer-only tool rows lost their "human's go"; the + commit message mentioned none of it. *Check:* `git show -- + AGENTS.md CONTRIBUTING.md | grep '^[-+]'` for every commit; any hunk outside + the PR's stated topic is blocking until explained. Extends L-224, L-339 and + L-486. *From:* #409, round 46, 2026-11-09. +- **L-605. When a safety fix's only way back is a step the device can't take, + the decision says so.** The 9a's gauge leaves POR only when Android reloads + the model, and a stock boot there costs userdata, so "refuse until reloaded" + meant "no battery for good". *Check:* for a refusal a PR relaxes, name what + clears the refused state on that device and whether AGENTS §4 allows it. + Extends L-284. *From:* kernel #234, round 46, 2026-11-09. + ## Shared code and the reference device @@ -874,6 +990,120 @@ never change, so reviews can cite them. *Check:* `gh pr list` for PRs touching the file, grep their heads for `printf`/`strto*`, and build a no-bootctl device's initramfs. Extends L-104 and L-423. *From:* #459 with #403, round 42, 2026-11-07. +- **L-534. A tuning-file change is cheetah-neutral when the file's name is a + sensor model only another board's compatible produces.** libcamera picks + `.yaml` by the subdev name, which `s5kgn1.c` takes from the match + data's `model`. *Check:* the driver's `v4l2_i2c_subdev_set_name` argument, + the match table, and `git grep` of the compatible in the gs201 DTs. Extends + L-206. *From:* #494, round 44, 2026-11-08. +- **L-565. An error-path-only fix in a shared driver is cheetah-neutral in + behaviour only while that error never happens, and its object still + changes.** Kernel #222's one `break` reallocated registers across + `s3c64xx_spi_transfer_one` (and moved the readl pool into `runtime_resume`'s + last line), and the 7 Pro has three SPI users that chunk in PIO. *Check:* + grep `logs/` for the error line the new branch follows (`I/O Error: rx-`: 0 + in 1000 logs) before calling the change invisible, and let the 7 Pro run + record "not exercised" with that count rather than "the fix works". Extends + L-51, L-206 and L-440. *From:* kernel #222, round 45, 2026-11-08. +- **L-566. A doc change we ask for in a shared package's plan is checked for + which phone it claims.** On #376 we asked that the 7 Pro's MODEM-PLAN stop + saying "a second start isn't supported" once the code changed; the reworded + line states the new behaviour as a 7 Pro fact, measured only on the 9a. + *Check:* for each sentence a PR changes under `device//`, find the run on + that device that supports it, or ask for "on the ; not yet run + here". Extends L-188 and L-31. *From:* #376, round 45, 2026-11-08. +- **L-567. A public device package tested next to a private companion is + checked for which safety nets live only in the companion.** #222's oriole + package installed cleanly, but only alongside a private package carrying the + reboot watchdog and a boot check, and `device.conf`'s `PACKAGE=` makes the + public one alone the image's device package. *Check:* when a smoke report's + package list names a `*-local-*` or private package, ask what it ships, and + map each safety file to the public package or to a "not supported yet" line + in the README. Extends L-61, L-158 and L-358. *From:* #222, round 45, + 2026-11-08. +- **L-568. L-8 runs without touching anyone's build directory.** Copy a kernel + output's `arch/arm64/boot/Image`, the device's DTBs, + `scripts/dtc/{dtc,fdtoverlay}`, `initramfs.cpio.lz4` and + `include/config/kernel.release` (and `initramfs.release`) into a scratch + `KERNEL_OUT`, then run `DEVICE=cheetah images` with main's `bin/omamobile` + (`git show origin/main:bin/omamobile`) and the PR's from the same worktree. + `images` writes only `$KERNEL_OUT/images`, and a stale build is fine for a + before/after compare. *Check:* six equal sha256s. Extends L-8 and L-194. + *From:* #507, round 45, 2026-11-08. +- **L-569. A fix that updates every `cmp`-pinned copy of a shared source goes + stale when a new package with the same pin merges first, and then it turns + main red.** #459 updated seven `reboot-to.c` copies; akita's package, with + the same `cmp` against cheetah's file, merged two days later (#456), so #459 + as it stands fails akita's `test/all` and needs an akita version that #509 + is about to take. *Check:* each round, for every open PR that edits a file + other packages pin, `git grep -l '' origin/main -- + 'packages/*/test/all'` against the PR's file list, and put the missing + packages and their next free versions in the merge plan. Extends L-257 and + L-426. *From:* #459 with #456 and #509, round 45, 2026-11-08. +- **L-570. A test kernel for `bin/omamobile push` needs four steps into its + `KERNEL_OUT`: `kernel`, `initramfs`, `images` (with `DEVICE=cheetah`) and + `modules`.** `push` refuses before any write when one is missing ("holds + images for … an unknown device", "build the initramfs first", the missing + modules tarball), so a skipped step costs a round trip, not the phone. + *Check:* a runbook that hands the human a test kernel lists all four with + the same `KERNEL_DIR`/`KERNEL_OUT`, in that order. *From:* the 2026-11-08 7 + Pro session. +- **L-606. A shared stop-path fix proven on one phone's unit is checked + against the other phone's unit settings.** #372's rfsd hold makes the 9a's + modem stop end in `success`, but the 9a's transient unit sends SIGINT to the + whole control group, while the 7 Pro's `omamobile-modem.service` uses + `KillMode=mixed` with SIGTERM to `unshare`, which issue #532 found doesn't + exit. *Check:* for a "now ends in success on both phones" claim, compare + `KillMode`, `KillSignal`, `TimeoutStopSec` and the main process of each unit + that runs the shared code, and ask for (or do) a stop on each. Extends L-206, + L-348 and L-492. *From:* #372 with issue #532, round 46, 2026-11-09. +- **L-607. "Enabled" read from `systemctl is-enabled`, or from "not masked", + is wrong for a unit started by a vendor wants link in one device package + and by nothing on the others.** #555's status line did that for a shared + unit. *Check:* for a switch over a shared unit, list each device package's + `*.target.wants/` links for it, and read `systemctl show -p WantedBy` rather + than `is-enabled`. Extends L-137 and L-206. *From:* #555, round 46, + 2026-11-09. +- **L-608. A feature split into "opt-in" and "helper" parts is checked for + which parts are actually behind the opt-in.** #556's inhibitor waits for + `modem-suspend-enable`, but sitd's screen-state reporting, written as M6's + helper, runs on every phone with sitd. *Check:* for each new behaviour in + the PR, find the condition that gates it in the shipped unit or script, and + list the devices it reaches with the opt-in off. Extends L-206 and L-458. + *From:* #556, round 46, 2026-11-09. +- **L-609. A hand copy that one PR's record reveals is checked against the + package another open PR ships for that phone.** #514's "Current state" + listed an AoC blacklist in `/etc/modprobe.d` on the 8 Pro, while #453's + first packaged boot was meant to test the package's own blacklist. *Check:* + for each hand-installed file a contributor's notes list on a phone, `git + grep` its role (modprobe, UCM, unit) across that author's open package PRs + for the device, and add it to that PR's "remove the hand copies" step. + Extends L-46. *From:* #453 with #514, round 46, 2026-11-09. +- **L-610. A stacked draft that carries another open PR's commits inherits + that PR's pending reference-phone run, and the review says whose run it + is.** Kernel #164's per-function diff showed 24 changed functions in + cheetah's `gs201-csis.o` and 16 in `imx386.o`, all from #63 and #103, whose + promised 7 Pro capture (10-28) the maintainer still owed. *Check:* map each + changed cheetah object to the commit and PR it comes from (patch-id against + the open heads), and grep those threads for the promised run before asking + the contributor for anything. Extends L-196 and L-480. *From:* kernel #164, + round 46, 2026-11-09. +- **L-611. A consumer-side "re-apply the pins" fix in a shared driver is shown + cheetah-neutral through the pinctrl core's early returns, node by node.** + For kernel #224, gs201's UFS has no `pinctrl-0`, so `dev->pins` is NULL; + gs101 and zuma have "default" only, so the sleep select is `IS_ERR` and the + default select hits `p->state == state`. *Check:* the reference phone's node + and overlays for `pinctrl-*`, then `pinctrl_bind_pins()` and + `pinctrl_select_bound_state()` on the base. Extends L-228. *From:* kernel + #224, round 46, 2026-11-09. +- **L-612. Before planning a contributor's own test of a shared-driver path, + check that their board's DT takes it.** Kernel #223's code runs only with + `maxim,fg-model`, which on our tree only cheetah and panther have, so the + author's Pixel 6 can't exercise it with the public tree. *Check:* `git grep + '' github/omamobile -- arch/`, and name the + phones that can test it. Extends L-490. *From:* kernel #223, round 46, + 2026-11-09. + ## Shell and scripts @@ -972,6 +1202,14 @@ never change, so reviews can cite them. holds only fakes; a generated-file check reads an input pinned in the repository with its version. Extends L-234 and L-410. *From:* #401, #408, issue #413, round 39, 2026-11-03. + Again in round 44: a "some `c N:*` line exists" pattern on #493 matched + unrelated wildcard lines (`c 5:*`, `c 136:*`); found by deleting the line + under test. + Again in round 45: #501's "reaches the MANIFEST" case read what its stub + `docker` printed, so it proved the plumbing and not the producer, and #505's + `tests/dipper-probe` checked that its needles are in `initramfs-inside.sh`, + always true, instead of feeding the real `initramfs/init` through the patch + step. - **L-467. `RestartPreventExitStatus=` covers the main process only; a pre-start refusal that must not be retried uses `ExecCondition=`.** #371's `ExecStartPre=` check exited 3 with `RestartPreventExitStatus=3`; on @@ -1053,6 +1291,222 @@ never change, so reviews can cite them. when sitd drops it mid-release, while sitd only drops ended calls. *Check:* list every way the daemon removes the object and the state the bridge is left in. Extends L-302. *From:* #461, round 42, 2026-11-07. +- **L-535. A patch that turns "a touch wakes" into "a touch is swallowed while + dark" changes what a stale dark flag costs.** Before #420's 0029, a lock + whose `displayDark` outlived the dark screen still woke on a touch; after + it, every touch is ignored until the lock's own wake clears the flag. + *Check:* list every path that can light the panel (power key, idle, call + watcher, Hyprland's own DPMS wakes, package version skew) and confirm each + clears the flag (here through `omarchy-shell lock wake`); where a skew can + light it without clearing it, ask for a `conflicts=` between the packages. + Extends L-161 and L-235. *From:* #420, round 44, 2026-11-08. +- **L-536. A guard that reads a display-synced sensor is checked for what the + sensor does with the display off.** omamobile-sensors' TMD3719 converts only + with the display state the HAL sends, the proxy sends "off" when the DSI + connector is off, and it keeps `ProximityNear` across releases, so #420's + pocket guard, claimed only while dark, may never read or may read stale. + *Check:* grep the backend for `DISPLAY_SYNCED` or its equivalent and the + proxy's `_release` before accepting a sensor-based guard, and ask for a + covered and an uncovered run with the panel off. Extends C-1. *From:* #420, + round 44, 2026-11-08. +- **L-537. "Reads the state before it acts" is checked for the time between + the read and the act.** #463's `unlock` reads the lock state, then wakes, + presses Return and waits 2 s before typing the PIN; an unlock in that window + (fingerprint, the person holding the phone) sends the PIN and a Return to + the focused app. *Check:* for any tool that injects input, list the sleeps + and actions between its guard and the sensitive write, and ask for the guard + again right before the write. Extends L-161. *From:* #463, round 44, + 2026-11-08. +- **L-538. A stricter check on a vendor tool's stderr is tried on a real input + with the system tool alone.** #491 started failing a copy on any debugfs + message outside a small allow-list, in a tool every install runs from the + release bundle, and its tests used stand-ins and a synthetic image. *Check:* + run only the host's tool (not the PR's) with the PR's exact command, as the + same user, on a scratch copy of a real image; count the lines the filter + would reject, then delete the copy. *From:* #491, round 44 (0 rejected on + the 7 Pro's 260705 vendor image); 2026-11-08. +- **L-539. A `--dry-run` that still writes local state is walked through every + runbook that pairs it with the real command.** `tools/release` runs + `repo-publish --dry-run stable` and then `stable`. On main the dry run + staged the new index, so the real promotion pruned stable's previous set at + every release (local stable: 45 files for 45 index entries); #492's record + fixes it, though the PR described only no-op dailies. *Check:* `git grep -n + -- '--dry-run' tools/release docs/` for each tool a PR changes, and run the + dry run and the real run back to back in the PR's test fixture. Extends + L-392. *From:* #492, round 44, 2026-11-08. +- **L-540. LXC 7's cgroup2 device rules are one-polarity lists, so "allow + before deny" is not a rule, and a global `a` after our include is the + hazard.** In the default allowlist mode, `bpf_device_add()` drops every + specific deny rule; a global `allow = a` or `deny = a` sets the mode and + clears every earlier rule. Our request on issue #465 and #493's comment both + assumed first-match order. *Check:* for any LXC device rule change, read + `src/lxc/cgroups/cgroup2_devices.c` at the packaged LXC tag, and ask what + mode the list is in, whether any `b` rule allows, and what in the generated + config is processed after our include. Extends L-31 and C-1. *From:* #493 + with issue #465, round 44, 2026-11-08. +- **L-541. A dynamic char major hard-coded in a shipped package couples it to + the kernel's built-in driver set.** Binder's 507 on cheetah comes from the + extended dynamic range, so a kernel update that adds a built-in driver with + a dynamic major moves it, and #493's fail-closed check then takes Waydroid + down until the package changes. *Check:* any `major:minor` in package config + at or above 234 and outside `Documentation/admin-guide/devices.txt`'s fixed + list gets a path-based rule, a value generated at start, or an update plan. + *From:* #493, round 44, 2026-11-08. +- **L-571. An allow line added because "Waydroid binds it" is checked for what + the node lets the container do to the host.** #493's `/dev/uhid` creates HID + devices that the host compositor reads, which is a way to inject input into + the host session; Android booted without it and logged nothing about it. + *Check:* for each new `lxc.cgroup2.devices.allow`, name the host object that + opening the node creates or reaches (uhid and uinput are host input, `kvm` + host CPU state, `mem` and `port` host memory and I/O), and ask for a failing + Android feature without it before it goes in. Extends L-540 and L-454. + *From:* #493, round 45, 2026-11-08. +- **L-572. A lock added to an input handler is checked for what a holder that + hangs does to every later press.** #508's `flock` without `-w` made a stuck + short-press action freeze the power key for the session, where main would + have let the next press through. *Check:* for any new `flock`, mutex or + queue in a key, touch or wake path, run the PR's harness with the slowest + helper made to sleep past the press interval, measure when the next press + acts on main and on the head, and ask for a bound. Extends L-161 (fail + towards the user being able to act). *From:* #508, round 45, 2026-11-08. +- **L-573. Deferring a surface's "on open" reads is checked against what the + surface shows first and what refreshes it while it's closed.** #518 queued + the shade's notification read ninth, behind the reveal, and the shade's + periodic read runs only while it's open (`running: root.opened`, first tick + at 3 s), so every open showed the previous open's list for about 0.65 s. + *Check:* for each read moved off the open path, `grep -n` its function for + the timers and watchers that call it, note their `running:` condition, and + compute when the first fresh value appears after opening; ask that what the + first screen shows goes first. Extends L-235. *From:* #518, round 45, + 2026-11-08. +- **L-574. (Provisional, not yet checked on a phone.) A network-sharing + feature is checked against the firewall the image turns on.** #525 makes the + hotspot's dnsmasq start, but firstboot's ufw denies incoming and forwarded + traffic, so a client's DHCP and DNS may never reach it, and the PR's test + (the server side came up) can't show that. *Check:* `git grep -n 'ufw ' + packages/omamobile-firstboot` for the defaults, and ask for one client test + (an address, then a ping out) before a "hotspot works" claim. Confirm or + drop once a client test has run. *From:* #525, round 45, 2026-11-08. +- **L-575. A Mesa `pkgrel` bump moves `_omamobile` with it (1.3 with + omamobile3, 1.4 with omamobile4).** The marker is what shows in `GL_VERSION` + and the libgallium name, so a bump that leaves it reports the old build on + the phone. *Check:* `git log -p -- packages/mesa/PKGBUILD | grep -E + '^[-+](pkgrel|_omamobile)='` on every Mesa PR. *From:* #500, round 45 + (missed in round 44), 2026-11-08. +- **L-576. A build host that is not Arch runs the tools' pacman steps in the + container, with that container's view of keys and users.** `repo-add` there + ran as `-u $(id -u)`, which under rootless Docker can't read the release + keyring (#544), and the Omarchy keyring isn't on the host at all (#547). + *Check:* a dry run of `tools/repo-publish` on a new build host before its + publish timer is enabled. *From:* #544, #547, 2026-11-08. +- **L-613. An `EXIT` trap that clears a hang marker also runs when systemd + times the unit out.** Bash runs the EXIT trap on SIGTERM, also mid-write + when the block is interruptible, so #510's cleanup that removes the marker + turned a timed-out hang into "finished", and the next boot would repeat it. + *Check:* for a boot script with a marker and `TimeoutStartSec=`, find which + code paths remove the marker, then run the script with its slow step + replaced by a FIFO open and `kill -TERM` it: the marker should survive. + Extends L-170 and L-468. *From:* #510, round 46, 2026-11-09. +- **L-614. A flag that blocks a repeated user action is checked for where it + is cleared.** #461's `releasing` stops a second hang-up while the first is + outstanding, but nothing clears it after a refusal or a timeout, so the + Phone app can then never end the call. *Check:* for every "in progress" flag + a PR adds to a user-facing method, `grep -n` every assignment and list the + states that clear it; a terminal error path with no clear is a question. + Extends L-302 and L-502. *From:* #461, round 46, 2026-11-09. +- **L-615. When a PR serializes one caller of a shared state change, the + review re-lists the callers on today's main, not on the PR's base.** #508 + locked the power key's short action; #420, merged a day later, added two + more display transitions in the same script that don't take the lock. + *Check:* `git diff origin/main -- ` for new entry points + that reach the same helpers (`wake_*`, `lock_dark`, `omarchy-system-lock`), + and ask whether each takes the lock. Extends L-462 and L-572. *From:* #508 + with #420, round 46, 2026-11-09. +- **L-616. Moving a UI removal behind an acknowledgment is checked against + what the row's own animation leaves on screen while it waits.** In #533, + `NotificationRow` folds to height 0 and only then calls + `forgetNotification`, so the row stays in the model, invisible, until the + reply; on a refusal it stays invisible until the next refresh, and a model + reset during the wait re-creates the delegate at full height. *Check:* read + the delegate's end-of-gesture code (the fold or fly-off) and the list's + refresh timers, list what the user sees on success, on failure and when a + refresh lands mid-wait, and ask the phone test to cover the last one. + Extends L-573. *From:* #533, round 46, 2026-11-09. +- **L-617. A feature flag that a backend must report starts false in the + UI.** #539's `shareAvailable: true` drew the VPN boxes on every open until + the state line came, and kept them if parsing failed. *Check:* for each + `*Available` property a page reads from a helper, its default and the + `catch` path. Extends L-161 (fail towards not offering what isn't there). + *From:* #539, round 46, 2026-11-09. +- **L-618. A Qt fixture that stands in for a production animation is checked + for how that animation is declared.** #518's test gates on a free-standing + `NumberAnimation` it starts by hand, while the real `revealAnimation` lives + in `Behavior on reveal`; whether a Behavior's animation reports `running`, + and when, decides whether the gate works on the phone (on Qt 6.12.0 it does, + synchronously on the property change). *Check:* when a fixture rebuilds an + animation, timer or handler outside its real context, write a ten-line + qmltestrunner case with the production declaration (a Behavior with an + `id`, plus a `Connections` on `runningChanged`) and log when the property + changes before accepting the fixture's result. Extends L-454. *From:* #518, + round 46, 2026-11-09. +- **L-619. A gesture strip at `z: 100` over a scrolling list is probed for + which of the two takes an upward drag.** #553's 36 px DragHandler strip at + the bottom of the Wi-Fi page overlapped the list's last ~18 px, and the + probe showed the strip wins: the page closed and the list didn't scroll. + *Check:* compute the overlap from the phone's real values (`gaps_out = 0` in + `hypr/phone.lua`, the panel padding), then run a 30-line qmltestrunner probe + with the same handler over a ListView and swipe once inside and once + outside the overlap. Extends L-160. *From:* #553, round 46, 2026-11-09. +- **L-620. A drag handler that measures `mouse.y - startY` inside an item its + own offset moves follows the finger at half speed.** Main's quick-settings + sheet and #553's card both do; a probe gave offsets `-10,-10,-20,-20,…` for + a finger moving 10 px a step, so a 60 px threshold needs 120 px. *Check:* + for any new drag that moves its own parent, run the probe, or read whether + the delta is taken in scene or window coordinates. *From:* #553, round 46, + 2026-11-09. +- **L-621. A surface condition that adds "or the keyboard is up" is checked + against every client that raises the keyboard, not only the one the PR is + about.** #557 meant the dock's and drawer's search, but `oskOpen` follows + squeekboard's visibility for any surface, so the strip (and its + drawer-opening swipe) also appears under quick settings' Wi-Fi password on + the home screen. *Check:* find where the flag comes from + (`omamobile-osk-watch`), list the surfaces with text fields that can be up + on the home screen (Wi-Fi, Bluetooth, Hotspot, the lock), and walk the new + branch for each. Extends L-160. *From:* #557, round 46, 2026-11-09. +- **L-622. Relaxing one term of a visibility condition can expose an old race + that the term used to mask.** In #557, `appOnScreen` kept the strip off + under a lock taken from the home screen whatever `sessionLocked` said; with + `|| oskOpen`, the asynchronous lock query's stale answer now matters there + too. *Check:* for each term a PR loosens, list the other terms that are + asynchronous or cached and ask what they read in the window the old term + covered. *From:* #557, round 46, 2026-11-09. +- **L-623. When a fix removes an error, check what that error was stopping.** + `omamobile-update` run as root over SSH had no `OMARCHY_PATH`, and Omarchy + 4.0.6's `omarchy-update-dev` died on the unbound variable before anything + ran; #548's first change passed `OMARCHY_PATH` on, which would have let a + root run go on to Omarchy's migrations, and Omarchy keeps the per-user + record of which ran in `$HOME`, so a root run re-runs every one as root (59 + on the 11-09 test install, through the NOTES gotcha's `OMARCHY_PATH=…`). + #548 now refuses root. *Check:* for a fix that makes a failing path + succeed, run the path with the fix and list what now executes after the old + failure point, as which user and with which `$HOME`, and ask which of those + steps keep per-user state. Extends L-29 and L-499. *From:* #548 with #560, + round 46, 2026-11-09. +- **L-624. A fix that refuses a command is grepped against our own runbooks + for that command.** #548 refuses `omarchy update` as root, while + `tools/release`'s test-install steps print it under "over USB SSH", where + the login is root, and that runbook is what led to the 11-09 run. + *Check:* for any new refusal, `git grep` the command in `tools/release`, + `docs/`, `device/*/*-PLAN.md` and the NOTES gotchas, and check the user each + one runs as (`tools/phone-ssh` is root). *From:* #548 with #560, round 46, + 2026-11-09. +- **L-625. A sleep test run through a direct `/sys/power/state` freeze doesn't + cover hooks added in the same PR.** #556's cycles were `rtcwake` runs, which + skip `system-sleep` hooks (AGENTS §4, the 9a NFC gotcha). *Check:* compare + each hook's commit time with the runs, and ask for cycles through + `systemctl suspend` for any new or changed `system-sleep` hook. Extends + L-392. *From:* #556, round 46, 2026-11-09. + ## Kernel (linux-omarchy-mobile) @@ -1628,6 +2082,165 @@ never change, so reviews can cite them. arch/arm64/boot/dts` for boards including a touched dtsi; `dt-validate` each on the merge. Extends L-195 and L-309. *From:* kernel #187, round 42, 2026-11-07. +- **L-542. "As Google's driver does" is traced to the end of the vendor + function, including what it does with the answer.** Kernel #194's fallback + follows `syna_tcm_v1_detect()` up to the `IDENTIFY`/`RESET` order, but + `syna_tcm_v1_parse_idinfo()` rejects a zero-length record, so on the unit + that needed the fix the stock driver would fail too: the empty-record path + is our own, and the real difference is probably earlier, in stock's + power-up. *Check:* follow the vendor function past the cited step to its + parse and error returns, and ask which branch the contributor's unit would + take under stock. Extends L-61 and L-77. *From:* kernel #194, round 44, + 2026-11-08. +- **L-543. A panel-ID guard relaxed for a new ID is checked against the byte + the vendor driver keys its commands on, and tested with the commands the + guard blocked.** Google's `tg4c_get_panel_rev()` reads only 0xDB, so kernel + #212's new ID3 gets the same command set; the guard existed for the rate + switch, which the PR hadn't run. *Check:* the vendor driver's + `get_panel_rev`/`read_id` for which ID bytes select commands, then ask for + the guarded paths (rate switch, DPMS) on the new panel. Extends L-117 and + L-211. *From:* kernel #212, round 44, 2026-11-08. +- **L-544. A register map with no public source gets its provenance in the + commit message.** LWIS DTs give a part's address and widths but leave + register sequences to the HAL, so a driver whose registers can't be cited + says how they were found. *Check:* grep Google's GPL tree for each register; + if one is absent, ask. Extends L-61 and L-177. *From:* kernel #213, round + 44, 2026-11-08. +- **L-545. A sentence corrected on one board is grepped across every board + that copied it.** Kernel #214 fixes akita's "the guard runs before the disks + appear" (L-528). The same words are in `zuma-husky.dts` and + `zumapro-tegu.dts`, and UFS is built in for every phone, so they are wrong + there too; only husky's had been noticed. *Check:* when a review corrects + copied text, `git grep -n '' github/omamobile -- arch/ + device/`, and judge each copy by the fact that made the first one wrong + (here `CONFIG_SCSI_UFS_EXYNOS=y` in the shared config). Extends L-528 and + L-257. *From:* kernel #214 with #206, round 44, 2026-11-08. +- **L-546. soc/gs is one tree, so an absent call in a shared driver says + nothing about one SoC.** We nearly told kernel #187's author that zuma has + no secure-ATU SMC because Google's `pcie-exynos-rc.c` has none; that file is + the same on the gs201 branch, where the SMC is real, so it comes from + another driver. *Check:* `cmp` the file across the board branches first, and + find where the vendor actually issues the SMC before saying "SoC X doesn't + use it". Extends L-58 and L-113. *From:* kernel #187, round 44 (a near miss + in drafting); 2026-11-08. +- **L-547. A phone run on a test kernel carries over a new base conflict when + the tested-to-resolved diff equals the base's own movement.** Kernel #187's + `zuma.dtsi` aliases conflicted hours after we said "merges cleanly"; the two + diffs matched exactly, which showed the 7 Pro kernel was still + representative without a rebuild. *Check:* resolve in scratch, compare `git + diff ` with `git diff `, and + grep the difference for any reference-phone path. Extends L-45, L-122 and + L-195. *From:* kernel #187, round 44, 2026-11-08. + Again in round 45: for kernel #187, `git diff --stat` listed only zuma, husky and akita files, and a per-function + object compare of the prebuilt base/test pair (same-source control objects + first, at 0 changes) answered "what changes on cheetah" without a rebuild; + give the contributor the expected tree id of the rebase. +- **L-577. A draft whose commits a sibling stack carries is checked by + patch-id per commit, and closed with a note to its author, not merged.** 22 + of kernel #156's 25 remaining commits are patch-identical in #187 and the + other 3 differ in context only; saying so, with ids, answers "is anything + lost if we close it", and a request made on the draft (gate the split) is + retired where the sibling's thread settled it. *Check:* `git cherry` against + the base, then `git patch-id --stable` on both lists, and grep the sibling + thread for each open request. Extends L-182 and L-429. *From:* kernel #156 + with #187, round 45, 2026-11-08. +- **L-578. A blob check that fails on one file is narrowed to the nodes the + test used before we ask for another boot.** Kernel #209's tested + `zuma-husky.dts` differed from the head only by other test nodes around it; + the `nfc@8` node, its pin groups, the PMU's `#clock-cells`, + `clk-exynos-clkout.c` and `nxp-nci/i2c.c` were identical. *Check:* for each + differing file, extract the nodes or functions the test exercised (`sed -n + '/