Skip to content

device-husky 0.1.11, device-oriole 0.2.1, device-tegu 0.2.17: the numbers #403's reboot-to needs - #683

Merged
derekross merged 1 commit into
mainfrom
device-versions-after-403
Nov 12, 2026
Merged

derekross merged 1 commit into
mainfrom
device-versions-after-403

Conversation

@derekross

Copy link
Copy Markdown
Owner

Follow-up to #403, as said there.

#403 changed src/reboot-to.c in every device package, but four had no new number on its branch. Without one the build keeps the old package, so those phones would not get the reboot-to that notes a deliberate restart.

Package was now
omamobile-device-husky 0.1.10 0.1.11
omamobile-device-oriole 0.2.0 0.2.1
omamobile-device-tegu 0.2.16 0.2.17

These three carry no boot image, so the bump only rebuilds the binary. Their test/all pass.

omamobile-device-cheetah stays at 0.1.51 on purpose. Its package carries the Pixel 7 Pro's boot image, which release phones write to slot B at the update. The image's inputs have changed twice since the last one that booted (#667): initramfs/init (#562, 61 lines) and reboot-to.c (#403). It gets 0.1.52 once an image built from this tree has booted on the 7 Pro, the way 0.1.51 did. Until then the 7 Pro's packaged reboot-to is the old one, and the modem stop before a push (AGENTS §2) still matters there.

🤖 Generated with Claude Code

…bers #403's reboot-to needs

#403 changed src/reboot-to.c in every device package, but four of them
had no new number on its branch: main had moved to the same one, or the
branch never bumped it. Without a new number the build keeps the old
package, so those phones would not get the reboot-to that notes a
deliberate restart.

Three of the four here. Their packages carry no boot image, so the bump
only rebuilds the binary.

device-cheetah stays at 0.1.51 on purpose. Its package carries the
Pixel 7 Pro's boot image, which release phones write to slot B at the
update, and the image's inputs have changed twice since the last one
that booted (#667): initramfs/init (#562) and reboot-to.c (#403). It
gets 0.1.52 once an image built from this tree has booted on the 7 Pro,
as 0.1.51 did.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross
derekross merged commit 2a31fbf into main Nov 12, 2026
2 checks passed
@derekross
derekross deleted the device-versions-after-403 branch November 12, 2026 03:54
chillerno1 added a commit to chillerno1/omarchy-mobile that referenced this pull request Nov 12, 2026
…after derekross#403

Upstream's reboot-to notes a deliberate restart for the modem's next start
(derekross#403, derekross#683). The Saga's copy must match the cheetah source (test/all), so
it takes the new file; the note is only written on a boot with the modem
up, which the Saga doesn't start yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…bers derekross#403's reboot-to needs (derekross#683)

derekross#403 changed src/reboot-to.c in every device package, but four of them
had no new number on its branch: main had moved to the same one, or the
branch never bumped it. Without a new number the build keeps the old
package, so those phones would not get the reboot-to that notes a
deliberate restart.

Three of the four here. Their packages carry no boot image, so the bump
only rebuilds the binary.

device-cheetah stays at 0.1.51 on purpose. Its package carries the
Pixel 7 Pro's boot image, which release phones write to slot B at the
update, and the image's inputs have changed twice since the last one
that booted (derekross#667): initramfs/init (derekross#562) and reboot-to.c (derekross#403). It
gets 0.1.52 once an image built from this tree has booted on the 7 Pro,
as 0.1.51 did.

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