Skip to content

omamobile-modem-sit 0.3.29, omamobile-mmd 0.1.2, omamobile-shell 0.2.99: SIM setup with no APN to type - #373

Merged
derekross merged 9 commits into
mainfrom
sim-setup
Nov 3, 2026
Merged

derekross merged 9 commits into
mainfrom
sim-setup

Conversation

@derekross

@derekross derekross commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

SIM setup that just works: no APN to type. On 2026-11-02 the SIM needed apn = vzwinternet typed into modem-sit.conf before sitd would start ("No APN configured"), and on 2026-11-03 it took five more typed values (attach_apn = none, ims_apn = IMS, ims_first = yes, internet_cid = 3 and four [profiles] lines) before IMS registered and calls and texts worked (cheetah NOTES 2026-11-03, IMS-SHANNON §11-12). This PR makes the carrier lookup produce all of them from the SIM.

Design notes are in docs/TELEPHONY-APPS-PLAN.md §7.6. The automatic path has not run on the phone yet; the values it produces for Verizon's codes are exactly the ones typed by hand on the 7 Pro on 2026-11-03. The phone checks are at the end of §7.6.

Merged with main on 2026-11-03

main moved under this PR (#384, #386, #387, #388: modem-sit 0.3.24-0.3.27 with attach_apn = none, ims_first, internet_cid, [profiles], carrier_manifest, ims_pcscf_from_isim, [audio] earpiece; the internet bearer's rmnet device found by omamobile-sit-data). It is merged in as a merge commit, main's code winning wherever both sides changed the same thing:

  • bringup.start() is main's order (radio state read, attach APN, every profile and NR mode before a single radio on; attach_apn = none; the modem-owned attach bearer; IMS first; internet_cid), with this PR's carrier lookup in front of it: the SIM is read once after the USIM is READY, and what isn't typed comes from the lookup.
  • data_network.py is main's device search (find_device, rmnet<CID-1> first); this PR's [data] roaming check runs on the device found, not on a fixed rmnet0.
  • paths.py, sit.py (GET_IMSI stays on the allow-list; main's ISIM exception alongside), modem-sit.conf (main's key comments, with auto where this PR adds it) and test_bringup.py (both sides' tests, main's adapted to the lookup) were merged by hand.

omamobile-modem-sit 0.3.29 (main is 0.3.27; #389 claims 0.3.28)

  • Automatic APNs, as before. [network] apn and attach_apn default to auto (empty means the same). With auto, sitd sends GET_IMSI (0x0400) once after the USIM is READY, keeps only the MCC/MNC and looks them up in the project's apn-overrides.conf, then in the system's mobile-broadband-provider-info (serviceproviders.xml, GNOME, CC-PDDC, a dependency now). primary="true" wins among providers sharing a code, then the provider listing the most codes.
  • The lookup now fills the rest of a carrier's setup. An override section can carry, with the [network] keys' meaning: attach_apn (an APN, or none: not sent), ims_apn, ims_first, internet_cid, and the data profiles as profile_<ID> lines in the [profiles] format; like = MCC/MNC lets a carrier's codes share one section. ims_apn, ims_first and internet_cid default to auto (the override's value, else ims, no, 1); an empty [profiles] takes the override's set, and any typed line replaces it. A typed value always wins, and a typed internet APN still takes the carrier's attach APN, bearer order and profiles.
  • Verizon's codes (the thirteen in the database's own list) now produce what registered IMS on 2026-11-03: apn = VZWINTERNET, attach_apn = none, ims_apn = IMS, ims_first = yes, internet_cid = 3, profiles 0 VZWINTERNET default,supl,dun ipv4v6, 2 IMS ia,ims ipv4v6, roaming ipv6, 3 VZWADMIN fota, 4 VZWAPP cbs,mms. The earlier override value attach_apn = vzwims (11-02) registered but never got IMS: it is gone, and the file says why. The carrier manifest stays the owner's setting: it names a file in the owner's own modem chroot.
  • No APN found. sitd skips the attach APN, the profiles and the internet bearer, registers, and goes on to IMS: calls and SMS work, status reports data_available: false. A bad [profiles] line still stops before the SIM, as on main.
  • Logs and status. The log names only the sources ("APN chosen from the carrier database", "attach APN chosen from the project's carrier overrides (none: not sent)", "bearer order and data profiles from the project's carrier overrides"). Never the IMSI, the MCC/MNC or an APN; the simulator test checks. Status: modem.apn (value, source, attach, attach_source; attach is none when none is sent) and sim.pin_lock.
  • Data roaming. [data] roaming, default yes; omamobile-sit-data reads it on every pass and drops the cellular route while roaming.
  • omamobile-sit-config (pkexec, polkit org.omamobile.modem-sit.configure, allow_active=yes) changes only apn, attach_apn and roaming, checks each value, keeps the comments, restarts nothing.

omamobile-mmd 0.1.2 (main is 0.1.1)

The bearer APN and InitialEpsBearerSettings come from sitd's status, not from a config value of auto; none leaves the attach settings empty.

omamobile-shell 0.2.96 (main is 0.2.94; #343 claims 0.2.95)

  • omamobile.mobilenetwork opens from Setup > Mobile network (only where the modem stack is installed) and from the Mobile data tile's chevron: carrier, registration, technology and signal; Mobile data and Data roaming switches; the APN in use with an override field and "Use the APN from the SIM"; Advanced: the attach APN, shown as "Not sent: the carrier profile's own" when it is none, with its own field; SIM PIN lock; after a save, "Restart now". Backend: omamobile-mobile-network.
  • omamobile-onboarding: with a SIM, setup names the carrier and says mobile data is set up automatically.

Checks

  • packages/omamobile-modem-sit/test/all (unit tests and the RIL against tools/sit-sim, the Verizon case included), packages/omamobile-mmd/test/all and packages/omamobile-shell/test/all pass.
  • tests/all and tools/pr-check origin/main pass.

No phone was used.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

derekross and others added 5 commits November 2, 2026 20:39
…ithout one

A reseller SIM on Verizon's network needed "apn = vzwinternet" typed
into modem-sit.conf before sitd would start, and then registered only with
the IMS APN as the initial attach APN. A SIM should just work.

With [network] apn and attach_apn at "auto" (the new default; empty means
the same), sitd sends GET_IMSI once after the USIM is READY, keeps only the
MCC/MNC and looks them up in the project's apn-overrides.conf, then in the
system's mobile-broadband-provider-info (CC-PDDC, now a dependency). The
attach APN is an override's attach_apn, else a database APN typed "ia",
else the internet APN. The only override is Verizon's codes: internet
vzwinternet (Verizon's own page), attach ims (our capture on 2026-11-02).
A typed value always wins. Only the source is logged, never the IMSI, the
network code or an APN; status carries the APNs in use and the SIM's PIN1
state for the shell.

Without an APN sitd no longer stops before the radio: it registers, skips
the internet bearer and goes on to IMS, and reports data unavailable.

[data] roaming (default yes, the behaviour so far) drops the cellular route
while roaming; omamobile-sit-data reads it on every pass. The new
omamobile-sit-config, run through pkexec (polkit: the active user), changes
only apn, attach_apn and roaming, and restarts nothing: an APN applies at
the next start-up, which needs a fresh CP.

tools/sit-sim answers GET_IMSI with a made-up subscriber part and logs the
attach APN. Overlaps #356/#364/#367 (0.3.9-0.3.11) in bringup.start(); the
attach_apn key matches #356's line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
With sitd 0.3.12 the config's APN can be "auto". The bearer's apn and
Modem3gpp.InitialEpsBearerSettings now show what sitd's status reports
(the internet APN and the attach APN), and fall back to the config's
values, with "auto" shown as no APN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
omamobile.mobilenetwork, opened from Setup > Mobile network (only where the
modem stack is) and the Mobile data tile's chevron: carrier, registration,
signal, Mobile data and Data roaming switches, the APN in use with a field
to type one, the attach APN under Advanced, and the SIM PIN lock. "No modem"
without the stack. omamobile-mobile-network reads sitd's public state, its
config and ModemManager, and changes settings through omamobile-sit-config
under pkexec; it never restarts the modem services, so an APN change offers
a restart of the phone.

omamobile-onboarding names the carrier and says mobile data is set up
automatically when a SIM is in and the stack runs; nothing to type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
The design of the automatic APN and attach APN, the carrier database and
its licence, the Mobile network page, what is logged, and the phone checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
The override said "ims", which was never tried as an attach APN. The SIM on
Verizon's network registered on 2026-11-02 (20:26 and 20:35) with vzwims as
the attach APN and vzwinternet for internet, so the override, its citation,
the comments, the design notes and the tests now say vzwims.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
derekross added a commit that referenced this pull request Nov 3, 2026
…m stack at boot, opt-in (stacked on #384) (#386)

* omamobile-modem-sit 0.3.21: attach as stock does on a Verizon network, IMS on the modem's attach bearer

On a Verizon-network SIM, stock's RIL sends no SET_INITIAL_ATTACH_APN for
the SIM's slot: the modem attaches with the carrier manifest's settings,
lists its attach bearer unsolicited (CID 2, IPv6, with three P-CSCF
addresses), and the IMS service announces that bearer with ADD_PDN_INFO.
0.3.20 sends an explicit attach APN, which most likely replaces the
manifest's attach and its P-CSCF request, and its own IMS setup comes back
without a P-CSCF, so IMS never registers.

- [network] attach_apn = none skips SET_INITIAL_ATTACH_APN; the profiles
  and the internet bearer go out as before.
- After registration, sitd waits up to 20 s for an active IPv6 or IPv4v6
  bearer it didn't set up that carries a P-CSCF, reading
  GET_DATA_CALL_LIST and IND_DATA_CALL_LIST_CHANGED, and logs each item as
  CID, type, status, active, P-CSCF and DNS counts (never addresses).
  Found: no IMS setup of its own, ADD_PDN_INFO from that bearer. Not
  found: 0.3.20's path (own IMS bearer, then the ISIM fallback).
- Bearers the modem brought up are recorded as modem-owned: activate()
  accepts them beside sitd's own and never uses their CID, deactivate()
  refuses them.
- The shipped conf documents a Verizon-network example as comments, and
  IMS-SHANNON.md section 11 has the gated runbook.

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

* omamobile-modem-sit 0.3.23: the IMS setup carries the IMS profile's APN types

Stock's setup builder copies the APN's whole supported-type bitmask into
the request (0xf1); for Verizon's IMS APN that is ims|ia (0x140), where
ours sent IMS alone (0x40). The modem matches setups against its
modem-cognitive profiles, and the ia bit marks the attach APN, so this
is the one byte left where our IMS setup differs from stock's. With a
[profiles] entry of the ims type for ims_apn, its bitmask is sent;
without one nothing changes.

IMS-SHANNON section 12 records the rest from libsitril: stock sends no
SET_INITIAL_ATTACH_APN for a modem-cognitive attach profile (so
attach_apn = none is its mode), the 0x0603 and 0x0613 layouts field by
field, that stock never uses CID 1 (its attach context) for a bearer of
its own, and a ranked list of further changes with a runbook.

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

* omamobile-modem-sit 0.3.24: IMS registers on Verizon's network: IMS first on CID 2, the internet on CID 3

Tested on the reference Pixel 7 Pro, 2026-11-03 02:00, Verizon-network
MVNO SIM, kernel 7.3.0-rc6-omamobile-g2219cc6cda77. The first IMS
registration on this phone: "state 2 (VoLTE registered), features 3",
then an SMS sent over IMS (AIMS_SEND_SMS accepted).

Stock's RIL keeps CID 1 for the modem's attach context and never sets a
bearer up on it; it sets the IMS bearer up first, on CID 2. On a network
that attaches on the IMS APN, sitd's internet setup on CID 1 replaced the
attach PDN, and the IMS bearer set up afterwards on CID 2 carried no
P-CSCF (every variant tried: attach APN IMS or none, IPv6 or IPv4v6,
P-CSCF requested, the carrier manifest, the ISIM's FQDN). With the IMS
bearer first on CID 2 the setup response carries three IPv6 P-CSCFs and
the modem's IMS stack registers within 2 s of ADD_PDN.

- [network] internet_cid (default 1, today's behaviour; 3 here): the
  CID of sitd's internet bearer. IMS stays on CID 2. paths() resolves
  any non-IMS CID to the internet record, so omamobile-sit-data (no
  configuration) keeps working, and its probe found rmnet2.
- [network] ims_first (default no): the IMS bearer and ADD_PDN before
  the internet bearer, as stock orders it; the internet comes up after
  the IMS setup whether or not IMS succeeded.
- The IMS setup also reads the P-CSCF from the data-call list entry when
  the setup response has none (the modem lists the attach bearer's PCO
  there on some firmware), and the setup carries the IMS profile's whole
  APN-type bitmask (ims|ia), as stock's does (0.3.23).

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

* NOTES: 2026-11-03, IMS registered and an SMS sent on a Verizon-network SIM

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

* omamobile-modem 0.1.13: the modem stack at boot, opt-in (omamobile-modem-boot.target)

Until 2026-11-03 the maintainer started the modem stack by hand every
boot: omamobile-modem, then omamobile-sitd, omamobile-sit data on and
omamobile-mmd. IMS registered on a Verizon-network SIM that night and an
SMS went out at 02:00, the condition set for starting it at boot.
Enabling the units one by one doesn't work: sitd Requires/After the
modem unit, which was Type=simple, so it ran while the CP was still
booting and exited ("CP is not ONLINE").

What changes, with nothing enabled by the package:

- omamobile-modem-boot.target is the one switch (systemctl enable; the
  next release enables it once the carrier configuration is automatic,
  #373). It wants the four units; each unit's own After= keeps the
  order, a missing unit is simply not started, and DefaultDependencies=no
  keeps multi-user.target (and omamobile-boot-success after it) from
  waiting on a registration that can take minutes. No wants link of any
  kind is shipped, and test/all holds the package to that.
- omamobile-modem-inhibit.service holds a systemd-inhibit sleep:idle
  block, required by and ordered before the modem unit, refused a manual
  stop, so it lasts until the reboot: suspend with the modem on has
  never run on this phone. The start script refuses to load a driver
  until the lock shows in systemd-inhibit --list.
- omamobile-modem.service is Type=notify: ready once CPIF's ports exist
  and the profile's read-only check has passed, before the CP is powered
  on. The CP's ONLINE is waited for by the device's sitd drop-in.
- The bring-up latch (modem-bringup-started) is written and synced
  before the first modprobe, as CONTRIBUTING 3.4 asks, not after the
  drivers and the check as before; a check that refuses removes it
  again, so a refusal doesn't cost the next boot its modem.
- A second marker, modem-up, written by the watcher at ONLINE (date and
  boot id) and removed by the unit's ExecStopPost when it is this
  boot's: a boot that ends with the modem up and no stop, a hang or a
  reset, leaves it, and the next boot refuses until a human has looked,
  so a hang after ONLINE can't become a reset loop. Only under the unit
  (INVOCATION_ID): a start by hand would have nothing to remove it.
- Nothing restarts the modem in place; the units have no Restart=.

Tests: the script's order (refusals, the inhibitor, the latch, modprobe,
the check with its rm, READY, exec), both refusals and --stopped and
--retry run for real against scratch markers, the units' relations and
the no-wants-link rule, systemd-analyze verify on the three units.

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

* device-cheetah 0.1.41: sitd waits for the CP's ONLINE before it runs

omamobile-modem.service (0.1.13) is ready once CPIF's ports exist, before
cbd has booted the CP, 10-30 s more; a sitd started on that alone exits
("CP is not ONLINE", seen 2026-11-03 with both units started at once).
This device's sitd drop-in adds ExecStartPre=omamobile-modem-cp
wait-online 120, the profile's own cbd timeout: a CP that never comes up
fails sitd, and the data fallback and the Phone and Messages bridge,
ordered after it, stay down until the reboot. Nothing is enabled: the
opt-in is omamobile-modem-boot.target, and the test checks that no wants
link for it or the four units is shipped. 0.1.41 leaves 0.1.40 to #372's
10-device-modem.conf in the same directory, which moves sitd's
Requires/After on the modem unit here; the two drop-ins are independent.

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

* MODEM-PLAN: M4.6, the gated runbook for the modem stack at boot

The one-switch form (omamobile-modem-boot.target, omamobile-modem 0.1.13,
device-cheetah 0.1.41) with its reasons: install and look (B0), enable
and reboot (B1), the chain in order with the inhibitor and the markers
(B2), data and the bridge with one SMS (B3), the second reboot that
proves the clean stop clears the modem-up marker (B4), and an optional
forced reset that proves the guard refuses (B5). Expect/pass, stop and
rollback per step; every reboot with the modem up costs one UFS pass.
The old M4.6 line, enabling the three units one by one, is marked
superseded: it started sitd before the CP was ONLINE.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 3, 2026
…on-network SIM) (#388)

Calls, texts and mobile data ran on the reference phone on 2026-11-03:
VoLTE and SMS over IMS, registration in 3 s, data behind Wi-Fi. The cell
names what is still by hand (the APNs and carrier manifest until #373,
the opt-in boot target, the earpiece needing stage media) and what is
unqualified (suspend with the modem up). Suspend stays WIP: its plan
moves the cell only after a day of use with auto-sleep on (P6).


Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
…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
@derekross derekross changed the title omamobile-modem-sit 0.3.12, omamobile-mmd 0.1.1, omamobile-shell 0.2.93: SIM setup with no APN to type omamobile-modem-sit 0.3.29, omamobile-mmd 0.1.2, omamobile-shell 0.2.96: SIM setup with no APN to type Nov 3, 2026
derekross and others added 2 commits November 3, 2026 09:30
… 0.2.99 over 0.2.97

Main took omamobile-modem-sit 0.3.28 (#364, the unconfirmed-hangup stop)
and omamobile-shell 0.2.97 (#394); #397 lands shell 0.2.98. This branch
keeps 0.3.29 and moves the shell to 0.2.99. tools/sit-sim keeps both
#364's --unconfirmed-hangup and this branch's --imsi-plmn/--no-imsi in
the usage block and the argument list.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
…e's IMS CID is the override's fault

Review of #373. MODEM-CLIENT.md's "no identity reads, but one" paragraph
and the apn comment in modem-sit.conf said GET_IMSI goes out when apn or
attach_apn is auto, from 0.3.12. choose_apn() sends it when any of apn,
attach_apn, ims_apn, ims_first or internet_cid is auto or empty, which
with the shipped defaults is every boot, and typing apn and attach_apn
alone still sends it for the bearer order; only typing all five reads no
IMSI. Both now say so, and that it landed in 0.3.29.

override_values() accepted internet_cid = 2 (the IMS bearer's CID), and
start() then stopped with a message blaming [network] internet_cid. The
override now refuses 2 itself, as it does 16: the value is left out, its
key is listed under 'refused', and choose_apn() logs that the project's
carrier override for this SIM had it, never the config and never the
network code. A test with such an override checks CID 1 and the message.

Also from the review: carrier_apn.py and omamobile-sit-config in
MODEM-CLIENT's module table, the [profiles] comment says the override's
profiles apply only when the SIM was read (not with all five keys typed),
and TELEPHONY-APPS-PLAN 7.6 names the versions after the merge with main
(shell 0.2.99; main's 0.3.28 is #364's).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross derekross changed the title omamobile-modem-sit 0.3.29, omamobile-mmd 0.1.2, omamobile-shell 0.2.96: SIM setup with no APN to type omamobile-modem-sit 0.3.29, omamobile-mmd 0.1.2, omamobile-shell 0.2.99: SIM setup with no APN to type Nov 3, 2026
derekross added a commit that referenced this pull request Nov 3, 2026
… the runbook points at main's modem-sit

Review of #382. apply() computed the binding and scanned every file of
the three mounted copies, then wrote base.json and start.json under /run,
before it looked at the enable file, and profile_setup dies on a non-zero
exit; so "off" cost a read of the copies and two files per modem start on
every phone with the package. apply now returns 0 before any read or
write when /etc/omamobile/modem-nv-overlay-enable is absent. An enable
file created after the modem started therefore finds no base record for
that boot: capture and diff say so and exit 0 (nothing is kept until the
reboot) instead of failing on the missing base.json.

test/nv-overlay step 10 checks that an unenabled apply and capture leave
nothing under /run, and that a capture and a diff after a mid-boot enable
keep nothing and exit 0.

MODEM-PLAN: the runbook's "Before" asked for omamobile-modem-sit 0.3.14
from the modem-sit-attach-apn branch, which is long on main (0.3.28);
it now points there and at #373's automatic path (0.3.29). The design's
"Start" bullet says that off returns before any read or write.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
derekross added a commit that referenced this pull request Nov 3, 2026
…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
derekross added a commit that referenced this pull request Nov 3, 2026
… overlay, off by default (#382)

* omamobile-modem 0.1.12: keep the modem's own NV writes in a per-phone overlay

The modem keeps the carrier profile it applies from the AP (0x4600 after
its 0x4602), its cell and band memory and its IMS state in NV, and asks
for a reset to load a new profile. With RAM copies of the backup that
are dropped at stop, the reboot that answers the reset throws the profile
away again, so IMS never gets its carrier settings and SMS and VoLTE
fail on networks that need them. Seeding NV from a stock boot isn't an
answer: users must never boot stock to make Linux work, and NV is per
phone, so nothing can be shipped.

The partitions stay exactly as protected as before: the ro=1 and
unmounted refusal, the RAM copies checked against the backup's
checksums, the stock salted checksum and the baseband guard are
unchanged. New is omamobile-modem-nv-overlay, per file because rfsd
keeps NV as files in the f2fs copies: at start, after the copies are
verified and before the stock checksum check, it lays the overlay in
/var/lib/omamobile/modem-nv-overlay (root, 0700) over them, only if
every file is on the allow-list (efs/nv_normal.bin with its salted MD5),
none is protected (nv_protected.*, efs_backup, identity- or
calibration-like names), the store matches its own checksums and it is
bound to the current modem-nv.sha256. Otherwise the overlay is set aside
with a journal line and the modem starts from the backup alone. The
modem's writes are captured after the CP power-off in the unit's stop
and every 30 minutes from a timer the unit pulls in, atomically (objects,
then MANIFEST by fsync and rename); writes to files off the allow-list
are logged and dropped. `omamobile-modem nv-overlay status|diff|capture|
reset` is the interface. Off until /etc/omamobile/modem-nv-overlay-enable
exists; MODEM-PLAN gets the design and the gated first hardware test,
AGENTS.md section 1 the rule.

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

* omamobile-modem 0.1.15: an unenabled NV overlay apply is a no-op, and the runbook points at main's modem-sit

Review of #382. apply() computed the binding and scanned every file of
the three mounted copies, then wrote base.json and start.json under /run,
before it looked at the enable file, and profile_setup dies on a non-zero
exit; so "off" cost a read of the copies and two files per modem start on
every phone with the package. apply now returns 0 before any read or
write when /etc/omamobile/modem-nv-overlay-enable is absent. An enable
file created after the modem started therefore finds no base record for
that boot: capture and diff say so and exit 0 (nothing is kept until the
reboot) instead of failing on the missing base.json.

test/nv-overlay step 10 checks that an unenabled apply and capture leave
nothing under /run, and that a capture and a diff after a mid-boot enable
keep nothing and exit 0.

MODEM-PLAN: the runbook's "Before" asked for omamobile-modem-sit 0.3.14
from the modem-sit-attach-apn branch, which is long on main (0.3.28);
it now points there and at #373's automatic path (0.3.29). The design's
"Start" bullet says that off returns before any read or write.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	packages/omamobile-shell/version
@derekross
derekross merged commit 60c0048 into main Nov 3, 2026
2 checks passed
@derekross
derekross deleted the sim-setup branch November 3, 2026 15:18
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>
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 3, 2026
…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>
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 4, 2026
… bring-up tests

The bring-up tests added with derekross#373 run start() with a client that answers SIM requests only, so the restart cleanup's bearer list failed to parse. They now stub clear_stale and release_owned, as the other bring-up tests do.
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 10, 2026
…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>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Nov 11, 2026
…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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…m stack at boot, opt-in (stacked on derekross#384) (derekross#386)

* omamobile-modem-sit 0.3.21: attach as stock does on a Verizon network, IMS on the modem's attach bearer

On a Verizon-network SIM, stock's RIL sends no SET_INITIAL_ATTACH_APN for
the SIM's slot: the modem attaches with the carrier manifest's settings,
lists its attach bearer unsolicited (CID 2, IPv6, with three P-CSCF
addresses), and the IMS service announces that bearer with ADD_PDN_INFO.
0.3.20 sends an explicit attach APN, which most likely replaces the
manifest's attach and its P-CSCF request, and its own IMS setup comes back
without a P-CSCF, so IMS never registers.

- [network] attach_apn = none skips SET_INITIAL_ATTACH_APN; the profiles
  and the internet bearer go out as before.
- After registration, sitd waits up to 20 s for an active IPv6 or IPv4v6
  bearer it didn't set up that carries a P-CSCF, reading
  GET_DATA_CALL_LIST and IND_DATA_CALL_LIST_CHANGED, and logs each item as
  CID, type, status, active, P-CSCF and DNS counts (never addresses).
  Found: no IMS setup of its own, ADD_PDN_INFO from that bearer. Not
  found: 0.3.20's path (own IMS bearer, then the ISIM fallback).
- Bearers the modem brought up are recorded as modem-owned: activate()
  accepts them beside sitd's own and never uses their CID, deactivate()
  refuses them.
- The shipped conf documents a Verizon-network example as comments, and
  IMS-SHANNON.md section 11 has the gated runbook.

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

* omamobile-modem-sit 0.3.23: the IMS setup carries the IMS profile's APN types

Stock's setup builder copies the APN's whole supported-type bitmask into
the request (0xf1); for Verizon's IMS APN that is ims|ia (0x140), where
ours sent IMS alone (0x40). The modem matches setups against its
modem-cognitive profiles, and the ia bit marks the attach APN, so this
is the one byte left where our IMS setup differs from stock's. With a
[profiles] entry of the ims type for ims_apn, its bitmask is sent;
without one nothing changes.

IMS-SHANNON section 12 records the rest from libsitril: stock sends no
SET_INITIAL_ATTACH_APN for a modem-cognitive attach profile (so
attach_apn = none is its mode), the 0x0603 and 0x0613 layouts field by
field, that stock never uses CID 1 (its attach context) for a bearer of
its own, and a ranked list of further changes with a runbook.

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

* omamobile-modem-sit 0.3.24: IMS registers on Verizon's network: IMS first on CID 2, the internet on CID 3

Tested on the reference Pixel 7 Pro, 2026-11-03 02:00, Verizon-network
MVNO SIM, kernel 7.3.0-rc6-omamobile-g2219cc6cda77. The first IMS
registration on this phone: "state 2 (VoLTE registered), features 3",
then an SMS sent over IMS (AIMS_SEND_SMS accepted).

Stock's RIL keeps CID 1 for the modem's attach context and never sets a
bearer up on it; it sets the IMS bearer up first, on CID 2. On a network
that attaches on the IMS APN, sitd's internet setup on CID 1 replaced the
attach PDN, and the IMS bearer set up afterwards on CID 2 carried no
P-CSCF (every variant tried: attach APN IMS or none, IPv6 or IPv4v6,
P-CSCF requested, the carrier manifest, the ISIM's FQDN). With the IMS
bearer first on CID 2 the setup response carries three IPv6 P-CSCFs and
the modem's IMS stack registers within 2 s of ADD_PDN.

- [network] internet_cid (default 1, today's behaviour; 3 here): the
  CID of sitd's internet bearer. IMS stays on CID 2. paths() resolves
  any non-IMS CID to the internet record, so omamobile-sit-data (no
  configuration) keeps working, and its probe found rmnet2.
- [network] ims_first (default no): the IMS bearer and ADD_PDN before
  the internet bearer, as stock orders it; the internet comes up after
  the IMS setup whether or not IMS succeeded.
- The IMS setup also reads the P-CSCF from the data-call list entry when
  the setup response has none (the modem lists the attach bearer's PCO
  there on some firmware), and the setup carries the IMS profile's whole
  APN-type bitmask (ims|ia), as stock's does (0.3.23).

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

* NOTES: 2026-11-03, IMS registered and an SMS sent on a Verizon-network SIM

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

* omamobile-modem 0.1.13: the modem stack at boot, opt-in (omamobile-modem-boot.target)

Until 2026-11-03 the maintainer started the modem stack by hand every
boot: omamobile-modem, then omamobile-sitd, omamobile-sit data on and
omamobile-mmd. IMS registered on a Verizon-network SIM that night and an
SMS went out at 02:00, the condition set for starting it at boot.
Enabling the units one by one doesn't work: sitd Requires/After the
modem unit, which was Type=simple, so it ran while the CP was still
booting and exited ("CP is not ONLINE").

What changes, with nothing enabled by the package:

- omamobile-modem-boot.target is the one switch (systemctl enable; the
  next release enables it once the carrier configuration is automatic,
  derekross#373). It wants the four units; each unit's own After= keeps the
  order, a missing unit is simply not started, and DefaultDependencies=no
  keeps multi-user.target (and omamobile-boot-success after it) from
  waiting on a registration that can take minutes. No wants link of any
  kind is shipped, and test/all holds the package to that.
- omamobile-modem-inhibit.service holds a systemd-inhibit sleep:idle
  block, required by and ordered before the modem unit, refused a manual
  stop, so it lasts until the reboot: suspend with the modem on has
  never run on this phone. The start script refuses to load a driver
  until the lock shows in systemd-inhibit --list.
- omamobile-modem.service is Type=notify: ready once CPIF's ports exist
  and the profile's read-only check has passed, before the CP is powered
  on. The CP's ONLINE is waited for by the device's sitd drop-in.
- The bring-up latch (modem-bringup-started) is written and synced
  before the first modprobe, as CONTRIBUTING 3.4 asks, not after the
  drivers and the check as before; a check that refuses removes it
  again, so a refusal doesn't cost the next boot its modem.
- A second marker, modem-up, written by the watcher at ONLINE (date and
  boot id) and removed by the unit's ExecStopPost when it is this
  boot's: a boot that ends with the modem up and no stop, a hang or a
  reset, leaves it, and the next boot refuses until a human has looked,
  so a hang after ONLINE can't become a reset loop. Only under the unit
  (INVOCATION_ID): a start by hand would have nothing to remove it.
- Nothing restarts the modem in place; the units have no Restart=.

Tests: the script's order (refusals, the inhibitor, the latch, modprobe,
the check with its rm, READY, exec), both refusals and --stopped and
--retry run for real against scratch markers, the units' relations and
the no-wants-link rule, systemd-analyze verify on the three units.

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

* device-cheetah 0.1.41: sitd waits for the CP's ONLINE before it runs

omamobile-modem.service (0.1.13) is ready once CPIF's ports exist, before
cbd has booted the CP, 10-30 s more; a sitd started on that alone exits
("CP is not ONLINE", seen 2026-11-03 with both units started at once).
This device's sitd drop-in adds ExecStartPre=omamobile-modem-cp
wait-online 120, the profile's own cbd timeout: a CP that never comes up
fails sitd, and the data fallback and the Phone and Messages bridge,
ordered after it, stay down until the reboot. Nothing is enabled: the
opt-in is omamobile-modem-boot.target, and the test checks that no wants
link for it or the four units is shipped. 0.1.41 leaves 0.1.40 to derekross#372's
10-device-modem.conf in the same directory, which moves sitd's
Requires/After on the modem unit here; the two drop-ins are independent.

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

* MODEM-PLAN: M4.6, the gated runbook for the modem stack at boot

The one-switch form (omamobile-modem-boot.target, omamobile-modem 0.1.13,
device-cheetah 0.1.41) with its reasons: install and look (B0), enable
and reboot (B1), the chain in order with the inhibitor and the markers
(B2), data and the bridge with one SMS (B3), the second reboot that
proves the clean stop clears the modem-up marker (B4), and an optional
forced reset that proves the guard refuses (B5). Expect/pass, stop and
rollback per step; every reboot with the modem up costs one UFS pass.
The old M4.6 line, enabling the three units one by one, is marked
superseded: it started sitd before the CP was ONLINE.

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

---------

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
…on-network SIM) (derekross#388)

Calls, texts and mobile data ran on the reference phone on 2026-11-03:
VoLTE and SMS over IMS, registration in 3 s, data behind Wi-Fi. The cell
names what is still by hand (the APNs and carrier manifest until derekross#373,
the opt-in boot target, the earpiece needing stage media) and what is
unqualified (suspend with the modem up). Suspend stays WIP: its plan
moves the cell only after a day of use with auto-sleep on (P6).

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
… overlay, off by default (derekross#382)

* omamobile-modem 0.1.12: keep the modem's own NV writes in a per-phone overlay

The modem keeps the carrier profile it applies from the AP (0x4600 after
its 0x4602), its cell and band memory and its IMS state in NV, and asks
for a reset to load a new profile. With RAM copies of the backup that
are dropped at stop, the reboot that answers the reset throws the profile
away again, so IMS never gets its carrier settings and SMS and VoLTE
fail on networks that need them. Seeding NV from a stock boot isn't an
answer: users must never boot stock to make Linux work, and NV is per
phone, so nothing can be shipped.

The partitions stay exactly as protected as before: the ro=1 and
unmounted refusal, the RAM copies checked against the backup's
checksums, the stock salted checksum and the baseband guard are
unchanged. New is omamobile-modem-nv-overlay, per file because rfsd
keeps NV as files in the f2fs copies: at start, after the copies are
verified and before the stock checksum check, it lays the overlay in
/var/lib/omamobile/modem-nv-overlay (root, 0700) over them, only if
every file is on the allow-list (efs/nv_normal.bin with its salted MD5),
none is protected (nv_protected.*, efs_backup, identity- or
calibration-like names), the store matches its own checksums and it is
bound to the current modem-nv.sha256. Otherwise the overlay is set aside
with a journal line and the modem starts from the backup alone. The
modem's writes are captured after the CP power-off in the unit's stop
and every 30 minutes from a timer the unit pulls in, atomically (objects,
then MANIFEST by fsync and rename); writes to files off the allow-list
are logged and dropped. `omamobile-modem nv-overlay status|diff|capture|
reset` is the interface. Off until /etc/omamobile/modem-nv-overlay-enable
exists; MODEM-PLAN gets the design and the gated first hardware test,
AGENTS.md section 1 the rule.

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

* omamobile-modem 0.1.15: an unenabled NV overlay apply is a no-op, and the runbook points at main's modem-sit

Review of derekross#382. apply() computed the binding and scanned every file of
the three mounted copies, then wrote base.json and start.json under /run,
before it looked at the enable file, and profile_setup dies on a non-zero
exit; so "off" cost a read of the copies and two files per modem start on
every phone with the package. apply now returns 0 before any read or
write when /etc/omamobile/modem-nv-overlay-enable is absent. An enable
file created after the modem started therefore finds no base record for
that boot: capture and diff say so and exit 0 (nothing is kept until the
reboot) instead of failing on the missing base.json.

test/nv-overlay step 10 checks that an unenabled apply and capture leave
nothing under /run, and that a capture and a diff after a mid-boot enable
keep nothing and exit 0.

MODEM-PLAN: the runbook's "Before" asked for omamobile-modem-sit 0.3.14
from the modem-sit-attach-apn branch, which is long on main (0.3.28);
it now points there and at derekross#373's automatic path (0.3.29). The design's
"Start" bullet says that off returns before any read or write.

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

---------

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
…99: SIM setup with no APN to type (derekross#373)

* omamobile-modem-sit 0.3.12: the APNs from the SIM, and registration without one

A reseller SIM on Verizon's network needed "apn = vzwinternet" typed
into modem-sit.conf before sitd would start, and then registered only with
the IMS APN as the initial attach APN. A SIM should just work.

With [network] apn and attach_apn at "auto" (the new default; empty means
the same), sitd sends GET_IMSI once after the USIM is READY, keeps only the
MCC/MNC and looks them up in the project's apn-overrides.conf, then in the
system's mobile-broadband-provider-info (CC-PDDC, now a dependency). The
attach APN is an override's attach_apn, else a database APN typed "ia",
else the internet APN. The only override is Verizon's codes: internet
vzwinternet (Verizon's own page), attach ims (our capture on 2026-11-02).
A typed value always wins. Only the source is logged, never the IMSI, the
network code or an APN; status carries the APNs in use and the SIM's PIN1
state for the shell.

Without an APN sitd no longer stops before the radio: it registers, skips
the internet bearer and goes on to IMS, and reports data unavailable.

[data] roaming (default yes, the behaviour so far) drops the cellular route
while roaming; omamobile-sit-data reads it on every pass. The new
omamobile-sit-config, run through pkexec (polkit: the active user), changes
only apn, attach_apn and roaming, and restarts nothing: an APN applies at
the next start-up, which needs a fresh CP.

tools/sit-sim answers GET_IMSI with a made-up subscriber part and logs the
attach APN. Overlaps derekross#356/derekross#364/derekross#367 (0.3.9-0.3.11) in bringup.start(); the
attach_apn key matches derekross#356's line.

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

* omamobile-mmd 0.1.1: the APNs sitd's start-up used, not "auto"

With sitd 0.3.12 the config's APN can be "auto". The bearer's apn and
Modem3gpp.InitialEpsBearerSettings now show what sitd's status reports
(the internet APN and the attach APN), and fall back to the config's
values, with "auto" shown as no APN.

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

* omamobile-shell 0.2.93: a Mobile network page, and the SIM in setup

omamobile.mobilenetwork, opened from Setup > Mobile network (only where the
modem stack is) and the Mobile data tile's chevron: carrier, registration,
signal, Mobile data and Data roaming switches, the APN in use with a field
to type one, the attach APN under Advanced, and the SIM PIN lock. "No modem"
without the stack. omamobile-mobile-network reads sitd's public state, its
config and ModemManager, and changes settings through omamobile-sit-config
under pkexec; it never restarts the modem services, so an APN change offers
a restart of the phone.

omamobile-onboarding names the carrier and says mobile data is set up
automatically when a SIM is in and the stack runs; nothing to type.

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

* TELEPHONY-APPS-PLAN: 7.6, SIM setup with no APN to type

The design of the automatic APN and attach APN, the carrier database and
its licence, the Mobile network page, what is logged, and the phone checks.

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

* omamobile-modem-sit 0.3.12: Verizon's attach APN is vzwims, as captured

The override said "ims", which was never tried as an attach APN. The SIM on
Verizon's network registered on 2026-11-02 (20:26 and 20:35) with vzwims as
the attach APN and vzwinternet for internet, so the override, its citation,
the comments, the design notes and the tests now say vzwims.

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

* omamobile-modem-sit 0.3.29: say when GET_IMSI is sent, and an override's IMS CID is the override's fault

Review of derekross#373. MODEM-CLIENT.md's "no identity reads, but one" paragraph
and the apn comment in modem-sit.conf said GET_IMSI goes out when apn or
attach_apn is auto, from 0.3.12. choose_apn() sends it when any of apn,
attach_apn, ims_apn, ims_first or internet_cid is auto or empty, which
with the shipped defaults is every boot, and typing apn and attach_apn
alone still sends it for the bearer order; only typing all five reads no
IMSI. Both now say so, and that it landed in 0.3.29.

override_values() accepted internet_cid = 2 (the IMS bearer's CID), and
start() then stopped with a message blaming [network] internet_cid. The
override now refuses 2 itself, as it does 16: the value is left out, its
key is listed under 'refused', and choose_apn() logs that the project's
carrier override for this SIM had it, never the config and never the
network code. A test with such an override checks CID 1 and the message.

Also from the review: carrier_apn.py and omamobile-sit-config in
MODEM-CLIENT's module table, the [profiles] comment says the override's
profiles apply only when the SIM was read (not with all five keys typed),
and TELEPHONY-APPS-PLAN 7.6 names the versions after the merge with main
(shell 0.2.99; main's 0.3.28 is derekross#364's).

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

---------

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
…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>
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