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?
a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.
So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864
Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.
*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does
I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?
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
Hello everyone,
Informations
Phone : Nexus 6
ROM : Euphoria OS 1.0 with included kernel
I have a little problem with the phone network...
I have just install the ROM (3days ago) and everything worked fine.
After the first reboot, I had a network problem: no more network (just phone)
Bluetooth is OK,Wifi also ect...
No extra apps installed.
Any idea?
Thanks
Edit : French phone/network (FreeMobile)
I am having issues over here also. My data randomly stopped working on my way down to memphis, randomly would start to work again. I tried a new rom, it slightly got better, but would cut out of data every 5 min. Kinda got it better by switching to tmo in the apn's. Now just installed sinless, and it is no longer working again.
So, same problem and no fix...? :/
Holy cow! I thought I was the only one! I mean this problem really sucks(and I have wasted a lot of my hours trying to fix it), and have been thinking of creating a thread on this problem until I saw yours.
Okay let me start with what I'm on:
N6: 64gb blue
Rom: Stock
Rooted: Yes
Any other modification: No, only think I did was unlock and do chainfire su root.
Network: VZW
I have had this phone since Dec with no issues other than random reboot every so often.
Now to the problem I had, I went out to the middle of MO for a weekend get away (on Feb 14th). The whole time I was out there it showed 1x even though I was still getting LTE speed. Didn't think much of it until we moved further into the hilly parts of MO were I lost service. Thought it was just where we were at, and thought it would come back once we got back to the hotel we were staying at. It never did. It would say "No Network found" only allow 911 calls.
Spent the next 4 days working With VZW with several trips to the store, and talking to tech support. They made sure my IMEI was not blocked on their side. We used several sim chips, they would all do the same thing, quickly connect then disconnect and go back to no service.
So I did a factory reset, still didn't help. I finally did a fastboot flash of 5.0.1 stock again, this fixed the issue. Until I used titanium backup to restore my sys setting. Then it would drop and not reconnect after the reboot. So I did fastboot flash again and it hasn't happened again since last Thurs. I just restored my app's again to make sure it wouldn't fail to connect over the weekend, and rebooted several times. No issues so far, but I called Motorola and they are RMAing me a new one, because I don't have any trust in this one anymore. They are out of 64gb ones, and they will get back to me in a week.
Questioned to anyone who has gotten a RMA from Motorola:
Are their "like new" replacements okay? I got a few from them when I had my droid x, and they were crap. So I wasn't sure if that is still the same for the N6 or not. I have a feeling its not, but just wanted to get other peoples input on that process.
Thank you for creating this thread, and for everyone's time!
Edit: Had the same issue network wouldn't work, however WIFI, Location, Bluetooth would.
Check your APNs..... make sure you are on the correct one, and that both of APN protocols say IPv4.
Sent from my Nexus 6
APN is for Internet(3G) and MMS, no?
Because we have a phone network (call & SMS) issues.
On my side, APN are OK, but still don't work...
Edit: New !
Everything works fine on :
- Paranoid Android 5 Alpha 1
- Chroma (Latest)
But not work on :
- Euphoria
- Stock ROM
Edit 2 : It works now !!
I seen that I had several issues around the APN side. I mean, I can't add APN, sometime I can. Sometimes APN reseted themselves, sometimes it was OK. Then, I had read the solution above: security tab.
I had just remove my 3rd party lockscreen (HiLocker). Restart the phone and voilà ! After the reboot, my phone ask me the pin code, and all APN are here.
I hope it can help...!
Some times I will see the APN settings, and sometimes I won't. Right now I don't. When it does show up it shows VZWINTERNET selected. There are ton of other options, but they don't work either when the problem was seen.
Is what your experiencing data going in and out? I'm on Sprint and I thought maybe it was just an issue with Sprint. I have or need to read up more on APN because it does get bothersome. I even have issues where sometimes my SMS gets hung up for minutes in sending mode before they actually send. Would be nice to have this corrected.
Sent from my Nexus 6 using Tapatalk
Casper34 said:
Check your APNs..... make sure you are on the correct one, and that both of APN protocols say IPv4.
Sent from my Nexus 6
Click to expand...
Click to collapse
This solved my problem. One of them was on IPv6.
T-Mobile Nexus 6; 32GB
Thanks!!
xjedi said:
This solved my problem. One of them was on IPv6.
T-Mobile Nexus 6; 32GB
Thanks!!
Click to expand...
Click to collapse
The thanks should go to @Circaflex though... he told me how to fix my issue and thought it could be useful here. I'm glad it was.
Sent from my Nexus 6
Casper34 said:
The thanks should go to @Circaflex though... he told me how to fix my issue and thought it could be useful here. I'm glad it was.
Sent from my Nexus 6
Click to expand...
Click to collapse
No my whole problem was that it would drop and no matter what I would do wouldn't reconnect to the network. I tried a lot of things to fix it (see above). APN would appear and then disappear from the menu. Right now its working on the network as of last Thurs. and APN options is not there.
collegencmc said:
No my whole problem was that it would drop and no matter what I would do wouldn't reconnect to the network. I tried a lot of things to fix it (see above). APN would appear and then disappear from the menu. Right now its working on the network as of last Thurs. and APN options is not there.
Click to expand...
Click to collapse
The APN option will not show for a CDMA Carrier, Sprint or VZW, in your case VZW. APNs are set by the Sim from Verizon so you shouldn't be messing with those, nor should the option show up under mobile network settings.
It was like you. Sometimes network was OK, and sometimes, it was down...
So current working theory is that it was a software issue that cause the problem. I'm just unclear as to why it happened, and how to stop it from occurring again . I do have OpenDNS enabled on the phone, could that cause the problem?
Heres my problem, I'll drop out of an LTE zone, and 3G/HSPA will come on line. Only if its on 3G I never get any data, and sometimes with HSPA too. Not until LTE comes back on line again, but then if I'm trying to stream say music 3G/HSPA wont let LTE take over again for a pretty long while.
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?