Repository navigation
omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: the Pixel 7 Pro's modem stack on by default - #398
Conversation
…: the Pixel 7 Pro's modem stack on by default The maintainer's decision of 2026-11-03: the next release ships the modem working out of the box (calls, texts and data on the tested network, M4.6 through three reboots). The switch of M4.6, omamobile-modem-boot.target, is now on by default on cheetah, and a boot that can't or shouldn't start the modem costs as little as possible: - omamobile-device-cheetah 0.1.43 enables the target with a vendor wants link under multi-user.target.wants, as it does for the AoC and Wi-Fi units; the four units the target wants get no link of their own, and omamobile-modem itself still enables nothing (its test holds it to that; tegu and raven are untouched). Off: systemctl mask the target. The stack's packages (omamobile-modem-sit, omamobile-mmd) join cheetah's ROOTFS_PACKAGES so the release image carries them. - A phone that isn't provisioned costs nothing: the modem and inhibit units carry ConditionPathExists= for the chroot, the NV checksums and the board id (what tools/phone-provision puts there), so both are skipped, not failed, and the inhibitor isn't held. The inhibitor needs its own copy because the modem unit's Requires= pulls it in even when that unit's conditions skip it. sitd skips itself without /dev/umts_ipc0; sit-data now does too, through a device drop-in: without it a condition-skipped sitd counted as started for sit-data's Requires=, and the fallback would have failed after 60 s and restarted every 10 s all boot. The start script checks the same three paths first, for a start by hand. - The modem-up guard clears itself after one refused boot: a stale marker still refuses that boot and logs where to look (journalctl -b -1), then moves to modem-up.refused-<time>-<pid> (the last three kept) so the next boot starts the modem again. A phone that hangs with the modem up every time loses the modem on every other boot at most, never for good. /etc/omamobile/modem-hold restores the old hard stop; --retry still clears both markers; the bring-up latch keeps its hard stop. - Every refusal leaves one short line in /run/omamobile/modem-refused, and the shell's Mobile data tile shows it under its name instead of "No modem" (omamobile-shell 0.2.98, tile-state.sh): no new notification path, the journal has the rest. Versions: #372 and #380 claim device-cheetah 0.1.42, #389 omamobile-modem 0.1.14 and #382 0.1.15, main has omamobile-shell 0.2.97 (#394); hence 0.1.43, 0.1.16 and 0.2.98. Docs: RELEASES (ROOTFS_PACKAGES, decision 12 amended, checklist step 6), the release notes draft (the modem known issue becomes what works and what still needs a hand), INSTALL, DEVICES, and MODEM-PLAN M4.6b with the runbook: install, two reboots, a refused-boot drill by planting a stale marker, the hold flag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
…0: review round 2, the modem-up guard bounded The review of #398 asked for three changes and a few corrections. The self-clearing modem-up guard was unbounded: a phone that hangs because the modem is up went up, hang, refused, up, hang, refused, for ever, with only a tile line on the boots in between. Now the refused copy the script already keeps is the counter: one automatic retry, then a hold. refuse_unclean keeps the marker and refuses "(held)" when a modem-up.refused-* copy exists (no clean stop since the last refusal); --stopped on this boot's marker removes the copies, so a clean stop resets the count; --retry clears both markers and the copies. The test's "four unclean boots in a row" block becomes "the second refusal holds, a clean stop resets", and M4.6b gets drill B9b for it. systemctl is-enabled reads "disabled" for a unit started by a vendor wants link alone (it reports /etc and /run links only), so B6's pass and stop lines expected the wrong answer and would have stopped a correct install; B6 now expects "enabled" before and "disabled" after the disable, and proves the link with ls -l of the /usr/lib link and systemctl list-dependencies --plain multi-user.target. The README, the target's header and the install message say the same, so nobody reads "disabled" and skips the mask. The read-only NV checksum check (M3.5) opens B6 as well as closing the runbook (AGENTS.md section 1). B8's is-active expectation is "failed inactive inactive active" (mmd runs). omamobile-shell takes 0.2.100: main is 0.2.98 after #397 and #373 is taking 0.2.99. The DEVICES cheetah fingerprint cell reads "works": #358 made it on by default. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
# Conflicts: # device/cheetah/MODEM-PLAN.md # packages/omamobile-modem/omamobile-modem.install # packages/omamobile-modem/version # packages/omamobile-shell/version
…r decision The case "the boot after a refused one starts the modem again" (and the --retry case) ran lib/omamobile-modem-start past the marker refusals and relied on the machine to stop it: on the laptop and in CI no sleep inhibitor is held, so the script refused there before any driver. On the phone, where tools/phone-install-package builds the package as an unprivileged user, the inhibitor is held, so the test went on into the real bring-up and failed on /sys/module/pcie_aspm/parameters/policy (permission denied) and then on omamobile-vendor's "run as root". The script takes a test-only OMAMOBILE_MODEM_TEST_STOP_AFTER_CHECKS=1 (documented in its header; no unit or install step sets it) and exits 0 right after the marker decision, before the link driver's sysfs read, the inhibitor wait, the first modprobe and the profile. The two cases use it and assert the decision itself: exit 0, the stale marker moved aside with its refused copy kept, no latch written, the earlier reason left for the tile (it is removed only once every refusal has passed, which the stop point comes before). The test also checks that the stop point sits between the marker decision and the sysfs read, the inhibitor and the latch, and that no unit sets the variable. Verified: packages/omamobile-modem/test/all as uid 1000, with and without a systemd-inhibit stand-in that reports the inhibitor held (the phone's case); tools/pr-check origin/main. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
# Conflicts: # docs/DEVICES.md # packages/omamobile-shell/version
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
|
Phone runbook M4.6b run on the reference Pixel 7 Pro, 2026-11-03, kernel
Also recorded today on this phone (other PRs): the modem registers and IMS comes up with the carrier manifest left empty, so the manifest isn't needed; #373's automatic setup chose Verizon's values from the SIM and registered; the earpiece at stage c9 with the boost converter on was clean by ear on a VoLTE call (#402). Smoke report below. phone-smoke: cheetahKernel
Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.1-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.10-1, omamobile-boot-update 0.1.0-1, omamobile-device-cheetah 0.1.43-1, omamobile-fingerprint 0.1.15-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.2-1, omamobile-modem 0.1.16-1, omamobile-modem-sit 0.3.29-1, omamobile-omarchy 0.1.31-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.94-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2 On the smoke report's "new dmesg errors": the 22 cpif lines are |
…tes file and the day's record (#405) * release notes 2026.11.03, device/cheetah NOTES, MODEM-PLAN: the first release's notes, and the day the modem worked through the apps docs/release-notes/2026.11.03.md is the draft made final for the 2026.11.03 release (kernel-2026.11.01, uname -r 7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install): the header comment gone, every 2026.MM.DD replaced, the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP), and the install paragraph's `<folder>` and `<factory image>` renamed to BACKUP-DIR and FACTORY-IMAGE.zip, which `tools/release tag` would otherwise refuse as placeholders. The modem bullet under "New in the last weeks" now says what works (calls, texts and data on the tested network, the APNs chosen from the SIM), and "Phones already running a development build" says that a provisioned phone's modem stack starts at boot once it has omamobile-device-cheetah 0.1.43, and how to keep it off (systemctl mask omamobile-modem-boot.target). The draft stays for the next release, as its own header says and tools/release expects. device/cheetah/NOTES.md records 2026-11-03 on the reference phone: calls and texts both ways through Phone and Messages (the first text between two Omarchy Mobile phones), IMS registered with no carrier manifest, sitd 0.3.29 choosing the SIM's values on its own, the earpiece clean at stage c9 with the boost converter on, #398's B6-B9b runbook passed with no UFS error-handler pass, the Messages agent fix (#394, #399), the open cpif oem_ipc0 lines, and the OMARCHY_PATH gotcha for omamobile-update over ssh. MODEM-PLAN's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as history, and M4.6b has its result. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * release notes 2026.11.03, DEVICES, FINGERPRINT-PLAN: the user-facing recovery, and the fresh-install fingerprint record The notes told a user to run omamobile-modem-start --retry, which isn't on PATH and by hand brings the modem up outside its unit; the recovery is the runbook's (clear the markers, restart). The draft's placeholders take the forms the tag stage accepts. The fingerprint cell records today's fresh-install run (T1-T3) instead of "being tested". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…ekross#373 and derekross#398 main took modem-sit 0.3.29 (derekross#373) and modem 0.1.15 and 0.1.16 (derekross#382, derekross#398) while this waited: the sitd exit lands as 0.3.30 and the modem changes as 0.1.17. The NV overlay's note now says the copies are f2fs on gs201 and ext4 on gs101; it works on the mounted copies, so nothing else in it changes for raven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Booting derekross#389's head on raven (2026-11-04, ge1e6adb69bbf): omamobile-modem is READY once CPIF's ports exist and the CP comes ONLINE about 3 s later, so omamobile-sitd, ordered only after the modem unit, started at once and exited ("CP is not ONLINE") at every boot. The wait for ONLINE that derekross#398 added is a device-cheetah drop-in, so raven never had it. device-raven now ships the same two drop-ins: sitd's ExecStartPre waits for ONLINE (up to cbd's own 120 s), and the data fallback is skipped without the modem's port. Cheetah is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… modem stack on by default The boot unit gets a vendor wants link, as the 7 Pro's target did in derekross#398, and conditions that skip it on a phone without the provisioning files or without CP drivers (the device tree's cpif node or the bring-up modules), so a boot that can't run it costs nothing. The README says what it costs and needs and how to turn it off (mask), the test holds the link and the conditions, the 9a's Modem and GNSS cells read works, and TELEPHONY-PLAN 2.8 is the gated runbook for enabling it on the palmtop.
…h, B4 Addresses the review on derekross#574. - AGENTS.md, the modem restart gotcha: it still called the 7 Pro's stack at boot opt-in (`systemctl enable omamobile-modem-boot.target`), which stopped being true with derekross#398. It now says the stack starts by default since device-cheetah 0.1.43 (MODEM-PLAN M4.6b), and that `systemctl mask` keeps it off from the next boot, as the target, the package's install message and the device README say: `disable` doesn't remove device-cheetah's vendor wants link. - AGENTS.md section 2: derekross#403 doesn't make `reboot-to` a clean stop. Its note lets the next boot's start clear a `modem-up` marker from the boot `reboot-to` ended, but the CP's ordered power-off and the NV capture still run only in the unit's stop, so the advice to stop the modem first stands with derekross#403 merged too. - MODEM-PLAN M4.6 B4 rebooted with `reboot-to omamobile` and expected the clean stop's "modem stopped (...): modem-up removed", which a raw reboot syscall can't produce. The step is there to show that a reboot's stop clears the marker, so it now reboots through systemd, as N5 does, and its pass line takes today's "timeout" result (derekross#532). The recorded results are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he 7 Pro's modem starts at boot by default (#574) * AGENTS.md: stop the modem before a push or a reboot-to reboot-to is a raw reboot syscall and bin/omamobile push ends in it, so neither stops omamobile-modem.service. Its clean stop never runs, the modem-up marker stays, and on the 7 Pro, where the modem starts at boot, the next boot skips the modem once as if the last one had hung; a second unclean end in a row holds it off until --retry. That happened on 2026-11-08 after a reboot-to bootloader taken to charge a flat battery. Add a bullet to the push notes in section 2: stop the unit first, under the human's go for the reboot, or use systemctl reboot when no reason is needed; what the stop costs today (about 40 s, logged as failed, marker still removed); why this is not the restart the modem gotchas forbid; and that the open #403 would make reboot-to count as a clean stop. The reboot-to gotcha and the NV overlay note in section 4 point to it; the NV note keeps nv-overlay capture as the narrower alternative. Part of #532 (its docs request only; the watcher and SIGTERM fixes are package changes). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * AGENTS.md, MODEM-PLAN: modem at boot by default, #403's reach, B4 Addresses the review on #574. - AGENTS.md, the modem restart gotcha: it still called the 7 Pro's stack at boot opt-in (`systemctl enable omamobile-modem-boot.target`), which stopped being true with #398. It now says the stack starts by default since device-cheetah 0.1.43 (MODEM-PLAN M4.6b), and that `systemctl mask` keeps it off from the next boot, as the target, the package's install message and the device README say: `disable` doesn't remove device-cheetah's vendor wants link. - AGENTS.md section 2: #403 doesn't make `reboot-to` a clean stop. Its note lets the next boot's start clear a `modem-up` marker from the boot `reboot-to` ended, but the CP's ordered power-off and the NV capture still run only in the unit's stop, so the advice to stop the modem first stands with #403 merged too. - MODEM-PLAN M4.6 B4 rebooted with `reboot-to omamobile` and expected the clean stop's "modem stopped (...): modem-up removed", which a raw reboot syscall can't produce. The step is there to show that a reboot's stop clears the marker, so it now reboots through systemd, as N5 does, and its pass line takes today's "timeout" result (#532). The recorded results are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MODEM-PLAN: M4.6b B8 and B9b reboot through systemd, as B4 now does Part of the review on #574. B8 plants another boot's modem-up marker so that "the reboot's clean stop keeps a marker that isn't this boot's", and its pass line reads the previous boot's "is another boot's ... kept"; B9b's planted reboot rests on the same stop hook, and its last "clean reboot" checks that `--stopped` removed the refused copies. All three rebooted with `reboot-to omamobile`, which stops no unit, so the stop hook they test never ran: the same gap as B4. They now reboot with `systemctl reboot`. The recorded results are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ekross#373, derekross#398 and derekross#416 main took modem-sit 0.3.29 (derekross#373) and 0.3.30 (derekross#416), and modem 0.1.15 and 0.1.16 (derekross#382, derekross#398), while this waited: the sitd exit lands as 0.3.31 and the modem changes as 0.1.17. The NV overlay's note now says the copies are f2fs on gs201 and ext4 on gs101; it works on the mounted copies, so nothing else in it changes for raven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ekross#373, derekross#398 and derekross#416 main took modem-sit 0.3.29 (derekross#373) and 0.3.30 (derekross#416), and modem 0.1.15 and 0.1.16 (derekross#382, derekross#398), while this waited: the sitd exit lands as 0.3.31 and the modem changes as 0.1.17. The NV overlay's note now says the copies are f2fs on gs201 and ext4 on gs101; it works on the mounted copies, so nothing else in it changes for raven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…0: the Pixel 7 Pro's modem stack on by default (derekross#398) * omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.98: the Pixel 7 Pro's modem stack on by default The maintainer's decision of 2026-11-03: the next release ships the modem working out of the box (calls, texts and data on the tested network, M4.6 through three reboots). The switch of M4.6, omamobile-modem-boot.target, is now on by default on cheetah, and a boot that can't or shouldn't start the modem costs as little as possible: - omamobile-device-cheetah 0.1.43 enables the target with a vendor wants link under multi-user.target.wants, as it does for the AoC and Wi-Fi units; the four units the target wants get no link of their own, and omamobile-modem itself still enables nothing (its test holds it to that; tegu and raven are untouched). Off: systemctl mask the target. The stack's packages (omamobile-modem-sit, omamobile-mmd) join cheetah's ROOTFS_PACKAGES so the release image carries them. - A phone that isn't provisioned costs nothing: the modem and inhibit units carry ConditionPathExists= for the chroot, the NV checksums and the board id (what tools/phone-provision puts there), so both are skipped, not failed, and the inhibitor isn't held. The inhibitor needs its own copy because the modem unit's Requires= pulls it in even when that unit's conditions skip it. sitd skips itself without /dev/umts_ipc0; sit-data now does too, through a device drop-in: without it a condition-skipped sitd counted as started for sit-data's Requires=, and the fallback would have failed after 60 s and restarted every 10 s all boot. The start script checks the same three paths first, for a start by hand. - The modem-up guard clears itself after one refused boot: a stale marker still refuses that boot and logs where to look (journalctl -b -1), then moves to modem-up.refused-<time>-<pid> (the last three kept) so the next boot starts the modem again. A phone that hangs with the modem up every time loses the modem on every other boot at most, never for good. /etc/omamobile/modem-hold restores the old hard stop; --retry still clears both markers; the bring-up latch keeps its hard stop. - Every refusal leaves one short line in /run/omamobile/modem-refused, and the shell's Mobile data tile shows it under its name instead of "No modem" (omamobile-shell 0.2.98, tile-state.sh): no new notification path, the journal has the rest. Versions: derekross#372 and derekross#380 claim device-cheetah 0.1.42, derekross#389 omamobile-modem 0.1.14 and derekross#382 0.1.15, main has omamobile-shell 0.2.97 (derekross#394); hence 0.1.43, 0.1.16 and 0.2.98. Docs: RELEASES (ROOTFS_PACKAGES, decision 12 amended, checklist step 6), the release notes draft (the modem known issue becomes what works and what still needs a hand), INSTALL, DEVICES, and MODEM-PLAN M4.6b with the runbook: install, two reboots, a refused-boot drill by planting a stale marker, the hold flag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * omamobile-modem 0.1.16, device-cheetah 0.1.43, omamobile-shell 0.2.100: review round 2, the modem-up guard bounded The review of derekross#398 asked for three changes and a few corrections. The self-clearing modem-up guard was unbounded: a phone that hangs because the modem is up went up, hang, refused, up, hang, refused, for ever, with only a tile line on the boots in between. Now the refused copy the script already keeps is the counter: one automatic retry, then a hold. refuse_unclean keeps the marker and refuses "(held)" when a modem-up.refused-* copy exists (no clean stop since the last refusal); --stopped on this boot's marker removes the copies, so a clean stop resets the count; --retry clears both markers and the copies. The test's "four unclean boots in a row" block becomes "the second refusal holds, a clean stop resets", and M4.6b gets drill B9b for it. systemctl is-enabled reads "disabled" for a unit started by a vendor wants link alone (it reports /etc and /run links only), so B6's pass and stop lines expected the wrong answer and would have stopped a correct install; B6 now expects "enabled" before and "disabled" after the disable, and proves the link with ls -l of the /usr/lib link and systemctl list-dependencies --plain multi-user.target. The README, the target's header and the install message say the same, so nobody reads "disabled" and skips the mask. The read-only NV checksum check (M3.5) opens B6 as well as closing the runbook (AGENTS.md section 1). B8's is-active expectation is "failed inactive inactive active" (mmd runs). omamobile-shell takes 0.2.100: main is 0.2.98 after derekross#397 and derekross#373 is taking 0.2.99. The DEVICES cheetah fingerprint cell reads "works": derekross#358 made it on by default. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * omamobile-modem 0.1.16: the start script's test stops after the marker decision The case "the boot after a refused one starts the modem again" (and the --retry case) ran lib/omamobile-modem-start past the marker refusals and relied on the machine to stop it: on the laptop and in CI no sleep inhibitor is held, so the script refused there before any driver. On the phone, where tools/phone-install-package builds the package as an unprivileged user, the inhibitor is held, so the test went on into the real bring-up and failed on /sys/module/pcie_aspm/parameters/policy (permission denied) and then on omamobile-vendor's "run as root". The script takes a test-only OMAMOBILE_MODEM_TEST_STOP_AFTER_CHECKS=1 (documented in its header; no unit or install step sets it) and exits 0 right after the marker decision, before the link driver's sysfs read, the inhibitor wait, the first modprobe and the profile. The two cases use it and assert the decision itself: exit 0, the stale marker moved aside with its refused copy kept, no latch written, the earlier reason left for the tile (it is removed only once every refusal has passed, which the stop point comes before). The test also checks that the stop point sits between the marker decision and the sysfs read, the inhibitor and the latch, and that no unit sets the variable. Verified: packages/omamobile-modem/test/all as uid 1000, with and without a systemd-inhibit stand-in that reports the inhibitor held (the phone's case); tools/pr-check origin/main. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * release notes: the carrier APNs come from the SIM, not by hand Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…tes file and the day's record (derekross#405) * release notes 2026.11.03, device/cheetah NOTES, MODEM-PLAN: the first release's notes, and the day the modem worked through the apps docs/release-notes/2026.11.03.md is the draft made final for the 2026.11.03 release (kernel-2026.11.01, uname -r 7.3.0-rc6-omamobile-g2219cc6cda77, the kernel of the 2026.11.02 test install): the header comment gone, every 2026.MM.DD replaced, the hardware matrix re-read against docs/DEVICES.md today (Modem works, Fingerprint works, Suspend WIP), and the install paragraph's `<folder>` and `<factory image>` renamed to BACKUP-DIR and FACTORY-IMAGE.zip, which `tools/release tag` would otherwise refuse as placeholders. The modem bullet under "New in the last weeks" now says what works (calls, texts and data on the tested network, the APNs chosen from the SIM), and "Phones already running a development build" says that a provisioned phone's modem stack starts at boot once it has omamobile-device-cheetah 0.1.43, and how to keep it off (systemctl mask omamobile-modem-boot.target). The draft stays for the next release, as its own header says and tools/release expects. device/cheetah/NOTES.md records 2026-11-03 on the reference phone: calls and texts both ways through Phone and Messages (the first text between two Omarchy Mobile phones), IMS registered with no carrier manifest, sitd 0.3.29 choosing the SIM's values on its own, the earpiece clean at stage c9 with the boost converter on, derekross#398's B6-B9b runbook passed with no UFS error-handler pass, the Messages agent fix (derekross#394, derekross#399), the open cpif oem_ipc0 lines, and the OMARCHY_PATH gotcha for omamobile-update over ssh. MODEM-PLAN's status line was from 2026-10-13 ("M4.2 needs a SIM"); it now says what works and what is open, with the old line kept as history, and M4.6b has its result. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d * release notes 2026.11.03, DEVICES, FINGERPRINT-PLAN: the user-facing recovery, and the fresh-install fingerprint record The notes told a user to run omamobile-modem-start --retry, which isn't on PATH and by hand brings the modem up outside its unit; the recovery is the runbook's (clear the markers, restart). The draft's placeholders take the forms the tag stage accepts. The fingerprint cell records today's fresh-install run (T1-T3) instead of "being tested". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…he 7 Pro's modem starts at boot by default (derekross#574) * AGENTS.md: stop the modem before a push or a reboot-to reboot-to is a raw reboot syscall and bin/omamobile push ends in it, so neither stops omamobile-modem.service. Its clean stop never runs, the modem-up marker stays, and on the 7 Pro, where the modem starts at boot, the next boot skips the modem once as if the last one had hung; a second unclean end in a row holds it off until --retry. That happened on 2026-11-08 after a reboot-to bootloader taken to charge a flat battery. Add a bullet to the push notes in section 2: stop the unit first, under the human's go for the reboot, or use systemctl reboot when no reason is needed; what the stop costs today (about 40 s, logged as failed, marker still removed); why this is not the restart the modem gotchas forbid; and that the open derekross#403 would make reboot-to count as a clean stop. The reboot-to gotcha and the NV overlay note in section 4 point to it; the NV note keeps nv-overlay capture as the narrower alternative. Part of derekross#532 (its docs request only; the watcher and SIGTERM fixes are package changes). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * AGENTS.md, MODEM-PLAN: modem at boot by default, derekross#403's reach, B4 Addresses the review on derekross#574. - AGENTS.md, the modem restart gotcha: it still called the 7 Pro's stack at boot opt-in (`systemctl enable omamobile-modem-boot.target`), which stopped being true with derekross#398. It now says the stack starts by default since device-cheetah 0.1.43 (MODEM-PLAN M4.6b), and that `systemctl mask` keeps it off from the next boot, as the target, the package's install message and the device README say: `disable` doesn't remove device-cheetah's vendor wants link. - AGENTS.md section 2: derekross#403 doesn't make `reboot-to` a clean stop. Its note lets the next boot's start clear a `modem-up` marker from the boot `reboot-to` ended, but the CP's ordered power-off and the NV capture still run only in the unit's stop, so the advice to stop the modem first stands with derekross#403 merged too. - MODEM-PLAN M4.6 B4 rebooted with `reboot-to omamobile` and expected the clean stop's "modem stopped (...): modem-up removed", which a raw reboot syscall can't produce. The step is there to show that a reboot's stop clears the marker, so it now reboots through systemd, as N5 does, and its pass line takes today's "timeout" result (derekross#532). The recorded results are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MODEM-PLAN: M4.6b B8 and B9b reboot through systemd, as B4 now does Part of the review on derekross#574. B8 plants another boot's modem-up marker so that "the reboot's clean stop keeps a marker that isn't this boot's", and its pass line reads the previous boot's "is another boot's ... kept"; B9b's planted reboot rests on the same stop hook, and its last "clean reboot" checks that `--stopped` removed the refused copies. All three rebooted with `reboot-to omamobile`, which stops no unit, so the stop hook they test never ran: the same gap as B4. They now reboot with `systemctl reboot`. The recorded results are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The maintainer's decision of 2026-11-03: the next release ships the Pixel 7 Pro's modem working out of the box. M4.6 (three reboots on 2026-11-03, #386) is the evidence; this turns its switch,
omamobile-modem-boot.target, on by default on cheetah and makes every boot that can't or shouldn't start the modem cost as little as possible. Nothing here was run on a phone: the runbook is MODEM-PLAN M4.6b (B6-B10), gated.Round 2 (review changes): the modem-up guard is bounded (one automatic retry, then a hold), B6 expects what
systemctl is-enabledreally prints for a vendor link and proves the link itself, B6 starts with the read-only NV checksum check, B8'sis-activeline is corrected, a B9b drill tests the bound, omamobile-shell takes 0.2.100, and the DEVICES fingerprint cell is brought in line with #358.What changes
On by default (omamobile-device-cheetah 0.1.43). A vendor wants link,
multi-user.target.wants/omamobile-modem-boot.target, as the package does for the AoC and Wi-Fi units. The four units the target wants get no link of their own,omamobile-modemitself still enables nothing (its test holds it to that), and tegu and raven are untouched. Off:systemctl mask omamobile-modem-boot.target. A vendor link survivesdisable, andsystemctl is-enabledreads "disabled" for a unit started by a vendor link alone (it reports/etcand/runlinks only), so the target's header, the install message and the README say so and name the proof (ls -lof the link,systemctl list-dependencies --plain multi-user.target).omamobile-modem-sitandomamobile-mmdjoin cheetah'sROOTFS_PACKAGES, so the release image carries them (tests/build-rootfs keeps them out of the shared list by design).A phone that isn't provisioned costs nothing.
omamobile-modem.serviceandomamobile-modem-inhibit.servicegetConditionPathExists=for the chroot, the NV checksums and the board id, the three thingstools/phone-provisionputs on the phone. Both are skipped, not failed: no restart, nothing in the latch, and the sleep inhibitor isn't held (it needs its own copy of the conditions because the modem unit'sRequires=pulls it in even when that unit is condition-skipped). sitd already skips itself without/dev/umts_ipc0;sit-datanow does too, through a device drop-in: without it a condition-skipped sitd counted as started for sit-data'sRequires=, and the data fallback would have failed after 60 s and restarted every 10 s for the whole boot.omamobile-mmdruns and waits for sitd, logging once. The start script checks the same three paths first, for a start by hand or--retry.The modem-up guard: one automatic retry, then a hold (omamobile-modem 0.1.16). A stale
modem-upstill refuses that boot and logsjournalctl -b -1 -u omamobile-modemand-kas where to look, then moves tomodem-up.refused-<time>-<pid>, so the following boot starts the modem again. That copy is the counter: if the retry's boot ends unclean too, the next boot finds the stale marker with the copy beside it (no clean stop since the last refusal), keeps the marker, makes no second copy and refuses "Off after a hang or reset (held)", as does every boot after, untilomamobile-modem-start --retry(clears both markers and the copies) orrm /var/lib/omamobile/modem-up*. A clean stop of this boot's marker (--stopped) removes the copies, so the count starts over. A flat battery or one forced reset costs one boot's modem; a phone that hangs because the modem is up stops after the second, instead of resetting on every other boot for ever.touch /etc/omamobile/modem-holdholds from the first unclean end. The bring-up latch keeps its hard stop on purpose (a hang in the bring-up itself is the one case nothing should repeat on its own).The tile says why (omamobile-shell 0.2.100). Each refusal leaves one short line in
/run/omamobile/modem-refused("Off after a hang or reset", "... (held)", "Off: not provisioned", ...); a start that gets past the refusals removes it.tile-state.shprints it asdata_statuswhen there is no sitd state, and the Mobile data tile shows it under its name instead of "No modem". No new notification path; the journal has the rest.Docs. RELEASES (
ROOTFS_PACKAGES, decision 12 amended, checklist step 6), the release notes draft (the "no calls, texts or data" known issue becomes what works on the tested network and what still needs a hand: APNs by hand until #373, the earpiece at stagemedia, no sleep with the modem up, the refused-boot behaviour with its bound), INSTALL, DEVICES (the modem row, and the cheetah fingerprint cell now reads "works": #358 made it on by default), and MODEM-PLAN M4.6b with the runbook: the NV checksum check (M3.5) first and last, install, two reboots, a refused-boot drill by planting another boot's marker (no forced reset needed), the bound (B9b: plant again with the modem up, expect "(held)" with the marker in place;rm -f /var/lib/omamobile/modem-up*and a reboot start the modem; the next clean reboot leaves no refused copy), the hold flag.Tests
packages/omamobile-modem/test/all: an unprovisioned phone (each of the three files missing) is refused in one line with no latch and the units carry the same conditions; the latch still refuses every boot; a stale marker refuses once and is moved aside, the next boot starts (up to the inhibitor check on a laptop); the second refusal holds (the marker stays, no second copy, "(held)" for the tile, the boot after refuses too); a clean stop of this boot's marker removes the copies and the next stale marker is refused once again; the hold flag holds from the first;--stoppedkeeps another boot's marker and its copy,--retryclears both markers and the copies; the reason file for each; the script's order (provisioning, markers, inhibitor, reason removed, latch, modprobe, check, READY, profile).packages/omamobile-device-cheetah/test/all: the target's vendor link, no link for the five units, the sit-data drop-in's condition, and that the target the link turns on is condition-skipped without the chroot.packages/omamobile-shell/test/tile-scripts.sh: no reason file prints onlydata=none; a reason becomesdata_status, cut to 48 characters; an empty file prints nothing (and the probe still exits 0).tests/packagesfor the three,tests/all,tools/pr-check origin/main, shellcheck-S warningon the touched scripts: pass.Versions
.installtext conflicts with both: resolve to this PR's wording plus theirs).Unsettled
ExecCondition=on the inhibitor running the same marker checks would skip both together: a follow-up.OMAMOBILE_BOOT_FILES=none), as everyphone-install-packageof it is.omamobile-device-cheetahdoesn't depend onomamobile-modem; the vendor link dangles harmlessly on a phone that removed the modem package (systemd tolerates a missing wanted unit). Anoptdependsline is a follow-up.🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d