Repository navigation
omamobile-device-cheetah 0.1.52: the boot image with #403's reboot-to and #562's init reaches installed phones - #691
Merged
Merged
Conversation
… 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>
This was referenced Nov 12, 2026
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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) andreboot-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 -r7.3.0-rc6-omamobile-g1a9d1d4e9289):initandusr/local/bin/reboot-to; none of initramfs: make development root protections descriptor-driven #562's policy files is in it;dtbo.imgis the same.boot,init_boot,vendor_bootanddtbo"already there",vendor_kernel_boot_bwritten and verified, the previous slot B saved./run0755, the root filesystem mounted without recovery, no UFS error-handler pass, the modem ONLINE.tools/phone-smokeafter that boot:phone-smoke: cheetah
Kernel
7.3.0-rc6-omamobile-g1a9d1d4e9289, tools ate4c92a80, 2026-11-12T13:16Z.The one "not ok" row is three
cpif: rx_multi_pdp … netif_receive_skblines, 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