Repository navigation
omamobile-telephony-tegu: Phone and Messages on the Pixel 9a through omamobile-mmd (stacked on #367 and #363) - #371
Conversation
|
Ran the packaged path on the palmtop (2026-11-03): |
|
Thanks. Splitting sitd's modem dependency into device drop-ins, with a virtual that forces them along, keeps the 7 Pro's unit exactly as it is, and I appreciate the care in the attach helper. While the stack below lands: the 9a plan's header still says no phone contact happened, while your comment reports a full run. Could you record that run with |
|
Rebased onto main and #367. The radio-state and signal-decode commits are dropped, since #381 has both. The plan (your notes on #370) now opens with what ran on 2026-11-02: kernel, versions, steps 1 to 6, and that opening Messages didn't start the agent. It cites #363 instead of the branch, and the task-report lines are gone. On which start stays: both, for different cases. #372's boot unit is for daily use (modem, sitd and mmd once the CP is ONLINE), and the attach helper is for a modem and sitd started by hand during bring-up and tests, where nothing should start the modem for you; the plan says so. The |
91ea0ad to
95cc4ff
Compare
7b563a6 to
fedc908
Compare
fedc908 to
5fa18a6
Compare
|
Thanks for recording the run and for the clear answer on the two ways to start the bridge. The split of sitd's modem dependency into device drop-ins checks out: on the 7 Pro the base unit plus cheetah's drop-in gives exactly today's Before it comes out of draft:
Two small ones: the plan's new line dates the removal of mmd's |
|
Thanks. The plan and the package README now put the Your question: no, #372's boot path hasn't run with |
87c356d to
abc4572
Compare
|
Your question found a real bug, thanks. I ran #372's boot path with this package installed, on the palmtop (2026-11-03, Two causes:
Neither pulls the RIL or the CP into a start, so the check now allows both, and only those (657e7a7). It still refuses sitd wanting anything else and the bridge wanting anything at all. A Re-run on the palmtop with the fixed helper and drop-in: The |
657e7a7 to
5571f3a
Compare
|
Thanks for running the boot path with this package installed. It caught a real problem: allowing exactly the bridge's own One thing in the new commit doesn't do what it says. systemd applies On my side, as before: #416 shipped device-cheetah 0.1.44 and modem-sit 0.3.30, which this branch's files now equal. At merge I'll give device-cheetah, device-raven, device-tegu, modem-sit and mmd the next free numbers after #403 and #367 (#407 has taken device-tegu 0.2.9 since). I'll also bring the new package's A question from the smoke report: that boot shows no sound card and no sensor proxy, while the §2.7 boot in #372 had both. Was the AoC down that time? |
|
I reproduced the refusal loop on systemd 262 and prepared the For the earlier smoke report: it shows neither a sound card nor a sensor proxy, and also no Wi-Fi interface. The saved boot excerpts don't establish whether AoC was down or why. I'll check the journal from that boot if it is still available, rather than guess. |
|
I checked the palmtop's journal for the November 3, 19:55 MST smoke run. That boot is no longer retained; the oldest available journal begins at 20:37 MST. I can't tell from the remaining evidence whether AoC was down on that run. |
|
The check is now It hasn't run on the palmtop yet, because the palmtop is in a suspend series. I'll do the boot path with it when that's done. |
|
I installed the package from 26751a9 on the palmtop. The installed files match that head, the package integrity check is clean, and the modem, sitd and bridge stayed active. The real The PR currently conflicts with main in |
|
I ran the boot-path check with 26751a9 installed. During an orderly reboot the modem reported CP OFFLINE before shutdown. On the next boot the modem came ONLINE, sitd reached LTE and IMS voice/SMS registration, and the bridge started and exported the ready SIM. Its service check passed, with zero bridge restarts. The protected-partition backup check matched before and after. The required smoke checks passed, but the full smoke was not clean: the saved kernel journal has the same Wi-Fi invalid-chanspec warning seen on the preceding boot and 46 AoC mailbox queue-full messages (45 on the preceding boot). The Wi-Fi warning is covered by kernel #191. The boot-reason field says watchdog; the matching archived shutdown log shows systemd's requested reboot and the kernel reaching |
|
Thank you, @W4HO-ham. When you're happy with it, please take this out of draft. Everything else is on my side at merge. I'll resolve the device-raven version conflict you spotted and give every package here the next free number. I'll also raise |
|
Thanks. Both paths have run on the palmtop and the tests pass, so I've taken it out of draft. Versions, depends and the squash message are yours at merge, as you said. |
|
Thank you, @W4HO-ham, and thanks for taking it out of draft. I have nothing |
26751a9 to
f5b6737
Compare
Trace the existing app, session agent, ModemManager-compatible bridge and sitd path. Record the tegu installation and unit prerequisites still missing on main, and an attended bridge-only test that preserves the running modem stack. Document the passing offline bridge and apps package suites, activation and audio limits, and the eventual board-specific image integration.
Keep sitd's canonical name while moving the modem dependency into device-owned policy drop-ins. Tegu checks an already running modem and CP ONLINE; cheetah and raven retain their existing starter relationship. Require the device policy capability during RIL upgrades. Add an opt-in telephony package with a bridge policy and attended helper. It checks live sitd readiness, refuses legacy unit shadows and competing managers, and starts only mmd and the graphical user's agent. The service recovery check permits live calls and registration loss; no helper enables or recovers the modem. Remove mmd's service-level conflict so a bridge start cannot stop another modem manager. Package exclusion and D-Bus name ownership remain. Retain the previously developed SIM, safe-release and audio changes in this stack. Validate the helper, dependency policies and composed units offline; run all seven affected/dependency package suites and build the new architecture-independent package without installing dependencies.
…start the bridge, and a plan that reads as one Record the palmtop run of Phone and Messages (kernel, versions, what passed, and that opening an app didn't start the agent), say which start fits which case, cite derekross#363 instead of a branch, and drop the lines that read like a task report.
…in 0.1.3, with this pull request The plan and the README dated the removal of the unit's Conflicts=ModemManager.service to mmd 0.1.1, and the bullet above still listed it as built; this pull request is what removes it, in 0.1.3.
…WantedBy and tmp.mount, and a refusal isn't retried With derekross#372's boot unit on and this package installed, the bridge's ExecStartPre refused every start: sitd wanted omamobile-mmd.service (the bridge's own WantedBy, once enabled) and both units wanted tmp.mount (systemd adds it). Neither pulls the RIL or the CP into a start, so both are allowed now. A refusal of --service-check exits 3, which the drop-in names in RestartPreventExitStatus=, so a refused bridge stays down instead of retrying every five seconds.
RestartPreventExitStatus= applies only to the main process, so an ExecStartPre= that refused with exit 3 was still restarted every RestartSec under Restart=on-failure. As an ExecCondition=, a refusal (any exit from 1 to 254) skips the start without a retry and without marking the bridge failed. Checked on systemd 262: ExecStartPre exiting 3 with RestartPreventExitStatus=3 restarted five times, ExecCondition exiting 3 skipped the start once.
…: versions past main after the rebase The rebase onto main dropped the two commits main already had and left these three packages changed without a version above main's.
f5b6737 to
8731972
Compare
|
Thank you, @W4HO-ham, for rebasing this onto main and fixing the versions The thing I was waiting for on my side, the 7 Pro's boot files on the build
Thanks for your patience with this one. |
… as the 9a's attach check expects it)
…rough omamobile-mmd (derekross#371) * tegu: plan Phone and Messages integration through mmd Trace the existing app, session agent, ModemManager-compatible bridge and sitd path. Record the tegu installation and unit prerequisites still missing on main, and an attended bridge-only test that preserves the running modem stack. Document the passing offline bridge and apps package suites, activation and audio limits, and the eventual board-specific image integration. * tegu: attach Phone and Messages to an attended running sitd Keep sitd's canonical name while moving the modem dependency into device-owned policy drop-ins. Tegu checks an already running modem and CP ONLINE; cheetah and raven retain their existing starter relationship. Require the device policy capability during RIL upgrades. Add an opt-in telephony package with a bridge policy and attended helper. It checks live sitd readiness, refuses legacy unit shadows and competing managers, and starts only mmd and the graphical user's agent. The service recovery check permits live calls and registration loss; no helper enables or recovers the modem. Remove mmd's service-level conflict so a bridge start cannot stop another modem manager. Package exclusion and D-Bus name ownership remain. Retain the previously developed SIM, safe-release and audio changes in this stack. Validate the helper, dependency policies and composed units offline; run all seven affected/dependency package suites and build the new architecture-independent package without installing dependencies. * device/tegu TELEPHONY-APPS-PLAN: the 2026-11-02 run, the two ways to start the bridge, and a plan that reads as one Record the palmtop run of Phone and Messages (kernel, versions, what passed, and that opening an app didn't start the agent), say which start fits which case, cite derekross#363 instead of a branch, and drop the lines that read like a task report. * TELEPHONY-APPS-PLAN, omamobile-telephony-tegu: mmd's Conflicts= goes in 0.1.3, with this pull request The plan and the README dated the removal of the unit's Conflicts=ModemManager.service to mmd 0.1.1, and the bullet above still listed it as built; this pull request is what removes it, in 0.1.3. * omamobile-telephony-tegu: the bridge's service check accepts its own WantedBy and tmp.mount, and a refusal isn't retried With derekross#372's boot unit on and this package installed, the bridge's ExecStartPre refused every start: sitd wanted omamobile-mmd.service (the bridge's own WantedBy, once enabled) and both units wanted tmp.mount (systemd adds it). Neither pulls the RIL or the CP into a start, so both are allowed now. A refusal of --service-check exits 3, which the drop-in names in RestartPreventExitStatus=, so a refused bridge stays down instead of retrying every five seconds. * omamobile-telephony-tegu: the bridge's service check is an ExecCondition RestartPreventExitStatus= applies only to the main process, so an ExecStartPre= that refused with exit 3 was still restarted every RestartSec under Restart=on-failure. As an ExecCondition=, a refusal (any exit from 1 to 254) skips the start without a retry and without marking the bridge failed. Checked on systemd 262: ExecStartPre exiting 3 with RestartPreventExitStatus=3 restarted five times, ExecCondition exiting 3 skipped the start once. * omamobile-device-cheetah 0.1.48, device-tegu 0.2.10, modem-sit 0.3.32: versions past main after the rebase The rebase onto main dropped the two commits main already had and left these three packages changed without a version above main's. * omamobile-telephony-tegu: depend on the device-tegu that lands with it (0.2.10) * omamobile-telephony-tegu: the dependency test reads device-tegu>=0.2.10 too --------- Co-authored-by: Derek Ross <derekross@gmail.com>
Stacked on #367 (and so #364, #356) and #363; mine is the top commit. Draft until the stack below merges.
TELEPHONY-APPS-PLAN (#370) step one: the 9a's sitd wiring packaged (it runs against an already active tegu modem; cheetah's and raven's start-up unchanged), and an opt-in
omamobile-telephony-tegupackage with the bridge, the omatel agent and an attended helper that starts onlyomamobile-mmdand the user agent, with readiness checks and a terminal confirmation. Installing it enables nothing.On the palmtop (2026-11-03, by hand, the same steps as the helper): with the modem and sitd running,
omamobile-mmdexported the modem on ModemManager's D-Bus API and handed the inbox's four texts over; with the user'somatel-agentstarted, Messages showed them, sent a text that arrived on the owner's phone, and Phone placed a call to the owner's phone with speakerphone audio. Two findings on the way: the agent is D-Bus activated but the app didn't activate it ("Messages service isn't running" until it was started), and sitd read the 9a's radio state 10 as "unknown", so the bridge showed the modem disabled and the bar an airplane glyph (fixed in #367's branch as 0.3.12).All seven affected package suites (21 attachment tests, offline systemd verification), the new package's build and
tools/pr-checkpass; one reference-XML comparison is skipped.