Repository navigation
Conversation
This was referenced Nov 3, 2026
Stopping a running modem in place has reset tegu. When release is not confirmed, try radio-off, log only the reason and radio/CP states, and exit sitd while keeping call ownership and the modem/NV server intact. Apply the same recovery to stale ownership at startup and unresolved shutdown. Treat the recovery as fatal even inside a socket request, skip a second hangup attempt during cleanup, and always restore the audio route. Radio off failures still require an attended reboot; nothing powers the CP off or restarts it automatically. Exercise missing release indications through sit-sim at the hangup deadline, service shutdown and stale-owner startup, plus failed radio-off handling.
The comment at 0xf1 read as if sending 0 there caused the 9a's status 36. The SIM test's record says otherwise: 0.3.7 sent the bitmap and still got 36, and 0.3.8's wait after the data permission fixed it. Comment only.
… off and waits for a reboot The docs and two runbooks still described the old path, which stopped the modem unit and powered the CP off, and waited for a journal line that can no longer appear. They now give the new behaviour and journal text, and say it has run only in the simulator.
Select the TAS2572 route only for google,tegu-aoc-snd-card. Save the controls, verify sink mute, configure the stock microphone/TDM routes, and start EP4 capture and EP5 playback as mono S16_LE at 8 kHz with 80-frame periods and two periods. Applying ALSA hardware parameters prepares each PCM once; do not prepare the modem stream twice. After PCM startup resets the amplifier profile, set both TAS digital gains to index 180 (-20 dB) and verify read-back before unmuting. A gain refusal unwinds the route and leaves call signalling available. Close PCMs before restoring controls, keep mute on cleanup failure, and retain the cheetah CS35L41 route and the default card=none configuration. Add fake-ALSA fault tests and the voice-window audit. The existing SRAM reservation is retained; no CPU mapping or phone operation is added.
Outgoing and incoming speakerphone calls with audio both ways, first on the daily kernel and then on in-tree drivers from the open kernel PRs, where data and a text ran too. The Modem cell says so, and what's left: echo cancellation, an earpiece, the modem's start at boot and the kernel PRs' merge.
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.
…ot, opt-in The 9a's modem only started by hand, from a bring-up script outside the package. omamobile-tegu-modem-up is now packaged: the kernel's own CP drivers when it has them, else the bring-up modules; the NV check, then a sleep inhibitor, then the drivers; a latch written before the drivers and cleared at CP ONLINE, so a start that never got there stops later boots until a human looks; the once-per-boot refusal; and with --phone the phone service and, when installed, the Phone and Messages bridge. omamobile-tegu-modem-boot.service runs it at boot, installed but never enabled by the package. A scratch-root test covers the driver choice, the order, the latch and the refusals.
… CP drivers load
The profile's check also wants CPIF's ports, so before the drivers it refused ("the CPIF port is not loaded") and the first boot start on the palmtop failed there. It runs after the drivers again, as the bring-up script had it; the inhibitor and the latch still come before any driver.
…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.
…audio Stage the owner-provided APMg3 uplink and downlink protobufs through the AoC output tuning services, confirm bounded acknowledgements, and refuse another tuning attempt after an unknown outcome. Set the speaker echo reference before capture and disable AEC during confirmed cleanup. Add a conservative top-speaker route with bottom attenuation and gain readback. Keep the complete amplifier profile 0: the examined native voice-handset case is a power-state delta, and the AoC sink bitmap controls are read-only. Document the distinction from stock voice/EM control and the attended qualification gate. Extract six speaker/handset tuning files from the owner image, with synthetic extraction and service-record tests. Defaults leave tuning and call audio disabled; no phone trial is claimed.
Reserve CID 3 for an explicit MMS activation with APN type bit 2. Require confirmed internet ownership and existing PS permission, without changing the attach profile or rewriting global permission. Preserve internet and IMS through refusal or an uncertain MMS outcome. Document mmsd-tng bearer selection, bridge and network requirements, the Messages backend, and offline and attended acceptance gates. Add failure coverage and a sit-sim setup/release test. No automatic MMS activation is introduced.
W4HO-ham
force-pushed
the
tegu-mms-bearer
branch
from
November 3, 2026 06:04
95bd8f3 to
aec94b7
Compare
Contributor
Author
|
Closing this one. #384 made the internet bearer's CID a setting (3 on your Verizon setup), and every CID but 2 now maps to the internet bearer's records, so a dedicated MMS bearer on CID 3 collides with it. On the palmtop's carrier the MMS APN is the internet APN, and #380 already sends MMS over the internet bearer for that case. When a carrier needs a separate MMS APN, a dedicated bearer can come back with its own CID setting and records. #380 is being rebuilt without it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #374 (and through it #371 and #372); this PR's own change is the last commit.
MMS needs its own data context on the carrier's MMS APN. This reserves context 3 for it, activated only on an explicit request with the MMS APN type. It goes ahead only when sitd already owns the internet context and has packet-service permission, and it doesn't change the attach profile or the global permission. If the network refuses, or the outcome is unknown, internet and IMS stay as they were. Nothing activates it automatically yet.
docs/TELEPHONY-APPS-PLAN.mdT3 covers the rest: how mmsd-tng picks the bearer, what the bridge and network setup need, the Messages side, and the offline and attended acceptance steps. The MMS APN comes from the owner's config, never from the repo.Tests:
tests/packages omamobile-modem-sit(failure cases and a setup/release run on the simulator),tools/pr-check. Not yet run on the palmtop.