At my work I get 0-1 bars of Sprint service, and my phone often roams onto Verizon (we have dozens of Verizon repeaters in our building). The problem is that quite frequently lately it will get stuck in roaming mode and never switch back to a Sprint tower. I have 6 bars of Sprint service at home, but it will remain in roaming mode. I have the newest PRL (60670), and the old PRI (1.34_003).
Anyone else ever experience this? Any idea what I can do to fix it?
I have had this happen in the past as well. What I did was go into settings and change the roaming option to "Sprint Only" which forces the phone to switch back to the Sprint network. Then you can change the roaming option back to "Automatic".
I get this a lot as well. I've started to make a habit of turning on airplane mode, then turning it back off... when it scans for signal it will go back to Sprint.
Sorry if i'm stealing this thread. Is it pretty bad if my phone has to go in roaming to get signal in most my house? I've seen the threads about people getting a airwave because they get dropped calls, but since i have to roam in more than half my house, does it seem possible i could get one from sprint?
And my house is in the middle of town, if you go outside there's 4g, but not inside.
fastamx79 said:
I get this a lot as well. I've started to make a habit of turning on airplane mode, then turning it back off... when it scans for signal it will go back to Sprint.
Click to expand...
Click to collapse
Same here, I just toggle airplane mode on and off.
Same thing on my EVO. It'll roam when it should but it won't switch back to Sprint when it should.
I chatted with Sprint asking why this happens. They just said I have free roaming. No reason why.
Yep, My Evo has been doing this as well. Been doing the airplane toggle trick. Thought about just leaving it, but was thinking that it may burn my battery faster? Anyone have any thoughts on that..
My PRL is also 60670, but I have the 1.71_003 PRI.
Guys if you have any type of active data connection the phone will not drop the roaming.
I roam at work too and if i turn on Aonline radio, tjen get in my car and drive, so long as the radio streaming is going iy will never drop the roaming.
Sent from my PC36100 using XDA App
Messed with the phone again tonight. Got stuck roaming again. I was not transmitting anything, and even ATK'd everything to make sure. Who knows, not really a big deal, unless I am eating more battery.
v_lestat said:
Guys if you have any type of active data connection the phone will not drop the roaming.
I roam at work too and if i turn on Aonline radio, tjen get in my car and drive, so long as the radio streaming is going iy will never drop the roaming.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That makes perfect sense. I sync with my Exchange server at work and the way EAS works is a constant connection between the client and server. One question though. Has your phone switched back to your carrier with no data connection?
Yeah just disable always-on data or cycle airplane mode to make it switch back. As long ad its maintaining a data connection it will wait to switch back from roaming so it doesn't unnecessarily disturb your connection if you're in a poor service area. It shouldn't be using any more battery.
Also, atk is bad.
Hi,
I bought my new Note in June. It's great, but I have a little problem. In my school, I carry the Note in my pocket. INSIDE the school, I don't have signal of any sort (data signal/for calls/for SMS), and my friends have the same problem. But the last week I have this problem: when I left the school, I recived again the data and mobile signal. But now, when I go out, I only recive data signal. Putting on Airplane mod/turning off and on data signal does not works. It loses the signal. I have to restart the phone and THEN I see the H+ icon with the two arrows. Outside of the school I HAVE data signal, because when I restart the Note, it comes again! Please I need help, I don't want to keep restarting my phone every time I left the school!!!
Greetings!
alancito10t
Similar issue happens at home but I have an at&t microcell and attribute losing data to that. I only notice that I lose 3g data when I try to send an mms and I get an error that says 'will try sending sms when data returns'. I just put the phone in airplane mode and then turn airplane mode back off. That seems to fix it. There was a thread a while back that mentioned a tip on disabling fast lock or fast wake something in the mobile network settings for at&t. The poster said it was enabled by default and that it did no good to our phones other than to make them slower connecting to at&t 3g. I hope someone remembers that thread.
inurb said:
Similar issue happens at home but I have an at&t microcell and attribute losing data to that. I only notice that I lose 3g data when I try to send an mms and I get an error that says 'will try sending sms when data returns'. I just put the phone in airplane mode and then turn airplane mode back off. That seems to fix it. There was a thread a while back that mentioned a tip on disabling fast lock or fast wake something in the mobile network settings for at&t. The poster said it was enabled by default and that it did no good to our phones other than to make them slower connecting to at&t 3g. I hope someone remembers that thread.
Click to expand...
Click to collapse
Do you know a solution for International version? Entering in Airplane mode or turning off data does not works.
I recently got a voice and text only sim card from Tbaytel (Rogers) to use on my spare phone while working up in Northwest Ontario (DMTS/Knet towers). I sim unlocked it (was a Bell phone) and I am having tons of problems. The phone is rooted and currently running JDCTeam Optimized CM12.1. Firstly, I can not get a signal consistently. If I go into the network settings and move between LTE/3G/2G etc. I will get a signal right away and it will send a text and call out (call outs have problems too I'll address that at the bottom) until I turn the screen off or the phone sleeps by itself. When I turn it on, it just says No Service/RogersTbaytel until I play with the network settings again. And, when it does get a signal after switching the settings around, it's full bars so it's not a tower or area issue.
As for the calling out, it will dial out when I have a signal and my other phone will receive it. However, the S4 phone kind of lags on the dial out and when I pick up the line with my other phone there is no voice transmission from either phone but the call seems to be connected. I also can not seem to end the call with the S4 but I have to end the call with my other phone.
I have tried a few different ROMs, the Google Play Edition 4.2.2 (IIRC) one, CM10.1, CM11 and they all have this same problem.
Any assistance would be greatly appreciated. I have decent knowledge with rooting and such but don't get super technical with me. I should be able to do just about anything with a bit of guidance though.
Thanks.
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
I use MVNOs because I am on a tight budget. With MintSim and MetroPCS which use T-mobile I had a below average signal on this phone and with Boost which uses Sprint I had a dreadful signal. Currently I'm using a Verizon MVNO which has an excellent signal except for one issue. The signal will be great for a day then it will become poor. The signal strength will not return to previous strength unless I power the phone down for a minute and then turn it back on. Then the signal will be great for about a day again until it goes bad and I have to turn the phone off and on again.
I tried a factory reset which didn't help. Toggling airplane mode on and off doesn't help. Rebooting the phone instead of powering off doesn't help. Changing the preferred network type in settings doesn't help.
If I type *#*#4636#*#* and change the network from LTE/CDMD/UMTS (Auto PRL) to one where LTE is replaced by a different network and then switch back to LTE/CDMA/UMTS that restores the strong LTE signal but powering the phone on and off is faster.
I could change the APN settings with T-Mobile but with Verizon the APN settings are greyed out and there is no way to edit the current APN or add a new one.
Mobile Data Always Active is already enabled in developer options.
Does anybody know what I could do so the Verizon network strength doesn't eventually drop requiring shutting the phone off and turning it back on to refresh the network connection?
I have owned a lot of phones over the years but never one with signal issues like the PH-1. Essential support won't help because they escalated my ticket to RMA when I was still on T-Mobile. Since an RMA would provide me with a refurbished phone that somebody else probably returned due to the signal strength issues I would rather figure out how to get my current phone to work right with Verizon if that's possible.
When I went out I had no data despite the signal meter showing a strong signal. It turned out my phone had the wrong APN (Verizon instead of Trac Wireless) but unlike GSM carriers the APN settings are locked so TotalWireless (which is owned by Trac Phone) had to send my phone the correct APN. My data actually works now and so far the signal has been very strong but it's too early to say if the same signal problem I wrote about will pop up again since the APN was only corrected a few hours ago.
If nobody else has experienced a similar issue with the quality of the Verizon signal losing strength after the phone has been asleep for an extended period of time then maybe my phone is defective after all. I guess I'll just keep my fingers crossed that the signal still looks good when I wake up tomorrow.