Problems Sending/Receiving MMS and Group Messages

MMS generally doesn’t work for me unless I switch to “Use Network DNS” and restart the phone. At least I think that’s what makes MMS work again.

I’ve tried several different messaging apps; they all behaved the same.

I’ve read that some network providers hard-code their own DNS lookup service into their network settings, but would that affect MMS? In contrast, I have no problems with accessing the internet in general, even when using Private DNS or preferred DNS.

I’ve also looked at whether enabling MMS over WiFi Calling or turning off the TrackerControl app has any effect, but I can’t tell if that’s helping. I think I’m sticking with the DNS theory.

@Manoj, I’ve seen MMS issues posted by several forum members recently. Any thoughts on this from Support or other users?

Possibly related, although I myself don’t understand the technicalities… See this PDF from the GSM Association: https://www.gsma.com/newsroom/wp-content/uploads/IR.67-v12.03.pdf (It’s a hundred pages long, so just search within the document for “MMS.”)

Anecdotal reports:

(“legacy version” Reddit) Tip: private DNS may interfere with MMS messages : GalaxyS9

And: 1.1.1.1 DNS Service | T-Mobile Community

And: MMS not sending - OnePlus Community

I have a story on this subject. I tried to revive an old phone of my own. I have “discount” SIM cards supplied by a supermarket. They previously used Three, more recently, Vodaphone. I was given a new contract at the changeover and new settings sent OTA. No issues.

When I introduced the SIM card to the reinstalled phone, it must have been recognised by the carrier because I got the standard message saying that they were sending setting OTA, but that they would send “another message later”.

A second message arrived with masses of information about MMS and how the service would use some odd variation of their airwaves and my WiFi another internet connection, which would be “specially linked” and carry one part of the MMS while they carried the text. I had to sign that I accepted, then new setting were sent OTA.

We hear about carriers worldwide changing to “modern standards” but the arrangement they described sounds very easy to break! I am not a user of MMS, so I cannot say whether their OTA settings actually worked.

I am a great believer is annoying carrier support at the first sign of difficulty!

1 Like

That’s very interesting. Seems related, given the GSMA doc I linked.

you can debug this: check mms hosts that apply to you from prebuilt/common/etc/apns-conf.xml · v1-q · e / os / android_vendor_lineage · GitLab or the settings menu and see if there are hostnames instead of IPs in in mmsc and mmsproxy. If so, very likely the hostnames do not resolve publicly and only with the DNS of your carrier network.

Edit: at least this is me guessing.

(thanks to your PDF I learned mms can be/is being delivered via smtp mmsc<->mmsc!)

1 Like

If I’m understanding your link, then, those are the preloaded APN settings that are part of /e/ builds? (Both official and unofficial?)

That shows for my carrier (Ting, which operates on T-mobile’s network):
apn carrier=“Ting” mcc=“310” mnc=“120” apn=“n.t8.ispsn” type=“default,supl,mms” mmsc=“http://mms.plspictures.com” mmsproxy=“68.28.31.7” mmsport=“80” protocol=“IPV4V6” roaming_protocol=“IPV4V6”

My APN settings, which I set manually, following Ting’s published instructions:

Name Ting Data
APN wireless.dish.com
MMSC http://wholesale.mmsmvno.com/mms/wapenc
APN type* default,admin,fota,mms,supl,hipri,internet,dun
MCC 310
MNC 240
APN protocol IPv4 / IPv6
APN roaming protocol IPv4 / IPv6

my hunch is wrong, those mmsc hosts resolve publicly

I am in UK, and I would pay to use MMS. (I believe typical here, implies some extra work for the carrier?)

In Setings > Network and Internet > Mobile network > Access point names, I see my carrier set at Vodaphone Pre Pay. However the settings are not a match with the APN settings found searching for MMS compatibility.

Then I find a preset APN named Vodaphone Pre Pay MMS, these setting do match the advertised settings. So I expect to be in business.

I imagine it is not especially relevant to the topic but I also see

In Setings > Network and Internet > Mobile network I see MMS messages Switch, Send and receive when mobile data is off. Off by default.

Edit, I found another version of the T&C, this was my misunderstanding from memory! It would be interesting if others experiencing MMS issues could comment on their ability to meet an assumed need to have a synchronous 85%+ wifi and 85%+ Moblle data connection.

(I could test the MMS service, but with me and recceiver paying, I do not have the motivation.) :blush:

I see this, too, but it only appears in the menu when mobile data is off and wifi is on.

Are you able to send and receive group messages without being charged for MMS? (Just curious, as these are sent as MMS usually.)

I get the same, that the switch is hidden when mobile data is on.

In a quick look, I found UK threads that describe setting up “text groups” but having some members not having proper contact!

I tried using the default Message app to send a group text message. It failed with a notification too long for the notification window, MMS is mentioned as the message trails off, I guess it said switch to the MMS service. Oddly the notification looked non standard and faded and is no longer findable.

Vodaphone suggests I use the Messages app, https://play.google.com/store/apps/details?id=com.google.android.apps.messaging, when found on Aurora it says it requires GSF.

Edit. I did connect with the notification after a few attempted resends! It said “Tap to MMS…” then opened the Mobile Network page, where it was 2 taps away from being able to select my “MMS enabled APN”

1 Like

I was fascinated by @tcecyk link to the Gitlab source code for apns-conf.xml, with some 3,800 and more entries. I realised eventually I had thrown a red herring, I edited my “old story” above, they could not have said that MMS would use my wifi, they would have said it used another internet connection.

I tried to grab the same info off my phone with some variation of

# content query --uri content://telephony/carriers

This required root and adb shell and I found some help with

$ adb shell content --help

But I could not extract what I wanted in an efficient way at first so will not include further detail. Edit, updated Post #16

As we have many with MMS difficulties my hypothesis is that MMS may not be carried by your carrier’s default APN settings. If you do not have MMS APN settings, I believe it is your carrier’s job to provide or send them on request.

Here’s what I have. I know my carrier already sent me his MMS APN setting, and this was confirmed by the image above.

Now let’s look at the MMS section of the two settings.

Meanwhile I searched the Gitlab sources and found my two tariffs.

Vodafone Pre Pay

<apn carrier="Vodafone Pre Pay"
mcc="234" mnc="15"
apn="pp.vodafone.co.uk" proxy="" port=""
user="wap" password="wap"

mmsc=""
type="default,supl" />

Vodafone Pre Pay MMS

<apn carrier="Vodafone Pre Pay MMS"
mcc="234" mnc="15"
apn="pp.vodafone.co.uk" proxy="" port=""
user="wap" password="wap"

mmsc="http://mms.vodafone.co.uk/servlets/mms"
mmsproxy="212.183.137.12" mmsport="8799"
type="mms" />

Finally this is what I extracted from the device.


Row: 492 _id=493,
name=Vodafone Pre Pay,
numeric=23415, mcc=234, mnc=15, carrier_id=-1, apn=pp.vodafone.co.uk,
user=wap, server=, password=wap, proxy=, port=,
mmsproxy=, mmsport=, mmsc=,

authtype=-1, type=default,supl,
current=1, protocol=IP, roaming_protocol=IP, carrier_enabled=1,
bearer=0, bearer_bitmask=0, network_type_bitmask=0, mvno_type=,
mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=0,
max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=0,
user_visible=1, user_editable=1, owned_by=1, apn_set_id=0, skip_464xlat=-1

and

Row: 496 _id=497,
name=Vodafone Pre Pay MMS,
numeric=23415, mcc=234, mnc=15, carrier_id=-1, apn=pp.vodafone.co.uk,
user=wap, server=, password=wap, proxy=, port=,
mmsproxy=212.183.137.12, mmsport=8799, mmsc=http://mms.vodafone.co.uk/servlets/mms,

authtype=-1, type=mms,default,supl,
current=1, protocol=IP, roaming_protocol=IP, carrier_enabled=1,
bearer=0, bearer_bitmask=0, network_type_bitmask=0, mvno_type=,
mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=0,
max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=0,
user_visible=1, user_editable=1, owned_by=1, apn_set_id=0, skip_464xlat=-1

Working conclusion, if looking at the graphical APN settings, you are seeing MMSC = Not set - you need to ask your carrier to supply the settings.

1 Like

For my carrier (which recently switched to a new style of SIM card, apparently to accommodate 5G capability), the MMS settings are incorporated into the main APN settings. In the case of their old-style SIMs, they were also part of the main APN settings, but their troubleshooting guide recommended an alternate setting if MMS was not working. In that case, two APNs were used, a main APN with the MMS settings removed, and an additional APN for MMS only. The phone would automatically choose whichever APN was appropriate for the function. This doesn’t work with the new SIMs, apparently.

It’s interesting that the Gitlab entry for my carrier is significantly different from what Ting now supplies, and which works on my phone. I haven’t tried the Gitlab settings, since I suspect they are outdated for Ting.

In any case, I think I can safely say that my particular issue is related to DNS, as MMS only works when I’m using Network DNS. Unfortunately.

Thanks for the fuller explanation of why your situation is special. I did rather think that I had gone off your topic! :blush:

I’m wondering if there’s a way to direct MMS to Network DNS, while keeping everything else on Preferred/Private DNS…

Probably not, I expect.

P.S. My internet connectivity always works, regardless of the DNS setting, so that’s not a concern. By the way, the Gitlab settings don’t even match the previous Ting settings, so I don’t know where those come from. https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide

I don’t know where those come from

if you click git blame in the upper right, the commit message of the respective line applying to your SIM can give insight. “Ting Data” is present, you can also search for the mmc+mnc numbers via [mcc="310" mnc="260"] (without the brackets).

What is adb shell getprop gsm.operator.numeric saying btw? (its mmc+mnc combined, no separator)

If its 310260 instead of 310240 (your help page has them as X1/X3 type SIMs, see the mnc difference), then your custom entry does not get applied, and too the Lineage and /e/ entries are outdated/incomplete to the current carrier specs.

1 Like

In the morning light, I see my syntax error(s)!

Now for Ting from 0.19-q-20211027142973-dev-a3xelte

content query --uri content://telephony/carriers --where "numeric='310240'"
Row: 0 _id=1202, name=Ting Data, numeric=310240, mcc=310, mnc=240, carrier_id=-1, apn=wireless.dish.com, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=http://wholesale.mmsmvno.com/mms/wapenc, authtype=-1, type=default,admin,fota,mms,supl,hipri,internet,dun, current=NULL, protocol=IPV4V6, roaming_protocol=IPV4V6, carrier_enabled=1, bearer=0, bearer_bitmask=0, network_type_bitmask=0, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=0, max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=0, user_visible=1, user_editable=1, owned_by=1, apn_set_id=0, skip_464xlat=-1

A second numeric I see used, 310260 produces 27 results, two include Ting.

content query --uri content://telephony/carriers --where "numeric='310260'"
Row: 11 _id=1214, name=Ting MMS, numeric=310260, mcc=310, mnc=260, carrier_id=-1, apn=wholesale, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=http://wholesale.mmsmvno.com/mms/wapenc, authtype=-1, type=default,mms,supl,admin, current=NULL, protocol=IP, roaming_protocol=IP, carrier_enabled=1, bearer=0, bearer_bitmask=0, network_type_bitmask=0, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=0, max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=0, user_visible=1, user_editable=1, owned_by=1, apn_set_id=0, skip_464xlat=-1
Row: 25 _id=1228, name=Ting Data, numeric=310260, mcc=310, mnc=260, carrier_id=-1, apn=wholesale, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=, authtype=-1, type=default,admin,fota,mms,supl,hipri,internet,dun, current=NULL, protocol=IPV6, roaming_protocol=IPV6, carrier_enabled=1, bearer=0, bearer_bitmask=0, network_type_bitmask=0, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=0, max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=0, user_visible=1, user_editable=1, owned_by=1, apn_set_id=0, skip_464xlat=-1

So that shows separate APNs: Ting Data and Ting MMS, but the one for Ting Data doesn’t remove the MMS settings (and it should, since the Ting MMS APN would cover for MMS, at least, according to Ting’s old troubleshooting guide).

By the way, a Ting rep told me there are no alternate settings with the new X3 SIM. (Which is the combined “Ting Data” APN, with MMS and all.)

So, just to check, are you in Germany?

My numbers come from my phone in the UK. What I extract from my device is not a carbon copy of the source apns-conf.xml. Maybe the install, re-writes the file to suit? This is supported by the fact that the source apns-conf.xml. has 5 hits for Ting.

You probably don’t want to come to conclusions on my secondhand data, but if my hypothesis were correct, neither a plan in Row: 0 or Row: 25, “Ting Data” would transmit MMS as I know it with an empty

mmsc=,

field. Only (on my device here) Ting MMS would be suitable.

My memory is that you are not in Germany, so perhaps you have to completely disregard my data.

I’m in the U.S.; Ting is a U.S. MVNO on T-mobile USA’s network. :slight_smile:

Quite possible.

can you disclose what your SIM really has as mnc value? (last digits of that numeric key)