Solution to those having MMS problems HTC Magic, Android phones in general - myTouch 3G, Magic General

Hi all,
After several ROM flashes later I finally realised that the problems I was having with sending/receiving MMS was not the ROM's fault at all. For some crazy reason you need to specify any IP addresses in the APN settings with leading zero's to make each segment 3 digits long.
E.g. 010.176.057.025 instead of just 10.176.57.25
E.g. On the Three Network in Australia you can set up your Internet/MMS APN in the one APN profile:
Name: 3services
APN: 3services
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: http://mmsc.three.net.au:10021/mmsc
MMS proxy: 010.176.057.025
MMS port: 8799
MCC: 505
MNC: 06
APN type: <Not set>
Hope this helps everyone else with MMS problems!

Related

Problem with AT&T and MMS

hehe so... got my happy self onto CM6 and fiddled around with some MMS threads here and there and everywhere to find out the APN settings... No dice on MMS
Then I plugged this in and it works for me
Name: wap.cingular
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
username: [email protected]
Pasword: CINGULAR1
Server: wireless.cingular.com
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS: Port: 80
MCC: 310
MNC: 410
Authentication type: <not set>
APN Type: <not set>
Then after saving it, I power cycled it and once I came back It's all good
hehe don't mean to be all repeatitive with the threads on the board kinda had to rip the settings from my t-mo wing.

Official (direct from TMOUS) MMS Settings

I flashed to the NAND rom, and of course, needed the correct APN settings. I've seen a number of requests for assistance, so here's what I got direct from the TMOUS tech support.
1. You need TWO APN's in there. One will be called T-Mobile Data and the other will be T-Mobile MMS
2. go to settings, wireless networks, Mobile networks, Access Point Names
3. click on the menu button and reset to default so that you can start from scratch.
4. once cleared, click on menu and then new APN
5. Name the new APN T-Mobile Data
6. Once created, click on it, and go into it. Fill in as follows... if it says <not set> below, this means skip it and do not touch it or change it in anyway
Name: T-Mobile Data
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: <not set>
Password: <not set>
Server: <not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: <not set>
MMS Port: <not set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
Authentication type: <not set>
APN type: <not set>
Once done with the above, back out, and hit the menu and add a new APN. This new APN will be called T-Mobile MMS. Once created, go into as you did above, and the settings will be virtually identical with the APN type: mms See below:
Name: T-Mobile MMS
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: <not set>
Password: <not set>
Server: <not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: <not set>
MMS Port: <not set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
Authentication type: <not set>
APN type: mms
Now back out of that, and you will see the two APNS listed. Only ONE will have the radio button available for you to select to activate. When you click the button, it will activate and light up green. When you do this, the 3G/H symbol may disappear for a second. Back out of there twice, and check to make sure that Mobile Network has a check mark next to it, and "Connected" Appears under that. If you see "connection failed" then it's a good idea to reboot your phone. Once you reboot, you can test MMS capability by simply sending yourself a picture message.
Have fun and say thanks.
Are you implying that it auto-switches between the two? If so then this is a fantastic discovery. Otherwise I truely see no real need for 2 APN's..
This actually makes sense. We were discussing mms on prepaid without data and it works, so we're pretty sure it goes through t-zones to send mms. The winmo roms probably do have code in them that automatically switches to send, not sure if android roms can figure it out, maybe the nexus one builds can.
Nothing to do with figuring anything out. Look at the last line of each settings, apn type.
The mms one should have "apn type mms ", whilst the data one ends " apn type default,supl "
So a default data type app like browser uses the default apn,mms uses the mms apn, and Supl I think is to do with quick GPS.
mms
I tried these settings..can send text..but cant send a picture.....any thoughts?

My MMS has stopped sending. Any suggestions?

MMS stopped sending pics a day or two ago. Does the 'sending spin dance'.
Any suggestions really appreciated.
Thanks
Check your MMS settings to see if they are correct for your carrier
Sent from my GT-I9100 using Tapatalk
I'm using Att and just have 'automatically select preferred network'
I had the problem last month. Try typing phone number manually no dashes or brackets. If it goes through just use the contacts cleanup App and fix your contacts.
Mike
have you checked the actual APN settings for our carrier? I have had it in the past when the settings get messed up.
Settings>Wireless&Networks>Mobile Networks>Access Point Names>select your APN which I assume is called ATT (or maybe Cingular by the looks of the settings I found on net) and check the settings are correct, mainly MMSC for MMS.
From looking on the net the settings should look something like this
Name: Cingular 410
APN: wap.cingular
Proxy: <Not set>
Port: <Not set>
Username: [email protected]
Password: CINGULAR1
Server: <Not set>
MMSC: http://mmsc.cingular.com/
MMS proxy: wireless.cingular.com
MMS port: 80
MCC: 310
MNC: 410
Authentication type: <Not set>
APN type: <Not set>
Worth a check.
Thank you. Those settings did it. Wonder how they got messed up?!
I copied and saved them.
Thanks again
richiewill83 said:
have you checked the actual APN settings for our carrier? I have had it in the past when the settings get messed up.
Settings>Wireless&Networks>Mobile Networks>Access Point Names>select your APN which I assume is called ATT (or maybe Cingular by the looks of the settings I found on net) and check the settings are correct, mainly MMSC for MMS.
From looking on the net the settings should look something like this
Name: Cingular 410
APN: wap.cingular
Proxy: <Not set>
Port: <Not set>
Username: [email protected]
Password: CINGULAR1
Server: <Not set>
MMSC: http://mmsc.cingular.com/
MMS proxy: wireless.cingular.com
MMS port: 80
MCC: 310
MNC: 410
Authentication type: <Not set>
APN type: <Not set>
Worth a check.
Click to expand...
Click to collapse
Excellent
Glad your sorted.
Not sure why they get messed up.
Sent from my GT-I9100 using xda premium

Cannot receive MMS on CM 7.1 (error mentions picture resolution or size)

Hi guys,
I'm not able to receive any MMS at all. I can send MMS, but when receiving, I get error message "The media content was not included due to a picture resolution or message size restriction".
Any ideas?
This is for TMobile USA
- Dan
HBOOT - 0.84.2000 (HBOOT from Desire Z)
Radio - 26.02.01.15_M2
ROM: Latest Kang of CM 7.1 (labeled as CM 7.2 RC0)
APN Settings for TMobile: (default APN settings)
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
username: None
password: ****
Server: *
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: <not set>
MMS Port: <not set>
MCC: 310
MNC: 260
Authentication Type: <not set>
APN Type: default, supl, mms
APN Protocal: IPv4

Getting VoLTE & Wifi Calling to work with Metro PCS SIM

I just recently got my Nexus 6p about a week ago. I was hoping since I have Metro PCS which is owned and operated by T-Mobile. I have the "WiFi calling" option enabled and as well the "enhanced 4g" option enabled for VoLTE. However neither Wifi Calling or VoLTE work. I found some other threads with the same issue and I tried the configurations suggested bit still I get neither feature to work. This is av real disadvantage since there areas in my home that have unreliable cell signal. Can anyone please help.?
sbonhomme said:
I just recently got my Nexus 6p about a week ago. I was hoping since I have Metro PCS which is owned and operated by T-Mobile. I have the "WiFi calling" option enabled and as well the "enhanced 4g" option enabled for VoLTE. However neither Wifi Calling or VoLTE work. I found some other threads with the same issue and I tried the configurations suggested bit still I get neither feature to work. This is av real disadvantage since there areas in my home that have unreliable cell signal. Can anyone please help.?
Click to expand...
Click to collapse
Have you set an E911 address for your account (or line) on the Metro website?
I had to do this on My T-Mobile site, and wait until the next day before it started to work.
It's a known issue with both TMO and METRO for Wi-Fi calling.
I did do that like 5 times and a confirmation text from metro that it has been stored but still nothing
Use the metro pcs APN name and the T-Mobile mmsc.
Where is says mvno type put none.
You may want try using the 3 T-Mobile ones. The second one is what is used for Wi-Fi calling.
Name: T-Mobile GPRS
APN: fast.t-mobile.com
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: default,supl
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Name: T-Mobile IMS
APN: ims
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: ims
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Name: T-Mobile MMS
APN: TMUS
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: mms
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
sbonhomme said:
I did do that like 5 times and a confirmation text from metro that it has been stored but still nothing
Click to expand...
Click to collapse
SpookyTunes said:
You may want try using the 3 T-Mobile ones. The second one is what is used for Wi-Fi calling.
I tried this and it worked to my surprise but only for a few minutes. Any other ideas?
Click to expand...
Click to collapse
You most likely connected to, and booted from T-Mobile's server. I would go to APN settings and do a reset (from the 3 dots menu).
If none of the default ones have an entry for ims under APN type, try adding this one;
NOTE: if the other(s) have APN protocol set to IPv4, use that, if IPv6, then use that instead. It may take some experimentation to get a working configuration.
Name: MetroPCS IMS
APN: ims.metropcs
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: ims
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
SpookyTunes said:
You most likely connected to, and booted from T-Mobile's server. I would go to APN settings and do a reset (from the 3 dots menu).
If none of the default ones have an entry for ims under APN type, try adding this one;
NOTE: if the other(s) have APN protocol set to IPv4, use that, if IPv6, then use that instead. It may take some experimentation to get a working configuration.
Name: MetroPCS IMS
APN: ims.metropcs
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: ims
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Click to expand...
Click to collapse
I just tried what you suggested and it doesn't seem to work. It dosent show Wifi Calling.
sbonhomme said:
I just tried what you suggested and it doesn't seem to work. It dosent show Wifi Calling.
Click to expand...
Click to collapse
You may want to contact MetroPCS and confirm that your account is provisioned for W-Fi calling (IMS), and if so, what the correct APN settings are. I am on T-Mobile postpaid, so it just worked after the E911 address was set.
SpookyTunes said:
You most likely connected to, and booted from T-Mobile's server. I would go to APN settings and do a reset (from the 3 dots menu).
If none of the default ones have an entry for ims under APN type, try adding this one;
NOTE: if the other(s) have APN protocol set to IPv4, use that, if IPv6, then use that instead. It may take some experimentation to get a working configuration.
Name: MetroPCS IMS
APN: ims.metropcs
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: ims
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Click to expand...
Click to collapse
SpookyTunes said:
You may want to contact MetroPCS and confirm that your account is provisioned for W-Fi calling (IMS), and if so, what the correct APN settings are. I am on T-Mobile postpaid, so it just worked after the E911 address was set.
Click to expand...
Click to collapse
I'll give that a shot.
I called metro customer service and they manually entered my e911 address the rep told me after 30 minutes it should say start working. A few hours went by and still nothing. It doesn't seem to work. I don't know what to do next I really need this feature.
sbonhomme said:
I called metro customer service and they manually entered my e911 address the rep told me after 30 minutes it should say start working. A few hours went by and still nothing. It doesn't seem to work. I don't know what to do next I really need this feature.
Click to expand...
Click to collapse
I finally got it to work. I'm on the newest build from google (MHC19I) and downloaded the mymetro app from the play store, and updated my e911 address from the app. Next I went to the apns in the settings menu, and deleted all the metro apns than 3 t-mobile apns was present and I selected the 2nd apn which is ims and rebooted the phone. Vote is working flawlessly for the last few hours, hope this helps anyone that needs it.
Just got my Nexus 6p and am having the same issue. Can you confirm this APN currently works?
EDIT:
This method worked for me
1. Submit your e911 address to metropcs. You can the my metro app from the playstore or call customer service and give it to them so they can put it in the system manually.
2. Go into the apn settings and maually delete each default metro pcs apn one by one. After deleteing them you should notice that the apns will default to showing t-mobile's apn settings. (Ex: T-MobileGPRS, T-Mobile IMS, T-Mobile MMS)
3. Click on the first apn that says "T-MobileGPRS" that is the setting that will edit. The other apns you can leave as is.
4. Once in the T-MobileGPRS setting change the Name from T-MobileGPRS to "MetroPCS".
5. Change the the APN from fast.tmobile.com to "fast.metropcs.com" . Leave all other settings as is and then save the changes.
6. Restart
Sent from my Nexus 6P using XDA-Developers mobile app
I'm thinking about taking my 6P to MetroPCS. Can anyone confirm that all these features are working correctly at this point in time? TIA.
Sent from my Nexus 6P using Tapatalk
Same for my pixel?
Hello,
I've got an s7 running nougat, going between lineage and crDroid roms running Nougat. I thought I had VoLTE and WiFi calling enabled, the options are on in my settings, calling is set to WiFi prefered, but then I was told that ims is where it's all at, and as the poster who told me this in another group, was quite right, I was wondering if anyone had an s7 going with MetroPCS and VoLTE, WiFi calling, and IMS working successfully? For completeness I've added these lines to my /system/build.prop file:
#ifdef VENDOR_EDIT
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
# persist.data.iwlan.enable=true
#endif
Thanks.
Got Wifi Calling working on Nexus 6p
Looks like this one is a winner for me! Added the T-Mobile IMS APN and Wifi Calling is back on my Nexus 6p. Thanks for the help!
SpookyTunes said:
You may want try using the 3 T-Mobile ones. The second one is what is used for Wi-Fi calling.
Name: T-Mobile GPRS
APN: fast DOT t-mobile DOT com
Click to expand...
Click to collapse
SpookyTunes said:
You may want try using the 3 T-Mobile ones. The second one is what is used for Wi-Fi calling.
Name: T-Mobile GPRS
APN: fast.t-mobile.com
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: default,supl
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Name: T-Mobile IMS
APN: ims
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: ims
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Name: T-Mobile MMS
APN: TMUS
Proxy: <Not set>
Port: <Not set>
Username: <Not set>
Password: <Not set>
Server: <Not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication Type: <Not set>
APN type: mms
APN protocol: IPv6
APN roaming protocol: IPv4
Bearer: <Unspecified>
MVNO type: <None>
MVNO value: <Not set>
Click to expand...
Click to collapse
Works! Thanks

Categories

Resources