Database Develop

Someimes My Nexus One won't send text messages or make phone calls unless I reboot :(

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?

[Q] Phone Roams All The Time

My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.

EtherBoo said:
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
Click to expand...
Click to collapse
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.

dr_w said:
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
Click to expand...
Click to collapse
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.

EtherBoo said:
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
Click to expand...
Click to collapse
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.

dr_w said:
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Click to expand...
Click to collapse
Alright, so, I have some interesting news.
I got a replacement device from Asurion - not just a replacement, a brand new device out of the box. I pulled it out of the box, swapped the SIM, same exact issue .
I went to Verizon and *****ed up a storm. They basically said "you bought it on eBay, not our problem" (I actually did Swappa - but they don't know Swappa and they do know eBay).
So I got the guy in the store to do some digging, and apparently Verizon has a point opened up with LG as they're seeing this on more and more devices - especially since KK came out. So I figured I could try an older radio. The device was on 12B when it arrived. I just flashed stock to 10B and it's the same issue. I don't know what's going on at this point - nothing makes sense but its apparently a known issue that's been appearing since the KK update.
I'm going to call Asurion and request a new device again since this one is doing the same thing, we'll see what happens. I'm still leaning towards hardware and thinking there was a slew of bad radios that went out.
Just for giggles - and I have no reason whatsoever to think this will work. I'm going to swap out the new SIM that came with the phone. Originally, I just put in my old SIM since the new one was taking too long to activate. I'm having the exact same issue I had previously. With that, I'm going to leave the new SIM in and see if it has the same dropping issue. The guy in the store had mentioned he could swap out the SIM but after a few days it will crap out again... which makes zero ****ing sense. Because of that, I might as well see what happens if I pop a new SIM in. While again, this makes 0 sense, I'm wondering if maybe the phone is frying the SIM somehow?
Again, it makes no sense at all, but I have nothing else left to try other than getting Asurion to repeatedly send me phones until I find one that works or they replace for another type of phone (which I REALLY don't want). I'll drop an edit in an hour or so if what I try makes a difference.
Quick Edit:
I COULD just keep going to the VZW store and have them repeatedly swap out SIMs since it will fix it for a few days .
EDIT:
Got the new SIM installed and it's working. The guy in the VZW store told me that we can keep swapping SIMs and the same issue will happen, which again, makes no sense to me. I'm at a bit of a loss to be honest. I wonder if it's possible that my old device was frying the SIMs (again, makes no sense) and that maybe the new SIM not going in my old device will fix the issue.

What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk

dr_w said:
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The only ROM I've ever run was CM11.
Same thing happened on stock though after flashing through the LG Flash Tool. Then, with the new phone from Asurion, used old SIM - 3G only. Used new SIM - 4G sticks.

[SOLVED] Phone network issue

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.

Nexus 6 LTE connecting issues... strange!

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.

Call dropping after 58.1.A.5.159 update

Hi folks,
after the last update I have a big problem: when I start a call suddently the signal goes 0 (on both SIMs) and I receive a "no network" error. After a few seconds the signals go back but sometimes I have to wait for 15 or 20 minutes to call otherwise the call drops again.
It happens even when receiving calls.
I have this problem at around 30/40% of calls I try to make and this is very disappointing because I use the phone for work and I do many calls everyday.
A user on an Italian forum had the same problem two updates ago, he told me that he solved after a reset of the phone. I'm desperate now, tomorrow it's holiday in Switzerland so I think I will do it.
NOTE: It's strange nobody on internet is talking about this problem... It's only me?

Having the same issues with this build.
I have the HK dual sim, which I flashed the SEA firmware onto last year.
I'm having to go back to my old phone until this is resolved, I have missed several calls because of it. I tried a factory reset, which seemed to clear it up for a short while, but the problem came back.

Same problem here. After the update of
51.1.A.5.159​I cannot receive or place calls
I cannot receive or send messages
IF I am inside a building. The network goes from 2 bars to 0 when I try to call. If i go outside of the building the cellular network is stronger (full) and calls are going through. I suspect there's something wrong with the baseband maybe? Which is what I was trying to search for yesterday. Was wondering if the current baseband for Android 11 is new or maybe it is the old one from Android 10?
Regardless, I can wholeheartedly say that Android 11 has basically shattered the signal strenght on this device to the point of making it useless. Now I can use it as a multimedia device... weeeheeeee.... Buy a premium device they say, it will be worth it, they say. Never had this issue on any of my Oneplus devices. Shame on Sony!
(btw my phone has the international software, not the HK one. using it on one single sim- XQ-AT-51).

The italian user told me now he's fine, the problem didn't came back.
Tomorrow I have a Switzerland holiday, I'm going to reset the phone to try to fix the problem.
Thanks for answering my question, it seems I'm not the only one with this problem. It's a pity there's no more official Sony forum to discuss these issues.

theskig said:
The italian user told me now he's fine, the problem didn't came back.
Tomorrow I have a Switzerland holiday, I'm going to reset the phone to try to fix the problem.
Thanks for answering my question, it seems I'm not the only one with this problem. It's a pity there's no more official Sony forum to discuss these issues.
Click to expand...
Click to collapse
Please do let us know how you get going. I too wanted to perform a factory reset but I've postponed it in case I could find some answers on the internet.

1ceb0x said:
Please do let us know how you get going. I too wanted to perform a factory reset but I've postponed it in case I could find some answers on the internet.
Click to expand...
Click to collapse
The phone is now restoring the backup from Google but this evening I don't think I will make a single call.
Tomorrow at work I will stress it (usually I make 1h of calls everyday, using both SIMs), and give you the results. Cheers!

The situation is maybe worse than before.
I don't remember if is it possible to downgrade. Xperifirm? Still works with new phones?
Otherwise I have to use my old XZ Premium because I have so many issues at work.

1ceb0x said:
Same problem here. After the update of
51.1.A.5.159​I cannot receive or place calls
I cannot receive or send messages
IF I am inside a building. The network goes from 2 bars to 0 when I try to call. If i go outside of the building the cellular network is stronger (full) and calls are going through. I suspect there's something wrong with the baseband maybe? Which is what I was trying to search for yesterday. Was wondering if the current baseband for Android 11 is new or maybe it is the old one from Android 10?
Regardless, I can wholeheartedly say that Android 11 has basically shattered the signal strenght on this device to the point of making it useless. Now I can use it as a multimedia device... weeeheeeee.... Buy a premium device they say, it will be worth it, they say. Never had this issue on any of my Oneplus devices. Shame on Sony!
(btw my phone has the international software, not the HK one. using it on one single sim- XQ-AT-51).
Click to expand...
Click to collapse
The thing I noticed is that the call drops when switching network from 4G to 2G. Expecially on my Italian SIM, i have a weak 4G signal in my office (1-0 bars) but I have a full 4 bars 2G signal. Before this update when I start a call you can clearly see the signal bar going from 0-1 to full 4 meaning the phone switched to 2G. After this update it was impossible to place a call from my office on my italian SIM because it fails in that 4G/2G switch.
I put that SIM in "GSM only" and I had no issues in managing calls. It's unpractical but works.
The problem is worse on my Swiss SIM (the one I use for work) that has no 2G coverage, so I leave it in 5G/LTE/WCDMA/ecc ecc and hope the best. But I see some switch happens even there ranging from 0-1 to 3 bars (I think is 4G/3G switch. I don't have 5G or 2G coverage in my office). So I can't do anything to avoid the issue, that happens randomly but it's quite frustrating

(...)Same problem on HK. Does anyone think that the problem will be solved with an update? Sony flagship haha. The gsm signal was much weaker than the former P20pro before .... 178. Now ..... disaster. I think the only asset Remaining that you can read "network unavailable" on a 4K screen

So far mine seems much better after the latest update 58.1.A.5.222.
Here's hoping it was a temporary glitch.

Please try to use only one SIM until new updates.
I have the same issues but with only one it works fine.
Do we have any news about a new update so far ?
Have a good day!

Today the 58.1.A.5.222A update arrived, I tested the phone and seems to be OK, tomorrow I will test it harder during the workday.
PS: since two weeks I was using my old XZ Premium and the 1 II was resting in the drawer. So sad. I tried to flash another firmware but I had errors on Flashtool and newflasher. Nothing worked wtf.

After a working day in my office with many calls on both SIMs (a place where the problem was at its best as wrote before) I can confirm you the update completely solved the problem.
So thanks to everybody for the support, I hope you'll also be able to fix it with this update.
beachbloke said:
So far mine seems much better after the latest update 58.1.A.5.222.
Here's hoping it was a temporary glitch.
Click to expand...
Click to collapse
"Temporary glitch" un par di balle*: 3 weeks with my old XZ Premium, and the actual flagship "Xperia 1 II" in the drawer! And resets, backups, restores, tests, copying gigabytes of data from and to the phone, hours of trying to flash other firmwares and receiving only errors...
* https://forum.wordreference.com/threads/par-di-balle.1875980/

theskig said:
Today the 58.1.A.5.222A update arrived, I tested the phone and seems to be OK, tomorrow I will test it harder during the workday.
PS: since two weeks I was using my old XZ Premium and the 1 II was resting in the drawer. So sad. I tried to flash another firmware but I had errors on Flashtool and newflasher. Nothing worked wtf.
Click to expand...
Click to collapse
I got the same software number and my problem still persists. Thank you for updating the thread with your findings. Glad to hear yours is working now.

Hello everyone, I faced the same issue on my device after updating to the software version mentioned by author, I've fixed the issue by flashing .280 software for SEA customisation. Original one was HK. So, now I'm able to use my phone as usual. Hope this tip will help somewho. Good luck with your devices.