Skip to content

omamobile-device-cheetah 0.1.53: reboot-to --help prints its usage on the Pixel 7 Pro too - #698

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

derekross merged 1 commit into
mainfrom
device-cheetah-0153

Conversation

@derekross

Copy link
Copy Markdown
Owner

#459's fix for the Pixel 7 Pro, held back from #696 until its boot image had booted.

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

  • Boot files staged from main on the release kernel's build. Against 0.1.52's initramfs exactly one file differs, usr/local/bin/reboot-to; init and dtbo.img are the same.
  • Installed with pacman. The hook: four of slot B's five images "already there", vendor_kernel_boot_b written and verified, the previous slot B saved.
  • After a clean restart: system "running", no failed unit, /run 0755, the root filesystem mounted without recovery, no UFS error-handler pass, the modem ONLINE, tools/phone-smoke passing (its one "not ok" row is the three cpif: rx_multi_pdp lines noted on omamobile-device-cheetah 0.1.52: the boot image with #403's reboot-to and #562's init reaches installed phones #691).
  • Then on the phone, with the modem up:
Command Result
reboot-to --help prints usage: reboot-to [REASON], exit 0
reboot-to -h exit 0
reboot-to -z exit 2

The boot id was the same before and after, no deliberate-restart note was written, and the modem stayed ONLINE.

After merge: the tested boot files go to the build machine before the next publish.

🤖 Generated with Claude Code

… the Pixel 7 Pro too

#459 made reboot-to print its usage for an option, where it used to take
the option as the reboot reason and restart the phone. The other eight
device packages got it with #696. The Pixel 7 Pro's waited, because its
package carries the boot image, which has reboot-to in it.

An image built from this tree booted on the phone on 2026-11-12, by the
path a release phone takes. Against 0.1.52's initramfs exactly one file
differs, usr/local/bin/reboot-to; init and the dtbo are the same. The
hook found four of slot B's five images already there and wrote
vendor_kernel_boot_b, verified. After a clean restart: system running,
no failed unit, /run 0755, no UFS error-handler pass, the modem ONLINE,
tools/phone-smoke passing.

Then, on the phone with the modem up: reboot-to --help prints the usage
and exits 0, -h exits 0, -z exits 2; the boot id is unchanged, no
deliberate-restart note is written, and the modem stays ONLINE.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross
derekross merged commit 9ea26df into main Nov 12, 2026
2 checks passed
@derekross
derekross deleted the device-cheetah-0153 branch November 12, 2026 14:51
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… the Pixel 7 Pro too (derekross#698)

derekross#459 made reboot-to print its usage for an option, where it used to take
the option as the reboot reason and restart the phone. The other eight
device packages got it with derekross#696. The Pixel 7 Pro's waited, because its
package carries the boot image, which has reboot-to in it.

An image built from this tree booted on the phone on 2026-11-12, by the
path a release phone takes. Against 0.1.52's initramfs exactly one file
differs, usr/local/bin/reboot-to; init and the dtbo are the same. The
hook found four of slot B's five images already there and wrote
vendor_kernel_boot_b, verified. After a clean restart: system running,
no failed unit, /run 0755, no UFS error-handler pass, the modem ONLINE,
tools/phone-smoke passing.

Then, on the phone with the modem up: reboot-to --help prints the usage
and exits 0, -h exits 0, -z exits 2; the boot id is unchanged, no
deliberate-restart note is written, and the modem stays ONLINE.

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