Repository navigation
omamobile-modem 0.1.11: depend on the device's modem policy, not on device-cheetah - #363
Conversation
Let supported device packages satisfy the modem runtime dependency without installing the conflicting cheetah device package. Cheetah and tegu provide omamobile-modem-policy, as raven already does. Keep CPIF, shared memory and the legacy modem link driver blacklisted on tegu so providing the policy does not permit automatic modem startup. Bump the three packages; modem startup remains explicitly gated.
|
Thanks, @W4HO-ham. This is the right fix. The virtual Merging it now at 0.1.11, ahead of my #382 (which moves to 0.1.12), since your telephony stacks already carry it; I'm writing the squash subject to name all three versions. Follow-ups, please, in a later PR: install device-tegu 0.2.8 on the palmtop and paste a |
…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.
|
Follow-ups: the two stale lines are fixed in #385. On |
…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.
…etah, after derekross#363 Section 2's omamobile-modem row still said the package depends on omamobile-device-cheetah. It now names the omamobile-modem-policy virtual. (The matching comment in omamobile-modem-start was fixed on main in the meantime.)
…#360) * device/tegu TELEPHONY-PLAN: call audio and starting the modem at boot The SIM test passed with everything started by hand. This plans the two steps to a palmtop that works as a phone on its own: the call audio route from the 9a's stock audio HAL (EP5 down, EP4 up, the TAS2572 gain caveat, the AoC voice window to audit) with the safety gap in sitd's call release to close first, and an opt-in boot start for the modem with its guards and the packaging fix. * device/tegu TELEPHONY-PLAN: what has run, and which section 2 items #363 and #372 do * device/tegu TELEPHONY-PLAN: a gated runbook for enabling the modem at boot Derek asked for one with #372: preconditions, one step per boot, Expect/Pass, stop conditions and rollback, with the cold boot, the clean shutdown that removes the latch and the UFS count recorded here.
…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.
…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.
…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.
…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.
…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.
…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.
…rough omamobile-mmd (#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 #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 #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>
…end on the device's modem policy (derekross#363) Let supported device packages satisfy the modem runtime dependency without installing the conflicting cheetah device package. Cheetah and tegu provide omamobile-modem-policy, as raven already does. Keep CPIF, shared memory and the legacy modem link driver blacklisted on tegu so providing the policy does not permit automatic modem startup. Bump the three packages; modem startup remains explicitly gated.
…derekross#360) * device/tegu TELEPHONY-PLAN: call audio and starting the modem at boot The SIM test passed with everything started by hand. This plans the two steps to a palmtop that works as a phone on its own: the call audio route from the 9a's stock audio HAL (EP5 down, EP4 up, the TAS2572 gain caveat, the AoC voice window to audit) with the safety gap in sitd's call release to close first, and an opt-in boot start for the modem with its guards and the packaging fix. * device/tegu TELEPHONY-PLAN: what has run, and which section 2 items derekross#363 and derekross#372 do * device/tegu TELEPHONY-PLAN: a gated runbook for enabling the modem at boot Derek asked for one with derekross#372: preconditions, one step per boot, Expect/Pass, stop conditions and rollback, with the cold boot, the clean shutdown that removes the latch and the UFS count recorded here.
…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>
omamobile-modemdepended onomamobile-device-cheetah, which conflicts with every other device package, so on the Pixel 9a it only installed withpacman -U -dd(the SIM test on 2026-11-02, #356). It now depends on the virtualomamobile-modem-policy, whichomamobile-device-ravenalready provides;omamobile-device-cheetah0.1.39 andomamobile-device-tegu0.2.8 provide it too.What the cheetah dependency actually supplied was its blacklist of CPIF and the shared-memory and link drivers, so that a device-tree node can't start the modem at boot. Tegu's package now carries the same three blacklist lines, so providing the policy doesn't open automatic modem start-up there: only the attended start loads them. No cheetah-only executable was used. The common start-up still picks
pcie-gs201-cpand its default properties name cheetah, so the 9a still needs its own start policy (device/tegu TELEPHONY-PLAN, #360).Each touched package's
test/all(tegu's gains a check for the blacklist) andtools/pr-checkpass. Not installed on the palmtop yet: it runs 0.1.10 installed with-dd.