Related
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
jacka$$1 said:
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
Click to expand...
Click to collapse
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Hey!
You dont want to lose your warranty, then use it!
Your phone seems to be faulty...
My phone is experiencing the same problem as of yesterday. Won't connect. Wonder if it's a T-Mobile issue.
laughter95 said:
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Click to expand...
Click to collapse
Its only glitchy coz you have stock rom
Cyanogen is really stable and adds alot of features / functionality.
Fair enough you dont want to lose warranty but i remember in the general thread that lots of hardware failures and others can still fix your n1 under warranty even though they unlocked the bootloader.
I too have this problem, hopefully the 2.2 update will fix the problems.
Can you guys confirm if its android or your service provider thats causing this...
laughter95 said:
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Click to expand...
Click to collapse
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
rensky said:
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
Click to expand...
Click to collapse
^ it worked! my phone reconnects to the cellular network after what Google/Tmo did for me on the phone!
I haven't tried calling tmobile, but it is NOT something that will be fixed by hopping on cyanogen's rom. I've been rooted on cyanogen's rom for quite some time and this problem still exists on my n1 which is SUPER annoying. I will try calling tmobile to see if they can fix it on their side, but rooting is not the fix here.
I had the same issue. I used anycut and phone info shortcut and changed the wireless default setting to us and it totally fixed the problem. Have not had that issue again.
-------------------------------------
Sent via the XDA Tapatalk App
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
I get this too with an at&t phone.
Have asked for a replacement device from HTC (since the reception is crappy to begin with).
I also have audio quality problems when reception is only 1-2 bars.
Will see if the new phone is better.
I had this problem regularly. It hasn't happened once since I upgraded to Froyo, so I think it has been fixed in that release.
sometimes have this too, i fix it by going to the settings > wireless > mobile networks > APN. at first i deleted and retyped my password in the selected APN, now i just click my network in the APN settings, don't change anything and leave. It immediately reconnects after that.
edit: and i have stock froyo & live in belgium.
I got a new, replacement phone from HTC today.
This new phone has a BIG PROBLEM with this issue.
Even if I am only without reception for a couple of seconds (go through the garage, etc.) it will not connect to any network until I reboot.
My old phone would only experience this problem maybe 25-35% of the time.
Very, very annoying!!!
wildfyr said:
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
Click to expand...
Click to collapse
I had similar issues and called tmobile support. I was first linked to Google support. They went through the similar process as described by in the first page. (#*#*4636*#*# select USA band etc). While I was on hold, they called t mobile tech support and had them reset network connection and tried to get me onto a different tower etc.
Tmobile support stated that my sim card (had for about 2 years) was the cause of the issue as they can't handle smartphones as well as their new sim cards. They also said the new sim should improve reception and connection stability (Don't see how a new sim could do this but what do I know?). Moreover, they noted my account and told me to go into the nearest store for a new sim card. Went into the nearest tmobile store told them the issue, they pulled up my account and gave me a new sim. Took less then 5 minutes and I have not had the issue with staying connected to the tmobile network.
I will update this after a few days to see if I still have the issue.
I have the same problems that i cannot connect to network here in germany. first i think it was my sim card, but befor i had another provider (E-Plus) where i had the same problems with reconnecting to network. and one day my eplus sim card is broken so i had to buy a new one by t-mobile. i have tried a lot of roms from here (cyanogen/ 5.0.7 /5.0.8T5 Kangorama rodriquezstyle and leofroyo) everyone seems to have the same problems with reconnecting to network. i hope im not alone with my problems and someone can help.
hmm...
Count me as another. I just upgraded to froyo and it went beserk. Had no service for a while. It would only come on after constantly tapping "select network automatically" until it kicked me out of the menu. It started getting better but kept kicking me out of 3g. I set it to stay always on 3g and it seems to be better... still I'm going to call tmobile and see if I can get a new sim as well.
Thanks for the info guys!
Like many others, my phone has a tendency to drop 3g unless I enable Data Roaming. This has been the case with My D1 with 2.3.3.
Now that I have the Droid 3, I have the same thing. No surprise there.
HOWEVER, when I enable Data roaming on my D3 and then go into an area where the phone drops to 1x then no data, I get a notification that Data connectivity has been lost because Data Roaming is Disabled.
If I pull down the notification bar, it says I can select the bar to go to the setting. I do. Sure enough, the Data Roaming Enable box is Unchecked.
I check the box. Go to my home screen, and the notification will reappear. I can do this all day.
If I go to my home screen, ignore the notification and go to settings, battery & data manager, then data delivery, the setting is unchecked....BUT....If I access the menu this way; the setting will be retained until the phone is brought to an area where data signal does the 3g to 1x to no signal thing. Then it starts all over again.
Any suggestions? Anyone else getting this? I received my D3 over a week ago, and finally exchanged the phone for another one. That phone lagged and had random freeze issues. This phone has none of those issues, but still has the Data Roaming Enable setting not retained problem.
Wasn't this an issue with CM7 at one point? The d3 claims to be running 2.3.4, but it is hard to tell with all the Motoskin draped over it.
I have also noticed that (in my area) if I have data roaming enabled, my battery life is much improved. With it off, my battery drops like a rock.
I have contacted Moto about the issue and reported the bug; but all I am getting is the "we'll look into it" brief email. Like I'm some kind of first-time Android user who doesn't know how to use my phone.
Please tell me someone out there is having this too, or that there is a patch that Moto just hasn't released yet....
Thanks in advance everyone.
UPDATE:
2nd phone, all data connection is lost. No phone, 1x or 3g. Phone is awake, and battery settings are set to Performance (No Battery Savings).
Data manager is disabled (no stoppage of data)
When going into an area where I ALWAYS had "EXTENDED NETWORK" data available at 1x speeds prior to this phone, the phone says no data connection.
I look and my Data Roaming Enabled checkbox has been unchecked.
I check the box, click OK to agree that I may incur Roaming charges. The phone will reconnect to data at 1x or 3g depending on where I am.
If I look at the phone 5 minutes later, the checkbox is Unchecked again for allow data roaming. Sometimes less.
This only happens after the phone goes into a weak coverage area.
I have tried rebooting the phone. The setting stays retained after reboot, but is lost as soon as I go into poor coverage.
I have tried factory reset. Setting stays until I reach a poor coverage area.
Already exchanged for another phone. Same issue.
Changed phone from Global to CDMA mode and network to automatic. Setting still does not hold.
It is most strange though, that it doesn't happen until after my home network is lost. The setting will hold until then.
Without that setting checked, I cannot connect to my "Extended Network", which in my area is a no-cost option. I keep checking the box, only I can't get the setting to stick when I go to a weak coverage area.
The coverage area should not make changes to the retention of allowing of data roaming checkbox. Something is improperly referenced in the software.
Motorola's out-of-country sweat-shop customer-no-service department wants me to ship my 2nd brand new phone to them (5-7 days for them to process and receive it+whatever it takes to ship to them) and take between 14-21 days to "repair" the phone, and then take another 5-7 days to package, ship and return to me (all at my expense). Why am I sending a new phone that is defective "out of the box" to be repaired??
So I'm supposed to go without my phone for 5 WEEKS because they have a software problem??? It can be duplicated every time, and on more than one phone. They have the old one. Fix that and send out the update please!!
Am I the only one that has had this issue? Seriously, no one else?
Any help would be greatly appreciated. This is frustrating as heck. I love the phone, but this is ridiculous and makes it rather un-usable depending on where I am. I NEVER had this with my D1! Moto, what happened?
Thanks everyone. +1 if you've had the issue please.
Same Problem
I also have this same problem.
After reading other forums, I thought it may just be the Droid 3 or a Motorola problem. I ended-up turning back in my Droid 3 after Motorola said it was a Verizon problem (which really is not the case). Now, after reading your thread, it makes me wonder if this is a Android OS issue.
I really hope it is not a OS issue, I have wanting an Android phone for a long time.
At my house it always kicks off the data roaming option. I really have no idea what is causing it.
Just wanted to post so that you know your not the only one!
Thank you.
I have run a logcat and have traced the problem to Motorola's battery and data manager service. It is not the OS itself, from what I can see.
It seems that under these particular conditions, the battery and data manager service crashes. Though this should not be a major problem in and of itself, though still not right and needs fixing there too. The service promptly restarts and then loads the settings that were enabled at the time of the crash from a secure data folder. (Or it's supposed to)
The problem comes into play when these settings are loaded. Enable Data Roaming is "loaded" as No(off) any time the service loads these values after a crash of the Battery and Data Manager service.
Unfortunately, as usual, Motorola is dragging their feet at releasing the source code for the Droid 3. This may or may not help the issue, as the Battery and Data Manager service that crashes is a part of Motoblur. Meaning, they aren't going to be forthcoming with the information.
They also are being a typical OEM in their refusal to believe that they could have made a mistake when programming and that they have something to fix.
My Droid 1 has run 2.3.3, 2.3.4, and 2.3.5 and this has NEVER been an issue keeping the setting retained. This is not an issue on our INC2, which is running 2.3.4 in all the same areas that cause my D3 phone to lose the setting. I am also running an Eris with 2.3.5 and it does not have the issue. This is strictly with the D3 from what I have seen.
It's funny how Moto is blaming Verizon for an issue they say doesn't exist. If there isn't a problem, how can that be the network's fault??? The network doesn't change that setting in the phone. Software changes it. In this case, poorly written software added onto the Android OS. Too bad, the OS works fine until Moto putzed with it (Blur).
The OS is not the issue here, it seems the D3 software has two problems:
1 the Battery and Data Manager service shouldn't crash like that.
2 it should return the proper settings if it does.
If I had the chance to do it all over again (knowing what I know now), I would have said send me an INC2 as a replacement. I honestly figured it was a phone hardware problem and the new phone (under warranty) would fix it.
Honestly, I am completely disappointed with this device. That may change when root is obtained and I can get rid of the poorly written trashware that seems to plague this phone. But right now I'm most disgusted with the fact that it doesn't work right and Motorola couldn't care less, even though it's their sofware that is the problem.
I have pruchased my last Motorola product, and am not holding my breath that Motorola will either care or fix their problem. I am certain the future rooted ROMs will be able to transform this lagtastic, glitch-ridden, battery pig into the elegant piece of hardware it has the potential of becoming.
Sorry Moto, sometimes the truth hurts.
Thanks for the support that it isn't only my phone or service area.
Others please +1 as you experience it. The issue is logcat documented and now confirmed on at least 4 devices.
Sent from my DROID3 using XDA Premium App
I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?
This is the response I received from Motorola. They need to get a move on with a fix for this huge goof up.
"Thank you for reaching out to Motorola.
We apologize for all the inconvenience and appreciate your patience. The Support Engineers have been made aware of the issue with the "Data Roaming" feature of the phone; and there are currently working on a possible resolution for a future update. You will need to manually change the roaming option back until fix is available. The Support Engineers have not provided an ETA on when this will be available.
If you have any additional questions or concerns please contact Customer Care at (800) 734-5870."
blkwlf said:
I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?
Click to expand...
Click to collapse
The latest developer update, which is currently in soak testing, has fixed the issue for me.
No formal release date yet on the over the air (ota) version's release date, but I would expect out in the next couple of weeks as long as everyone else had the same results I had with the test update.
Update will upgrade system version from 5.5.959 to 5.6.890, and the baseband radio will be updated at that time as well as the kernel.
So there does seem to be a fix, despite the terrible customer service at Motorola. Honestly, it sucks! I had this update last week, and I'm sure somebody knew this was intended to fix the problem. Not once has Moto asked for information or applied for releasing a phone that was not ready.
Instead, we got canned bot responses and the general feeling that Moto just doesn't care now that they have our money. It is really sad.
Lets hope Google can straighten it out.
Fingers crossed. Though now that we have root, and a custom recovery possibly by week's end; I could care less about Moto. My next phone won't be Motorola...fool me once, shame on you; fool me twice, shame on me.
Sent from my rooted, de-bloated, test-updated DROID3 using xda premium
wattnxt said:
The latest developer update, which is currently in soak testing, has fixed the issue for me.
Click to expand...
Click to collapse
I have also flashed to 5.6.890, re-rooted and de-bloated. So far, the new radio has done nothing to help my issues with the data roaming becoming disabled. Have you tested the new software under the same conditions as the old?
I may have to retract my last statement... my phone did auto disable the Data Roaming once after updating, but since then it has been fine. Hopefully the update truly did fix it!
Sent from my DROID3 using XDA App
I have purposely tried to get the setting to fail. Same result for me as you saw; I got the same old warning once and have not seen it again in over a week now.
For me this was huge, as it failed 20 plus times a day at work. All I had to do was walk down one specific corridor, and by the time I got to the other end my setting would have been unchecked. So going a week with it staying retained (in global mode too by the way) is monumental proof for me it is fixed.
Now I have seen this on the D2 global twice this last week. They don't have a fix yet either, but technically this one isn't official until it's pushed ota.
Good luck all. More news as I have it.
Sent from my DROID3 using xda premium
I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!
Baconstrip said:
I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!
Click to expand...
Click to collapse
So... do the update. You won't regret it
blkwlf said:
So... do the update. You won't regret it
Click to expand...
Click to collapse
I was thinking about it, but I was hoping to wait until it's officially released. Taking longer than I expected
Still happening in 5.6.890
I'm also suffering this very annoying problem, and have found no solution for it.
I'm using stock XT862 5.6.890 and I need to re-enable data roaming 20 times a day. I use a carrier in Spain that has very little owned towers so it's doing national roaming very often. Every time I switch from an owned tower to a roaming tower, I get the "Data roaming is disabled" notification and need to go to "Battery & data manager" -> "Data delivery" to re-enable it.
I have searched A LOT and tried all solutions I have seen, i.e. modifying build.prop in a myriad of ways, but it still happens.
I have also tried Minimoto v1.7 which has XT862 5.7.906 but it's even worse: It still happens but that ROM has stripped out Battery & data manager so I can't even enable Data roaming. A shame because the ROM is really awesome.
Please help a poor soul! :angel:
I finally took the problem in my own hands and managed to make a small app that re-enables data roaming at the touch of a button.
I needs to be installed as a system app for it to work, but it works! :laugh:
You can get it here http://forum.xda-developers.com/showthread.php?t=2165364
My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151
flash a different radio/modem.
Same here. Just spoke to T-MOBILE and rep said it is an issue with a lot Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Edit: change all to a lot
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
That is probably the same issue. I can receive texts, but can't send without a reboot.
So far.. the 5.39 developer modem has kept connection for an hour. Which is good considering how intermittent it was.
What really blows is that my phone and service was perfect until this event.
Even in the mountains of the Philippines last year, my phone worked perfect.
You may try dp5 my WiFi and Mobil got a lot better, but I'm not on t mobil. Flashing only the radio is maybe not enough, if you are on stock anyway you have nothing to loose
Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.
tmicrd68 said:
Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.
Click to expand...
Click to collapse
Interesting.. I hit the speedtest app right after a reboot to check, and it immediately borked my connection several times in a row. I like your theory..
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..
Jeff_in_LA said:
My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
Jeff_in_LA said:
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!
Click to expand...
Click to collapse
JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
You guys have a lot of company... > http://www.androidpolice.com/2016/08/04/some-nexus-6-owners-report-data-outages-on-t-mobile/
I'm running stock N6, not rooted; bootloader locked; on T-Mo. While on WiFi, with WiFi calling enabled, I would get out of range of WiFi and cel data would not return without full reboot. If I disable WiFi calling before leaving WiFi service, cel data flipped as normal. I tested again with manual WiFi disable and if WiFi calling was on before the cut out, cel data never flipped on.
[Edit] I did notice though that when it does flip like it's supposed to, I'm connected at 3G. LTE doesn't kick on.
simms22 said:
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..
Click to expand...
Click to collapse
Stated what T-Mobile told me.
Ok, I did flash the beta radio 5.39.
It might be coincidence, but my phone has a solid connection for three hours now.
Hopefully they fixed it on their end.
I am not seeing this on my N6. Still on 5.1.1 LVY48H.
toastgodsupreme said:
I am not seeing this on my N6. Still on 5.1.1 LVY48H.
Click to expand...
Click to collapse
what radio can work on 5.1
Cause i have flyme rom, but have calls issue, ian not receiving any call. The other end saids it rings but my phone does not ring at all on calls.
It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.
ttabbal said:
It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.
Click to expand...
Click to collapse
T-Mobile acknowledges the issue. The one universal is that it's with the N6, not with other phones. There are a bunch of carriers around the world that are having the problem.
When mine breaks, SMS fails. The only mobile connectivity available to me is phone calls.
The Reddit thread mentioned above has people saying that disabling Location Services works. Far from ideal over time, but if it's true, it's something. I tried that. We'll see how it goes. Freezing Google Connectivity Services is nice, if it works without introducing other problems, because it would allow us to keep using whatever connectivity we like without data breaking.
I had a Bluetooth connectivity problem a year or more ago that surfaced literally out of nowhere and on every device I tested, a little more than ten of them. This was independent of ROM, root status, device, anything. The feature in question worked on every Android device we had tried one day (and for more than a year prior) and failed on every one the next. Sounds crazy, but it's what happened. Google barely paid attention to my bug reports and ran me in circles when they did. Never got fixed.
I trust this matter will.
Both my nexus6s are doing this with heavy GPS aps, data will shut down.
Sent from my Nexus 6 using XDA-Developers mobile app
I've had GCS frozen for a long time, running 5.39 radio & it happened to me. There is definitely something occurring substantially with our devices/network be it software or hardware based. Apparently T-Mobile & Google are working on it but the fix might not come until next week. I'll probably install latest N preview when I get home.
Hi! Thanks for reading my problem.
I have a tmobile note 8 that I have successfully switched to verizon firmware according to the guide here. It got the verizon boot logo and bloatware just like vzw phone.
It work perfectly after the switch, 4g lte ,call or text all work.
But it will drop after a while of use. It can be a few hours or few minutes. I cannot receive call, cannot access internet, cannot make call...
If I restart it all will become working again for a while. Any recommendation how to fix it? Thanks again.
I have a note 8 (SM-N950F/DS) for about three weeks now. I am using FP on AT&T network. When I just got it, especially while I was moving in the car or train, it would lost the data connection quite often even though showing full bar signal. I had to put it on air plane mode then switched back to reconnect.
Then after 1-2 weeks of use, the issue went away. I don't know it was due to the latest update (I am on Dec security patch now) or some kind of the phone learning my travel pattern.
Benson830 said:
Hi! Thanks for reading my problem.
I have a tmobile note 8 that I have successfully switched to verizon firmware according to the guide here. It got the verizon boot logo and bloatware just like vzw phone.
It work perfectly after the switch, 4g lte ,call or text all work.
But it will drop after a while of use. It can be a few hours or few minutes. I cannot receive call, cannot access internet, cannot make call...
If I restart it all will become working again for a while. Any recommendation how to fix it? Thanks again.
Click to expand...
Click to collapse
caiwh said:
I have a note 8 (SM-N950F/DS) for about three weeks now. I am using FP on AT&T network. When I just got it, especially while I was moving in the car or train, it would lost the data connection quite often even though showing full bar signal. I had to put it on air plane mode then switched back to reconnect.
Then after 1-2 weeks of use, the issue went away. I don't know it was due to the latest update (I am on Dec security patch now) or some kind of the phone learning my travel pattern.
Click to expand...
Click to collapse
Interesting, My phone lost it while I m at work... not even moving
For the longest time I thought was alone here. VZ Wireless Note 8 user here. My signal also just drops out of no where. When I look at my screen the 4G LTE upload up arrow is the only one turning up and down. Sometimes this issue will go away on its own after a few minutes or longer. But, randomly out of nowhere this started to happen. Few weeks now and counting I'm guessing it has something to do with a update that I recently upgraded to. I never had this issue when I first had my phone.....
I also have the problem.. Also Verizon branded Note 8.
I see a global Android update coming to possibly address this
From Android Headlines (AH):
"New Android Update For Galaxy Note 8 Improves LTE Stability"
"The latest Android update for the Galaxy Note 8 was designed to improve the stability of the phablet’s 4G LTE functionality as it specifically addresses a bug that occasionally caused interruptions of such connections, as revealed by a changelog published by Samsung earlier this week. The update appears to be rolling out on a global level, with its distribution officially starting on Wednesday, 15 days after the Seoul-based phone maker launched the latest security patch for the same handset."
Starting this month..
Anyone with ideas how to resolve this in the meantime?
I am still having this problem after oreo update.. I don't think I want samsung anymore..
Ok guys those who have Verizon, go to settings, mobile settings and change network to cdma and reset your settings. Turn off the phone, pop the sim tray out, power up ur phone while sim is out and turn off the phone again, this time push ur sim card in and turn on your phone. It should solve the problem of signal being dropped. Good luck.