Skip to content

omamobile-device-cheetah 0.1.52: the boot image with #403's reboot-to and #562's init reaches installed phones - #691

Merged
derekross merged 1 commit into
mainfrom
device-cheetah-0152
Nov 12, 2026
Merged

derekross merged 1 commit into
mainfrom
device-cheetah-0152

Conversation

@derekross

Copy link
Copy Markdown
Owner

Held back from #683 on purpose, and now tested.

The Pixel 7 Pro's package carries its boot image, and release phones write it to slot B at the update. Two of the image's inputs changed since 0.1.51: initramfs/init (#562) and reboot-to.c (#403). This bump waited for an image built from this tree to boot on the phone.

The run, 2026-11-12, by the path a release phone takes (Omarchy 4.5.0-3, uname -r 7.3.0-rc6-omamobile-g1a9d1d4e9289):

  • Boot files staged from main on the release kernel's build, with a release initramfs. Against 0.1.51's initramfs exactly two files differ, init and usr/local/bin/reboot-to; none of initramfs: make development root protections descriptor-driven #562's policy files is in it; dtbo.img is the same.
  • The package was built on the phone and installed with pacman. The hook: boot, init_boot, vendor_boot and dtbo "already there", vendor_kernel_boot_b written and verified, the previous slot B saved.
  • After a clean restart the phone booted it: system "running", no failed unit, /run 0755, the root filesystem mounted without recovery, no UFS error-handler pass, the modem ONLINE.

tools/phone-smoke after that boot:

phone-smoke: cheetah

Kernel 7.3.0-rc6-omamobile-g1a9d1d4e9289, tools at e4c92a80, 2026-11-12T13:16Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-g1a9d1d4e9289, slot b, up 135s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 95G free
kernel health (required) ok no oops or BUG; 0 WARN, 55 error lines in dmesg (52 known, of them cpif message for a channel nobody opened x48, 3 new)
new dmesg errors not ok cpif: rx_multi_pdp: PCIE: N<N: ERR! netif_receive_skb x3
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok Synaptics TouchComm Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 99% Discharging, 30 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 48 °C

The one "not ok" row is three cpif: rx_multi_pdp … netif_receive_skb lines, a different CPIF message from the ones #684 now counts (48 of those are counted as known in this report, the first on a phone). They are on the modem's data path and are not from this change; they want their own look.

After merge: the boot files are restaged on the build machine before the next publish, or the build skips this package as stale.

🤖 Generated with Claude Code

… and #562's init reaches installed phones

The Pixel 7 Pro's package carries its boot image, and release phones
write it to slot B at the update. Two of the image's inputs changed since
0.1.51: initramfs/init (#562: the optional root label check, development
handover and RAM rescue keys, all unset for this phone) and reboot-to.c
(#403: it notes a deliberate restart). 0.1.51 was held until an image
built from this tree had booted on the phone.

It has, on 2026-11-12, by the path a release phone takes: the package
built with boot files staged from main on the release kernel
(7.3.0-rc6-omamobile-g1a9d1d4e9289) and installed with pacman. Against
0.1.51's initramfs exactly two files differ, init and reboot-to; the dtbo
is the same. The hook found four of slot B's five images already there
and wrote vendor_kernel_boot_b, verified, with the previous slot B saved.
After a clean restart the phone booted it: system running, no failed
unit, /run 0755, the root filesystem mounted without recovery, no UFS
error-handler pass, the modem ONLINE, and tools/phone-smoke passing.

With this the 7 Pro's packaged reboot-to is #403's too.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross
derekross merged commit ac1e089 into main Nov 12, 2026
2 checks passed
@derekross
derekross deleted the device-cheetah-0152 branch November 12, 2026 13:27
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…reboot-to and derekross#562's init reaches installed phones (derekross#691)

The Pixel 7 Pro's package carries its boot image, and release phones
write it to slot B at the update. Two of the image's inputs changed since
0.1.51: initramfs/init (derekross#562: the optional root label check, development
handover and RAM rescue keys, all unset for this phone) and reboot-to.c
(derekross#403: it notes a deliberate restart). 0.1.51 was held until an image
built from this tree had booted on the phone.

It has, on 2026-11-12, by the path a release phone takes: the package
built with boot files staged from main on the release kernel
(7.3.0-rc6-omamobile-g1a9d1d4e9289) and installed with pacman. Against
0.1.51's initramfs exactly two files differ, init and reboot-to; the dtbo
is the same. The hook found four of slot B's five images already there
and wrote vendor_kernel_boot_b, verified, with the previous slot B saved.
After a clean restart the phone booted it: system running, no failed
unit, /run 0755, the root filesystem mounted without recovery, no UFS
error-handler pass, the modem ONLINE, and tools/phone-smoke passing.

With this the 7 Pro's packaged reboot-to is derekross#403's too.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant