Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 55 additions & 1 deletion device/cheetah/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,58 @@

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`
Expand Down Expand Up @@ -93,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

Expand Down