Skip to content

omamobile-modem-sit 0.3.20, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, show the modem in the shell - #381

Merged
derekross merged 11 commits into
mainfrom
modem-sit-attach-apn
Nov 3, 2026
Merged

derekross merged 11 commits into
mainfrom
modem-sit-attach-apn

Conversation

@derekross

Copy link
Copy Markdown
Owner

Stacks on #356 (W4HO-ham's 0.3.5-0.3.9 data-call fixes): this branch starts from #356's head, so merge #356 first. #364 (0.3.10) and #373 (0.3.12, sim-setup) also touch the bring-up and need renumbering or a hand merge after this.

Tested on the reference Pixel 7 Pro on 2026-11-02, with a Verizon-network MVNO SIM:

Before After
Never registered (internet APN as attach APN) Registers on the IMS APN
53 s to 10+ min to register 3.3 s after radio on
Data bearer on the wrong rmnet omamobile-sit-data finds the carrying device; ping and HTTPS over cellular
Mobile tile "No modem", airplane icon Tile and bar show LTE and signal (with #377)
IMS: no P-CSCF, no registration Unchanged: needs the carrier profile to persist in NV (separate PR)

What changed is in the commit message. The new settings (attach_apn, [profiles], ims_pcscf_required, carrier_manifest) all default to today's behaviour, so other carriers are unchanged.

device/cheetah/MODEM-PROVIDER-PROFILES.md records stock's two carrier databases, its order of requests and the APNs for this SIM type, from the owner's factory image. It has field names and APN names only, no Google file contents.

Checks: packages/omamobile-modem-sit/test/all, packages/omamobile-mmd/test/all (one skip: the ModemManager XML isn't installed here) and tools/pr-check origin/main pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

W4HO-ham and others added 9 commits November 2, 2026 15:16
…stock

The palmtop's first SIM test registered on LTE and then got status 36 (REGULAR_DEACTIVATION) for the internet bearer, twice. Our setup differed from stock's in the PDU session ID: sitd reserved one with ALLOC_PDU_SESSION and sent it at 0xf6, but Android allocates one only for a bearer over Wi-Fi (IWLAN), and the 9a's own protocol library copies the framework's value, 0 on LTE and NR, into the request. Both bearers now send 0 and the modem picks the ID; an older ownership record with an allocated ID is still released on deactivation.

sit-sim logs the ID it receives and the simulator test checks for 0 with no ALLOC or REL. The 0xf1 comment now says what stock puts there: the APN-type bitmap, not an MTU. It still sends zero.
The modem reports Android DataFailCause numbers, which stock's RIL passes through unchanged. A refused APN is 27 or 33. 36 is REGULAR_DEACTIVATION. The 9a's runbook pointed at the APN for the status it got on 2026-11-02.
…r it, and snapshot around the NR change

A refused SETUP_DATA_CALL answered "36" three times on the palmtop on 2026-11-02 and nothing else was kept: the record beyond its first five bytes was dropped, and the two or three messages the modem sent about a second later were lost because sitd had already closed the channel. Now the whole record goes to a private file in RAM, the channel stays open five seconds while each indication is logged by name and length (a data-call list change decoded to status, CID, active and PDP type), and the registration state and data-call count are logged before and after the NR change, so the next refusal says more than a number.

The probe's first request waits 20 s: the CP answered GET_SIM_STATUS 9.4 s after ONLINE.
…L, as stock

The 983-byte setup request carries the APN's supported-types bitmap as a u32 at 0xf1: the Pixel 9a's stock builder copies ApnSetting's mask there (vendor.radio.base ApnSetting::SetSupportedTypesBitmask, member +0x160; the stream library's builders write it at 0xf1). Ours sent 0 there, under a comment calling it an MTU, and the 9a's modem answered every internet setup with status 36 (REGULAR_DEACTIVATION) on 2026-11-02, three times, with the session ID fixed in between. The internet bearer now sends DEFAULT (1) and the IMS bearer IMS (0x40).

The attach request copies the setup's first 233 bytes, so it keeps bytes 0xf1 to 0xf4 zero explicitly: stock's 251-byte attach builder leaves them zero. Its roaming PDP type at 0xf8 is now named for what it is.
…sion before the setup

On 2026-11-02 five setups in a row were answered with status 36 within 150 ms, each followed within a second by three IND_REG_FAILED, two IND_NTW_STATE_CHANGED and an empty data-call list: the modem was re-attaching around the request, whatever its cause. The setup now waits until the modem has sent nothing for three seconds after the data permission (at most twenty), logging each indication by name and keeping the raw packets in a private file for decoding, then reads the registration again and waits up to a minute for it if it was lost, and only then sends the setup.
Six CP starts over six boots, all attended: the SIM read, LTE registration every time, five data requests refused with status 36, then, with the RIL letting the modem settle after the data permission, the internet and IMS bearers up, mobile data over rmnet0, and texts both ways. The record is under the runbook; the Modem cell stays WIP with what works on the owner's kernel.
…each the service

0.3.6 and 0.3.8 read indications themselves while the setup waited and after a refusal, and only logged and kept them: an SMS arriving in that window got neither stored nor acknowledged. They're now handed to the service's own handler as well, as everywhere else, with a test for an SMS in both windows. MODEM-PLAN now says what the run showed and no more: the three IND_REG_FAILED were LTE cause 10 (implicitly detached), whether the data permission triggers it isn't proven, and only byte 132 of the refused record is the IPC extension version.
…s network in seconds, carry data, and show the modem in the shell

Tested on a Pixel 7 Pro with a Verizon-network MVNO SIM on 2026-11-02. On top of #356 (0.3.9).

- [network] attach_apn: some networks attach only on their IMS APN.
  Verizon's never registered while the internet APN was the attach APN,
  and registered once the IMS APN was. Empty means "same as apn".
- [profiles]: every modem-managed data profile in stock's
  SET_DATA_PROFILE layout (IDs, APN-type bits, PDP types), so the modem
  has the carrier's full table before radio on.
- Stock's order: attach APN, profiles and NR mode, then radio on once
  with no AT+CFUN cycle. NR mode is set right after radio on when the
  modem refuses it with the radio off (error 2). Registration went from
  53 s to 10+ min down to 3.3 s after radio on.
- omamobile-sit-data finds the rmnet device that carries the bearer by
  probing; it isn't rmnet<CID-1> once the attach is on another APN. A stop
  during the probe puts every candidate back.
- /run/omamobile-sit stays 0710 root:wheel (SIT clients no longer chmod
  it to 0700), so the shell's tile can read state.json again.
- IMS: P-CSCF extension decoding, the P-CSCF request in an IMS-APN
  attach, and [network] ims_pcscf_required (yes keeps today's behaviour).
- [network] carrier_manifest: answers the modem's own carrier-config
  request (0x4602) with one OEM_SET_CARRIER_CONFIG_MANIFEST naming a
  manifest from the owner's image, and holds the IMS stack start until
  the modem's status. Empty by default; nothing reads SIM identities.
  extract-vendor-chroot copies vendor/firmware/carrierconfig for it.
- Logging: runtime registration changes, IND_REG_FAILED causes,
  carrier-config status, IND_PHONE_RESET bytes and registration time.
- Radio state 10 (Android's RadioState ON) is "on", and the LTE signal
  comes from IND_SIGNAL_STRENGTH. omamobile-mmd exports both, so the
  Mobile tile and the bar show the network.

IMS still doesn't register without the carrier profile persisting in
the modem's NV; that is the NV overlay's PR.
device/cheetah/MODEM-PROVIDER-PROFILES.md records stock's databases,
order and APNs for this SIM type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
…ISIM's P-CSCF, IMS failure logging

Tested on the reference Pixel 7 Pro on 2026-11-02 (Verizon-network SIM).

- With carrier_manifest set, the radio goes on only after the modem's
  carrier config status (0x4601), as stock orders it. Before, the status
  came 11 s after radio on and the modem stopped searching; now it
  registers in 3.3 s with the profile in place.
- [network] ims_pcscf_from_isim (default yes): when the IMS bearer's PCO
  has no P-CSCF, read the ISIM's EF_PCSCF (6F09) through SIM_IO. The
  transport allows SIM_IO only for GET RESPONSE / READ RECORD of that one
  file on the ISIM AID; nothing else of the ISIM is read or logged. FQDN
  entries are resolved over the IMS bearer, then the host resolver; IPv6
  results fill ADD_PDN's list. On this network the entry is an FQDN that
  resolves only on the carrier's IMS DNS, which the host can't reach (the
  modem owns that bearer), so IMS still doesn't register.
- omamobile-sitd.service also allows AF_INET/AF_INET6, for that lookup.
- IND_AIMS_REGISTRATION is logged (state, features, status, the stack's
  reason text; never the URI).
- NR mode is set right after radio on when the modem refuses it with the
  radio off (error 2).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross derekross changed the title omamobile-modem-sit 0.3.16, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, show the modem in the shell omamobile-modem-sit 0.3.19, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, show the modem in the shell Nov 3, 2026
… IMS-SHANNON.md

From a read of stock's IMS service (ShannonIms) on the owner's image,
recorded in device/cheetah/IMS-SHANNON.md (request layouts, the order of
AIMS requests, the registration state and reason values):

- The IMS bearer takes the home IP type of the [profiles] entry typed ims
  for ims_apn (IPv4v6 on Verizon's network: 0xda=3, 0xdb=3), else IPv6
  as before.
- ADD_PDN carries IP type 3, the IPv4 address, IPv4 P-CSCFs and IPv4 DNS
  for an IPv4v6 bearer; an IPv6-only bearer gives the same bytes as 0.3.19.
- Stock's OMA-DM hidden-menu item goes out before ADD_PDN.
- The ISIM's P-CSCF FQDN is also resolved through the internet bearer's
  DNS, as stock resolves it on the default network.
- Registration indications log the state and reason names.

Stock never sends ADD_PDN for IMS without a P-CSCF, and status 5 is
IMS_SERVICE_REGISTER_FAIL, its answer to an empty list. On the 7 Pro
(2026-11-03) the IPv4v6 IMS bearer still carried no P-CSCF and the
ISIM's FQDN didn't resolve on the internet bearer's DNS, so with
ims_pcscf_required = yes sitd now skips IMS like stock. Whether the
line is provisioned for VoLTE is the open question.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
@derekross derekross changed the title omamobile-modem-sit 0.3.19, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, show the modem in the shell omamobile-modem-sit 0.3.20, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, show the modem in the shell Nov 3, 2026
# Conflicts:
#	packages/omamobile-modem-sit/lib/bringup.py
#	packages/omamobile-modem-sit/lib/data_call.py
#	packages/omamobile-modem-sit/test/test_data_call.py
#	packages/omamobile-modem-sit/version
@derekross
derekross merged commit 9ae9e7b into main Nov 3, 2026
2 checks passed
@derekross
derekross deleted the modem-sit-attach-apn branch November 3, 2026 05:29
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…t rmnet0 and rmnet2

derekross#381 found that the internet bearer isn't always on rmnet<CID - 1>, and records the device omamobile-sit-data finds in /run/omamobile-sit/data-interface. sitd's internet address report and the bridge's internet bearer now use that device (nothing is exported before it's found), and the bridge takes the MMS bearer's device from sitd's MMS status. A dedicated MMS bearer's device is [mms] interface, rmnet2 by default, since probing it the way the internet one is found needs an answer that an MMSC needn't give.

The note that the address never reaches a world-readable copy was wrong once the bridge publishes it: any client on the system bus can read a bearer's Ip4Config, as with ModemManager. It now says that. The shared-APN test uses a neutral placeholder APN.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 3, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 4, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 9, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 9, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 9, 2026
…dem latch until a clean shutdown, and the 9a's screen-on at start

The latch was cleared as soon as the CP reached ONLINE, so a hang or reset after that would have started the modem again at every boot. It now stays until the modem profile's unit stops cleanly at shutdown (an ExecStopPost that runs only when the unit's result is success), and the next boot refuses while it's there, as TELEPHONY-PLAN 2.4 plans. The start also refuses a pcie_gs201_cp already loaded without allow_hw, as omamobile-modem-start does, and waits with wait-online instead of reading the state once a second.

The screen-on that makes the 9a's modem send signal reports is now set only by tegu's sitd drop-in (OMAMOBILE_SIT_SCREEN_ON_AT_START), so the 7 Pro's start-up is unchanged; derekross#381 already decodes the reports.

The README and the boot unit give the order, the preconditions (slot B marked successful, a kernel with linux-omarchy-mobile#172, the charger for the first boots) and the rollback; the test checks the latch is on disk before any driver loads, that it stays past ONLINE, and the allow_hw refusal.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s network in seconds, carry data, show the modem in the shell (derekross#381)

* omamobile-modem-sit 0.3.5: no PDU session ID on cellular bearers, as stock

The palmtop's first SIM test registered on LTE and then got status 36 (REGULAR_DEACTIVATION) for the internet bearer, twice. Our setup differed from stock's in the PDU session ID: sitd reserved one with ALLOC_PDU_SESSION and sent it at 0xf6, but Android allocates one only for a bearer over Wi-Fi (IWLAN), and the 9a's own protocol library copies the framework's value, 0 on LTE and NR, into the request. Both bearers now send 0 and the modem picks the ID; an older ownership record with an allocated ID is still released on deactivation.

sit-sim logs the ID it receives and the simulator test checks for 0 with no ALLOC or REL. The 0xf1 comment now says what stock puts there: the APN-type bitmap, not an MTU. It still sends zero.

* MODEM-PLAN: status 36 is a regular deactivation, not a refused APN

The modem reports Android DataFailCause numbers, which stock's RIL passes through unchanged. A refused APN is 27 or 33. 36 is REGULAR_DEACTIVATION. The 9a's runbook pointed at the APN for the status it got on 2026-11-02.

* omamobile-modem-sit 0.3.6: keep a refused setup's record, listen after it, and snapshot around the NR change

A refused SETUP_DATA_CALL answered "36" three times on the palmtop on 2026-11-02 and nothing else was kept: the record beyond its first five bytes was dropped, and the two or three messages the modem sent about a second later were lost because sitd had already closed the channel. Now the whole record goes to a private file in RAM, the channel stays open five seconds while each indication is logged by name and length (a data-call list change decoded to status, CID, active and PDP type), and the registration state and data-call count are logged before and after the NR change, so the next refusal says more than a number.

The probe's first request waits 20 s: the CP answered GET_SIM_STATUS 9.4 s after ONLINE.

* omamobile-modem-sit 0.3.7: send the APN-type bitmap in SETUP_DATA_CALL, as stock

The 983-byte setup request carries the APN's supported-types bitmap as a u32 at 0xf1: the Pixel 9a's stock builder copies ApnSetting's mask there (vendor.radio.base ApnSetting::SetSupportedTypesBitmask, member +0x160; the stream library's builders write it at 0xf1). Ours sent 0 there, under a comment calling it an MTU, and the 9a's modem answered every internet setup with status 36 (REGULAR_DEACTIVATION) on 2026-11-02, three times, with the session ID fixed in between. The internet bearer now sends DEFAULT (1) and the IMS bearer IMS (0x40).

The attach request copies the setup's first 233 bytes, so it keeps bytes 0xf1 to 0xf4 zero explicitly: stock's 251-byte attach builder leaves them zero. Its roaming PDP type at 0xf8 is now named for what it is.

* omamobile-modem-sit 0.3.8: let the modem settle after the data permission before the setup

On 2026-11-02 five setups in a row were answered with status 36 within 150 ms, each followed within a second by three IND_REG_FAILED, two IND_NTW_STATE_CHANGED and an empty data-call list: the modem was re-attaching around the request, whatever its cause. The setup now waits until the modem has sent nothing for three seconds after the data permission (at most twenty), logging each indication by name and keeping the raw packets in a private file for decoding, then reads the registration again and waits up to a minute for it if it was lost, and only then sends the setup.

* device/tegu MODEM-PLAN, DEVICES: the SIM test passed on 2026-11-02

Six CP starts over six boots, all attended: the SIM read, LTE registration every time, five data requests refused with status 36, then, with the RIL letting the modem settle after the data permission, the internet and IMS bearers up, mobile data over rmnet0, and texts both ways. The record is under the runbook; the Modem cell stays WIP with what works on the owner's kernel.

* omamobile-modem-sit 0.3.9: indications seen during the setup's wait reach the service

0.3.6 and 0.3.8 read indications themselves while the setup waited and after a refusal, and only logged and kept them: an SMS arriving in that window got neither stored nor acknowledged. They're now handed to the service's own handler as well, as everywhere else, with a test for an SMS in both windows. MODEM-PLAN now says what the run showed and no more: the three IND_REG_FAILED were LTE cause 10 (implicitly detached), whether the data permission triggers it isn't proven, and only byte 132 of the refused record is the IPC extension version.

* omamobile-modem-sit 0.3.16, omamobile-mmd 0.1.1: register on Verizon's network in seconds, carry data, and show the modem in the shell

Tested on a Pixel 7 Pro with a Verizon-network MVNO SIM on 2026-11-02. On top of derekross#356 (0.3.9).

- [network] attach_apn: some networks attach only on their IMS APN.
  Verizon's never registered while the internet APN was the attach APN,
  and registered once the IMS APN was. Empty means "same as apn".
- [profiles]: every modem-managed data profile in stock's
  SET_DATA_PROFILE layout (IDs, APN-type bits, PDP types), so the modem
  has the carrier's full table before radio on.
- Stock's order: attach APN, profiles and NR mode, then radio on once
  with no AT+CFUN cycle. NR mode is set right after radio on when the
  modem refuses it with the radio off (error 2). Registration went from
  53 s to 10+ min down to 3.3 s after radio on.
- omamobile-sit-data finds the rmnet device that carries the bearer by
  probing; it isn't rmnet<CID-1> once the attach is on another APN. A stop
  during the probe puts every candidate back.
- /run/omamobile-sit stays 0710 root:wheel (SIT clients no longer chmod
  it to 0700), so the shell's tile can read state.json again.
- IMS: P-CSCF extension decoding, the P-CSCF request in an IMS-APN
  attach, and [network] ims_pcscf_required (yes keeps today's behaviour).
- [network] carrier_manifest: answers the modem's own carrier-config
  request (0x4602) with one OEM_SET_CARRIER_CONFIG_MANIFEST naming a
  manifest from the owner's image, and holds the IMS stack start until
  the modem's status. Empty by default; nothing reads SIM identities.
  extract-vendor-chroot copies vendor/firmware/carrierconfig for it.
- Logging: runtime registration changes, IND_REG_FAILED causes,
  carrier-config status, IND_PHONE_RESET bytes and registration time.
- Radio state 10 (Android's RadioState ON) is "on", and the LTE signal
  comes from IND_SIGNAL_STRENGTH. omamobile-mmd exports both, so the
  Mobile tile and the bar show the network.

IMS still doesn't register without the carrier profile persisting in
the modem's NV; that is the NV overlay's PR.
device/cheetah/MODEM-PROVIDER-PROFILES.md records stock's databases,
order and APNs for this SIM type.

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

* omamobile-modem-sit 0.3.19: the carrier profile before radio on, the ISIM's P-CSCF, IMS failure logging

Tested on the reference Pixel 7 Pro on 2026-11-02 (Verizon-network SIM).

- With carrier_manifest set, the radio goes on only after the modem's
  carrier config status (0x4601), as stock orders it. Before, the status
  came 11 s after radio on and the modem stopped searching; now it
  registers in 3.3 s with the profile in place.
- [network] ims_pcscf_from_isim (default yes): when the IMS bearer's PCO
  has no P-CSCF, read the ISIM's EF_PCSCF (6F09) through SIM_IO. The
  transport allows SIM_IO only for GET RESPONSE / READ RECORD of that one
  file on the ISIM AID; nothing else of the ISIM is read or logged. FQDN
  entries are resolved over the IMS bearer, then the host resolver; IPv6
  results fill ADD_PDN's list. On this network the entry is an FQDN that
  resolves only on the carrier's IMS DNS, which the host can't reach (the
  modem owns that bearer), so IMS still doesn't register.
- omamobile-sitd.service also allows AF_INET/AF_INET6, for that lookup.
- IND_AIMS_REGISTRATION is logged (state, features, status, the stack's
  reason text; never the URI).
- NR mode is set right after radio on when the modem refuses it with the
  radio off (error 2).

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

* omamobile-modem-sit 0.3.20: request the IMS bearer as stock does, and IMS-SHANNON.md

From a read of stock's IMS service (ShannonIms) on the owner's image,
recorded in device/cheetah/IMS-SHANNON.md (request layouts, the order of
AIMS requests, the registration state and reason values):

- The IMS bearer takes the home IP type of the [profiles] entry typed ims
  for ims_apn (IPv4v6 on Verizon's network: 0xda=3, 0xdb=3), else IPv6
  as before.
- ADD_PDN carries IP type 3, the IPv4 address, IPv4 P-CSCFs and IPv4 DNS
  for an IPv4v6 bearer; an IPv6-only bearer gives the same bytes as 0.3.19.
- Stock's OMA-DM hidden-menu item goes out before ADD_PDN.
- The ISIM's P-CSCF FQDN is also resolved through the internet bearer's
  DNS, as stock resolves it on the default network.
- Registration indications log the state and reason names.

Stock never sends ADD_PDN for IMS without a P-CSCF, and status 5 is
IMS_SERVICE_REGISTER_FAIL, its answer to an empty list. On the 7 Pro
(2026-11-03) the IPv4v6 IMS bearer still carried no P-CSCF and the
ISIM's FQDN didn't resolve on the internet bearer's DNS, so with
ims_pcscf_required = yes sitd now skips IMS like stock. Whether the
line is provisioned for VoLTE is the open question.

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

---------

Co-authored-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <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.

2 participants