Skip to content

omatel-agent 0.2.4-3, omamessages 0.2.2-2: MMS and EmergencyOnly (changes every phone; draft) - #936

Draft
johannSo wants to merge 1 commit into
derekross:mainfrom
johannSo:hotdog-mms
Draft

johannSo wants to merge 1 commit into
derekross:mainfrom
johannSo:hotdog-mms

Conversation

@johannSo

Copy link
Copy Markdown

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.

  1. The agent follows ModemManager's EmergencyOnly property. That property clears just after "registered", so after a modem restart ModemState stayed "emergency-only" (and Messages not ready) until the agent restarted.

  2. MMS and group messages through mmsd-tng:

    • pictures and attachments both ways;
    • group conversations;
    • MmsReady;
    • the MMS settings group.

    mmsd-tng is packaged in device/hotdog: the OnePlus 7T Pro (community port) #931.

⚠️ This one changes every phone, so it's a draft

Both apps are shared, so unlike the other OnePlus 7T Pro PRs this can't be gated per device:

  • The store moves to schema 2: MMS parts, plus triggers for deleted messages.
  • Messages shows the attach button and the MMS settings group.
  • 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.
  • Unchanged: text to one person stays SMS, through the 0.2 calls.

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

  • Phone: OnePlus 7T Pro (hotdog)
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-g7539ca3e06f6
  • Packages changed, with versions: omatel-agent 0.2.4-3, omamessages 0.2.2-2

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • pkgrels bumped and in the commit subject
  • Commits have area prefixes and bodies that say why; AI help is a Co-Authored-By: trailer
  • The patches' own tests (store, mmsd-tng mock, settings file) ran in the port's build. The numbers in them are fictional 555 numbers.

On the phone

  • I ran this on my own phone (installed: omatel-agent 0.2.4-3, omamessages 0.2.2-2):
    • MMS sent and received;
    • the agent came up ready after a reboot (MODEM-PLAN R4, R8).
  • What I did not test: any Pixel, or the schema migration on a Pixel's existing message store
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace

🤖 Generated with Claude Code

… 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant