Skip to content

omamobile-modem 0.1.22, omamobile-modem-sit 0.3.35, device-raven 0.1.36: the modem runtime on the Pixel 6 Pro - #389

Open
robotosaith wants to merge 16 commits into
derekross:mainfrom
robotosaith:omamobile-sim-pr0-v2
Open

robotosaith wants to merge 16 commits into
derekross:mainfrom
robotosaith:omamobile-sim-pr0-v2

Conversation

@robotosaith

@robotosaith robotosaith commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

What and why

The modem runtime only knew the Pixel 7 Pro. On the Pixel 6 Pro (raven) its NV partitions are ext4, not f2fs, so on main it stops at the efs mount before any daemon runs. omamobile-modem now mounts each NV copy as what it is, and on a gs101 board checks that the per-phone props.conf says raven before cbd and rfsd start. Two smaller fixes from running it daily: the user is told when the modem crashes, and sitd ends in one line instead of a traceback when the CP goes away. raven's MODEM-PLAN gains section 11 (the link at system suspend), which these follow.

Device and build

  • Phone: Pixel 6 Pro (raven)
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf (raven's integration kernel: CPIF for gs101 isn't published yet)
  • Packages changed, with versions: omamobile-modem 0.1.18, omamobile-modem-sit 0.3.34, omamobile-device-raven 0.1.34 (next free on 2026-11-10's main)

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages passes (or the packages I touched: omamobile-modem, omamobile-modem-sit, on every commit)
  • Each changed package has its version bumped, and the new version is in the commit subject
  • Commits have area prefixes and bodies that say why; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (plan, step, result): the profile check passes, efs, efs_backup and modem_userdata mount as ext4 from their RAM copies, rfsd verifies the NV checksums, and the CP reaches ONLINE at boot.
  • What I did not test: calls, texts and data (this SIM has its PIN lock on, and the RIL has no PIN entry yet, so sitd stops at the SIM), the crash notice (no crash happened), and cheetah, which is almost unchanged: the f2fs check moved from profile_check into profile_setup (after the NV tmpfs and the modem image are mounted; it won't fire, since CONFIG_F2FS_FS=m is in the shared fragment), and the crash record now also keeps the Wi-Fi host's pcie: lines. Two things are new on the 7 Pro too: a modem crash raises a "Cellular stopped" notification, and sitd exits with one line when the CP goes away. The smoke report's CPIF lines are the unpublished kernel's: a channel nobody opened while sitd is off, and an optional GPIO raven's DT doesn't name.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)
tools/phone-smoke report

phone-smoke: raven

Kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at 0d328a0, 2026-11-03T11:17Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, slot b, up 202s
storage guard (required) ok 49 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 198 error lines in dmesg (52 known, of them ASoC no backend DAIs (PipeWire probe) x1, 146 new)
new dmesg errors not ok cpif: mif_gpio_get_value: GET GPIO N is not valid x57; cpif: rx_demux: PCIE: ERR! N is not opened x17; cpif: pass_skb_to_demux: PCIE: N<N: ERR! N>recv_skb fail (N) x17
systemd units ok none failed
USB gadget (required) ok bound to 11110000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panfrost
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok s6sy761
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 95% Discharging, 31 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 46 °C

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-device-raven 0.1.30-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.1-1, omamobile-modem 0.1.17-1, omamobile-modem-sit (number set at merge)-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, omamobile-voice 0.1.0-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

🤖 Generated with Claude Code

derekross added a commit that referenced this pull request Nov 3, 2026
…p of 0.1.13

main moved under this PR: #386 made omamobile-modem.service Type=notify
with the sleep inhibitor (Requires=/After= omamobile-modem-inhibit.service),
the modem-boot target and the two markers in lib/omamobile-modem-start;
#384, #387 and #388 brought the modem-sit keys that registered IMS on the
7 Pro on 2026-11-03.

Resolved:
- omamobile-modem.service keeps main's Requires=/After= and adds the
  overlay's Wants=omamobile-modem-nv-overlay.timer, so the timer hangs off
  the real unit; the stop's capture still runs in profile_stop after the CP
  power-off (profiles/modem.conf merged clean).
- install: one loop over the five units; the .install note keeps both
  the boot-target line and the overlay line.
- AGENTS.md section 4: main's longer "never restart" bullet (the modem-up
  marker), the overlay's NV bullet.
- version 0.1.15: main is 0.1.13 and #389 claims 0.1.14.
- MODEM-PLAN: the NV overlay section says what 2026-11-03 showed (IMS
  registers without NV persistence; what the overlay still buys).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross

Copy link
Copy Markdown
Owner

Thank you for the port and for running it on raven with a smoke report. I read the props order, the watcher's notify path and the sitd except path, and they're consistent. Three things before I merge:

  1. modem_device_check in profiles/modem.conf hard-codes ro.hardware=raven for every gs101 board, but google,gs101 also matches oriole and bluejay (device/oriole is google,gs101-oriole), so their owners would be refused. Could it derive the board from google,gs101-<board>, or check the platform only?
  2. MODEM-PLAN §11 names the fixes as omamobile-modem 0.1.11 / modem-sit 0.3.5; they land as 0.1.14 / a modem-sit number I'll set at merge (0.3.28 went to omamobile-modem-sit 0.3.21: leave an unconfirmed call release for an attended reboot #364 this morning).
  3. "Nothing changes for cheetah" overstates it a little: the f2fs check moved out of profile_check into profile_setup (after the NV tmpfs and modem image are mounted; it won't fire, since CONFIG_F2FS_FS=m is in the shared fragment), and the cheetah crash record now also takes the Wi-Fi host's …pcie: lines. An honest "almost unchanged on cheetah" line in the body would do.
    I'll merge this first and rebase my omamobile-modem 0.1.15: keep the modem's own NV writes in a per-phone overlay #382 on top of it at omamobile-modem 0.1.15.

derekross added a commit that referenced this pull request Nov 3, 2026
…1-03 keys (modem-sit 0.3.29, mmd 0.1.2, shell 0.2.96)

main moved under this PR (#384, #386, #387, #388): modem-sit 0.3.24-0.3.27
brought attach_apn = none, ims_first, internet_cid, [profiles],
carrier_manifest and ims_pcscf_from_isim, and the internet bearer's rmnet
device is now found by omamobile-sit-data. Where both sides changed the
same thing, main's code wins: bringup.start() is main's order with the
carrier lookup in front of it (the SIM read once after the USIM is READY,
what isn't typed comes from the lookup); data_network.py is main's device
search with this PR's roaming check on the device found; paths.py, sit.py,
modem-sit.conf and test_bringup.py merged by hand.

What registered IMS and carried calls and texts on the 7 Pro on
2026-11-03 (NOTES, IMS-SHANNON 11-12) was five typed values beyond the
APN, so the lookup now produces them: an override section carries
attach_apn (an APN or none), ims_apn, ims_first, internet_cid and
profile_<ID> lines, and "like = MCC/MNC" lets a carrier's codes share one
section. ims_apn, ims_first and internet_cid default to auto; an empty
[profiles] takes the override's set. Verizon's codes give apn =
VZWINTERNET, attach_apn = none, ims_apn = IMS, ims_first = yes,
internet_cid = 3 and stock's four profiles. The 11-02 value attach_apn =
vzwims registered but never got IMS: gone, and the file says why. mmd
treats none as no attach settings; the Mobile network page shows it as
"Not sent: the carrier profile's own".

Versions: modem-sit 0.3.29 (main 0.3.27, #389 claims 0.3.28), mmd 0.1.2
(main 0.1.1), shell 0.2.96 (main 0.2.94, #343 claims 0.2.95).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
modem_device_check required ro.hardware=raven on every gs101 phone, so a
Pixel 6 (google,gs101-oriole) or 6a (google,gs101-bluejay) with its own
props.conf would have been refused. The board now comes from the first
google,gs101-<board> compatible, and props.conf must name that board with
platform gs101. Other SoCs return at once, as before. Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
The crash notice is omamobile-modem 0.1.14, and the sitd exit lands in
whichever omamobile-modem-sit release derekross#389 merges as (0.3.28 went to
derekross#364). Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith robotosaith changed the title omamobile-modem 0.1.14, omamobile-modem-sit 0.3.28: the modem runtime on the Pixel 6 Pro omamobile-modem 0.1.14, omamobile-modem-sit: the modem runtime on the Pixel 6 Pro Nov 3, 2026
@robotosaith

Copy link
Copy Markdown
Contributor Author

Thanks for the careful read. All three are in:

  1. modem_device_check now takes the board from the first google,gs101-<board> compatible and asks props.conf for that board with platform gs101, so oriole and bluejay pass with their own props, and a props file naming another board is refused. Other SoCs return at once as before. test/all covers raven, oriole, bluejay, the wrong board, a wrong platform and cheetah (7496ec2).
  2. MODEM-PLAN §11 now says omamobile-modem 0.1.14, and for the sitd exit "the release omamobile-modem 0.1.22, omamobile-modem-sit 0.3.35, device-raven 0.1.36: the modem runtime on the Pixel 6 Pro #389 lands in", so it stays right whatever number you give it (74b674e). The PR title no longer names a modem-sit version.
  3. You're right, I've put an "almost unchanged on cheetah" line in the description that says both things: the f2fs check now runs in profile_setup after the mounts, and the crash record keeps the Wi-Fi host's pcie: lines.

Merging this first and rebasing #382 on it at 0.1.15 sounds good. One thing for #382 while you're there: raven's NV copies are ext4 (that's this PR's mount change), so the overlay's "files in the three f2fs copies" will need the same type check before it's raven-ready.

robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
modem_device_check required ro.hardware=raven on every gs101 phone, so a
Pixel 6 (google,gs101-oriole) or 6a (google,gs101-bluejay) with its own
props.conf would have been refused. The board now comes from the first
google,gs101-<board> compatible, and props.conf must name that board with
platform gs101. Other SoCs return at once, as before. Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
The crash notice is omamobile-modem 0.1.14, and the sitd exit lands in
whichever omamobile-modem-sit release derekross#389 merges as (0.3.28 went to
derekross#364). Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 3, 2026
…0: the Pixel 7 Pro's modem stack on by default (#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: #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

* 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 #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

* 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>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
modem_device_check required ro.hardware=raven on every gs101 phone, so a
Pixel 6 (google,gs101-oriole) or 6a (google,gs101-bluejay) with its own
props.conf would have been refused. The board now comes from the first
google,gs101-<board> compatible, and props.conf must name that board with
platform gs101. Other SoCs return at once, as before. Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
The crash notice is omamobile-modem 0.1.17, and the sitd exit lands in
whichever omamobile-modem-sit release derekross#389 merges as (0.3.28 went to
derekross#364). Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith robotosaith changed the title omamobile-modem 0.1.14, omamobile-modem-sit: the modem runtime on the Pixel 6 Pro omamobile-modem 0.1.17, omamobile-modem-sit 0.3.30: the modem runtime on the Pixel 6 Pro Nov 3, 2026
@robotosaith

Copy link
Copy Markdown
Contributor Author

Rebased onto today's main after #373, #382 and #398: omamobile-modem is now 0.1.17 and the sitd exit lands as modem-sit 0.3.30. Two things met #382's overlay: profile_check keeps your overlay-tool check and adds the board check (the f2fs check stays in profile_setup, as before), and the overlay itself works on the mounted copies, so it needs nothing for raven's ext4 beyond its note now saying f2fs on gs201 and ext4 on gs101. Tests and pr-check pass on the tip.

@derekross

Copy link
Copy Markdown
Owner

Thanks for the quick turnaround and for carrying the rebases onto #382 and #398. I checked each point against the new head: the board now comes from google,gs101-<board> with tests for raven, oriole, bluejay and cheetah; §11 names 0.1.17; and the body has the "almost unchanged on cheetah" line. I read cheetah's path through again. The board check returns at once there, and the typed mount comes out as the same mount -t f2fs, just after the copies are in place.

Before I merge:

  1. Which head ran on your raven? The smoke report is from 11:17Z, before both rebases (one of them put the overlay's apply step between the mounts and the checksum check), and its package list has been edited by hand ("omamobile-modem-sit (number set at merge)"). Could you boot the current head once, confirm the profile check, the ext4 mounts, the NV checksums and CP ONLINE, and paste the smoke report exactly as the tool prints it?
  2. On my side: since 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 the modem starts at every boot on the Pixel 7 Pro, so I'll boot mine on 0.1.17 before merging.

Small things, fine in the same push:

  • The body's cheetah line could also mention the crash notification and sitd's one-line exit. Both are new on the 7 Pro too, and I think both are right there.
  • t=$(blkid …) runs under the runner's set -euo pipefail, so if blkid finds no type the start stops before your "is …, not ext4 or f2fs" message. || true lets the message print.
  • notify() writes nothing to the journal, which §11 itself runs into. One line saying how many sessions it notified would let a crash report confirm it.
  • §11 says the sleep inhibitor "isn't in the package". Since omamobile-modem 0.1.13 it is (omamobile-modem-inhibit), so a dated line there would keep the plan right. When you get a chance, please also push the CPIF suspend fixes §11 describes to a branch.

On numbers: omamobile-modem 0.1.17 is also used by #403, and modem-sit 0.3.30 by other open PRs too. I'll set whichever lands second at merge, and I'll write the squash message myself, since the first commit still says nothing changes on cheetah.

robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 4, 2026
…urnal, §11 notes

Review on derekross#389:
- profile_setup: blkid finding no type no longer stops the start under
  set -e before the "is ..., not ext4 or f2fs" message; it prints it.
- notify() says in the journal whom it notified ("notified N of M
  session(s)", or why none), so a crash report can confirm it.
- MODEM-PLAN §11: a dated line that the sleep inhibitor is in the package
  since omamobile-modem 0.1.13 after all, and where the three CPIF
  suspend fixes it describes are pushed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 4, 2026
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>
@robotosaith

Copy link
Copy Markdown
Contributor Author

Thanks for checking cheetah's path again. All in 4da03c5 and e97fbe7:

  1. Current head on raven: booted omamobile-modem 0.1.22, omamobile-modem-sit 0.3.35, device-raven 0.1.36: the modem runtime on the Pixel 6 Pro #389's head as installed (omamobile-modem 0.1.17, modem-sit 0.3.30; NV partitions checked against the 2026-11-03 backup first, all matching and read-only) on 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf. The profile check passed ("preconditions met"), efs, efs_backup and modem_userdata are mounted as ext4, the three NV files match stock's checksums ("stock checksum matches", and rfsd's own "checksum : verified"), and the CP was ONLINE 8 s after the unit started.

    That boot also found a bug: sitd failed at every raven boot with "CP is not ONLINE". The modem unit is READY when CPIF's ports exist, about 3 s before ONLINE, and the wait for ONLINE that 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 added is a device-cheetah drop-in, so raven never had it. e97fbe7 gives device-raven the same two drop-ins (sitd's wait-online 120, and sit-data's ConditionPathExists=/dev/umts_ipc0), so cheetah is unchanged. On the next boot (the drop-ins copied to /etc, since this phone's device-raven is omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) #401's 0.1.32), sitd waited for ONLINE and then stopped at the SIM: "the SIM PIN lock is on", main's stop-at-once. The smoke report flags exactly that, plus the same CPIF lines as before and omamobile-audio 0.5.15, device-raven 0.1.32: raven's speakers through protection at stage media (stacked on #400) #401's mailbox burst:

phone-smoke

phone-smoke: raven

Kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, tools at e97fbe73, 2026-11-04T07:50Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf, slot b, up 71s
storage guard (required) ok 49 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 309 error lines in dmesg (64 known, of them ASoC no backend DAIs (PipeWire probe) x1, 245 new)
new dmesg errors not ok wc-mbox N: Try increasing MBOX_TX_QUEUE_LEN x118; cpif: mif_gpio_get_value: GET GPIO N is not valid x60; cpif: rx_demux: PCIE: ERR! N is not opened x15
systemd units not ok failed: omamobile-sitd.service
USB gadget (required) ok bound to 11110000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panfrost
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok s6sy761
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 88% Discharging, 22 °C
sound cards ok googleaocsndcar
sensors ok AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 46 °C

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.15-1, omamobile-device-raven 0.1.32-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.17-1, omamobile-modem-sit 0.3.30-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, omamobile-voice 0.1.0-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

Small things:

  • t=$(blkid … || true), and the message says "of no known type" when it's empty.
  • notify() logs "notified N of M session(s): TITLE" (or why it sent nothing), also when OMAMOBILE_NOTIFY_CMD is set.
  • §11 has a dated line saying the inhibitor is in the package since 0.1.13. The three CPIF suspend fixes are on omamobile-gs101-cpif-suspend (on omamobile-gs101-cpif, not yet signed off), and §11 links it.
  • The body's cheetah line now also names the crash notification and sitd's one-line exit.

device-raven 0.1.31 is taken by #400 too; please renumber at merge as you said.

robotosaith and others added 13 commits November 11, 2026 12:55
The runtime only knew cheetah's S5300. The Pixel 6 Pro (raven, gs101)
runs the same stock rfsd and cbd in the chroot, with two differences:

- its NV partitions are ext4, not f2fs, so each copy is mounted as what
  it is (blkid), and f2fs is only loaded when a copy needs it;
- props.conf names cheetah, so on a gs101 board the profile checks that
  the per-phone props.conf says raven and gs101 before any daemon runs,
  or cbd and rfsd would take the other board's paths.

omamobile-device-raven already provides omamobile-modem-policy, so the
package installs on raven as it is; nothing here changes what cheetah
runs (its copies are f2fs and its board check returns at once).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On raven the modem's PCIe link died 93 minutes into a boot. Nothing
said so: sitd exited, mobile data had no bearer, and the next crash
record's kernel lines were only this tool's own umts_boot0 opens, since
the dead link's one repeated message had pushed everything else out.

- A critical notification in every session when the CP leaves ONLINE:
  no calls, texts or data until a restart, and where the record is.
- The record's kernel lines take the PCIe link driver's lines too, drop
  CPIF's open/release lines for this tool's ioctls, and fold a repeated
  message into one line and a count, so the start of a flood survives.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When the CP crashed under it, sitd died with a traceback through the
SIT read (EOFError: SIT channel closed). If the CP is no longer ONLINE
after an EOFError, OSError or RuntimeError, it now exits with "the modem
went away (...): calls, SMS and data are off until the phone restarts";
omamobile-modem.service has the crash record and the notification. With
the CP still ONLINE the error is raised as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What the modem watcher and sitd changes in this series answer: two
suspends with the CP ONLINE, two crashes, and the kernel fixes on test
since.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
modem_device_check required ro.hardware=raven on every gs101 phone, so a
Pixel 6 (google,gs101-oriole) or 6a (google,gs101-bluejay) with its own
props.conf would have been refused. The board now comes from the first
google,gs101-<board> compatible, and props.conf must name that board with
platform gs101. Other SoCs return at once, as before. Review of derekross#389.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The crash notice is omamobile-modem 0.1.17, and the sitd exit lands in
whichever omamobile-modem-sit release derekross#389 merges as (0.3.28 went to
derekross#364). Review of derekross#389.

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>
test/nv-overlay checks that the overlay is applied after the NV copies
are mounted and before the checksum check, by finding the mount line in
profile_setup. That line is now `mount -t "$t"` (each copy mounted as
what it is, ext4 on gs101), so the search came back empty and the test
ended non-zero after every check had passed. CI caught it; my local runs
only read the ok lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…urnal, §11 notes

Review on derekross#389:
- profile_setup: blkid finding no type no longer stops the start under
  set -e before the "is ..., not ext4 or f2fs" message; it prints it.
- notify() says in the journal whom it notified ("notified N of M
  session(s)", or why none), so a crash report can confirm it.
- MODEM-PLAN §11: a dated line that the sleep inhibitor is in the package
  since omamobile-modem 0.1.13 after all, and where the three CPIF
  suspend fixes it describes are pushed.

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
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>
…s after today's main

main has moved past this branch's numbers (omamobile-modem 0.1.20,
modem-sit 0.3.34 and device-raven 0.1.34 have shipped), so the three
packages take the next ones. Raven's MODEM-PLAN section 11 names the
modem's crash notice by the release this lands in, as it already does
for modem-sit's, rather than by a number that moves.

device-raven's test/all keeps both the speaker-protection block from
derekross#401 and this branch's sitd/sit-data drop-in block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The watcher runs in the profile's private mount namespace, which is made
at boot before the user's /run/user/<uid> tmpfs is mounted; inside it
that directory stays empty, so after a crash notify() found no session
bus and said nothing (review on derekross#389: unit start 14:42:49, /run/user/1000
mounted 14:43:11, the bus socket missing from inside the namespace).

notify() now looks for sessions through /proc/1/root/run/user, at each
call, and runs the send under nsenter --target 1 --mount when its mount
namespace differs from PID 1's. The profile's own isolation is left as
it is. On raven on 2026-11-11 the one notice that arrived came from a
modem started by hand after login, as this predicts.

The test runs notify() with the bus absent, then present: nothing is
sent the first time, one send through nsenter the second.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Entering PID 1's mount namespace wasn't enough. On raven, with the modem
started at boot before login, the watcher found the session through
/proc/1/root but the send failed: omarchy-notification-send's
busctl --user, run from inside the profile's PID namespace and cgroup,
was refused ("Failed to connect to user scope bus via local transport:
Operation not permitted").

The watcher now asks PID 1 for the send: systemd-run --uid=<user> with
the session's bus address, waiting for it. PID 1 starts it in the host's
namespaces and its own cgroup, and its output reaches the journal. A
failed send logs its exit code and last line instead of nothing, and
nsenter and runuser are gone.

Tested on raven, 2026-11-11, 7.3.0-rc6-omamobile-push1-ge1e6adb69bbf:
modem started 12:51:42 with no session, the bus absent inside the
watcher's namespace, the user logged in, then the modem stopped:
"notified 1 of 1 session(s): Cellular stopped". The first version of
this fix, on the same steps, logged "notified 0 of 1" with the busctl
error above.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith

Copy link
Copy Markdown
Contributor Author

Rebased onto today's main to clear the conflict (only packages/omamobile-modem/version) and took the next free numbers: omamobile-modem 0.1.21, omamobile-modem-sit 0.3.35, device-raven 0.1.35. Change them at merge if others land first.

@derekross

Copy link
Copy Markdown
Owner

Thank you, this is the fix I hoped for, and you found the second half yourself: the bus lookup through PID 1's view wasn't enough, and sending through a transient unit keeps the profile's isolation exactly as it was. The test covers the case I asked for (no bus at start, a bus later), CI is green on this head, and thanks for rebasing and renumbering again.

One thing before I merge, and your own test shows it. You checked the notice by stopping the modem, and it arrived: "notified 1 of 1 session(s): Cellular stopped". The watcher treats every move away from ONLINE as a crash, and a stop powers the modem off while the watcher is still polling, so a deliberate systemctl stop omamobile-modem now puts a critical "The modem crashed … until the phone restarts" notification on the screen. On the 7 Pro we stop the modem by hand before every push, so this would show up daily. Until now it couldn't reach the session, which is why nobody noticed.

The stop already leaves a mark before it powers the modem off: the intent-<invocation> file in /run/omamobile-modem that profile_stop writes. Could the watcher skip the notice when one is there (and log "stopped" rather than a crash), with a test for both cases: ONLINE then gone with an intent file, nothing sent; without one, one send? The crash record on a stop is #532 and can stay for that issue.

On numbers: omamobile-modem 0.1.21 and device-raven 0.1.35 are also claimed by another open pull request, so if that one lands first I'll move yours up by one at merge. I'll write the squash message with the numbers the files carry; no need to edit the title.

@derekross

Copy link
Copy Markdown
Owner

A note on numbers, nothing for you to change in the code: #403 merged today and took omamobile-modem 0.1.21 and omamobile-device-raven 0.1.35, the two numbers this branch also carries. The two merge without a conflict, because the lines are equal, so nothing would have warned either of us and the Pixel 6 Pro's package would have kept its old build.

When you next merge main into this branch, please take omamobile-modem 0.1.22 and omamobile-device-raven 0.1.36, or leave both and I'll set them at merge. omamobile-modem-sit 0.3.35 is also claimed by three other open PRs (#669, #374, #376); I'll set that one at merge too.

robotosaith and others added 2 commits November 12, 2026 07:00


derekross#403 merged and shipped omamobile-modem 0.1.21 and device-raven 0.1.35,
the numbers this branch also carried. The lines were equal, so the merge
of main raised no conflict, and the Pixel 6 Pro's package would have
kept its old build. Both take the next numbers. modem-sit stays at
0.3.35; other open pull requests claim it too, and it is set at merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith robotosaith changed the title omamobile-modem 0.1.18, omamobile-modem-sit 0.3.34, device-raven 0.1.34: the modem runtime on the Pixel 6 Pro omamobile-modem 0.1.22, omamobile-modem-sit 0.3.35, device-raven 0.1.36: the modem runtime on the Pixel 6 Pro Nov 12, 2026
@robotosaith

Copy link
Copy Markdown
Contributor Author

Thanks for catching that. Merged main and took omamobile-modem 0.1.22 and omamobile-device-raven 0.1.36 (2687806); omamobile-modem-sit stays at 0.3.35 for you to set at merge.

@derekross

Copy link
Copy Markdown
Owner

Thanks for taking the numbers: the branch now carries omamobile-modem 0.1.22 and omamobile-device-raven 0.1.36, both free on main and on every other open pull request. omamobile-modem-sit 0.3.35 is claimed by four others, so I'll set that one when I merge, as we said. CI is green on this head.

One thing is still open, and I think my note about numbers the next day buried it, sorry: the stop notice from my comment of 11-11. On this head the watcher still calls notify() for every move away from ONLINE, so a deliberate systemctl stop omamobile-modem puts "Cellular stopped: The modem crashed … until the phone restarts" on the screen. On the 7 Pro we stop the modem by hand before every push, so that would show daily.

The stop already leaves its mark before the power-off: profile_stop writes /run/omamobile-modem/intent-$INVOCATION_ID (holding the invocation ID), /run is visible inside the profile's namespace, and the watcher has the same INVOCATION_ID as rfsd's wrapper. Could the watcher make the same test that wrapper makes (a 32-hex ID, a regular file that isn't a symlink, content equal to the ID) and, when it holds, log that the modem was stopped and send nothing? With tests for the three cases: ONLINE then gone with this invocation's intent, nothing sent; without one, one send; a wrong or symlinked intent, still one send. The crash record on a stop is #532 and can stay as it is.

When that's in I'll run it on my Pixel 7 Pro: a stop before a push (no notification, the "stopped" line in the journal) and a reboot. The send itself has run on your raven and not on a 7 Pro; once a stop no longer triggers it I have no harmless way to trigger it there, so I'll note it as not exercised on the 7 Pro rather than ask you for more. Then I'll merge, and write the squash message myself.

The watcher took every move away from ONLINE for a crash, and a stop
powers the CP off while it is still polling, so a deliberate
`systemctl stop omamobile-modem` (run before every push on the 7 Pro)
put "Cellular stopped: The modem crashed" on the screen once the notice
could reach the session.

profile_stop writes /run/omamobile-modem/intent-$INVOCATION_ID, holding
the ID, before the power-off, and the watcher runs under the same
invocation. It now makes the same test rfsd's job makes (a 32-hex ID, a
regular file that isn't a symlink, its content the ID) and, when it
holds, logs that the modem was stopped and sends nothing. The crash
record on a stop stays as it is (derekross#532).

test/watch-stop.py drives watch() through ONLINE then OFFLINE: with this
invocation's intent nothing is sent; without one, with another ID's, or
with a symlinked one, one notice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotosaith

Copy link
Copy Markdown
Contributor Author

Thanks, and no need to apologise, it was easy to miss under the numbers. Done in a0a0bf3: the watcher now makes the same test as rfsd's wrapper (a 32-hex INVOCATION_ID, /run/omamobile-modem/intent-<id> a regular file, not a symlink, holding that ID). When it holds, it logs "the CP left ONLINE during this invocation's stop: the modem was stopped, nothing sent" and sends no notice. The crash record on a stop stays for #532.

test/watch-stop.py drives watch() through ONLINE then OFFLINE in your three cases (this invocation's intent: nothing sent; no intent: one send; another ID's or a symlinked intent: one send), plus a missing INVOCATION_ID. test/all passes in the Arch container. No version change: omamobile-modem stays at 0.1.22.

@derekross

Copy link
Copy Markdown
Owner

Thank you, this is exactly the test I had in mind, and you added the symlink case and the missing-ID case on top. I read stop_intended() next to rfsd's job in modem.conf and they make the same three checks; the intent is written before the power-off and nothing removes it until the unit's processes are gone, so the watcher can't miss it. I also broke the check three ways here (no call, no symlink test, no content compare) and your tests caught each one. CI is green on a0a0bf3f, and the modem, modem-sit and device-raven tests pass on a merge with today's main.

Nothing more is needed from you. What's left is mine:

  1. My Pixel 7 Pro: a stop before a push with the screen on (no notification, the "modem was stopped, nothing sent" line in the journal), then a reboot. The send itself has run on your raven and not on a 7 Pro; I'll try it there with a direct call and note the result either way.
  2. Numbers: after your last merge of main, main took omamobile-modem-sit 0.3.35 (omamobile-modem-sit 0.3.35: its tests no longer read the phone's own network devices #677) and omamobile-device-raven 0.1.36 (device packages: the version numbers #459's reboot-to needs #696). The lines are equal again, so nothing conflicts and nothing would have warned us. I'll push omamobile-modem-sit 0.3.36 and omamobile-device-raven 0.1.37 to your branch as one commit on top before I merge; omamobile-modem 0.1.22 is still free. No need to touch them yourself.

One small thing, for a follow-up if you like, not for this PR: the last case in test/watch-stop.py doesn't patch RUN, so it reads the real /run/omamobile-modem of the machine that runs it, and it still passes with the 32-hex check taken out. A case with RUN patched, a short INVOCATION_ID and a matching intent-<short> file would hold that line too.

I'll write the squash message myself.

robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…rst (derekross#410)

CI's test job took 934 s on derekross#389, three suites most of it in a row
(omamobile-audio 316 s, omamobile-shell 263 s, omamobile-modem-sit 138 s).
The suites now run up to OMAMOBILE_TEST_JOBS at once (default: the CPUs,
at most 8; 1 runs them one at a time), the slow ones first, each suite's
output printed together when it ends.

A result is written aside and moved into place, so a report never reads
it half written; a suite that ends without a result fails as
"not ok - NAME (no result)"; and each suite stops after
OMAMOBILE_TEST_TIMEOUT seconds (default 1800) and fails with its log
printed, since output is held until a suite ends.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ses the sleep block (derekross#424)

A modem start that is refused before any link driver loads (a stale marker, the bring-up latch, a phone that isn't provisioned) kept the "don't sleep with the modem up" block for the whole boot, although no modem was up. It now releases the block, so the phone can sleep that boot. A link module that fails to load is a refusal with a reason for the Mobile data tile, where the script used to leave through set -e with modprobe's status. A successful start is unchanged.

Tested by the contributor on a Pixel 6 Pro. Tested on a Pixel 7 Pro on 2026-11-10 (7.3.0-rc6-omamobile-push1-gc7fb37460f84, this change with derekross#389): with a bring-up marker placed by hand the next boot refused, logged "no modem driver loaded: sleep is no longer blocked this boot", held no inhibitor and loaded no link module; removing the marker and starting the unit brought the CP ONLINE with the block back. A normal boot before it: ONLINE, a call and a text each way.
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.

2 participants