Troubleshooting and Understanding MMS

[npesall]

I'm no farther ahead than I was a month ago on this issue.  Still no functioning MMS on Verizon since mid-May.  Any progress from any of you?

yes, but only connected to "vzwapp" apn, which is limited in connectivity compared to the "vzwinternet" apn

Same here - MMS has been fine with vzwapp APN set in both gnome-settings and Chatty.  Even when the modem storage filled-up and blocked incoming SMS, MMS has worked.

If anyone wants to tinker with this option - I set the gnome-settings APN to "internet" and data worked.

[treebeard]

I'm no farther ahead than I was a month ago on this issue.  Still no functioning MMS on Verizon since mid-May.  Any progress from any of you?

yes, but only connected to "vzwapp" apn, which is limited in connectivity compared to the "vzwinternet" apn

Same here - MMS has been fine with vzwapp APN set in both gnome-settings and Chatty.  Even when the modem storage filled-up and blocked incoming SMS, MMS has worked.

If anyone wants to tinker with this option - I set the gnome-settings APN to "internet" and data worked.

Yes, but MMS won't.  I'm normally set at vzwapp but switch to vzwinternet for the few minutes I occasionally need for internet data.  Work is underway to support dual APNs.

[pikurasa]

My APN list on Verizon is almost a dozen entries...switching to vzwapp to see what happens. Anyone doing anything with the MMSC values?

Also, any consensus on what "purple accounts" is good for?

You'll have to use vzwapp for the MMSC as well if you want to get MMS messages.  I think purple accounts are for IRC.

SUCCESS! Set both the APN under Settings->Mobile Networks and in Chatty preferences to vzwapp, an the MMSC to http://mms.vtext.com/servlets/mms
 and the flood of missed texts, both SMS and MMS came inbound.

I have tried:

Code:

CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL

and with the APN set to `vzwapp` in Gnome Settings.

...but it does not work for me.

I also tried a few other things. For example, https://www.reddit.com/r/ting/comments/u...msung_s10/ suggests `http://vzpix.com/servlets/mms` for MMSC, but that does not seem to work for me either.

I did get a glimmer of hope when someone received my outbound MMS while tinkering with the settings, but unsure what the settings were when they were sent.

That being said, I cannot wait for the "flood of missed texts, both SMS and MMS" to come inbound.

When I run `mmsdtng -d` with the aforementioned configuration (MMSC=vzwapp and either CarrierMMSC=http://mms.vtext.com/servlets/mms or http://vzpix.com/servlets/mms), the error I get is "Fail to get data (http status = 404)".

Any thoughts on what might be missing?

[alaraajavamma]

Code:

CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL

I am not sure because there are so many variables between different carriers but maybe you can try to add the MMS port number

Code:

CarrierMMSC=http://mms.vtext.com/servlets/mms:80

[treebeard]

I have tried:

Code:

CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL

and with the APN set to `vzwapp` in Gnome Settings.

...but it does not work for me.

That's what is working for me.  What OS are you using?  Do you have Chatty > v0.6?

[pikurasa]

I have tried:

Code:

CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL

and with the APN set to `vzwapp` in Gnome Settings.

...but it does not work for me.

That's what is working for me.  What OS are you using?  Do you have Chatty > v0.6?

Good question!

Chatty is version 0.6.7 according to the GNOME software repo gui (whatever it is called).

As for the OS, it is PostMarketOS. Why? Because the version of Monjaro that shipped with the phone was super flaky, even after updates (it would shut off erratically, for example.)

I have a microSD with Mobian on it that I would like to try, but it seems I have installed to eMMc. The PinePhone docs say this is higher in the boot order than the SD card on some devices. There are ways to circumvent the boot order, but I have yet to figure that out. So I figure that, in the meantime, I will try and get as far as I can with this, which seems to be very stable at the moment.

Would you mind to do my a favor and paste everything you have for .mms/modemmanager/mms (other than IMSI)? I want to make certain that I have precisely what you have, and that there are no other variables. (I so want to feel the flowing of the MMS )

Thank you!

[treebeard]

Would you mind to do my a favor and paste everything you have for .mms/modemmanager/mms (other than IMSI)? I want to make certain that I have precisely what you have, and that there are no other variables. (I so want to feel the flowing of the MMS )

Code:

[Modem Manager]
CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true
IMSI=xxxxxxxxxxxx

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=1100000
MaxAttachments=25
AutoCreateSMIL=true
ForceCAres=false

[npesall]

Another interesting fun fact:  I added an APN in gnome settings named Verizon, but left the actual APN name entirely blank.  I was able to use mobile data normally.  However, I still was not able to use MMS in Chatty with the APN set to vzwapp.

[treebeard]

Another interesting fun fact:  I added an APN in gnome settings named Verizon, but left the actual APN name entirely blank.  I was able to use mobile data normally.  However, I still was not able to use MMS in Chatty with the APN set to vzwapp.

Check the log/journal where mmsdtng is initializing.  A snippet of mine:

Code:

mmsdtng[889]: ../plugins/modemmanager.c:set_context() Setting Context...
mmsdtng[889]: ../src/service.c:mms_service_set_mmsc() service 0x55880a3e70 mmsc http://mms.vtext.com/servlets/mms
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Current Context APN: vzwapp, mmsd-tng settings MMS APN: vzwapp
mmsdtng[889]: ../plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context...
mmsdtng[889]: ../src/service.c:mms_service_set_apn() Service APN Set to vzwapp
mmsdtng[889]: ../src/service.c:mms_service_set_resolvers() service 0x55880a3e70 resolvers: ipv4: 198.224.177.135,198.224.176.135, ipv6: 2001:4888:45:ff00:432:d::,2001:4888:46:ff00:430:d::
mmsdtng[889]: ../plugins/modemmanager.c:set_context() DNS from modemmanager IPv6: 2001:4888:45:ff00:432:d::,2001:4888:46:ff00:430:d::, IPv4: 198.224.177.135,198.224.176.135
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Current Context APN: vzwinternet, mmsd-tng settings MMS APN: vzwapp
mmsdtng[889]: ../plugins/modemmanager.c:set_context() Current Context APN: vzwinternet, mmsd-tng settings MMS APN: vzwapp
mmsdtng[889]: ../plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 0 context_active 1
mmsdtng[889]: ../plugins/modemmanager.c:bearer_handler() checking for failure
mmsdtng[889]: ../plugins/modemmanager.c:bearer_handler() No failures
mmsdtng[889]: ../src/service.c:mms_service_bearer_notify() service=0x55880a3e70 active=0 iface=wwan0 proxy=(null)

Look especially for that "You are connected to the correct APN! Enabling context..."

[pikurasa]

Would you mind to do my a favor and paste everything you have for .mms/modemmanager/mms (other than IMSI)? I want to make certain that I have precisely what you have, and that there are no other variables. (I so want to feel the flowing of the MMS )

Code:

[Modem Manager]
CarrierMMSC=http://mms.vtext.com/servlets/mms
MMS_APN=vzwapp
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true
IMSI=xxxxxxxxxxxx

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=1100000
MaxAttachments=25
AutoCreateSMIL=true
ForceCAres=false

I have the same.

Still no luck.

I want to the Verizon store today and the person there thought mmsc=http://mms.vtext.com/servlets/mms and apn=vzwinternet should be fine as that is what her phone (iPhone, I think) is set to. She is on the 5G network, FWIW.

(As an aside: surprisingly, the person who helped me was like, "oh, I '/love/' GNU/Linux" and seemed interested in the phone.)

Are others who have had success on the 4G network, like me, or 3G? (I don't believe PinePhone does 5G, but I could be wrong.)

As for the logs, if I have mmsc=http://mms.vtext.com/servlets/mms and apn=vzwinternet (in both chatty and gnome settings), I get http 7 errors. If I have mmsc=http://mms.vtext.com/servlets/mms and apn=vzwapp (in both chatty and gnome settings), I get http 404 errors.

Oddly enough, I seem to be able to send text with images (presumably mms) when set to mmsc=http://mms.vtext.com/servlets/mms and apn=vzwapp (in both chatty and gnome settings), but not able to receive them (I know I have missed group MMS texts b/c I am in constant communication with another person who I am in the group with). Also, oddly enough, I see some files in .mms/modenmanager that look suspiciously like MMS data (but not entirely human readable). This makes me wonder if I am receiving the MMS, but maybe chatty is not correctly adding them to the database. Or maybe, those files are a list of MMS that are suppose to be retrieved, but are failing to be retrieved. I have no idea, but curiosity is overwhelming me at the moment.

Also, another weird thing is, when I run: `mmcli -m any --time` it prints 2024-06-06 (but the timestamp on the debugger is the correct time).

Also notable is the output for `mmcli -m any --messaging-list-sms` is /modemblahblah/somenumber "(receiving)" (as in "not yet "received"???)