Repository navigation
omamobile-modem 0.1.13, device-cheetah 0.1.41: the Pixel 7 Pro's modem stack at boot, opt-in (stacked on #384) - #386
Merged
Merged
Conversation
…, 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
…PN 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
…irst 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
…k SIM Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
…dem-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
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
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
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
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
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #384 (
modem-sit-stock-attach, sitd 0.3.24, merged into this branch first): this PR's own commits are the top three. Nothing here has run on a phone; the runbook below is for the maintainer.The Pixel 7 Pro's modem stack at boot, opt-in. Until tonight it was started by hand every boot:
omamobile-modem(cbd, rfsd, "CP ONLINE"), thenomamobile-sitd,omamobile-sit data onandomamobile-mmd; IMS registered and an SMS went out at 02:00, the condition set for this. Enabling the units one by one (the old M4.6 line) doesn't work: sitdRequires/Afterthe modem unit, which wasType=simple, so it ran while the CP was still booting and exited ("CP is not ONLINE").omamobile-modem0.1.13omamobile-modem-boot.target: the one switch,systemctl enable omamobile-modem-boot.targetthen reboot. ItWants=the four units (a missingomamobile-mmdis simply not started); each unit's ownAfter=keeps the order;DefaultDependencies=nokeepsmulti-user.target(andomamobile-boot-success, which runs after it) from waiting on a registration that can take minutes. No package ships a wants link, and the tests hold them to that. The next release enables it by default once the carrier configuration is automatic (omamobile-modem-sit 0.3.29, omamobile-mmd 0.1.2, omamobile-shell 0.2.99: SIM setup with no APN to type #373).omamobile-modem-inhibit.service:systemd-inhibit --what=sleep:idle --mode=block, required by and ordered before the modem unit,RefuseManualStop=yes, so it lasts until the reboot (stopping the modem unit doesn't stop it:Requires=is one way). The start script refuses to load a driver until the lock shows insystemd-inhibit --list(aType=simpleunit is "started" at its fork).omamobile-modem.serviceisType=notify: READY once CPIF's ports exist and the profile's read-only check has passed, before the CP is powered on, so sitd'sConditionPathExists=/dev/umts_ipc0andAfter=see the ports. The CP's ONLINE is waited for by the device drop-in below.modprobe(CONTRIBUTING 3.4); until now it was written after the drivers and the check. A check that refuses removes it again: a refusal is not a hang./var/lib/omamobile/modem-up: written by the watcher at ONLINE (date and boot id), removed byExecStopPost=omamobile-modem-start --stoppedwhen it is this boot's. A boot that ends with the modem up and no stop (a hang, a reset) leaves it, and the next boot refuses with "ended without a clean stop" until a human has looked: a hang after ONLINE can't become a reset loop. A refused start'sExecStopPostsees another boot's marker and keeps it. The marker is only kept under the unit (INVOCATION_ID): a hand-run--retrywould have nothing to remove it. Recovery:omamobile-modem-start --retry, orrmthe marker andsystemctl start omamobile-modem.Restart=noon the modem and sitd; sit-data and mmd restart only themselves.omamobile-device-cheetah0.1.41omamobile-sitd.service.d/20-cp-online.conf:ExecStartPre=/usr/lib/omamobile-vendor/omamobile-modem-cp wait-online 120(the profile's cbd timeout). A CP that never comes up fails sitd, and sit-data and mmd, ordered after it, stay down. 0.1.41 leaves 0.1.40 to omamobile-device-tegu 0.2.12: start the Pixel 9a's modem and phone service at boot, opt-in #372's10-device-modem.confin the same directory (it moves sitd'sRequires/Afteron the modem unit into the device policy); the two files are independent, butversion,PKGBUILDandtest/allwill conflict textually with that stack, and whichever lands second resolves it.omamobile-sit-dataandomamobile-mmd: untouched. TheirWantedBy=omamobile-sitd.serviceinstall sections stay for the by-hand path (omamobile-sit data onissystemctl start omamobile-sit-data); at boot the target wants them directly, and theirAfter=omamobile-sitd.serviceputs them behind sitd's READY (registered). Whether the phone has sit-data's own wants link enabled isn't known from here; with the target it doesn't matter.Docs: MODEM-PLAN M4.6 is the gated runbook (install and look; enable and reboot; the chain, the inhibitor and the markers; data and one SMS; a second reboot proving the clean stop clears the marker; an optional forced reset proving the guard refuses), with Expect/Pass, stop and rollback per step and the UFS pass per reboot. AGENTS.md's modem bullet names the second marker.
Not settled offline
omamobile-modemruns, so it gets the inhibitor,Type=notifyand the markers too, but it has no sitd drop-in yet: it would need its own20-cp-online.confbefore enabling the target there.omamobile-sitdagainst the (condition-skipped) generic modem unit; tegu uses its ownomamobile-tegu-modem-boot(omamobile-device-tegu 0.2.12: start the Pixel 9a's modem and phone service at boot, opt-in #372) and shouldn't enable this target.systemd-notify --readyfrom the script relies onNotifyAccess=all; first boot shows whether READY arrives before sitd's condition is checked (B2's journal).Tests:
tests/packages omamobile-modem omamobile-device-cheetah omamobile-modem-sit omamobile-mmd,tests/all,tools/pr-check origin/main; shellcheck isn't installed here (CI runs it in the package tests).🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d