Repository navigation
Conversation
911b873 to
adbbfcb
Compare
adbbfcb to
2865441
Compare
66a5ec8 to
924cb6b
Compare
…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>
8c1596a to
04dc240
Compare
c4133cc to
a7bf43f
Compare
c7826b2 to
04c49ab
Compare
0e58d5d to
190121d
Compare
…-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.
3188d56 to
388eed8
Compare
… 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.
|
On your suggestion from #374: the bridge now leaves the internet bearer's |
|
Thank you for c1fc4a9, @W4HO-ham. Leaving the bearer's |
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.
# Conflicts: # tests/all
# Conflicts: # tests/all
|
The aarch64 build log and The source is fetched by the pinned checksum, the four patches apply, 33 of 33 targets build, and Five compiler warnings, all in upstream's code: three times |
…, 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).
|
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 It stays a draft for now, for two reasons that aren't about the MMS code:
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 For the first publish of the package I'd like one line from the palmtop showing |
|
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. |
…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.
…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>
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.
omamobile-sit-datafound), address and DNS.state.jsondoesn't.Interface, plus its address and the carrier's DNS inIp4Config. 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.meson testincheck(). 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 testand a phone-smoke report come with that run. Showing a picture in Messages needs the omatel apps' T3 changes.Tests:
tests/packagesfor omamobile-modem-sit (WAP join, migration, the internet report), omamobile-mmd (the bearer's device, address and DNS) and mmsd-tng, plustools/pr-check.