Repository navigation
Conversation
… EmergencyOnly Two changes not in an omatel or omamessages release yet, as patches on the released sources: - The agent read ModemManager's EmergencyOnly only on state changes, and that property clears just after "registered", so after a modem restart ModemState stayed "emergency-only" (and Messages not ready) until the agent restarted. It now watches the property as well. - MMS and group messages through mmsd-tng: pictures and attachments both ways, group conversations, MmsReady, and the MMS settings page. omamessages builds against the patched omatel crates (copies of the two omatel patches) until releases carry the new API. Unlike the rest of the OnePlus 7T Pro's work, this changes the apps on every phone, because both packages are shared: the store moves to schema 2 (MMS parts and the forgotten-message triggers), Messages shows the attach button and the MMS settings group, and a group conversation's text goes as MMS. On a phone without mmsd-tng (every Pixel today) an attachment or a group message is kept as failed with "The MMS service (mmsd-tng) isn't running" and Retry; text to one person stays SMS through the 0.2 calls. These are better taken into the omatel and omamessages repositories and released from there; this commit is how the port carries them meanwhile. Tested on the OnePlus 7T Pro: MMS sent and received (owner), and the agent came up ready after a reboot (device/hotdog/MODEM-PLAN.md R4, R8). Not run on a Pixel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 of 9 tasks
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.
What and why
omatel-agent 0.2.4-3 and omamessages 0.2.2-2: the OnePlus 7T Pro's (#931) messaging changes, as patches on the released app sources.
The agent follows ModemManager's
EmergencyOnlyproperty. That property clears just after "registered", so after a modem restartModemStatestayed "emergency-only" (and Messages not ready) until the agent restarted.MMS and group messages through mmsd-tng:
MmsReady;mmsd-tng is packaged in device/hotdog: the OnePlus 7T Pro (community port) #931.
Both apps are shared, so unlike the other OnePlus 7T Pro PRs this can't be gated per device:
These patches would be better landed in the omatel and omamessages repositories and released from there. This PR shows what the port carries until then. It is independent of #931–#935: they merge without it. Without it the 7T Pro still has SMS and calls, but no MMS.
Device and build
uname -r):7.3.0-rc6-omamobile-push1-g7539ca3e06f6Checks (no phone needed)
tools/pr-check origin/mainpassesCo-Authored-By:trailerOn the phone
userdata, weakens the storage guard, or reads registers from userspace🤖 Generated with Claude Code