This is one for the search engines since I couldn't find an answer for this out there for this so hopefully this helps someone else.
My MMS messages were suddenly failing to send. I took a look at my logcat and saw that for some reason even though the MMS service was pulling the correct MMSC from the profile, the OkHTTP API was failing to connect to localhost. My only guess is that apparently the MMSC http URL was sending an HTTP redirect to something that my device was resolving to localhost since I could connect to the MMSC with my web browser and ping it successfully by name with a terminal client without it resolving to 127.0.0.1 (localhost). I tried disabling my ad blocker since that's the only thing I could think of that could be causing a DNS resolve to 127.0.0.1, but that wasn't it.
I also knew that my MVNO had updated their MMSC and so I tried adding in a new APN with those settings, with the new MMSC entered both by name and by IP address (note: with OnePlus you always need to specify an MVNO type, in my case GID, for a custom APN to save). From the logcat, I saw that the MMS service was unbelievably still using the grayed out APN profile with the old MMSC, even after a reboot. I verified that my custom APN was in fact selected. I tried deleting the storage from several different phone services, as well as locating and deleting the custom APN file, to no avail.
Finally, I figure out what was going on. OnePlus has an evil APN locking file at:
/system/etc/apns-conf.xml
If an APN name on your SIM matches with an APN name in this file, then you are locked to that APN even if you have defined and selected a custom APN!
So, I made a backup copy of this file first, then I located the grayed out APN profile in this file (search by APN name), deleted it, and rebooted. Looking at the logcat though, I still saw that the phone was not using my custom APN profile!! It turned out that there was a second match for the APN name in this file. I deleted that as well, rebooted, and voila - no more grayed out APN in my APN settings that I'm locked to and can't edit. I verified in logcat that my phone was now using my custom APN profile and now my MMS are working again!
Hope this helps someone else!
Notes:
I'm using the last Oreo/ OxygenOS 5.1.11 for best xPosed support, but I did see on the OP forums that other people were having issues with their MMS and APN grayed out even with Pie on several different OP phones.
Yes, I have an older SIM from my MVNO, but not that old
Related
Long story short here, I've got a Milestone I threw 2.0 Brazillian ROM on back before 2.1. Updated to 2.1 and for some reason when I try to enter the APN settings from Telus, it flat out won't save the APN.
I've tried calling Telus for the settings but the ones they give and the APN settings including the MMC port and servers are seemingly doing nothing, the only way I can get online with it is through WiFi. My current OS is a legitimate 2.1 Brazillian [only way I know is the language it installed on 2.1 was Portuguese].
Any ideas? If it means anything, the phone is unlocked but it's being used on Telus anyhow.
Try giving the apn a different name like telus1 and see if that works. Had a gent in my store with an N1 yesterday and he couldn't save his apn with the exact same settings as mine. Not sure what it was but when he saved it Roger's and had a dummy one saved as Rogers (using internet.com as apn with no other settings which works for internet but lacks mms functionality) it worked.
Let me know!!
Jim
-------------------------------------
Seny via Tapatalk from my Nexus One
This is a little late but it might help somebody else...
The reason why your APN is not saving is because you're changing the default values of MCC and MNC. If this is different to build value, your APN will disappear.
So, to save your APN, you need to use ADB to pull build.prop from system using the following command:
adb pull /system/build.prop
Once you've pulled build.prop to you offline location, change the value for "ro.cdma.home.operator.numeric" to something to match your MNC and MCC number. Combine the two to give you 6digits e.g. Telus is 302220.
Once this is done, do the following using ADB again.
adb remount
adb push build.prop /system/
That should fix your APN issue!!!
i pulled the file but i dont have that variable ro.cdma.home.operator.numeric
what to do now?
Hello guys,
I happen to have the very same issue with my APN, with a HTC Legend (2.2 rom, but I had this with 2.1 too). I can't change the MNC (which is set to 10 by default) to the correct value for my carrier : 01. I've spent hours trying to figure this out, and googling for an answer, but all I could find is "it is caused by the lecture of SIM's default MNC and you can't change it". Until I read your answer, which seemed at first glance to be the one, but I too didn't find the line "ro.cdma.home.operator.numeric", and after adding it manually, I was unable to push the file back onto the droid : "Directory not empty".
I'd consider you as a demi-god if you could help us out here
Sorry for my poor english btw
cytrax said:
This is a little late but it might help somebody else...
The reason why your APN is not saving is because you're changing the default values of MCC and MNC. If this is different to build value, your APN will disappear.
So, to save your APN, you need to use ADB to pull build.prop from system using the following command:
adb pull /system/build.prop
Once you've pulled build.prop to you offline location, change the value for "ro.cdma.home.operator.numeric" to something to match your MNC and MCC number. Combine the two to give you 6digits e.g. Telus is 302220.
Once this is done, do the following using ADB again.
adb remount
adb push build.prop /system/
That should fix your APN issue!!!
Click to expand...
Click to collapse
I'm with Koodo (Telus subsidiary) and It also has the 302220 MNC/MCC. I can use Go SMS to send MMS, but I cannot receive them for some reason. I've tried this fix, put in the apns but still no luck. ... one of the odd things though, is when I open the APN editor (Voice dial "Open A-P-Ns") it doesn't show any valid APNs, but the apn managers do.
Any ideas on how I can get my MMS functioning? Data works, just not MMs.
[-- Edit --]
I'm using the settings from Koodo's site : http://koodomobile.com/en/ab/non-koodo-phone-data-setup.shtml ; they're largely identical to Telus' except for the name of the APN and the inclusion of /koodo in the mmsc proxy.
Proxies 74.49.0.18 ; mms server http://aliasredirect.net/proxy/koodo/mmsc blah blah blah ..
Does anyone else have this issue?
I didn't have this issue until I did a factory reset yesterday. I have checked my data settings for my phone and the default messaging app and I do not see a setting that would be affecting me. MMS messages download immediately if I am on only a mobile network.
Checking different websites online led me to checking the APN settings for the T-Mobile network. I checked them against the settings that are provided on the T-Mobile website and I see that mine do not match completely. Mine differs from their site in 3 places:
I am missing the MMS Protocol field,
APN type is set to default,mms,supl
and my APN protocol is set to IPv6 instead of IPv4/IPv6
I'm a new user so it won't let me link to the support page but it is below:
HTML:
https://support.t-mobile.com/docs/DOC-30273
I tried manually creating an APN to match their website but I still cannot find the MMS Protocol field. Also, it switches back to the original APN whenever I check back.
I'm not sure if anyone else has had this issue but I think my next step is to call their customer service and see if they can reset something on their end.
If I have inadvertently re-created another's work I apologize. I did not find this method in any of the closely related threads but it's so simple it should be there somewhere. Let me know and I'll gladly give credit where credit is due. That being said here we go
OK, Quick and dirty as usual...How to get working hotspot bypass on rooted nougat. It works on initial root or you can edit the build prop back to 310000 n reboot. Okay, so more or less follow the rooting method in godpowerrr's thread unless you're already rooted then pickup at the adding APNs below:
https://forum.xda-developers.com/sprint-s7-edge/how-to/sm-g935p-spr-root-nougat-7-0-data-t3568780 Thanks be to @godpowerrr
Follow all the steps, except just leave wifi on while you run through the process.
When you get to the steps with the build.prop edits don't do it yet.
Go into settings-connections-Mobile Networks-Access Point Names: click "add" in the top right.
Add this APN;
Name: Whatever you want to name it.......LTE HOTSPOT
APN: n.ispsn
Proxy: not set
Port: not set
Username: not set
Password: not set
Server: not set
MMSC: http://mms.sprintpcs.com
Multimedia Message Proxy: 68.28.31.7
Multimedia Message Port: 80
MCC: 310
MNC: 120
Authentication Type: not set
APN type: default,mms,dun <-----no spaces after commas
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
Turn APN on/off: APN tuned on
Bearer: LTE
Mobile virtual......: none
Mobile virtual.....: not set
NOW CLICK SAVE AND IT WILL DISAPPEAR- don't worry, it'll re-appear later.
now go back to the root guide and pick up where you left off changing the build.prop values. when you change to 310120 the new apn will populate.
This is where you need the MSL- manually select the new APN you created. Either way you should have a full functioning hotspot.
To sum it up you can add a Custom APN by changing the build.prop, creating the APN, saving, and changing it back. Have fun
Better method here-
https://forum.xda-developers.com/sprint-s7-edge/how-to/one-hotspot-bypass-tested-nougat-msl-t3591763
Anybody try this yet? It's lonely in here...
izzibew26 said:
Anybody try this yet? It's lonely in here...
Click to expand...
Click to collapse
I'm trying to bypass the tether check for an AT&T S7 (G930A) on Nougat... You happen to have any insight on how to port this process?
Thanks for the info, I'll do some research myself to see if I can get anywhere with it.
HumanCaviar said:
I'm trying to bypass the tether check for an AT&T S7 (G930A) on Nougat... You happen to have any insight on how to port this process?
Thanks for the info, I'll do some research myself to see if I can get anywhere with it.
Click to expand...
Click to collapse
1st look at your normal LTE APN and write down all the info.
I'm not sure exactly what at&t has for the equivalent of ro.cdma.default_numeric but I would suppose it has something similar. search for the combined combination of your MCC and MNC. that's the number you'll want to change. as you can see from the OP, sprint is 310, and 120. so the combined numbers are 310120. you'll see the numbers when you look at your APN.
edit the build.prop line to 310000. reboot and go through the op steps to create(add) an identical APN to the one you wrote down. settings-connections-Mobile Networks-Access Point Names: click "add" in the top right. The only changes that would be made would be the name of the APN and the addition of dun to the APN type line. everything else will look just like your stock APN from earlier. make sure to click save and it will disappear. then change your build.prop line back to what it originally was and reboot. it should show up in the list of your APNs now. then, using your msl and ##data#, go into apn settings and select the new apn you created. Hope it works. pm me if you run into roadblocks, also i'd like to know the build.prop/APN info if there are issues.
izzibew26 said:
1st look at your normal LTE APN and write down all the info.
I'm not sure exactly what at&t has for the equivalent of ro.cdma.default_numeric but I would suppose it has something similar. search for the combined combination of your MCC and MNC. that's the number you'll want to change. as you can see from the OP, sprint is 310, and 120. so the combined numbers are 310120. you'll see the numbers when you look at your APN.
edit the build.prop line to 310000. reboot and go through the op steps to create(add) an identical APN to the one you wrote down. settings-connections-Mobile Networks-Access Point Names: click "add" in the top right. The only changes that would be made would be the name of the APN and the addition of dun to the APN type line. everything else will look just like your stock APN from earlier. make sure to click save and it will disappear. then change your build.prop line back to what it originally was and reboot. it should show up in the list of your APNs now. then, using your msl and ##data#, go into apn settings and select the new apn you created. Hope it works. pm me if you run into roadblocks, also i'd like to know the build.prop/APN info if there are issues.
Click to expand...
Click to collapse
Seems as though AT&T handles DUN provision checks in a fundamentally different way... Couldn't find my MMC+MNC string in build.prop.
Ended up getting a solution here @ https://forum.xda-developers.com/showpost.php?p=71547500&postcount=4
Thanks for the reply!
Hey, thanks for posting this method, worked for me.
izzibew26 said:
Anybody try this yet? It's lonely in here...
Click to expand...
Click to collapse
Does this unthrottle the hotspot as well? Lol. Do you have any information on how to unthrottle the data speeds? Sprint has me throttled to 1mb speeds when i should be getting around 60mb/s.
stebomurkn420 said:
Does this unthrottle the hotspot as well? Lol. Do you have any information on how to unthrottle the data speeds? Sprint has me throttled to 1mb speeds when i should be getting around 60mb/s.
Click to expand...
Click to collapse
Honestly I have no idea how sprint does their throttling. I can't say I've ever been in that situation. Give it a shot, see if it has any effect
Sent from Uranus, the only planet with a ring on the inside
izzibew26 said:
If I have inadvertently re-created another's work I apologize. I did not find this method in any of the closely related threads but it's so simple it should be there somewhere. Let me know and I'll gladly give credit where credit is due. That being said here we go
OK, Quick and dirty as usual...How to get working hotspot bypass on rooted nougat. It works on initial root or you can edit the build prop back to 310000 n reboot. Okay, so more or less follow the rooting method in godpowerrr's thread unless you're already rooted then pickup at the adding APNs below:
https://forum.xda-developers.com/sprint-s7-edge/how-to/sm-g935p-spr-root-nougat-7-0-data-t3568780 Thanks be to @godpowerrr
Follow all the steps, except just leave wifi on while you run through the process.
When you get to the steps with the build.prop edits don't do it yet.
Go into settings-connections-Mobile Networks-Access Point Names: click "add" in the top right.
Add this APN;
Name: Whatever you want to name it.......LTE HOTSPOT
APN: n.ispsn
Proxy: not set
Port: not set
Username: not set
Password: not set
Server: not set
MMSC: http://mms.sprintpcs.com
Multimedia Message Proxy: 68.28.31.7
Multimedia Message Port: 80
MCC: 310
MNC: 120
Authentication Type: not set
APN type: default,mms,dun <-----no spaces after commas
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
Turn APN on/off: APN tuned on
Bearer: LTE
Mobile virtual......: none
Mobile virtual.....: not set
NOW CLICK SAVE AND IT WILL DISAPPEAR- don't worry, it'll re-appear later.
now go back to the root guide and pick up where you left off changing the build.prop values. when you change to 310120 the new apn will populate.
This is where you need the MSL- manually select the new APN you created. Either way you should have a full functioning hotspot.
To sum it up you can add a Custom APN by changing the build.prop, creating the APN, saving, and changing it back. Have fun
Click to expand...
Click to collapse
I have completed the whole process and was able to enter the new VPN. However, when changing the buildprop back I am unable to select the new access point. I have tried the ##DATA# and nothing happens. Any ideas?
rideblue193 said:
I have completed the whole process and was able to enter the new VPN. However, when changing the buildprop back I am unable to select the new access point. I have tried the ##DATA# and nothing happens. Any ideas?
Click to expand...
Click to collapse
Not sure why the ##data# dialer code wouldn't work unless you rooted at the same time and possibly missed a step or disabled the app it triggers. Make sure you click "save" after you have the new APN all written up, then it will show up when you change your build.prop back to 310120. Also make sure your editor has been granted root permissions. Just throwing a few things out there, there are so many little things you could've possibly missed.
izzibew26 said:
Not sure why the ##data# dialer code wouldn't work unless you rooted at the same time and possibly missed a step or disabled the app it triggers. Make sure you click "save" after you have the new APN all written up, then it will show up when you change your build.prop back to 310120. Also make sure your editor has been granted root permissions. Just throwing a few things out there, there are so many little things you could've possibly missed.
Click to expand...
Click to collapse
It turns out, I'm pretty stupid. Apparently didn't know how to spell DATA. That or it just started working randomly. However, when testing I still get "You have not subscribed to the Hotspot service"
I've checked and after the ##DATA# and entering my MSL I'm able to select the custom APN. It just wont allow tether. I don't know if it makes a difference, but I'm rooted on 7.0 Nougat S7 Edge
rideblue193 said:
It turns out, I'm pretty stupid. Apparently didn't know how to spell DATA. That or it just started working randomly. However, when testing I still get "You have not subscribed to the Hotspot service"
I've checked and after the ##DATA# and entering my MSL I'm able to select the custom APN. It just wont allow tether. I don't know if it makes a difference, but I'm rooted on 7.0 Nougat S7 Edge
Click to expand...
Click to collapse
double check the apn you selected, once you have the "dun" segment there it shouldn't say that. also might want to throw in a full powerdown and reboot, might be residual.
izzibew26 said:
double check the apn you selected, once you have the "dun" segment there it shouldn't say that. also might want to throw in a full powerdown and reboot, might be residual.
Click to expand...
Click to collapse
Thank you for the help. Without it and your guide I wouldn't have gotten it working. I combined your guide with another (both had different settings) and found a combination that works for me.
If anyone is having issues like I did, follow izzibew26's original guide, but instead Authentication Type: not set change to Authentication Type: None
This was also posted as a reply on the Pixel 2 XL Q&A forum here and I figured other T-Mobile Pixel 2 users would find this useful since this fix works on both the Pixel 2 and Pixel 2 XL.
Situation
My wife was unable to send MMSs on T-Mobile with her Pixel 2. Finally realized it had to do when connected to Wi-Fi, but only when connected to the EAP Wi-Fi at work. Since we work for the same company, I tested with my Pixel 2 XL and it is happening to me too. It works fine at home on our Wi-Fi and on the mobile network, but not when we are on our work's Wi-Fi. I can disable Wi-Fi at work and the MMS sends. Both phones have the same dysfunction. I normally use Google Voice and I never receive MMSs directly to my phone and had not noticed the issue up to this point.
I did a test where I added my Google Voice number and my wife's number in a group message with my phone's number and tested connecting on Wi-Fi, mobile network, and work Wi-Fi and every time we are on the work's Wi-Fi, MMSs fail to send or receive. I know it is happening to only Pixel 2s and no one else because my wife's previous phone, a T-Mobile Galaxy S7, worked fine on any network to send/receive MMSs. I have reset network settings and APN settings back to default, no change. From what research on the issue I could find, people were changing APN settings. Looking at the APN settings, I realized the two T-Mobile MMS listings have the APN listed as "TMUS," whereas the default APN is listed as "fast.t-mobile.com." Since "TMUS" is not a valid domain name, I changed the first T-Mobile MMS APN to fast.t-mobile.com and MMS started working on the work's Wi-Fi. I reset my APN settings back to default and it stopped working on my work's Wi-Fi again (as expected). I thought that I should leave the default APNs alone, just in case, and decided to create a third T-Mobile MMS APN with fast.t-mobile.com as the APN. This third T-Mobile MMS APN somehow allows MMSs to work on the company's Wi-Fi.
Fix
This fix seems to be the least amount of work and is very easily undone.
Go to Settings > Network & Internet > Mobile network > Access Point Names.
Tap on the 3 dot menu at the upper-right and select "Reset to default."
Create a new APN with the following settings:
Name: T-Mobile MMS
APN: fast.t-mobile.com
Proxy, Port, Username, Password, and Server: Not Set
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc (When typing this in, make sure auto correct doesn't change anything since URLs are case sensitive!)
MMS Proxy and MMS Port: Not Set
MCC: 310 (Should already be set)
MNC: 260 (Should already be set)
APN Type: mms
APN Protocol: IPv6
APN Roaming Protocol: IPv4
Bearer: Unspecified
MVNO Type: None
MVNO Value: Not Set
Tap on the 3 dot menu and select "Save."
Reboot your phone for good measure (may not be necessary) and open Android Messages.
Send a MMS or group MMS on and off the Wi-Fi network you are having issues on to see if it sends. If you have several queued up messages that haven't sent, you may need to tap to resend them and they may become out of order on the recipient's end.
If you ever wanted to undo these changes, you can either reset the APN settings or remove the fast.t-mobile.com one.
Conclusions
The main thing to note about this is that it is the same as the other T-Mobile MMS APNs, but has TMUS replaced with fast.t-mobile.com. If you look at the actual default fast.t-mobile.com APN, you'll notice that "mms" isn't listed among the others in APN Type. I feel, if I could edit that default fast.t-mobile.com APN, the problem would be fixed by adding ",mms" at the end. I assume one could duplicate everything in the default one and add it that way, but I wanted to provide the simplest, non-invasive fix possible that would not result in any future or unforeseen problems. When the phone/Google Messages/text message app consults the APNs while on an enterprise Wi-Fi connection, I assume it goes through each one to attempt to find one with MMS in the APN type and then attempts to contact the APN via its domain name, but fails since TMUS is not valid. I am not sure why it doesn't go ahead, verifies a working data connection, and then sends the MMS using http://mms.msg.eng.t-mobile.com/mms/wapenc as it seems to do fine on other Wi-Fi networks. The phones are like, "Whelp, I'm on an enterprise Wi-Fi connection and I need me an MMS APN with a FQDN or I aint workin'!" I do not know what makes my company's Wi-Fi so different from my home Wi-Fi aside from it using EAP authentication. This wasn't a problem on my wife's previous phone (T-Mo Galaxy S7). I had the 2016 Pixel for a while, but I use Google Voice and would not normally notice the MMS issues.
If anyone has a good theory as to wth is going on, please contribute! I think its some sort of wonky Oreo issue. I hope this helps anyone who was as frustrated as I was!
Every family group text used to be a nightmare. This solved all my MMS maladies. Thank you for the nice writeup!
Hi all,
Prior to today, my wife's Pixel 2 had been working fine using cellular data and MMS on an AT&T MVNO - Airvoice Wireless. This morning I Installed the November security update. This afternoon, cellular data was not working. Found out that the Airvoice Wireless APN was missing from the phone's set up. Tried entering it several times but each time when I pressed 'Save' there was no AV APN. Tried again entering a few settings at a time. All was good until I changed the second to last APN setting, ' MVNO type', from the default entry of 'GID', to 'None'. As soon as I changed the entry to 'None' and saved the APN, the AV Wireless APN disappeared. I reentered the APN settings yet again and left MVNO type set to GID. Data works, but MMS does not.
I know that when I initially set up the phone, MVNO type was set to 'None' per the recommended AV settings. Its set to None on my Nexus 5X and everything works. Something has changed, and I am assuming that the latest security update is the cause.
I've Googled MVNO type but haven't really found an explanation for the MVNO type settings options. In addition, when any of the available options other than None is selected; SPN, IMSI, or GID, another field, 'MVNO value' becomes active. It has a 4 digit hex number and I have no idea what it needs to be set too.
Next steps will be to call AV customer support and/or Google support. (Really hoping I don't have to do a factory reset)
I want to see if anyone else has experienced this issue or has any recommendations.
Thanks in advance for the assistance.
Frank
Same problem here. I use Consumer Cellular that uses ATT towers and APN was gone
Called Google and they admitted to the problem. Tried to get me to reset it or send me a another phone.
I just went to Consumer Cellular web site and found the APN and created a new one
Running ok now
BTW the way I left MVNO type as GID and appears to be ok ...My 5x APN is fine