[Solved] Bluetooth tethering on GSM Developer Edition - Moto X General

Until a few days ago I was using Bluetooth tethering between my Nexus 7 and GSM Galaxy Nexus on an AT&T GoPhone plan to provide the Nexus 7 with an Internet connection when away from Wifi. This was working with no trouble. Early this week I ordered a Nexus 5 and a GSM Developer Edition Moto X. Since the Nexus 5 arrived first, I got a micro SIM at the local AT&T store and has them transfer my account over to that SIM. BT tethering with the Nexus 5 was working fine. Today I got a nano SIM and a new Go Phone account for the Moto X so I can use both actively and hopefully decide which one I like better.
Initially, BT tethering between the Nexus 7 and Moto X did not work - while the Nexus 7 thought it was connected, the Moto X did not show that it was connected, the tethering notification didn't appear, and the Chrome on the Nexus 7 reported that it had no connection when trying to load a web page. I noticed that the APN settings were different between the Nexus 5 and the Moto X, so I created a new APN and duplicated the settings from the Nexus 5. This improved things - the Moto X now shows that it's connected, and the tethering notification appears, but Chrome on the Nexus 7 still reports no connection.
I have Internet Connection Sharing checked under the Nexus 7's bluetooth connection listed on both the Nexus 5 and Moto X, and I've tried restarting the Moto X after making the APN changes.
APN settings on Moto X (original plain, modified bold):
Name: AT&T PHONE Modified
APN: phone
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: Not set http://mmsc.mobie.att.net
MMS Proxy: Not set proxy.mobile.att.net
MMS Port: Not set 80
MCC: 310
MNC: 410
Authentication type: Not set
APN type: default,supl,hipri,dun default,mms,supl,fota
APN Protocol: IPv4
APN roaming protocol: IPv4
APN enable/disable: APN enabled (grayed out)
Bearer: Unspecified
MVNO type: None
MVNO value: Not set (grayed out)
Any suggestions on how to make this work, preferably without additional software (which I don't think I should need on the Dev Ed)?

Not sure about Bluetooth tethering, but the mobile hotspot feature on the developer edition works just fine on AT&T and does not do an entitlement check. That would give you faster speeds as well.

bugsy said:
Not sure about Bluetooth tethering, but the mobile hotspot feature on the developer edition works just fine on AT&T and does not do an entitlement check. That would give you faster speeds as well.
Click to expand...
Click to collapse
My main use of tethering with the Nexus 7 is for traffic data in a GPS app. Since bandwidth is not an issue for this application I prefer to use Bluetooth because of it's lower power consumption. If I used Wifi hotspot I would feel it necessary to take my phone out and plug it in, which I don't do with Bluetooth.

After several more attempts at this I finally restarted both devices, and was able to use the original APN settings on the Moto X. I'm pretty sure that the Nexus 7 was getting confused by trying to reconnect to a previously connected Nexus 5.

Related

Wanted: Wifi only

Hi for my xperia x10 I had wifi only for a while and all of a sudden it started to connect to the internet using the phone company's gsm/edge/etc.
How do I turn it back to WIFI ONLY. I don't want to pay for internet because I don't have a web plan.
My apn is set up correctly; so I don't know what's going on. It just switched all of a sudden:
Name: T-mobile
Apn: Wap.voicestream.com
mmsc: http://216.155.174.84/servlets/mms
Uncheck the box next to mobile network in settings
Now I can't receive/send picture msgs. =(

Nexus 4 not connecting to data using Straight Talk via Att

Hello, I recently signed up with Straight Talk via AT&T and am not able to get my Data services to connect or send/receive any MMS. I have configured my APN settings multiple times now and actually just got off the phone with straight talk about this issue as well. They were no help.
I am using Straight Talks at&t network and my phone reads this under settings>about phone>status...
Mobile Network Type: HSPA:10
Service State: In service (I have 4 bars)
Mobile Network state: Disconnected
Also when I go to the *#*#4636#*#* menu, It says this...
GPRS service: Disconnected
GSM disconnects: ========DATA=======
How can I fix this and get data and mms to work??
If you find anything out, please tell us! I'm starting to think its something that is wrong with the phone...
interesting... I just joined straight talk today using ATT micro sim and i have the same issue... I also have full bars.
I used the following APN and it didn't work for me.
Straight Talk
APN: att.mvno
Port: 80
Proxy: not set
MMSC: http://mmsc.cingular.com
MMS Proxy: 66.209.11.33
mms port: 80
MCC: 310
MNC: 410
I'm beginning to wonder if straight talk is starting block ATT micro sim activation..?
I was able to get on using their T-Mobile APN settings.
Straight Talk
APN: wap.tracfone
Port: 8080
Proxy: not set
MMSC: http://mmsc.tracfone.com
MMS Proxy: not set
mms port: not set
MCC: 310
MNC: 410
mclain1 said:
interesting... I just joined straight talk today using ATT micro sim and i have the same issue... I also have full bars.
I used the following APN and it didn't work for me.
Straight Talk
APN: att.mvno
Port: 80
Proxy: not set
MMSC: http://mmsc.cingular.com
MMS Proxy: 66.209.11.33
mms port: 80
MCC: 310
MNC: 410
I'm beginning to wonder if straight talk is starting block ATT micro sim activation..?
I was able to get on using their T-Mobile APN settings.
Straight Talk
APN: wap.tracfone
Port: 8080
Proxy: not set
MMSC: http://mmsc.tracfone.com
MMS Proxy: not set
mms port: not set
MCC: 310
MNC: 410
Click to expand...
Click to collapse
On the AT&T on ST,
I didn't set the first Port you have listed after APN, I left it as "not set" instead of 80.
To the OP can you list what you set your APN to? Did you look at the Straight Talk thread in general area?
Also it might sound weird but check under Settings > Mobile Network Settings > Data enabled.
For some reason it wouldn't be checked for me when I was flashing a ROM or going back to stock ROM.
These are my settings:
Name: StraightTalk ATT
APN: att.mvno
Proxy: not set
Port: not set
Username: not set
Password: not set
Server: not set
MMSC: http://mmsc.cingular.com
MMS Proxy: 66.209.11.33
MMS Port: 80
MCC: 310
MNC: 410
Authentication type: not set
APN type: default,supl,mms
APN protocol: IPv4
Bearer: Unspecified
bitojoe said:
Hello, I recently signed up with Straight Talk via AT&T and am not able to get my Data services to connect or send/receive any MMS. I have configured my APN settings multiple times now and actually just got off the phone with straight talk about this issue as well. They were no help.
I am using Straight Talks at&t network and my phone reads this under settings>about phone>status...
Mobile Network Type: HSPA:10
Service State: In service (I have 4 bars)
Mobile Network state: Disconnected
Also when I go to the *#*#4636#*#* menu, It says this...
GPRS service: Disconnected
GSM disconnects: ========DATA=======
How can I fix this and get data and mms to work??
If you find anything out, please tell us! I'm starting to think its something that is wrong with the phone...
Click to expand...
Click to collapse
Here are the APN (Settings>Wireless & Networks.. More...>Mobile networks>Access Point Names) configuration I use to effectivly send/receive MMS:
APN: att.mvno
Proxy: Not set
Port: 80 (some report having better results not setting the Port, but It works for me this way)
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mmsc.cingular.com
MMS proxy: 66.209.11.33
MMS Port: 80
MCC: 310
MNC: 410
Athentication type: PAP or CHAP
APN type: default,supl,mms (no spaces)
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
Be sure to Save, and Reboot after making changes.
(Also, delete the AT&T APN if its in the list... Click on it, then press menu discard)
mclain1 said:
...
I'm beginning to wonder if straight talk is starting block ATT micro sim activation..?
Click to expand...
Click to collapse
Why would the block something they sell and offer service through.
Its also noted on their site, that MMS may not work on some devices
"Updating your APN settings does not guarantee MMS (Multimedia/Picture Messaging) will work." Quoted from StraightTalk.com
I just got off the phone with Straight Talk and I bought a new AT&T micro sim card from Walmart. I asked if they are still supporting it, and they said absolutely, they will continue to. Just FYI
bitojoe said:
Hello, I recently signed up with Straight Talk via AT&T and am not able to get my Data services to connect or send/receive any MMS. I have configured my APN settings multiple times now and actually just got off the phone with straight talk about this issue as well. They were no help.
I am using Straight Talks at&t network and my phone reads this under settings>about phone>status...
Mobile Network Type: HSPA:10
Service State: In service (I have 4 bars)
Mobile Network state: Disconnected
Also when I go to the *#*#4636#*#* menu, It says this...
GPRS service: Disconnected
GSM disconnects: ========DATA=======
How can I fix this and get data and mms to work??
If you find anything out, please tell us! I'm starting to think its something that is wrong with the phone...
Click to expand...
Click to collapse
I had the same thing happen to me today and I am on ATT sim. I sent straight talk an email and they sent back a response asking me to call
855-222-2355. The agent had me make sure my data was on then I turned off the phone for 1 minute why she did something on her side. After that it started working again. I asked her what she did so the next time this happens I could just say this has happened before and this is how they fixed it. The agent stated to just call the number above and state that your data is not working and they will resolve the issue. No help, but that is what happened to me.
ropesguru said:
I sent straight talk an email and they sent back a response asking me to call
855-222-2355.
Click to expand...
Click to collapse
Same problem. Straight Talk has been working for months, and all of a sudden yesterday no data. I am lucky if I use data a handful of times a month, so I know I am not over any limits. I am glad I printed out Google maps before I left on my trip as a backup, because it was a 120 mile trek. I went to an AT&T store while on the road out of desperation and a person was kind enough to look at the phone and believes the hardware is OK and it is a Straight Talk issue. I am assuming the "Mobile Network State = Disconnected" I am getting is not a good thing. I will give them a call today.
EDIT: Just got off the phone with Straight Talk. They gave me new APN settings, and this is the first time since I have had Straight Talk (4 months) that I am able to get data at my house (It worked while on the road). It is also the first time I ever saw the little capital "H" near the signal icon, whatever that is. I am in quite a dead zone and previously could only use wifi. Yippee! I also see that "Mobile Network State = Disconnected" had nothing to do with getting data as it works now and it is still listed as Disconnected.
EDIT: These are the new settings that Straight Talk gave me:
Name: Straight Talk
APN: att.mvno
Proxy: not set
Port: not set
Username: not set
Password: not set
Server: not set
MMSC: http://mmsc.cingular.com
MMS Proxy: 66.209.11.33
MMS Port: 80
MCC: 310
MNC: 410
Authentication type: not set
APN type: not set
APN protocol: IPv4
APN roaming protocol: iPv4
Bearer: Unspecified
And these were my original settings
EDIT: As pointed out in a subsequent post below, these are the settings that the person in the AT&T store put in. He erased my original settings, which as I recall I got from the Straight Talk site or the sim card instructions.
Name: ATT WAP
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
Username: not set
Password: not set
Server: cingulargprs.com
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: Not set
MCC: 310
MNC: 410
Authentication type: not set
APN type: default,supl.mms
APN protocol: IPv4
APN roaming protocol: iPv4
Bearer: Unspecified
pjc123 said:
Same problem. Straight Talk has been working for months, and all of a sudden yesterday no data. I am lucky if I use data a handful of times a month, so I know I am not over any limits. I am glad I printed out Google maps before I left on my trip as a backup, because it was a 120 mile trek. I went to an AT&T store while on the road out of desperation and a person was kind enough to look at the phone and believes the hardware is OK and it is a Straight Talk issue. I am assuming the "Mobile Network State = Disconnected" I am getting is not a good thing. I will give them a call today.
EDIT: Just got off the phone with Straight Talk. They gave me new APN settings, and this is the first time since I have had Straight Talk (4 months) that I am able to get data at my house (It worked while on the road). It is also the first time I ever saw the little capital "H" near the signal icon, whatever that is. I am in quite a dead zone and previously could only use wifi. Yippee! I also see that "Mobile Network State = Disconnected" had nothing to do with getting data as it works now and it is still listed as Disconnected.
EDIT: These are the new settings that Straight Talk gave me:
Name: Straight Talk
APN: att.mvno
Proxy: not set
Port: not set
Username: not set
Password: not set
Server: not set
MMSC: http://mmsc.cingular.com
MMS Proxy: 66.209.11.33
MMS Port: 80
MCC: 310
MNC: 410
Authentication type: not set
APN type: not set
APN protocol: IPv4
APN roaming protocol: iPv4
Bearer: Unspecified
And these were my original settings:
Name: ATT WAP
APN: wap.cingular
Proxy: wireless.cingular.com
Port: 80
Username: not set
Password: not set
Server: cingulargprs.com
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS Port: Not set
MCC: 310
MNC: 410
Authentication type: not set
APN type: default,supl.mms
APN protocol: IPv4
APN roaming protocol: iPv4
Bearer: Unspecified
Click to expand...
Click to collapse
Those original settings weren't for StraightTalk but for AT&T. Two totally different services.
---------- Post added at 10:00 AM ---------- Previous post was at 09:56 AM ----------
bitojoe said:
Hello, I recently signed up with Straight Talk via AT&T and am not able to get my Data services to connect or send/receive any MMS. I have configured my APN settings multiple times now and actually just got off the phone with straight talk about this issue as well. They were no help.
I am using Straight Talks at&t network and my phone reads this under settings>about phone>status...
Mobile Network Type: HSPA:10
Service State: In service (I have 4 bars)
Mobile Network state: Disconnected
Also when I go to the *#*#4636#*#* menu, It says this...
GPRS service: Disconnected
GSM disconnects: ========DATA=======
How can I fix this and get data and mms to work??
If you find anything out, please tell us! I'm starting to think its something that is wrong with the phone...
Click to expand...
Click to collapse
FYI the phone won't connect to mobile data until you are using it, its to save the battery. That's why it shows as disconnected in mobile network state. To verify this turn off wifi, if your connect to it, open a browser using your mobile data then check phone status.
kzoodroid said:
Those original settings weren't for StraightTalk but for AT&T. Two totally different services.
Click to expand...
Click to collapse
Thanks for spotting that. Those are not the original settings I put into the phone; I thought they didn't look right. Apparently yesterday, instead of creating a new APN set, the guy in the AT&T store overwrote my Straight Talk settings while testing out my phone (Not too bright). It really doesn't matter, as neither settings worked properly anyway. I am only getting 1 Mpbs download and 0.10 Mpbs upload at my house now (better than the zero I was getting before), but I am going to have to take a drive later to see what improvement I get.
kzoodroid said:
FYI the phone won't connect to mobile data until you are using it, its to save the battery. That's why it shows as disconnected in mobile network state. To verify this turn off wifi, if your connect to it, open a browser using your mobile data then check phone status,
Click to expand...
Click to collapse
I see.
EDIT: The highest data speed I am getting is 1.09 Mbps no matter where I go, even running SpeedTest while staring at a several cell towers (Where the signal strength gets better). I gather that is bad from the numbers I see elsewhere?

[SOLVED] I9505G AT&T MMS Issue

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.

Blu life pure AT&T settings voice, MMS and Data

I'm one of the people hanging onto an AT&T unlimited data plan with white knuckles and I got tired of the apple structure so I got my hands on an unlocked Blu Life Pure hoping to try out android for a while. So I swapped the sim out of my iPhone 5s and luckily most of the APN info was already there so voice worked right out of the box and I could send texts but I couldn't receive any. I set up the legacy cingular settings and could send and receive texts but when I left the safety of my wifi I had no data. The fix was incredibly easy. Here are the APN settings that transferred over.
APN: phone
APN Type: default,mms,supl
MMSC: httpCOLONSLASHSLASHmmscDOTmobileDOTattDOTnet/
MMS proxy: proxyDOTmobileDOTattDOTnet
MMS port: 80
MCC: 310
MNC: 410
AUTH type: not set
APN Protocol: IPv4
APN roaping protocol: IPV4
APN enabled: Yes
Bearer: unspecified
What fixed it for me was making a second APN item with these same settings but I changed the AUTH type specifically to "NONE" and that did it.
Hope that helps.

Settings Showing Wrong Carrier

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

Categories

Resources