Skip to content

mmsd-tng 2.6.4, omamobile-modem-sit, omamobile-mmd: picture messages on the Pixel 9a over the internet bearer - #380

Closed
W4HO-ham wants to merge 44 commits into
derekross:mainfrom
W4HO-ham:tegu-mms-apps-stack
Closed

W4HO-ham wants to merge 44 commits into
derekross:mainfrom
W4HO-ham:tegu-mms-apps-stack

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #378 (and through it #376, #374, #372, #371, #367 and #364); this PR's own changes are the top three commits.

Picture messages for the 9a, receive first. This is rebuilt without the dedicated MMS bearer (#375, closed), since #384 made the internet bearer's CID a setting and CID 3 is now the internet bearer on your Verizon setup.

  • sitd: an MMS notification is a WAP push, often in several parts, and only the first part carries the WAP port. Stored parts now keep their port (old partial records are migrated), and a joined binary message is delivered as data only when its port is the WAP push one. sitd's status for authorised clients also carries the internet bearer's device (the one omamobile-sit-data found), address and DNS. state.json doesn't.
  • mmd: the internet bearer gets that device as Interface, plus its address and the carrier's DNS in Ip4Config. Those are readable on the system bus, as with ModemManager. mmsd-tng binds to that device and resolves the MMSC through those servers, so MMS goes over cellular with Wi-Fi up, without touching the system's routes or DNS.
  • mmsd-tng 2.6.4 for aarch64, with three small patches and meson test in check(). Nothing is enabled and no carrier settings ship.

On the palmtop's carrier the MMS APN is the internet APN. On 2026-11-02 a second bearer on it took the IMS bearer down, which is why nothing is set up just for MMS. A carrier with a separate MMS APN isn't supported yet.

TELEPHONY-APPS-PLAN 1.7 has the attended runbook, receive first. Not yet run: the palmtop has been down since its overnight sleep test. The aarch64 build log with meson test and a phone-smoke report come with that run. Showing a picture in Messages needs the omatel apps' T3 changes.

Tests: tests/packages for omamobile-modem-sit (WAP join, migration, the internet report), omamobile-mmd (the bearer's device, address and DNS) and mmsd-tng, plus tools/pr-check.

@derekross

Copy link
Copy Markdown
Owner

Direction for this one is in my comment on #374, which covers #374, #375, #376, #378 and #380 together.

@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch 3 times, most recently from 911b873 to adbbfcb Compare November 3, 2026 13:23
@W4HO-ham W4HO-ham changed the title mmsd-tng 2.6.4, omamobile-modem-sit 0.3.22, omamobile-mmd 0.1.4: picture messages on the Pixel 9a mmsd-tng 2.6.4, omamobile-modem-sit, omamobile-mmd: picture messages on the Pixel 9a over the internet bearer Nov 3, 2026
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch from adbbfcb to 2865441 Compare November 3, 2026 14:04
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch 5 times, most recently from 66a5ec8 to 924cb6b Compare November 3, 2026 15:28
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
W4HO-ham force-pushed the tegu-mms-apps-stack branch 4 times, most recently from 8c1596a to 04dc240 Compare November 3, 2026 16:01
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch 2 times, most recently from c4133cc to a7bf43f Compare November 3, 2026 17:46
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch 2 times, most recently from c7826b2 to 04c49ab Compare November 3, 2026 21:22
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch 2 times, most recently from 0e58d5d to 190121d Compare November 4, 2026 02:55
…-tng

mmsd-tng fetches MMS over a ModemManager bearer whose APN is the MMS APN, binds to its Interface and resolves the MMSC through the DNS in its Ip4Config. Where the MMS APN is the internet APN, that's the internet bearer, so the bridge now gives it the device omamobile-sit-data found (rmnet0 until sitd knows) and, while data is up, its address and the carrier's DNS from sitd's status.
The FT AEC reference changes nothing for the built-in microphone, the modem mixer's ASP stays off during our calls, stock applies wideband tuning to narrowband voice, and stock runs a speaker compensation tuner we don't.
…t bearer

mmsd-tng 2.6.4 for aarch64 from upstream's tag, with four small patches (the own number when ModemManager exports none, a socket closed on a failed interface bind, modern libphonenumber linkage) and meson test in check(). Nothing is enabled and no carrier settings ship; the example config is the owner's to fill in.

TELEPHONY-APPS-PLAN 1.7 now says what's ready for MMS on the 9a, where the MMS APN is the internet APN and MMS goes over the internet bearer, and gives an attended runbook, receive first.
With the tuning confirmed and the DSP in its telephony mode, the echo still came back after a few seconds, and AoC Modem Mixer ASP Mode (block 19, where the tuning goes) read ASP_OFF during the calls. With tegu_aec on, the route now sets it to ASP_ON before the upload and restores it after the call. Not yet tried on a call.
… MMS received

mmsd-tng logged "Couldn't create IP config from dictionary: 'method not given'" for the bearer's empty Ip6Config. An empty config is now method 0 (unknown), as libmm-glib expects. TELEPHONY-APPS-PLAN records the first picture received on the palmtop over the internet bearer.
With the tuning sent before the streams, the far end heard no echo for 2-3 s and then the echo again, with ASP on and at stock's microphone gain alike (2026-11-03). The AoC starts its voice path at the playback start ("Start voice call" in the kernel log, after our upload), which may set it up afresh. The tuning now goes up after both streams have started, while the call sink is still muted; a failed upload closes the streams and keeps the sink muted as before. Not yet tried on a call.
@W4HO-ham
W4HO-ham force-pushed the tegu-mms-apps-stack branch from 3188d56 to 388eed8 Compare November 4, 2026 11:19
… reports its device

Before sitd had reported a device, the bridge named rmnet0. On the 7 Pro, with a different attach APN, rmnet0 can briefly be another bearer's device, so mmsd-tng could bind to the wrong one. MM itself leaves a bearer's interface empty until it has one.
@W4HO-ham

W4HO-ham commented Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

On your suggestion from #374: the bridge now leaves the internet bearer's Interface empty until sitd reports the device, the way MM leaves it before a bearer has one, rather than guessing rmnet0 (c1fc4a9). The bridge test checks it's empty at first and follows sitd's rmnet1 once reported. The mmd tests pass.

@derekross

Copy link
Copy Markdown
Owner

Thank you for c1fc4a9, @W4HO-ham. Leaving the bearer's Interface empty until sitd reports the device is just what I had in mind, and the test that follows it from empty to rmnet1 covers it. Nothing else from me while this is a draft. When the lower PRs settle, a rebase onto them will pick up #371's ExecCondition and #372's latest commit.

The commits under this pull request's own are on main now in their merged form (derekross#356 to derekross#372, derekross#590), so the result is today's main plus this pull request's own commits, replayed on it; only version files conflicted, and they keep main's numbers.
The commits under this pull request's own are on main now in their merged form (derekross#356 to derekross#372, derekross#590), so the result is today's main plus this pull request's own commits, replayed on it; only version files conflicted, and they keep main's numbers.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The aarch64 build log and meson test result for mmsd-tng, from this branch's head (0f6bdedf, today's main merged in), built natively on the Pixel 9a with makepkg -f as the palmtop's user, nothing installed from it. gcc 16.1.1, meson 1.12.1, libmm-glib 1.24.2, libphonenumber 9.0.43, protobuf 36.1, abseil-cpp 20260817.0, libsoup3 3.8.1, c-ares 1.34.9.

The source is fetched by the pinned checksum, the four patches apply, 33 of 33 targets build, and check() passes:

[33/33] Linking target mmsdtng
==> Starting check()...
1/4 mmsdtng:test wsp               OK              0.02s
2/4 mmsdtng:test mms               OK              0.03s
3/4 mmsdtng:test service providers OK              0.02s
4/4 mmsdtng:test phone utils       OK              0.03s

Ok:                4
Fail:              0

ok - pinned source, patches, aarch64 recipe and opt-in configuration
==> Finished making: mmsd-tng 2.6.4-1 (Wed 11 Nov 2026 06:59:22 PM MST)

Five compiler warnings, all in upstream's code: three times wsputil.c:191: assignment discards 'const' qualifier, and twice 'temp_number' may be used uninitialized through glib's g_free. The whole log is 258 lines; say if you want it attached.

…, and the echo still back after 2 s

The last two changes of this stack had no result in the plan. With ASP on (11-03) and with the tuning sent after the voice streams start (11-11, two calls from this head) the far end hears no echo for about 2 s and its own voice for the rest, as before them. The plan records both and says what to read during the next call.
…test

The commit before this one took a merge of main with the conflict in this file still marked; this resolves it.
# Conflicts:
#	packages/omamobile-device-raven/version
#	tests/all
…nt uplink

Read through four calls on 2026-11-12, the AoC's own log and the call's
mixer controls show nothing changing a few seconds in: the controls are
set once, both tuning uploads arrive and are answered, and the APMg3
processor is enabled. What the log does show is the uplink's samples
staying near zero for the first 5 s after each answer, with the owner
talking and, in one call, with the laptop counting aloud beside the
palmtop; after that the uplink carries both. So the seconds without echo
in the earlier results were not cancellation.

A call to a talking clock shows the echo with no listener: quiet uplink
during the ticks, loud samples during the announcements.

bringup/call-audio-watch.py is the read-only watcher (palmtop) and
call-levels.py reads its output (laptop).
@derekross

Copy link
Copy Markdown
Owner

Thank you for the build log. A native aarch64 build from the pinned source with all four patches applied, 33 of 33 targets and four of four meson test cases is what I asked for, and I checked that nothing under packages/mmsd-tng, omamobile-mmd or omamobile-modem-sit changed between the head you built and today's, so it stands. I also went through the package offline: the patch checksums match, the unit starts nothing by itself, the example config ships placeholders only, and the test holds all of that. The 11-03 receive in the plan, a picture fetched over rmnet0 with Wi-Fi up and without touching the system's routes or DNS, is the design working as intended.

It stays a draft for now, for two reasons that aren't about the MMS code:

  1. It sits on omamobile-modem-sit: opt-in 9a call tuning upload and earpiece audio #374, omamobile-modem-sit: a second start in the same boot gets data and IMS back #376 and omamobile-modem-sit 0.3.19, 0.3.20: the AoC's tuning acknowledgement, and its DSP in telephony mode #378 and carries all three, and the call-tuning pair is going to take a while yet. As far as I can see the picture-message work needs none of it. Would you be willing to bring it as its own pull request on main: the WAP-push change in sitd, the bearer's device, address and DNS in the bridge, and the mmsd-tng package? It would be a third of the size and could move on its own.
  2. The bridge and sitd changes reach the 7 Pro too (the bearer's Interface starts empty now, and the IP configs are new), so I owe it one attended run on my phone before it merges. That one is on me.

Two small things when you touch it next: the description still says the palmtop run hasn't happened and counts three patches where there are four; and omamobile-mmd changes here without a version change (I'll set the numbers at merge, but tell me if you'd rather bump it yourself in the split).

For the first publish of the package I'd like one line from the palmtop showing mmsd-tng installed from the built package and the user unit reaching the session bus on that install, since the 11-03 run was a hand build. And a question: are any of the four patches on their way upstream? The two behaviour ones look like fixes they'd want.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Done as you asked: the picture-message work is #697 now, on main by itself (the five commits that were this one's own, picked without a conflict; all three package suites pass there). The description there counts four patches, says what ran on the palmtop and what is still owed (the line from the installed package, this evening), and answers your question on upstream: none of the four has been sent yet, and I'll send the two behaviour ones. I'm closing this one in its favour; the build log stays here and #697 points at it.

@W4HO-ham W4HO-ham closed this Nov 12, 2026
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 13, 2026
…ream merge requests, the bridge's dependency

The patches are numbered 0001 to 0004, and the README says which two are
offered upstream (mmsd!133, mmsd!134), so the next version bump knows what
to drop; its paragraph on the AUR recipe is one sentence, and it points at
section 1.7. The plan says derekross#697 where it said derekross#380. omamobile-mmd depends
on the modem-sit that reports the bearer; the number is a placeholder for
the one set at merge.
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.

2 participants