Repository navigation
Conversation
…r's address for the bridge An MMS notification is a WAP push, often in several parts, and only the first part carries the WAP port. Stored parts now keep their port (old partial records are migrated), and a joined binary message is delivered as data only when its port is the WAP push one; any other is replaced by a short notice. The codec keeps a binary part without a port when it's one of a concatenated set. sitd's status for authorised clients now carries the internet bearer's device (the one omamobile-sit-data found), address and DNS, so the bridge can give mmsd-tng the bearer it fetches MMS over where the MMS APN is the internet APN. state.json doesn't carry them; the bridge's Ip4Config, like ModemManager's, is readable on the system bus. (cherry picked from commit 35d7a1e)
…-tng mmsd-tng fetches MMS over a ModemManager bearer whose APN is the MMS APN, binds to its Interface and resolves the MMSC through the DNS in its Ip4Config. Where the MMS APN is the internet APN, that's the internet bearer, so the bridge now gives it the device omamobile-sit-data found (rmnet0 until sitd knows) and, while data is up, its address and the carrier's DNS from sitd's status. (cherry picked from commit 7b2622d)
…t bearer mmsd-tng 2.6.4 for aarch64 from upstream's tag, with four small patches (the own number when ModemManager exports none, a socket closed on a failed interface bind, modern libphonenumber linkage) and meson test in check(). Nothing is enabled and no carrier settings ship; the example config is the owner's to fill in. TELEPHONY-APPS-PLAN 1.7 now says what's ready for MMS on the 9a, where the MMS APN is the internet APN and MMS goes over the internet bearer, and gives an attended runbook, receive first. (cherry picked from commit 876e407)
… MMS received mmsd-tng logged "Couldn't create IP config from dictionary: 'method not given'" for the bearer's empty Ip6Config. An empty config is now method 0 (unknown), as libmm-glib expects. TELEPHONY-APPS-PLAN records the first picture received on the palmtop over the internet bearer. (cherry picked from commit 388eed8)
… reports its device Before sitd had reported a device, the bridge named rmnet0. On the 7 Pro, with a different attach APN, rmnet0 can briefly be another bearer's device, so mmsd-tng could bind to the wrong one. MM itself leaves a bearer's interface empty until it has one. (cherry picked from commit c1fc4a9)
|
A correction to the description, on the patches going upstream: I wrote that I'd send the two behaviour ones. Not for now. The owner has no account on GitLab, where mmsd-tng lives, so none of the four has been sent and none is on its way. They stay as patches in the package; if that changes I'll say so here. |
|
An update on the patches going upstream: the owner made a GitLab account after all, and the two behaviour fixes are offered to mmsd-tng now, each rebuilt on its current master (33 of 33 targets, |
|
Thank you for bringing the picture-message work onto main by itself. It reads much more easily as five commits than it did on top of the call-tuning stack, and I like how it is built: nothing is enabled, no carrier settings ship, the address stays out of This is my first full read of it. I checked the package by hand, since CI can't build it: upstream's 2.6.4 archive has the checksum in the PKGBUILD, the four patches apply with no fuzz in What I'd like before it leaves draft:
Some smaller things, as you see fit:
After that it's my turn: this changes the phone service and the bridge on the Pixel 7 Pro too (the database gains a column, the binary-message path, the bearer's properties), so I'll run it there before I merge: a text and a long text each way, a call, the bearer's device against the recorded one, cellular data with Wi-Fi off, and a picture sent to it to see what Messages shows. One thing I still have to decide on my side is whether our repository should publish mmsd-tng before Messages can use it. I'll tell you here. |
…tests for the binary-message rules omamobile-sit-data writes data-interface before it probes a candidate, so that a killed run can be cleaned up, and sitd's status read that file: for the seconds of a probe it reported a device that might not carry the bearer (rmnet0 on the Pixel 7 Pro, where rmnet1 does). The data service now writes a second record, data-interface-kept, only once a candidate has answered, removes it before it takes the configuration down, and the status reads that one. A test reads the status during each probe. Tests pin what goes on as data: a concatenated 8-bit message with no port in any part, or with another port in its first part, is not data; nor is a WAP push in the reserved alphabet or with compressed content. Each fails when its condition is removed.
…s installed omatel-agent leaves a message with data and no text for the MMS service, so on a phone without mmsd-tng a picture message's notification showed nothing in Messages. On main only a multi-part one showed the "cannot display yet" placeholder, because its later parts decoded as text; with whole pushes delivered as data that went too. The bridge now exports the placeholder as the text, with no data, unless /usr/bin/mmsdtng exists. --mms-daemon sets that path for the tests.
…ream merge requests, the bridge's dependency The patches are numbered 0001 to 0004, and the README says which two are offered upstream (mmsd!133, mmsd!134), so the next version bump knows what to drop; its paragraph on the AUR recipe is one sentence, and it points at section 1.7. The plan says derekross#697 where it said derekross#380. omamobile-mmd depends on the modem-sit that reports the bearer; the number is a placeholder for the one set at merge.
|
Thank you for the full read. Three commits on top, 869caa0, e5f1764 and 50e1a31.
The smaller ones:
Both packages' |
….3.36 Main took 0.3.36 for nr_after_radio_on, so the status that names the internet bearer's device, address and DNS is 0.3.37, and the bridge depends on that one.
|
The palmtop run from this head (item 4), 2026-11-13. First, what moved on the branch since your review: main took The run: the three packages built on the palmtop from 24bbeb5 and installed with the modem off, then a clean reboot, so the modem, sitd and the bridge started at boot from them. The bearer next to the data service's records (LTE, IMS registered, Wi-Fi connected):
Pictures received with Wi-Fi up: two. The owner sent two pictures from an iPhone a few minutes earlier, while the palmtop was between reboots. On this boot the bridge listed the two WAP pushes at 15:11:13, a second after sitd reported IMS SMS registered (it had listed them on the boot before too, where mmsd-tng wasn't started and omatel-agent logged "binary SMS (WAP push): left for the MMS service"). mmsd-tng started at 15:12:40 and had both fetched by 15:12:48:
I haven't looked at what Messages shows for them; that is the apps' side.
phone-smoke: teguKernel
Packages: hyprland 0.57.0-3.3, libcamera 0.7.2-4.23, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.18-1, omamobile-device-tegu 0.2.16-1, omamobile-fingerprint 0.1.17-1, omamobile-firstboot 0.1.4-1, omamobile-gnss 0.2.9-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.4-1, omamobile-modem 0.1.20-1, omamobile-modem-sit 0.3.37-1, omamobile-omarchy 0.1.43-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.127-1, omamobile-telephony-tegu 0.1.0-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1.1 |
|
Thank you. All five points are answered, and the run from this head is what I asked for: built from 24bbeb5, started at boot, the bearer's What's left is mostly mine:
|
The picture-message work from #380, on main by itself, as you asked there: the five commits that were #380's own, picked onto today's main without the call-tuning stack (#374, #376, #378) under them. They applied without a conflict. #380 can close once this is the one you read.
omamobile-sit-datafound), address and DNS.state.jsondoesn't.Interface, plus its address and the carrier's DNS inIp4Config, readable on the system bus as with ModemManager. The interface stays empty until sitd reports its device, and the IP configs always carry a method. mmsd-tng binds to that device and resolves the MMSC through those servers, so MMS goes over cellular with Wi-Fi up, without touching the system's routes or DNS.meson testincheck(). Nothing is enabled and no carrier settings ship.On the palmtop's carrier the MMS APN is the internet APN; a carrier with a separate MMS APN isn't supported yet.
Run on the palmtop. TELEPHONY-APPS-PLAN 1.7 has the receive of 2026-11-03: a picture fetched over
rmnet0with Wi-Fi up, from a hand build of mmsd-tng. On 2026-11-11 the package itself was built on the palmtop (native aarch64, the pinned source, all four patches, 33 of 33 targets, 4 of 4meson testcases; the log is on #380) and installed. Still owed, and I'll add it here: the line you asked for,mmsd-tnginstalled from the built package with its user unit reaching the session bus on that install. The palmtop is in a sleep series today with the modem off; it comes this evening.Your two notes from #380.
omamobile-mmdchanges here without a version change: please set it at merge with the others. And the patches: none of the four has gone upstream yet. The two behaviour ones (closing the socket when the interface bind fails, and using the configured number when the modem reports no own numbers) are fixes I think they'd take, and I'll send them.It reaches the 7 Pro too (the bearer's
Interfacestarts empty, the IP configs are new), so it waits for your attended run there, as you said.Tests on this branch:
tests/packages omamobile-modem-sit omamobile-mmd mmsd-tng(all three suites pass) andtools/pr-check origin/main.