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.
Related
I have a 5.5 on EE in the uk which connects fine. My wife however, has the 4.7 version and is with talkmobile in the uk. Everything (calls, texts etc.) works correctly except Mobile Internet - if I turn Wifi off I can't use the internet. Mobile data is switched on. I spent an hour with "support" on the talkmobile website chat, resetting APN, entering a new APN with the following settings:-
Name - Talkmobile
APN - talkmobile.co.uk
APN type - internet+mms
...but that didn't work
I also tried with the following settings from geeksquad website but they didn't work either.
Name - Talkmobile
APN - talkmobile.co.uk
MMSC - http://mms.talkmobile.co.uk/servlets/mms
MMS Proxy - 212.183.137.12
MMS Port - 8799
APN type - If given a choice, select internet+mms, if the keyboard appears enter *
Grateful for any ideas.
I had sim issues with Tpo network in UK they use ee network and as APN default can't be edited no idea why its hard to add APN every time tried didn't show if i reset defaults and select cancel rather than ee or life mobile I could then add a new APN but still not able to edit default APN I find that bit odd ,
Sent from my 6045Y using Tapatalk
We gave up on talkmobile, whatever settings we tried with tm support we couldn't get it to work. Switched to Virgin and everything good now.
My Problem(s)::crying:
SMS messages give an immediate error that they could not be sent. MMS messages say sending for many minutes before finally giving the same error.
Did it ever work?
Yes. I had sent and received SMS messages after flashing. Cannot confirm MMS, becuase I had not used it since flashing my ROM.
What precipitated / brought the problem to the fore?
I was trying to get Sprint voicemail working on my recently flashed phone ([ROM][OFFICIAL][KitKat 4.4.4][moto_msm8960_jbbl] PAC-ROM 4.4.4.RC-2). I tried several apk's for Sprint's Visual Voice. I could not get 5.x or 6.x to work. After following a few dead end threads with those, I installed Google Voice and was trying to use it for my Sprint voicemail. With each of these I uninstalled and rebooted before going on the next try.
I see threads about Google Hangouts causing problems with Sprint SMS /MMS. It is installed, but I am unfamiliar with the App because I have never used it. I think it is only there because Google Voice needs it.
I have used Google Voice on my laptop to call Red Pocket Mobile when I need to troubleshoot my phone. So, before I installed it on my phone I already had it set up in my google account. Not sure how/why that matters, but there is the possibiltiy that some configuration setting in my account is wrong for integrating with my XT897.
Basic Troubleshooting Info:
I can do any of these without a problem on wi-fi or LTE: Google Play Store, Chrome, Firefox, etc. I am also able to make and receive voice calls.
In PAC-ROM:
Settings - Wireless Networks - More... -
Default SMS app is set to Messaging
Voice+:
Setting this to Disabled and rebooting does not fix
Setting this to my Google Voice gmail account does not fix
u need to set the APN for MMS i think.
Settings->Network Settings->APN
there you need to add a Entry
for SMS iam not sure
APN Info
huhu1312 said:
u need to set the APN for MMS i think.
Settings->Network Settings->APN
there you need to add a Entry
for SMS iam not sure
Click to expand...
Click to collapse
SMS was working with the APN I created for Red Pocket Mobile before I started trying to get my voice mail to work.
Here is the APN I created for Red Pocket Mobile:
Name: Red Pocket
APN: n.r6.ispsn
Proxy: Not set
Port: not set
username: [my_cell_number]@redpocket.sprintpcs.com
Password: not set
Server: not set
MMSC: http//mms.sprintpcs.com
mms proxy: 68.28.31.7
mms port: 80
MCC: 310
MNC: 120
Authentication Type: Not set
APN type: default,mms
APN protocol: IpV4/ipV6
APN roamingprotocol : IpV4/ipV6
you changed your network?
if u are on sprint now u need to set this apn
Name Sprint
APN cinet.spcs
Proxy blank
Username blank
Password blank
Server blank
MMSC http://mms.sprintpcs.com/servlets/mms
MMS Proxy 68.28.31.7 6
MMS Port 80
MMC 234
MNC 15
Authentication type not set
APN Type internet + mms
APN Protocol IPv4
APN enable/disable blank
Read more at: http://www.4gtricks.com/2014/08/sprint-apn-settings-sprint-4g-apn-settings.html
huhu1312 said:
you changed your network? ...
Click to expand...
Click to collapse
No, my phone company is Red Pocket Mobile. They are a Sprint MVNO.
Yesterday evening I was out for work. I received an SMS message on my phone. I noticed that my phone was showing 4 bars of signal. I only usually see 1 or 2 at my house. I thought that might be the problem. Unfortunately, I tried sending and got the same errors for SMS and MMS even with 4 bars of signal.
This morning, I installed Network Cell Info Mini in my phone just now using LTE. It shows I have +-100 dBm of signal. Trying to send MMS over the same network still produces the same error.
I also found this thread of similar problems in Sprint's forums.
I would recommend restoring stock, make sure EVERYTHING works that you need to work before flashing any aftermarket ROM.
If it all works on the stock ROM, then you know you have a software configuration issue / limitation.
arrrghhh said:
I would recommend restoring stock, make sure EVERYTHING works that you need to work before flashing any aftermarket ROM.
If it all works on the stock ROM, then you know you have a software configuration issue / limitation.
Click to expand...
Click to collapse
Sorry it took so long to post a follow-up on this. I finally had time to meticulously do this.
This is what I did that worked:
1. flashed my rooted Jelly Bean stock ROM back on with TWRP
2. after i booted up i updated the PRL then successfully sent and received a txt
3. flashed back my pac-rom
4. after rebooting, successfully sent and received a txt :victory:
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
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