Skip to content

DEVICES: the Pixel 7 Pro's modem works (calls, texts, data on a Verizon-network SIM) - #388

Merged
derekross merged 1 commit into
mainfrom
devices-modem-20261103
Nov 3, 2026
Merged

derekross merged 1 commit into
mainfrom
devices-modem-20261103

Conversation

@derekross

Copy link
Copy Markdown
Owner

The Modem cell and its detail row for the Pixel 7 Pro, after the night of 2026-11-02/03: calls, texts and mobile data on a Verizon-network SIM (VoLTE and SMS over IMS, registration in 3 s). The row names what is still by hand (APNs and the carrier manifest until #373, the opt-in boot target from #386, the earpiece route needing stage media) and what is unqualified (suspend with the modem up).

Suspend stays WIP on purpose: SUSPEND-PLAN says the cell moves to "works" only after P6 (a day of use with auto-sleep on) and a release that turns auto-sleep on by default; neither has happened.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

…on-network SIM)

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).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross
derekross merged commit 0f43776 into main Nov 3, 2026
2 checks passed
@derekross
derekross deleted the devices-modem-20261103 branch November 3, 2026 08:11
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
…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>
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