Hey Everyone,
I am not certain how specific this issues is to my exact situation, so I am describing every related aspect that I can.
Details
Phone: HTC MT3G (3.5mm Jack version), rooted, running CM 6.1.0 RC1
Network: Wind Mobile (in Canada)
-- please indicate if any other details are needed for troubleshooting --
Issue
Wind mobile offers an unlimited plan that includes data, provided you stay within what they call their "Home Zone (ie the metropolitan area known as GTA, in my case). When travelling outside of the Home Zone, you enter an Away Zone. This is essentially roaming on Rogers network, using 2G (Edge) for data. This costs a lot and so naturally I don't want to roam.
Before the phone was rooted and upgraded, I had checked the box to in settings to disable data while roaming. I travelled in and out of the Home Zone and it worked as expected - that is, turning off the data connection as soon as the network switched from Home to Away. As expected, it re-enabled data upon re-entering the Home Zone.
Since rooting/updating, this functionality seems to have disappeared. I have the box checked, but as soon as I step into an Away Zone, it switches to 2G and starts using data whilest roaming. At first, I thought this might be because I performed the upgrade process in an away zone and as such, the phone would associate that with being "Home". However it keeps data across Home and Away (which negates that theory as "Home" should now be "Away" and data disabled.
I wiped and started again in a Home Zone, with no success.
So:
1) Is there something I am doing wrong, or a known way to remedy this issue?
If not,
2) Is there any way to disable 2G (similar to the way you can disable 3G for battery savings?) This would be an indirect way to solve the issue, as the only time 2G is used is when the phone is in an Away Zone.
Thanks for any advice and help you can provide!
Bump - any ideas?
I've had this problem for a while now but it's starting to get extremely annoying. If I'm not connected to WiFi I will have no mobile data at all. I can still send texts or make a phone call but I can't go on the internet or receive MMS. I've tried at least 5 different APN settings and I've made sure that "Data Enabled" is checked but nothing works. When I contacted AT&T they said there is nothing they can do because it is not an AT&T device.
BeastKiller450 said:
I've had this problem for a while now but it's starting to get extremely annoying. If I'm not connected to WiFi I will have no mobile data at all. I can still send texts or make a phone call but I can't go on the internet or receive MMS. I've tried at least 5 different APN settings and I've made sure that "Data Enabled" is checked but nothing works. When I contacted AT&T they said there is nothing they can do because it is not an AT&T device.
Click to expand...
Click to collapse
Maybe you should try again, but this time tell them you'll drop them like a hot potato if they don't give you the correct APN settings. They're doing false advertising by telling you just because it's not their device that they cannot help you. Oh really jerks? I'd ask them why the f you pay full price like everyone else then. Try playing rough, maybe you'll get a response. I'd answer you but I don't know AT&T's settings. I use T-Mobile.
After some research, it may be a problem on their end. They may have you set up for a non-smartphone data plan or HSPA or LTE, not HSPA+ data. Look at your statement and see what plan you're on. You can always call them and make sure you're set up with HSPA+. Tell them to die in a ditch if they refuse to service a paying customer. Try reading this: http://forums.androidcentral.com/google-nexus-4/226814-anyone-activated-nexus-4-att.html
BeastKiller450 said:
I've had this problem for a while now but it's starting to get extremely annoying. If I'm not connected to WiFi I will have no mobile data at all. I can still send texts or make a phone call but I can't go on the internet or receive MMS. I've tried at least 5 different APN settings and I've made sure that "Data Enabled" is checked but nothing works. When I contacted AT&T they said there is nothing they can do because it is not an AT&T device.
Click to expand...
Click to collapse
I'm having a similar issue that seems to have started around 4-5 days ago. I'm in the Twin Cities area, btw, if that matters.
Prior to that, I was only the victim of the occasional data drop or ARP offload delayed-notification issue.
The problem usually, but not aways, occurs when I leave a WIFI area and get handed off to the cell towers. I get no data, but calls/SMS works fine. Anywhere from 5-15 minutes later, I will get mobile data again, but only briefly before it goes away again.
The issue can also occur when seemingly changing towers, or going from HSPA > HSPA+.
On occasion, when the problem is occuring, my cell bars will still show blue as google services don't know they've been disconnected, but when I attempt to access, for instance, gmail or GNow, I will get no connection. Finally the bars will turn grey as the phone attempts to (apparently) cycle the radio.
Oddly, I stopped into a retail store here locally and the gal said they were having data issues so I figured it'd be fixed. That was 5 days ago. 3 days ago I called customer care and logged a case. They've found no issues with their towers or my provisioning thus far.
I also switched out my SIM card. No change.
At this point I think I'm going to walk over to T-Mobile and try a prepaid SIM to see if it's the phone or really and truly something with AT&T's network.
I'll post a logcat here if anyone is interested but I couldn't find too much interesting within it.
dispatch said:
I'm having a similar issue that seems to have started around 4-5 days ago. I'm in the Twin Cities area, btw, if that matters.
Prior to that, I was only the victim of the occasional data drop or ARP offload delayed-notification issue.
The problem usually, but not aways, occurs when I leave a WIFI area and get handed off to the cell towers. I get no data, but calls/SMS works fine. Anywhere from 5-15 minutes later, I will get mobile data again, but only briefly before it goes away again.
The issue can also occur when seemingly changing towers, or going from HSPA > HSPA+.
On occasion, when the problem is occuring, my cell bars will still show blue as google services don't know they've been disconnected, but when I attempt to access, for instance, gmail or GNow, I will get no connection. Finally the bars will turn grey as the phone attempts to (apparently) cycle the radio.
Oddly, I stopped into a retail store here locally and the gal said they were having data issues so I figured it'd be fixed. That was 5 days ago. 3 days ago I called customer care and logged a case. They've found no issues with their towers or my provisioning thus far.
I also switched out my SIM card. No change.
At this point I think I'm going to walk over to T-Mobile and try a prepaid SIM to see if it's the phone or really and truly something with AT&T's network.
I'll post a logcat here if anyone is interested but I couldn't find too much interesting within it.
Click to expand...
Click to collapse
I've been on the T-Mobile network now for about an hour and I have had ZERO of the aforementioned issues. The phone definitely handles leaving WIFI > HSPA better as well.
I'm traveling in Europe with my Sprint Galaxy S5 Sport running Android 5.0 on Sprint's global roaming plan, which is awesomely providing me with free 2G data in Germany, Spain, and England. However, every 30 seconds, if I'm connected to the international carrier's data network, my phone's Wi-Fi turns itself on to search for Wi-Fi networks nearby. Being on 2G and constantly searching for Wi-Fi networks is causing my battery to die twice as fast, which is the last thing I need while traveling abroad.
I've been through ALL the settings to be sure location is not using Wi-Fi (and even that location is turned off), that Google is not scanning Wi-Fi for random crap, not always scanning for networks, unchecked and killed Connections Optimizer, disabled Wi-Fi power saving mode via *#0011#, booted the phone in safe mode, killed every running app... Still, once I connect to an international carrier's data network (in this case Movistar in Spain), my Wi-Fi turns on after about 30 seconds. I turn it off, the cycle repeats.
If I turn off mobile data or unregister from the network or go into airplane mode, Wi-Fi does not turn itself on automatically. When I am on my home network, Wi-Fi does not turn itself on automatically. Only when actively connected to data on an international network.
I have talked to a few people at Sprint and they simply advise to disable Wi-FI notifications - which obviously does not solve my battery-drain problem - or factory reset the phone. However, the behavior feels too calculated to be that simple. It seems like a "feature" Sprint would try to sneak in to minimize use of international data roaming when possible, perhaps even for the customer's benefit.
Has anyone heard of this? Is it a bug? "Enhancement?" Something new they're doing for the global roaming plans? Or just a crazy software glitch as SprintCares suggests?
Thanks!
EDIT: Another data point from Reddit: this also seems to happen for people roaming domestically, not limited to international.
Took my first international trip since getting the 6P. I called to add international services. In the Bahamas, I can get voice, but no data.
I spent a hour hour on the phone with VZW, but they were unable to assist. Took the SIM out, rebooted, checked a dozen settings - nothing.
This is the first negative experience I've had with the phone.
Anyone else have experience with this, or have any thoughts/ideas?
I have had a similar problem anytime I am away from my home network. Two observations from me: (1) the phone does not give any indication on whether it's connected to a data network or not when roaming (all you see is the "R" symbol in the signal strength meter whether you have data or not) and (2) most of the time it doesn't connect automatically- if you toggle data roaming or airplane mode, it connects to data, but this disappears when handing off to the next tower.
This is clearly a bug- if I move my SIM from the 6P to my iPhone 6, i get continuous roaming data, so it's nothing to do with the provider. I wish there was a fix as it's a pain in the b**t.
Not very helpful I know, but you're not alone with this issue
My wife and I live up in the foothills of Colorado where there are no Sprint cell towers. There is one cell tower which our Sprint S7 edges can barely pick up that comes and goes and indicates that we are roaming. For a few seconds our phones might see it but then it will go away for minutes, then it will come back only to go away again ... etc. In any event, it was necessary to use Wifi calling when we are at my home. Prior to the Nougat upgrade everything was fine. As soon as we walked into the house our S7 edges would connect, Wifi calling would activate and would be functional. After the Nougat update we have discovered that Wifi calling no longer works unless we can also see that one roaming cell tower. Then Wifi calling turns on, stays on and we can make/receive calls. I emphasize that this behavior occurs with both our phones.
This problem makes all the Sprint stores basically useless. Since they are located where there are towers, Wifi calling works as expected. As a result Sprint has been absolutely no help. I am wondering if anybody else has had problems with Sprint Wifi calling when unable to see a cell tower? If so could you work around the problem? I am open to suggestions. I consider this a bug in the Spring S7 edge firmware.
BTW, I know that when I can make a call, Wifi calling is used because the pop-up "Congratulations you just made a Wifi call" appears. I purposedly have not turned that off to be sure I am not using that one roaming tower. What is interesting is that I only need to be able to see the "R" by the triangle showing cell tower strength (don't need any bars) and then the Wifi calling icon will turn on. At that point I can make a phone call and even if I lose the connection to that one cell tower (i.e. the "R" disappears) the Wifi call will remain active. I can go anywhere in my house and not drop the call. But once I hang up, the Wifi calling icon will gray out with a slash through it, the phone will indicate that there is no network and the phone can only make emergency calls.
If I cannot get a fix to this problem then I might just have to go back to the last Marshmallow firmware and block the update if possible.
just for the hell of it to check, I turned on airplane mode and left it for 5 mins, leaving it on turned wifi on, and wifi calling connected within a few seconds of wifi connecting. I am on the nougat update. I have absolutely no cell signal as that is turned off. I am able to make calls without a problem.
Reboot your phone into recovery and clear cache and try again.
also, you may want to check and make sure "smart switch" is turned off. it's under the connections > wifi > advanced > smart network switch. I haven't tested it, but in theory it might demand you be connected to a cellular network to work and be causing your problem.
nosympathy said:
just for the hell of it to check, I turned on airplane mode and left it for 5 mins, leaving it on turned wifi on, and wifi calling connected within a few seconds of wifi connecting. I am on the nougat update. I have absolutely no cell signal as that is turned off. I am able to make calls without a problem.
Reboot your phone into recovery and clear cache and try again.
also, you may want to check and make sure "smart switch" is turned off. it's under the connections > wifi > advanced > smart network switch. I haven't tested it, but in theory it might demand you be connected to a cellular network to work and be causing your problem.
Click to expand...
Click to collapse
Thanks for the suggestions. I tried several things. First I verified that I already had "smart switch" turned off. So I went ahead and turned it back on... no love with that feature either turned on or off. Second, I rebooted as you suggested into recovery and cleared the cache. That also did not fix the problem. Third I tried the same experiment as you and turned on airplane mode. I waited a bit (maybe not the same 5 minutes) and then turned on the Wifi and Wifi calling. Again no love. I even tried to make a call and the phone told me I had to turn off airplane mode. For whatever reason Wifi calling will only activate when the phone can see that one tower and starts roaming. At least I can use your experiment to demonstrate the problem at a Sprint store. I might just try using Odin to flash nougat and start clean and see if I cannot get this to work that way. I really don't want to go back to using the Airave although that was pretty reliable for me.
Paul Ganci said:
Thanks for the suggestions. I tried several things. First I verified that I already had "smart switch" turned off. So I went ahead and turned it back on... no love with that feature either turned on or off. Second, I rebooted as you suggested into recovery and cleared the cache. That also did not fix the problem. Third I tried the same experiment as you and turned on airplane mode. I waited a bit (maybe not the same 5 minutes) and then turned on the Wifi and Wifi calling. Again no love. I even tried to make a call and the phone told me I had to turn off airplane mode. For whatever reason Wifi calling will only activate when the phone can see that one tower and starts roaming. At least I can use your experiment to demonstrate the problem at a Sprint store. I might just try using Odin to flash nougat and start clean and see if I cannot get this to work that way. I really don't want to go back to using the Airave although that was pretty reliable for me.
Click to expand...
Click to collapse
So question is, if you go somewhere with signal and wifi you can connect too, turn on airplane mode, leave it on and turn wifi on, does wifi calling work. If not then for sure a reset is in order.
If it does work, then that just tells me the phone isn't really turning everything off with airplane mode on (which is lame) and sprint just goofed up the nougat update and you are the extremely small % that falls victim.
I haven't been able to get WiFi calling to work on my Edge since new. UNTIL I upgraded to Nougat. Now it seems to be working fine. Go figure.
nosympathy said:
So question is, if you go somewhere with signal and wifi you can connect too, turn on airplane mode, leave it on and turn wifi on, does wifi calling work. If not then for sure a reset is in order.
If it does work, then that just tells me the phone isn't really turning everything off with airplane mode on (which is lame) and sprint just goofed up the nougat update and you are the extremely small % that falls victim.
Click to expand...
Click to collapse
Okay some interesting data. I did exactly this experiment this morning. I drove into my office, connected up to the office WiFi and placed my phone into airplane mode. I then turned on WiFi and WiFi calling. Voila I could make a WiFi call!
However I did not stop there. One of the keys to all this is that the one tower happens to cause "roaming" if my phone was lucky enough to connect to it. So for grins I changed the network mode from automatic to LTE/CDMA (Sprint & Verizon are CDMA). When I was back at the house guess what... WiFi calling now works. Interestingly the phone is in "searching for service" mode which implies that the one cell tower seen from my house is either AT&T or T-Mobile which use GSM. By turning off automatic mode everything worked.
It is kind of a bummer but what seems to fix the issue is to choose Connections->Mobile networks->Network mode->LTE/CDMA. Each time a switch is made from Connections->Mobile networks->Network mode->Automatic back to Connections->Mobile networks->Network mode->LTE/CDMA, etc. the phone has to be rebooted. Unfortunately while traveling in a car Automatic mode is desired and at the house LTE/CDMA is best. Switching back and forth will be a PITA because of the reboot but at least I don't have to go back to the Airave.
I tried to explain this to the Sprint rep. on the phone this evening but he did not understand. Over the weekend I might try a clean install via Odin and see if that improves things. I hate doing that because it takes a fair amount of time to put the phone apps back together. I also have my doubts it will fix anything. IMO something broke with the Nougat upgrade and nothing I do will fix it. And as you point out, I am in that very tiny percentage of people who might actually experience an issue.
Paul Ganci said:
Okay some interesting data. I did exactly this experiment this morning. I drove into my office, connected up to the office WiFi and placed my phone into airplane mode. I then turned on WiFi and WiFi calling. Voila I could make a WiFi call!
However I did not stop there. One of the keys to all this is that the one tower happens to cause "roaming" if my phone was lucky enough to connect to it. So for grins I changed the network mode from automatic to LTE/CDMA (Sprint & Verizon are CDMA). When I was back at the house guess what... WiFi calling now works. Interestingly the phone is in "searching for service" mode which implies that the one cell tower seen from my house is either AT&T or T-Mobile which use GSM. By turning off automatic mode everything worked.
It is kind of a bummer but what seems to fix the issue is to choose Connections->Mobile networks->Network mode->LTE/CDMA. Each time a switch is made from Connections->Mobile networks->Network mode->Automatic back to Connections->Mobile networks->Network mode->LTE/CDMA, etc. the phone has to be rebooted. Unfortunately while traveling in a car Automatic mode is desired and at the house LTE/CDMA is best. Switching back and forth will be a PITA because of the reboot but at least I don't have to go back to the Airave.
I tried to explain this to the Sprint rep. on the phone this evening but he did not understand. Over the weekend I might try a clean install via Odin and see if that improves things. I hate doing that because it takes a fair amount of time to put the phone apps back together. I also have my doubts it will fix anything. IMO something broke with the Nougat upgrade and nothing I do will fix it. And as you point out, I am in that very tiny percentage of people who might actually experience an issue.
Click to expand...
Click to collapse
Just out of curiosity have you tried turning your roaming off? Or adjust the settings to not connect?
Sent from Uranus, the only planet with a ring on the inside
izzibew26 said:
Just out of curiosity have you tried turning your roaming off? Or adjust the settings to not connect?
Sent from Uranus, the only planet with a ring on the inside
Click to expand...
Click to collapse
Thanks for the idea.
So while my wife and I were having lunch in town this afternoon, I took our phones and toggled LTE/CDMA and Automatic modes. When we arrived at the house with the phones in Automatic mode WiFi calling worked. I think as long as the phones do not roam and connect to that GSM cell tower, WiFi calling seems to work. So I put both our phones into Home only mode (Settings->Connections->Mobile networks->Data roaming->Roaming network->Home only). So far so good. Both our phones have had WiFi calling activated now for several hours so I think the strategy works. Turning roaming on and off is not as painful as changing the network mode. Still the Nougat behavior is very different, I dare say, broken from Marshmallow behavior.
Paul Ganci said:
Thanks for the idea.
So while my wife and I were having lunch in town this afternoon, I took our phones and toggled LTE/CDMA and Automatic modes. When we arrived at the house with the phones in Automatic mode WiFi calling worked. I think as long as the phones do not roam and connect to that GSM cell tower, WiFi calling seems to work. So I put both our phones into Home only mode (Settings->Connections->Mobile networks->Data roaming->Roaming network->Home only). So far so good. Both our phones have had WiFi calling activated now for several hours so I think the strategy works. Turning roaming on and off is not as painful as changing the network mode. Still the Nougat behavior is very different, I dare say, broken from Marshmallow behavior.
Click to expand...
Click to collapse
It's weird and I would bet money something they accidentally broke and such odd and perfect conditions have to be met to make it present itself, they probably had no idea. The sad thing is, this bug probably affects so few people, and most will probably not be tech people and will just get frustrated and switch carriers, and so the bug probably won't ever get fixed, except by accident possibly.
On a side note have you tried changing your location settings to GPS only. If you have it set for a method that looks for towers that might be the issue right there. GPS-LOCATING METHOD-DEVICE ONLY.
Sent from Uranus, the only planet with a ring on the inside
Greyed out apn settings
Need help I rooted my s7 edge sm-g935p sprint it is updated to the latest update and I have my msl code but can not access my apn settings they are greyed out even if I dial data and try to access it that way please help
..
izzibew26 said:
Wrong thread. Right section, wrong thread. There are 2 ways. I'm assuming you're attempting hotspot bypass
Sent from Uranus, the only planet with a ring on the inside
Click to expand...
Click to collapse
Sorry about that can you hook me up with the thread
YES I am trying to bypass have wifi sharing app but tends to make the rooted phone lag
...
I just tried the experiment. That did not work and in fact broke WiFi calling. So far the only solution is to toggle the LTE/CDMA and Automatic network modes where there is a Sprint tower preferably and then turn off roaming as I drive up to the house. Then WiFi calling works without issue. Nice thought though.
Sent from my SM-G935P using XDA-Developers Legacy app
Paul Ganci said:
I just tried the experiment. That did not work and in fact broke WiFi calling. So far the only solution is to toggle the LTE/CDMA and Automatic network modes where there is a Sprint tower preferably and then turn off roaming as I drive up to the house. Then WiFi calling works without issue. Nice thought though.
Sent from my SM-G935P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Paul Ganci said:
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Click to expand...
Click to collapse
try ##72786# in your dialer
Paul Ganci said:
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Click to expand...
Click to collapse
Found the fix... Updated the PRL & Profile. I guess the phone lost its mind and could not find it once the WiFi was dropped.
Many retail mobiles have "Wifi Calling" function but not any menu entry to enable , The APP can check the hidden function and enable it if can use.
https://play.google.com/store/apps/details?id=com.widget7.wifi.calling