Picked up a new m8 today and I am wishing to not use tmobile's dns servers and change it to either google's or opendns servers. Is this possible? I am aware of all the apps out there that 'change' dns settings but I am looking to change settings for cellular network and not just when i am on WIFI. I can't believe this can't be done on a rooted device. My goal here is to change nameserver internally and not rely on an app etc. Thanks in advance
I don't think you can do that.. there are no tcp over ip packets being sent when you are using gsm. It's a different protocol stack. And unfortunately, it's in T-Mobile's control.
No guarantee, but if you change the CID to 1111111 you might be able to do it, but it will take some more researching.
Related
I have a slightly odd requirement, and I wondered if there was any way to fix it:
My carrier has a partnership with a second carrier so we can roam on each others networks for no extra cost.
Where I live, my own carrier only gives me a 2G signal, whereas the other gets 3G. Thing is, I have to physically select the other network. If it's on Automatic, it always "prefers" my own carrier.
This is fine until I'm on the other side of town where the other network gets no signal at all. I then have to manually select my own carrier again!
Is there any way to get it to prefer the other network, or even more ideally, prefer the one that offers the better signal at any given point?
Hi,
a bit of *bump* because I'm struggling with the same issue. I had such option on my previous samsung i780 (oooold) and it worked like a charm.
Currently my mobile operator has 2 roaming partners and if I want to change quickly the preferred order (because in some location it might have better coverage but only there and only for a while) I wold have to switch simcard to the old phone...
Isn't there at even a separate aplication to do that? Does andorid API allow such modification?
Glad I'm not the only one!
Interesting you mention an app to do it... i've not looked actually. If an app can access the list of networks and actually set the phone to use one, then I guess it would be possible. I'll check it out...
to the best of my understanding this is somewhat network option/setting and when suggesting an app I was thinging abount some way to read this setting, modify it and then save/send back to network. It would be a matter of access to the network settings from the API and knowledge how to operate it....
Still investigating this. Looks like the stuff to access the list of networks is in some internal APIs, so a little harder to access. I'll post back when I learn more...
Hey I hope you guys can figure this out have you tried the *#*#4636#*#* command and changed the radio? This will select the most preferred network.. e.g. I'm with Telstra in Australia, the stock radio defaults to 2100MHz but Telstra's HSPA+ is 850Mhz.. so I have to switch to AUS2 radio so it defaults to that every time.
Sent from my Galaxy Nexus using xda premium
@Simmo3D
It's not about the radio band but about the service provider itself.
As I could not find a thread about this specifically, I am posting this solution as it works for me.
On the Galaxy S2 SGH-T989 is where this pertains to though other users might encounter similar problem with other phones on simple mobile.
Stock 2.3.6 Rom
When you turn on the portable hotspot feature with this phone, what it does is disconnect your "Simple Mobile" APN and inserts and connects using a new APN called "Tethering". When you try connecting with your PC to your hotspot's ssid, it takes you to a web page on t-mobile.com informing you with an error 503 or some other error stating that its not available. I assume t-mobile is detecting that you are not their customer and blocks it.
it takes you here:
-------------------------------------------------------
http://androidapi.t-mobile.com/apppack/mvno.html
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
---------------------------------------------------------
The reason is because that APN tries to connect to "pcweb.tmobile.com". What you have to do is once you activate your hotspot, you have to edit the apn (while it is running) and change it from pcweb.tmobile.com to simple.
No other setting is needed. I am using "APN manager" which I paid for on the market and it is well worth it. I have used it for other purposes besides this and it allows you to edit the APN while it is live. Hope this helps other simple mobile users...
Also, you have to edit this "Tethering" APN every time you run the hotspot and delete the last one as it will just keep adding the new one with the t-mobile settings every time.
Anyone else out there with another solution please post it..
pcdocta said:
As I could not find a thread about this specifically, I am posting this solution as it works for me.
On the Galaxy S2 SGH-T989 is where this pertains to though other users might encounter similar problem with other phones on simple mobile.
Stock 2.3.6 Rom
When you turn on the portable hotspot feature with this phone, what it does is disconnect your "Simple Mobile" APN and inserts and connects using a new APN called "Tethering". When you try connecting with your PC to your hotspot's ssid, it takes you to a web page on t-mobile.com informing you with an error 503 or some other error stating that its not available. I assume t-mobile is detecting that you are not their customer and blocks it.
it takes you here:
-------------------------------------------------------
http://androidapi.t-mobile.com/apppack/mvno.html
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
---------------------------------------------------------
The reason is because that APN tries to connect to "pcweb.tmobile.com". What you have to do is once you activate your hotspot, you have to edit the apn (while it is running) and change it from pcweb.tmobile.com to simple.
No other setting is needed. I am using "APN manager" which I paid for on the market and it is well worth it. I have used it for other purposes besides this and it allows you to edit the APN while it is live. Hope this helps other simple mobile users...
Also, you have to edit this "Tethering" APN every time you run the hotspot and delete the last one as it will just keep adding the new one with the t-mobile settings every time.
Anyone else out there with another solution please post it..
Click to expand...
Click to collapse
Have you tried foxfi and wifi tether?
Looks like a good alternative. Thanks..
Sent from my SGH-T989 using XDA
Thanks!
This thread saved me! While I did not follow the instructions, it got me thinking to check the apn settings on my phone. As it turned out my apn was changed to a different apn when i turned on my hotspot and all I had to do was select my original apn again and tethering began to work! Awesome!
I'm using a freetel FTU152D (Samurai Kiwami) on Simple Mobile. It does change the APN every time I turn on the Hotspot, but fixing the APN settings doesn't seem to do anything; other devices connect to the wifi, but still can't see the internet. Meanwhile, I still have internet access on the FTU152D. Any ideas?
RichSPK said:
I'm using a freetel FTU152D (Samurai Kiwami) on Simple Mobile. It does change the APN every time I turn on the Hotspot, but fixing the APN settings doesn't seem to do anything; other devices connect to the wifi, but still can't see the internet. Meanwhile, I still have internet access on the FTU152D. Any ideas?
Click to expand...
Click to collapse
I've used my FTU152D as a Wi-Fi source using the dialog in settings and it works fine. Other devices can connect. My FTU152D is rooted with kingroot, however, would that make a difference?
nazcalito said:
I've used my FTU152D as a Wi-Fi source using the dialog in settings and it works fine. Other devices can connect. My FTU152D is rooted with kingroot, however, would that make a difference?
Click to expand...
Click to collapse
I rooted mine early on with kingroot, but unrooted it when I couldn't find any third party ROMs. I think I tried the Hotspot while it was rooted, but I don't remember for sure. I'll have to try it again.
I have a T-Mobile G3 and I am unable to set my APN (a copy since the built-in one is not editable) to IPV4. If I do that, the phone does not connect to the mobile data network. Looking at the logs, I get this error:
D/MobileDataStateTracker(28614): default: Received state=DISCONNECTED, old=CONNECTING, reason=apnFailed
Setting IPV6 or IPV4/IPV6 will quickly connect.
I also found some references to 6to4 when connecting to the network. I didn't copy them, but I'll dig through to find them and update.
On other versions, can you use your APN with IPV4 only? If my theory is correct, the T-Mobile version being IPV6 only is breaking international roaming, which is a pretty big deal (most of the internet, let alone other operators, is not IPV6 enabled yet).
If anyone with a handset that isn't T-Mobile test this, it would be appreciated. Really need my international roaming and nobody is sure of the cause yet.
Sent from my LG G3
I'm having ipv4 issues and roaming issues as well. I called tmobile twice about it and they won't help me unless I'm in a foreign country having the data issue or after my data resets because I'm maxed on roaming data allowance
NewZJ said:
I'm having ipv4 issues and roaming issues as well. I called tmobile twice about it and they won't help me unless I'm in a foreign country having the data issue or after my data resets because I'm maxed on roaming data allowance
Click to expand...
Click to collapse
What is the max allowed??
50mb/month
This note 5 is the first phone I have with AT&T that's getting a non-local (2600::380::....) IPv6 address from the cell tower. I wasn't getting ipv6 on my nexus 6 last week (same LTE network.)
Does anyone know if this was something that AT&T recently enabled, or if they are only doing router announcements to specific APN's and/or h/w?
garyd9 said:
This note 5 is the first phone I have with AT&T that's getting a non-local (2600::380::....) IPv6 address from the cell tower. I wasn't getting ipv6 on my nexus 6 last week (same LTE network.)
Does anyone know if this was something that AT&T recently enabled, or if they are only doing router announcements to specific APN's and/or h/w?
Click to expand...
Click to collapse
From what I have read AT&T has started their plans for IPv6 since 2012 and started roughly mid 2014 rolling them out on the cellular network. They state the roll out will be slow, so it is possible they just turned it on by you. Is it possible also that it was not enabled on the Nexus 6 by default?
KennyG123 said:
Is it possible also that it was not enabled on the Nexus 6 by default?
Click to expand...
Click to collapse
It's possible, but I'd think it would have to be on the carrier side if that was the case. With the nexus device, I was using the same firmware that everyone in Europe (and most of Asia) is using - and many of them were getting ipv6 numbers.
As well, my home wifi network (ipv6 dual stack) would result in an ipv6 address assigned to the handset.
Actually, to be more accurate, they were getting RA's. Android doesn't do DHCPv6 at all.
It's quite possible that AT&T just got around to turning it on in my area at the same time I switched phones, but that'd be an interesting coincidence. The more I think about this, the more I'm convinced it was related to the APN. I'm unable to check now, but I'm starting to wonder if the default APN for the nexus6 on AT&T blocks ipv6.
garyd9 said:
It's possible, but I'd think it would have to be on the carrier side if that was the case. With the nexus device, I was using the same firmware that everyone in Europe (and most of Asia) is using - and many of them were getting ipv6 numbers.
As well, my home wifi network (ipv6 dual stack) would result in an ipv6 address assigned to the handset.
Actually, to be more accurate, they were getting RA's. Android doesn't do DHCPv6 at all.
It's quite possible that AT&T just got around to turning it on in my area at the same time I switched phones, but that'd be an interesting coincidence. The more I think about this, the more I'm convinced it was related to the APN. I'm unable to check now, but I'm starting to wonder if the default APN for the nexus6 on AT&T blocks ipv6.
Click to expand...
Click to collapse
This guy states his was set for IPv4 by default instead of the normal ipv4/ipv6 setting.
Where are you seeing ipv6? In system settings >about device>status ? That looks like ipv4/ipv6 from your phone to att's internal network.
I did check ip6.me and that showed an ipv6 address, but couldn't be sure that was legit. ..
quordandis said:
Where are you seeing ipv6? In system settings >about device>status ? That looks like ipv4/ipv6 from your phone to att's internal network.
I did check ip6.me and that showed an ipv6 address, but couldn't be sure that was legit. ..
Click to expand...
Click to collapse
I'm using a third party program to check the IP addresses (one that specifically shows IPv6.) The same IP shows under settings->about->status.
The 2600:: address it's showing is a legit global IPv6 assignment, and android ONLY does SLAAC (not DHCPv6) so it must be seeing an ipv6 RA.
On the other hand, I can't ping it from the outside, so it appears that AT&T has some proxy between the phones and the "rest of the world." What I don't understand is why they'd be assigning proper global IPv6 addresses behind a proxy unless it's a stage in a larger rollout. (If they intended to keep things behind the proxy, they should be using fc00::/7 range addressing - or addresses starting with FD.)
For YOU, what ipv6 address are you seeing when wifi is turned off? If it starts with "260", it's part of AT&T's global block.
garyd9 said:
I'm using a third party program to check the IP addresses (one that specifically shows IPv6.) The same IP shows under settings->about->status.
The 2600:: address it's showing is a legit global IPv6 assignment, and android ONLY does SLAAC (not DHCPv6) so it must be seeing an ipv6 RA.
On the other hand, I can't ping it from the outside, so it appears that AT&T has some proxy between the phones and the "rest of the world." What I don't understand is why they'd be assigning proper global IPv6 addresses behind a proxy unless it's a stage in a larger rollout. (If they intended to keep things behind the proxy, they should be using fc00::/7 range addressing - or addresses starting with FD.)
For YOU, what ipv6 address are you seeing when wifi is turned off? If it starts with "260", it's part of AT&T's global block.
Click to expand...
Click to collapse
Yep, when not on WiFi, and just on data, IPv6 block starts with 2600. Interestingly, my IPv4 address starts 10.102 - so guessing that's internal IP. Not at all surprised that 2600 block is not accessible from "outside". That said, I'd be curious to see if two phones on the same ATT switch would be able to communicate with each other over the internal network? My inclination is that it's not at all possible, but...who knows?
quordandis said:
Yep, when not on WiFi, and just on data, IPv6 block starts with 2600. Interestingly, my IPv4 address starts 10.102 - so guessing that's internal IP. Not at all surprised that 2600 block is not accessible from "outside". That said, I'd be curious to see if two phones on the same ATT switch would be able to communicate with each other over the internal network? My inclination is that it's not at all possible, but...who knows?
Click to expand...
Click to collapse
I have a broadband modem (LTE) on my work machine, and when I connect to AT&T with that, i do NOT get an ipv6 address. Then again, it's using the older LTE apn of "broadband"
I am currently using a firetv with fire os 5.2.6.0 and would like to know if there is any way i can get my local channels.
The internet i am gives me an ip address located in new york so directv wont give me the local channels for my zip code.
i tried to spoof my location using the guides of sideloading play services and enabling mock location using adb but the fake gps fails when i type in my zipcode and wont change anything.
When I last used DTVNow, the locale was based on your billing address.
Tinkerer76 said:
When I last used DTVNow, the locale was based on your billing address.
Click to expand...
Click to collapse
yeah it is, my billing and actual device location are in the same zip code but im using cellular internet and the ip location shows up as new york.
TripOG said:
yeah it is, my billing and actual device location are in the same zip code but im using cellular internet and the ip location shows up as new york.
Click to expand...
Click to collapse
It shouldn't matter what your IP address is. I use the DTN app on my phone over cellular data and it brings up my local channels. It's all about billing zipcode. Your local area might not have any local channels yet. You can check by zipcode here: http://www.directv.com/DTVAPP/packProg/attLocalChannels.jsp?assetId=att_cms_local_channels
Yes I get my local channels over cellular data on devices with gps but I don't believe the firetv has gps so it uses the device ip location which is a few states away.
fr0st420 said:
It shouldn't matter what your IP address is. I use the DTN app on my phone over cellular data and it brings up my local channels. It's all about billing zipcode. Your local area might not have any local channels yet. You can check by zipcode here: http://www.directv.com/DTVAPP/packProg/attLocalChannels.jsp?assetId=att_cms_local_channels
Click to expand...
Click to collapse
I believe it matters when you don't have gps to determine location.