Bought my wife an I9505G. We have AT&T service in Denver, CO. When we got the device, it didn't have 4.3 on it, and it prompted soon after we had it on our WiFi. We went to a local AT&T store to get a new SIM card. We received a new SIM (as her old SIM was from a SGH-I777 Galaxy S2) and LTE is showing on the status bar. She has had issues receiving and sending MMS messages. Chomp was telling her that the APN settings were wrong. I had forgotten to put any APN settings in the phone, and the AT&T rep didn't enter any either. He probably thought that I'd do it since I bought the phone. So I Googled which APN settings to use. Here's what is selected now:
Name: AT&T PTA
APN: pta
Proxy: NOT SET
Port: NOT SET
Username: NOT SET
Password: NOT SET
Server: NOT SET
MMSC: http://mmsc.mobile.att.net
MMS Proxy: proxy.mobile.att.net
MMS Port: 80
MCC: 310
MNC: 410
Authentication Type: None
APN type: default,admin,fota,mms,supl,hipri
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
Bearer: Unspecified
MVNO type: None
What's strange is that if I turn off WiFi, I can send MMS picture messages from the phone and receive them on the phone. It's very odd. When I turn WiFi back on, I'm unable to send or receive MMS pictures on the GS4. Again, I'm running 4.3. My BaseBand version is I9505GUEUBMH5
Has anyone else seen this issue? Am I using the wrong APN for AT&T? Thanks!
EDIT: I'm adding my SpeedTest results using the app. 10.33Mbps Down, 2.59Mbps Up.
My wife was able to successfully send me an MMS picture message from her school's WiFi network. She confirmed she was able to surf on their WiFi first before sending the MMS. This really does point a finger at the DD-WRT firmware running on my WRT-54G Linksys router. This thread is the only thread I could find that sounded similar to my issue.
Also, I forgot to post what my APNs are currently. I found them in this thread.
Code:
**NOTE: All unmentioned fields should read "<Not set>".
APN 1 (Up to 3.5G HSDPA/HSUPA only, 7.2mbps):
Name: Cingular
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,fota,dun
APN 2 (Up to 3.75G HSPA+ only, 21mbps):
Name: AT&T HSPA+
APN: phone
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,dun
APN 3 (LTE, ALL THE mbps):
Name: AT&T LTE
APN: pta
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,hipri,internet
APN 4:
Name: Cingular MMS
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
MMSC: http://mmsc.cingular.com
MMS proxy: wireless.cingular.com
MMS port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: mms
APN 5:
Name: AT&T LTE MMS
APN: pta
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: hipri,mms
Has anyone seen this issue? Thanks!
Update
I've tried other APNs, but that wasn't solving the issue. Wife can send MMS on _any_ other network except ours. That's not an APN setting, that's a weird network issue. Based on the link I gave you guys in the first post, I thought, maybe DD-WRT was the issue. The DD-WRT device I have is only acting as an AP in my network. I have pfSense as the router for my network.
I just picked up a new Asus RT-AC66U yesterday, set it up as AP only and connected the wife's phone. Her phone wasn't sending or receiving MMS with the new AP. The phone still has 3 of 4 bars available right now when it won't send an MMS. Then I thought, let's take the pfSense box out of the mix. So I tried hooking the RT-AC66U up as the default router/firewall/AP. I reconnected both phones back to its 5GHz SSID. I was able to send and receive MMS pictures on the wife's phone. It started looking like an issue with my pfSense firewall. Then, I realized that my home network's IP range is 10.0.0.0/24. AT&T’s LTE network is also in the 10.x.y.z range. Its probably not the exact range I have at home, but its close. When I tried the Asus router, it defaulted to a 192.168.1.0/24 network. So I tried to set my pfSense box to the same range. I had issues with the router taking that range. It would serve out dhcp on that range, but I couldn't ping anything outside. I have no idea why. It got late last night, so I reset back to my default 10.0.0.0/24.
Today, I plan on backing up the pfSense config, issuing a factory reset and running stock at 10.0.0.0/24 and see if the issue still happens. If it does, I'll factory reset again, and try 192.168.1.1/24. We'll see which one works.
SOLVED!
I have finally solved the issue. I'm so happy it's fixed. For those that happen upon this thread, here's what I did:
Since I had nothing blocked in the firewall rules, and I had Outbound Manual NAT enabled that wasn't the issue. I was in the #pfsense channel, and someone happened to come in complaining about not a ping not resolving. Specifically, he was trying to ping:
Code:
ping some_DNS_name_on_internet
It was supposed to resolve to a PRIVATE IP address, in his case, 10.0.0.1. I could get it to resolve from my work connection (not behind pfSense). So I began pinging the MMSC and MMS addresses in the APNs I listed earlier. All of them resolved and/or responded, except one:
Code:
proxy.mobile.att.net
Behind the pfSense 2.1 firewall, it wouldn't resolve. From anywhere else (from the phone disconnected from WiFi, from my office network) that address would resolve:
Code:
$ ping proxy.mobile.att.net
PING proxy.mobile.att.net (172.26.39.1) 56(84) bytes of data.
^C
--- proxy.mobile.att.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
But look at the address it was resolving to! I thought that since I had disabled blocking RFC1918 on my WAN port and LAN port, the address would have resolved. It didn't. The user in #pfsense said that it's not a bug, but a feature of dnsmasq and that pfSense was "protecting us from ourselves". Very strange I thought. But what's even stranger, was the fact that AT&T was deliberately resolving a DNS name to an RFC 1918 address on the PUBLIC internet. My only guess is that the phone will try the WiFi first, find that this address resolves to 172.26.39.1 address, then use it's LTE radio to connect to the address since it's all on AT&T's network anyway. Probably a static route on the LTE radio? No idea.
Since it was clear that pfSense wasn't resolving this address correctly, I decided to put a "Host Over Ride" in the Services: DNS Forwarder. I added this:
Code:
proxy mobile.att.net 172.26.39.1 AT&T MMS Proxy
Once I did that, everything worked as expected. She can send and receive MMS. It was amazing. I've been struggling with this for a week, and now it's working. That also means I can go buy _me_ the same phone
I really hope that my struggles can help someone in the future.
Nice debug work!
Sent from my Nexus 7 using XDA Premium HD app
Thank you again!! I thanked you on the other forum but wanted to here as well so others that may experience this know it does fix it.
This must be an android 4.3 issue as my ATT GS4 running 4.2.2 doesn't experience this.
Thanks,
Mike
CNLiberal said:
SOLVED!
I have finally solved the issue. I'm so happy it's fixed. For those that happen upon this thread, here's what I did:
Since I had nothing blocked in the firewall rules, and I had Outbound Manual NAT enabled that wasn't the issue. I was in the #pfsense channel, and someone happened to come in complaining about not a ping not resolving. Specifically, he was trying to ping:
Code:
ping some_DNS_name_on_internet
It was supposed to resolve to a PRIVATE IP address, in his case, 10.0.0.1. I could get it to resolve from my work connection (not behind pfSense). So I began pinging the MMSC and MMS addresses in the APNs I listed earlier. All of them resolved and/or responded, except one:
Code:
proxy.mobile.att.net
Behind the pfSense 2.1 firewall, it wouldn't resolve. From anywhere else (from the phone disconnected from WiFi, from my office network) that address would resolve:
Code:
$ ping proxy.mobile.att.net
PING proxy.mobile.att.net (172.26.39.1) 56(84) bytes of data.
^C
--- proxy.mobile.att.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
But look at the address it was resolving to! I thought that since I had disabled blocking RFC1918 on my WAN port and LAN port, the address would have resolved. It didn't. The user in #pfsense said that it's not a bug, but a feature of dnsmasq and that pfSense was "protecting us from ourselves". Very strange I thought. But what's even stranger, was the fact that AT&T was deliberately resolving a DNS name to an RFC 1918 address on the PUBLIC internet. My only guess is that the phone will try the WiFi first, find that this address resolves to 172.26.39.1 address, then use it's LTE radio to connect to the address since it's all on AT&T's network anyway. Probably a static route on the LTE radio? No idea.
Since it was clear that pfSense wasn't resolving this address correctly, I decided to put a "Host Over Ride" in the Services: DNS Forwarder. I added this:
Code:
proxy mobile.att.net 172.26.39.1 AT&T MMS Proxy
Once I did that, everything worked as expected. She can send and receive MMS. It was amazing. I've been struggling with this for a week, and now it's working. That also means I can go buy _me_ the same phone
I really hope that my struggles can help someone in the future.
Click to expand...
Click to collapse
mjolsen said:
Thank you again!! I thanked you on the other forum but wanted to here as well so others that may experience this know it does fix it.
This must be an android 4.3 issue as my ATT GS4 running 4.2.2 doesn't experience this.
Thanks,
Mike
Click to expand...
Click to collapse
That or AT&T actually found this issue and forced Samsung to add it to TouchWiz. My buddy with the stock AT&T GS4 TW tested and didn't have the same issue either (behind a pfSense fw).
I wish I could help the other guy out. Hopefully, he starts pinging and finds a different DNS name that's not resolving.
Sent from my Nexus 7 using Tapatalk now Free
How do fix with DD-WRT instead of pfsense?
CNLiberal said:
SOLVED!
I have finally solved the issue. I'm so happy it's fixed. For those that happen upon this thread, here's what I did:
Since I had nothing blocked in the firewall rules, and I had Outbound Manual NAT enabled that wasn't the issue. I was in the #pfsense channel, and someone happened to come in complaining about not a ping not resolving. Specifically, he was trying to ping:
Code:
ping some_DNS_name_on_internet
It was supposed to resolve to a PRIVATE IP address, in his case, 10.0.0.1. I could get it to resolve from my work connection (not behind pfSense). So I began pinging the MMSC and MMS addresses in the APNs I listed earlier. All of them resolved and/or responded, except one:
Code:
proxy.mobile.att.net
Behind the pfSense 2.1 firewall, it wouldn't resolve. From anywhere else (from the phone disconnected from WiFi, from my office network) that address would resolve:
Code:
$ ping proxy.mobile.att.net
PING proxy.mobile.att.net (172.26.39.1) 56(84) bytes of data.
^C
--- proxy.mobile.att.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
But look at the address it was resolving to! I thought that since I had disabled blocking RFC1918 on my WAN port and LAN port, the address would have resolved. It didn't. The user in #pfsense said that it's not a bug, but a feature of dnsmasq and that pfSense was "protecting us from ourselves". Very strange I thought. But what's even stranger, was the fact that AT&T was deliberately resolving a DNS name to an RFC 1918 address on the PUBLIC internet. My only guess is that the phone will try the WiFi first, find that this address resolves to 172.26.39.1 address, then use it's LTE radio to connect to the address since it's all on AT&T's network anyway. Probably a static route on the LTE radio? No idea.
Since it was clear that pfSense wasn't resolving this address correctly, I decided to put a "Host Over Ride" in the Services: DNS Forwarder. I added this:
Code:
proxy mobile.att.net 172.26.39.1 AT&T MMS Proxy
Once I did that, everything worked as expected. She can send and receive MMS. It was amazing. I've been struggling with this for a week, and now it's working. That also means I can go buy _me_ the same phone
I really hope that my struggles can help someone in the future.
Click to expand...
Click to collapse
Does anyone know how to make the same above fix when using DD-WRT instead of pfsense?
Augestflex said:
Does anyone know how to make the same above fix when using DD-WRT instead of pfsense?
Click to expand...
Click to collapse
A quick Google search revealed these links:
http://www.dd-wrt.com/wiki/index.php/DNSMasq_-_DNS_for_your_local_network_-_HOWTO
http://www.dd-wrt.com/phpBB2/viewto...previous&sid=243a53e3e59317ddc85602bf85dfa997
CNLiberal said:
My wife was able to successfully send me an MMS picture message from her school's WiFi network. She confirmed she was able to surf on their WiFi first before sending the MMS. This really does point a finger at the DD-WRT firmware running on my WRT-54G Linksys router. This thread is the only thread I could find that sounded similar to my issue.
Also, I forgot to post what my APNs are currently. I found them in this thread.
Code:
**NOTE: All unmentioned fields should read "<Not set>".
APN 1 (Up to 3.5G HSDPA/HSUPA only, 7.2mbps):
Name: Cingular
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,fota,dun
APN 2 (Up to 3.75G HSPA+ only, 21mbps):
Name: AT&T HSPA+
APN: phone
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,dun
APN 3 (LTE, ALL THE mbps):
Name: AT&T LTE
APN: pta
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: default,agps,supl,hipri,internet
APN 4:
Name: Cingular MMS
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
MMSC: http://mmsc.cingular.com
MMS proxy: wireless.cingular.com
MMS port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: mms
APN 5:
Name: AT&T LTE MMS
APN: pta
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MMS protocol: WAP 2.0
MCC: 310
MNC: 410
APN type: hipri,mms
Has anyone seen this issue? Thanks!
Click to expand...
Click to collapse
Thank you!!! That worked on my dd-wrt, i manually added a dns entry pointing that hostname to that IP and I am now good. You rock.
CNLiberal said:
A quick Google search revealed these links:
http://www.dd-wrt.com/wiki/index.php/DNSMasq_-_DNS_for_your_local_network_-_HOWTO
http://www.dd-wrt.com/phpBB2/viewto...previous&sid=243a53e3e59317ddc85602bf85dfa997
Click to expand...
Click to collapse
Thanks, I had actually searched google several times, but did not realize that changing/adding an A record was the same as what I needed to do.
Thanks for the tip.
Augestflex said:
Thanks, I had actually searched google several times, but did not realize that changing/adding an A record was the same as what I needed to do.
Thanks for the tip.
Click to expand...
Click to collapse
So that worked for you, too? My Nexus 5 should arrive this week, and I'm hoping it'll "just work" with the APNs I listed above and the change on the firewall.
Hello guys I need your help my 1+5 8GB model is having issues with few of my gaming apps that requires network connection (Mobile Legends, Marvel).
I'm on T-Mobile network, it works flawlessly in my S8+. But when I used it to my 1+5 I get network errors in my games and some social media apps too. I tried making another apn. The results are still the same. ?
Hi, I was looking for a post that can be related with my issues. You have this issue only with Cellular DATA? My issues is that some APPS don't detect a network connection. The built-in VPN is one of them and the other one is CSIP, my VOIP client. See if you can configure a VPN connection on your phone, it doesn't matter the server or credentials. If you have the same issue it won't even try to connect. All my APPs work fine on Wifi, it is just on Cell DATA where I experience this issue.
Try setting APN Protocol to IPv4 or IPv4/IPv6. See if that helps. You may need to create a new APN setting.
jbdrthapa said:
Try setting APN Protocol to IPv4 or IPv4/IPv6. See if that helps. You may need to create a new APN setting.
Click to expand...
Click to collapse
I did exactly what you said and it works. The problem is the the APN automatically assigned has APN protocol on IPV6. I checked another T-Mobile SIM on a OP2 and it has many more APN options than my OP5. And the one my OP5 uses with IPV6 the OP2 has it IPV4/IPV6. Thank you so much for the info.
Awesome
I have a note 20 ultra purchased on xfinity mobile, fully paid and unlocked. I switched to Google Fi for a month and now switched to Verizon. When I was on xfinity mobile and google fi, my network settings would correctly show the carrier name. Now that I have a verizon SIM in my phone, the phone says xfinity mobile again. All services work correctly and I have contacted xfinity to confirm that the device is not registering on their service, so it is definitely going through Verizon, but still showing xfinity mobile. Do I need to flash either Verizon or unlocked firmware? Reset network settings? Any information would be very helpful.
Xfinity uses Verizon's network, so it's possible it thinks it's back on Xfinity. I would suggest resetting network first and see if the name is corrected.
rjohnstone said:
Xfinity uses Verizon's network, so it's possible it thinks it's back on Xfinity. I would suggest resetting network first and see if the name is corrected.
Click to expand...
Click to collapse
Network settings have now been reset and the phone has been restarted. The network name still shows as xfinity mobile. Is the network name itself likely aesthetic as long as the phone appears to be running on the correct network?
DankDano said:
Network settings have now been reset and the phone has been restarted. The network name still shows as xfinity mobile. Is the network name itself likely aesthetic as long as the phone appears to be running on the correct network?
Click to expand...
Click to collapse
Network name is typically set by the SIM card. You may also want to verify you're using a Verizon APN setting and not Xfinity.
Beyond that, flashing a Verizon branded firmware will do it, but it really shouldn't come to that.
rjohnstone said:
Network name is typically set by the SIM card. You may also want to verify you're using a Verizon APN setting and not Xfinity.
Beyond that, flashing a Verizon branded firmware will do it, but it really shouldn't come to that.
Click to expand...
Click to collapse
The attached screenshot is my current APN. Adding one is grayed out.
DankDano said:
The attached screenshot is my current APN. Adding one is grayed out.
Click to expand...
Click to collapse
It thinks it's still on the Xfinity MVNO connection.
Edit your existing or add a new APN and set it to active.
Name: VZW
APN: vzwinternet
Proxy:
Port:
Username:
Password:
APN: vzwinternet
Proxy:
Port:
Username:
Password:
Server:
MMSC: http://mms.vtext.com/servlets/mms
MMS proxy:
MMS port: 80
MCC:
MNC:
Authentication type:
APN type: default,supl,mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
APN PPP phone number: Not set