Beta support: MMS on chatty/mmsd on Modem Manager - help/testing wanted!

[0x070]

Got mmsd-tng installed from sid and pulling MMS messages to Modem Manager with SMSWAP set to true.  Can confirm Mint Mobile (US T-Mobile MVNO) works. Oddly Mobian defaults Mint mobile sim to T-Mobile's mobilenet APN so had to change the apn for the modem to

Code:

Name: Internet/MMS2
APN: Wholesale

and ~/.mms/modemmanager/mms

Code:

[Modem Manager]
CarrierMMSC=http://wholesale.mmsmvno.com/mms/wapenc
MMS_APN=Wholesale
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=110000
MaxAttachments=25
AutoCreateSMIL=false

Running into redirect issues attempting to clone chatty from the /wip/sadiq/mm-account branch.  Going to attempt the python messenger method to verify completed delivery. But great news is 18 hours on and my modem hasn't clogged or crashed.  Thanks for the great work.

I'm on Mint Mobile as well. My ~/.mms/modem manager/mms file matches yours, but my apn settings are Name: Ultra, APN: Wholesale.

I'm able to receive MMS in the newly compiled chatty app (the MMS wip Branch), but only if the original Chatty is uninstalled. Any text sent through the branched Chatty is sent twice for some reason.

[jfenn2199]

Got mmsd-tng installed from sid and pulling MMS messages to Modem Manager with SMSWAP set to true.  Can confirm Mint Mobile (US T-Mobile MVNO) works. Oddly Mobian defaults Mint mobile sim to T-Mobile's mobilenet APN so had to change the apn for the modem to

Code:

Name: Internet/MMS2
APN: Wholesale

and ~/.mms/modemmanager/mms

Code:

[Modem Manager]
CarrierMMSC=http://wholesale.mmsmvno.com/mms/wapenc
MMS_APN=Wholesale
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=110000
MaxAttachments=25
AutoCreateSMIL=false

Running into redirect issues attempting to clone chatty from the /wip/sadiq/mm-account branch.  Going to attempt the python messenger method to verify completed delivery. But great news is 18 hours on and my modem hasn't clogged or crashed.  Thanks for the great work.

I'm on Mint Mobile as well. My ~/.mms/modem manager/mms file matches yours, but my apn settings are Name: Ultra, APN: Wholesale.

I'm able to receive MMS in the newly compiled chatty app (the MMS wip Branch), but only if the original Chatty is uninstalled. Any text sent through the branched Chatty is sent twice for some reason.

Thank you I will try that tonight.  Ran into syntax errors attempting to run the python-messaging method from the wiki.

[jfenn2199]

Successfully compiled chatty from the wip/sadiq/mm-account (still encountering redirect error via git clone but was able to download the branch as a tar.gz and compile from that) branch and received all MMS messages from Sunday to today (including a group message which I was unknowingly added to Sunday.

Interestingly enough I tried to test installing on an SD card and using the same mobian-installer-pinephone-phosh-20210516.img which I flashed my phone with and following the same processes of sudo apt update + sudo apt upgrade + reboot after initial install then changing sources.list from Bullseye to unstable, then update/upgrade/reboot again, and finally installing mmsd-tng and setting my apn the same as my primary install (except using Ultra name as 0x007 so will test with my Internet/MMS2 naming and edit this report) resulted in the non-matching modem number error and threw an error on receiving messages in systemctl status check (will add error when testing with Internet/MMS2 name on APN).

[cjhead]

@kop316 

Thank you for all your hard work! This is incredible!

I've been able to get so far on my own and was hoping somebody else could please help me finish.

I'm running Mobian on the Verizon network and so far have done this:

Installed mmsd-tng through Mobian's sid repository # mmsd-tng version 1.0~beta4
Compiled and built the wip/sadiq/mm-account chatty

Edited the /home/mobian/.mms/modemmanager/mms file as follows:

Code:

[Modem Manager]
CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwinternet
CarrierMMSProxy=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=false

When I run mmsdtng -d, I'm able to see that MMS are coming in but that's as far as it goes for me.

Code:

mmsd-tng[3324]: MMS transaction id: 22EC5E8C380000004AB0000201
mmsd-tng[3324]: MMS version: 1.0
mmsd-tng[3324]: From: xxxxxxxxxx/TYPE=PLMN # phone number redacted
mmsd-tng[3324]: Subject: (null)
mmsd-tng[3324]: Class: Personal
mmsd-tng[3324]: Size: 30720
mmsd-tng[3324]: Expiry: 2021-07-07T18:05:17-0400
mmsd-tng[3324]: Location: http://63.55.224.23/servlets/mms?message-id=
mmsd-tng[3324]: ../src/service.c:mms_service_push_notify() about to store_meta_open 2
mmsd-tng[3324]: ../src/service.c:mms_service_push_notify() did store_meta_open 2
mmsd-tng[3324]: ../src/service.c:mms_service_push_notify() did create_request
mmsd-tng[3324]: ../src/service.c:activate_bearer() service 0x5598f905c0 setup 0 active 0
mmsd-tng[3324]: ../src/service.c:activate_bearer() service 0x5598f905c0 waiting for 20 seconds
mmsd-tng[3324]: ../plugins/modemmanager.c:set_context() Setting Context...
mmsd-tng[3324]: ../src/service.c:mms_service_set_mmsc() service 0x5598f905c0 mmsc http://mms.vtext.com/servlets/mms
mmsd-tng[3324]: ../plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsd-tng[3324]: ../plugins/modemmanager.c:set_context() Current Context APN: vzwinternet, mmsd-tng settings MMS APN: vzwinternet
mmsd-tng[3324]: ../plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context...
mmsd-tng[3324]: ../plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/1 active 1 context_active 1
mmsd-tng[3324]: ../plugins/modemmanager.c:bearer_handler() active and context_active, bearer_notify
mmsd-tng[3324]: ../src/service.c:mms_service_bearer_notify() service=0x5598f905c0 active=1 iface=wwan0 proxy=(null)
mmsd-tng[3324]: ../src/service.c:mms_service_bearer_notify() interface wwan0 proxy (null)
mmsd-tng[3324]: ../src/service.c:mms_service_bearer_notify() Proxy is set to 0
mmsd-tng[3324]: ../src/service.c:process_request_queue() service 0x5598f905c0
mmsd-tng[3324]: ../src/service.c:process_request_queue() location http://63.55.224.23/servlets/mms?message-id=
mmsd-tng[3324]: ../src/service.c:resolve_host() Binding resolver queries to interface wwan0
mmsd-tng[3324]: ../src/service.c:resolve_host() All Nameservers: 2001:558:feed::1,2001:558:feed::2,2001:4888:34:ff00:386:d::,2001:4888:35:ff00:383:d::,75.75.75.75,75.75.76.76,198.224.144.135,198.224.145.135
mmsd-tng[3324]: ../src/service.c:resolve_host() IPv6 Nameservers: 2001:558:feed::1,2001:558:feed::2,2001:4888:34:ff00:386:d::,2001:4888:35:ff00:383:d::
mmsd-tng[3324]: ../src/service.c:resolve_host() Only using ipv6 nameservers
mmsd-tng[3324]: Failed to resolve host: Domain name not found
mmsd-tng[3324]: ../src/service.c:resolve_host() Unable to resolve host to IPv6, retrying with IPv4...
mmsd-tng[3324]: ../src/service.c:resolve_host() Restoring original list of nameservers
mmsd-tng[3324]: ../src/service.c:resolve_callback() Found IP for '63.55.224.23': 63.55.224.23
mmsd-tng[3324]: ../src/service.c:resolve_host() Using URI for request: http://63.55.224.23/servlets/mms?message-id=
mmsd-tng[3324]: ../src/service.c:soupmessage_network_event_cb() Socket is bound to wwan0
> GET /servlets/mms?message-id= HTTP/1.1
> Soup-Debug-Timestamp: 1625263538
> Soup-Debug: SoupSession 1 (0x559901e220), SoupMessage 1 (0x5598f9e0d0), SoupSocket 1 (0x7f8c023db0)
> Host: 63.55.224.23
> Accept-Encoding: gzip, deflate
> Connection: Keep-Alive

< HTTP/1.1 404 Not Found
< Soup-Debug-Timestamp: 1625263538
< Soup-Debug: SoupMessage 1 (0x5598f9e0d0)
< Server: Apache
< Content-Type: text/html
< Date: Fri, 02 Jul 2021 22:05:38 GMT
< Connection: Keep-Alive
< Content-Length: 0

mmsd-tng[3324]: Fail to get data (http status = 404)
mmsd-tng[3324]: ../src/service.c:on_message_done() status: 404
mmsd-tng[3324]: ../src/service.c:on_message_done() data size = 0
mmsd-tng[3324]: ../src/service.c:on_message_done() request->result_cb=0x558744f914 vs. retrieve_conf=0x558744f914/send_conf=0x558744a470/notify_resp=0x558744cb20
mmsd-tng[3324]: Fail to get data (http status = 404)
mmsd-tng[3324]: retry later

Thank you again!

[itstoughtofocus]

Got mmsd-tng installed from sid and pulling MMS messages to Modem Manager with SMSWAP set to true.  Can confirm Mint Mobile (US T-Mobile MVNO) works. Oddly Mobian defaults Mint mobile sim to T-Mobile's mobilenet APN so had to change the apn for the modem to

Code:

Name: Internet/MMS2
APN: Wholesale

and ~/.mms/modemmanager/mms

Code:

[Modem Manager]
CarrierMMSC=http://wholesale.mmsmvno.com/mms/wapenc
MMS_APN=Wholesale
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=110000
MaxAttachments=25
AutoCreateSMIL=false

Running into redirect issues attempting to clone chatty from the /wip/sadiq/mm-account branch.  Going to attempt the python messenger method to verify completed delivery. But great news is 18 hours on and my modem hasn't clogged or crashed.  Thanks for the great work.

 


I also use Mint and I've tried off and on to get mmsd working but it never quite worked right. The messages would show in ~/.mms/modemmanager/ but when I tried to read them with any of the options listed on the mobian wiki there was always an error. Well, when I read through your settings I realized what my issue might be. I had been setting MMS_APN to Mint or MintMMS instead of setting it to the APN for data which is Wholesale. When I did that and restarted mmsd, it processed through all my mms messages sitting in ~/.mms/modemmanager and they popped right up in my compiled version of chatty. So, thanks for sharing!

----

After getting mms setup on mobian, I decided to try my luck on setting everything up on my preferred pinephone distro (I run arch btw). While getting mmsd setup I built vgmms (https://git.sr.ht/~anteater/vgmms) on my pinebook pro (it took 40 minutes but that's still less than half the time it takes to build on the pinephone). Vgmms is pretty barebones and doesn't seem to display your contacts names, but it does send and receive picture messages and group chats along with regular sms. It's also snappier than chatty. Has anyone else tried out vgmms? Are there other alternative chat programs out there?

Thanks to everyone who's worked to get this as far as we are now!

[adamplumb]

I've installed the latest mmsdtng (beta5) and I'm running into this dbus error when I start.

$ mmsdtng -d
mmsd-tng[8136]: MMSD-TNG version 1.0~beta5
mmsd-tng[8136]: Lost Dbus Connection! Exiting....

I seem to have the dbus service running so I'm not sure what's happening. Any ideass?

[adamplumb]

I used the d-feet utility to determine that ModemManager is using the name "org.freedesktop.ModemManager1" on the system bus and mmsd-tng is using the name ".ModemManager". For some reason maybe these are conflicting? Not sure, and not sure what to do about it yet.

[adamplumb]

Just following up on my own post, I was trying to start mmsdtng as root, which won't work due to not being attachable to the user's d-bus session.  I set up an XDG autostart using the file from here: https://pkgs.alpinelinux.org/contents?br...=community to /etc/xdg/autostart/mmsd.desktop.  Then reboot, and that should do it.

[ragreenburg]

Got mmsd-tng installed from sid and pulling MMS messages to Modem Manager with SMSWAP set to true.  Can confirm Mint Mobile (US T-Mobile MVNO) works. Oddly Mobian defaults Mint mobile sim to T-Mobile's mobilenet APN so had to change the apn for the modem to

Code:

Name: Internet/MMS2
APN: Wholesale

and ~/.mms/modemmanager/mms

Code:

[Modem Manager]
CarrierMMSC=http://wholesale.mmsmvno.com/mms/wapenc
MMS_APN=Wholesale
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=110000
MaxAttachments=25
AutoCreateSMIL=false

Running into redirect issues attempting to clone chatty from the /wip/sadiq/mm-account branch.  Going to attempt the python messenger method to verify completed delivery. But great news is 18 hours on and my modem hasn't clogged or crashed.  Thanks for the great work.

I'm on Mint Mobile as well. My ~/.mms/modem manager/mms file matches yours, but my apn settings are Name: Ultra, APN: Wholesale.

I'm able to receive MMS in the newly compiled chatty app (the MMS wip Branch), but only if the original Chatty is uninstalled. Any text sent through the branched Chatty is sent twice for some reason.

So I uninstalled Chatty and installed the MMS WIP branch but now I can't see chatty anywhere. I followed all the steps from the wiki installing Chatty but still am not seeing a chatty app. Is there something I'm missing?

[jfenn2199]

Got mmsd-tng installed from sid and pulling MMS messages to Modem Manager with SMSWAP set to true.  Can confirm Mint Mobile (US T-Mobile MVNO) works. Oddly Mobian defaults Mint mobile sim to T-Mobile's mobilenet APN so had to change the apn for the modem to

Code:

Name: Internet/MMS2
APN: Wholesale

and ~/.mms/modemmanager/mms

Code:

[Modem Manager]
CarrierMMSC=http://wholesale.mmsmvno.com/mms/wapenc
MMS_APN=Wholesale
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=110000
MaxAttachments=25
AutoCreateSMIL=false

Running into redirect issues attempting to clone chatty from the /wip/sadiq/mm-account branch.  Going to attempt the python messenger method to verify completed delivery. But great news is 18 hours on and my modem hasn't clogged or crashed.  Thanks for the great work.

I'm on Mint Mobile as well. My ~/.mms/modem manager/mms file matches yours, but my apn settings are Name: Ultra, APN: Wholesale.

I'm able to receive MMS in the newly compiled chatty app (the MMS wip Branch), but only if the original Chatty is uninstalled. Any text sent through the branched Chatty is sent twice for some reason.

So I uninstalled Chatty and installed the MMS WIP branch but now I can't see chatty anywhere. I followed all the steps from the wiki installing Chatty but still am not seeing a chatty app. Is there something I'm missing?

You'll be able to run chatty from the build directory in the chatty directory, so assuming downloaded and built in home folder

Code:

sh ~/chatty/build/run

On debian I was unable to build a .deb using gpb as directed but was able to use Ninja to install.  So from the ~/chatty/build directory

Code:

ninja install

And reboot.  Then you should have your chatty launcher back and be able to receive notifications for SMS messages like normal (at this time I'm not getting notifications on MMS messages).

Make sure that if your settings in ~/.mms/modemmanager/mms have

Code:

AutoProcessSMSWAP=true

then change that to

Code:

AutoProcessSMSWAP=false

and with that you should have full MMS messages rolling into chatty.