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] HELP: Lost cellular data and service

Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.

rmx36 said:
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
Click to expand...
Click to collapse
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first. EDIT: NOPE! Flashing the stock kernel from the ROM did not do it. Looks like total reformat/flash is next!

markwebb said:
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first.
Click to expand...
Click to collapse
I just got my Nexus 6 and I am also on Verizon and had the cell coverage drop too. I backed up my apps with titanium backup and did a factory reset and signal came back. I only had it for a day and went to Canada and on my way back to the US I noticed the cell bars were gone. I was just rooted and boot loader unlocked and otherwise stock. I read online that others had this issue when they got to places in the US that had little or no signal. I also noticed that under cellular network settings it loads up with Global under the preferred network type even though it has an option for "LTE (recommended)" and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected. With global selected it works perfectly with calls and LTE, so not sure what that means or if my selecting LTE made it drop the signal after going back from Canada.

Yep, total flash of factory image fixed it. Sigh. Early enough in the day for me to get everything set up again.

Same. About to do it too... I've done too many factory resets with this already. Kind of annoying.

I am in the same boat. Had no problems until I flashed bliss 1.5 then was stuck on 3g. Tried a clean flash of Slim and still stuck on 3g. I will try a stock rom but I am not very hopeful at this point. It's looking a like a reformat here as well :/

Ended up having to format everything and start from scratch again. I'm running a stock ROM now and in weary to try another cm ROM

Don't know if it'll help, but try LTE Discovery app in the Play Store. I use it from time to time to reset my data connection.

Having the same issue, running CM12 daily, have been for a week or so. Midday today it drops LTE, 3g data was working, then a few minutes later to no data. I didn't change anything, nothing new installed. I did reboot the phone at some point before this but that is all...
My only fix was to backup via trwp, restore stock rom, factory reset, reboot & let sim activate, then restore cm12 via twrp... it's a 20-30 min fix all said and done.... pita
Maybe its something Verizon is doing, because I didn't change anything and then next thing you know no data. I hope it's a simple fix for CM12 but I see this popping up more the last few days. Hopefully someone will figure it out. I like CM and prefer it over stock but I am not going to do this multiple times a day just to keep CM...

lohonda said:
...and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected.
Click to expand...
Click to collapse
I just checked and global is still an option for me. I've bounced back and forth, looking to see if anything changes..

Same thing has happened to me last night, lost connection to VZW cell and data. Looking at the field test menus, it seems like the SIM/device understand GSM but NOT CDMA anymore. So I believe the issue has something to do with that. Tried everything, but will nuke and repave most likely....also lost Global as well. and LTE Discovery shows GSM stuff nothing for CDMA
Tried the SIM in another device and it works so its not the SIM.

OK I tried a world of things to recover like some of you may have....its something in Userdata because if I flash everything but userdata it wont work. I am going to try and recover from the backup I had before this happened to see if that works....otherwise rebuild from scratch
will post back
UPDATE: So restoring a backup seems to be ok once you get the SIM back.

Having the same issue over here as well... After a month or AI of having the 6, now I randomly drop service where I would normally have full LTE. I almost NEVER get LTE now and am at most on H with a couple bars then it drops out again. Have also.noticed WiFi connection is very shakey.
Any one find a fix?

I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.

th3g0d said:
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
Click to expand...
Click to collapse
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)

quidpro said:
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
Click to expand...
Click to collapse
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Edit: OK, just pinpointed MY issue. I have to wait for the "no service" text to change into "emergency calls only" before entering my pin or I don't have any service just the exclamation mark :/

th3g0d said:
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Click to expand...
Click to collapse
Thanks. I told her about it and she will give it a try, or just remove the pin altogether as a test. It is a weird issue. She is missing important calls from her elderly parents at night and it is rather frustrating. Turning wifi off also seems like a bad fix.

Lost mobile data with an exclamation mark, I can still make calls.

Edit: added details.
I have had my Nexus 6 for 3 days and first installed my Straight Talk SIM yesterday. Everything worked fine for less than a day then I started getting MMS picture messages failing. Now I get no mobile data. I swapped my SIM with my wifes, also on straight talk and mine with hers and I get the same issue and mine works fine in her phone.
I have rebooted many times, I have checked my APN settings and even have tried alternatives.
I have done a few searches and see other have this or very similar issues but I have not found anything that fixes my issue.
I am running Pure Nexus with the stock kernel.

tjlmbklr said:
Edit: added details.
I have had my Nexus 6 for 3 days and first installed my Straight Talk SIM yesterday. Everything worked fine for less than a day then I started getting MMS picture messages failing. Now I get no mobile data. I swapped my SIM with my wifes, also on straight talk and mine with hers and I get the same issue and mine works fine in her phone.
I have rebooted many times, I have checked my APN settings and even have tried alternatives.
I have done a few searches and see other have this or very similar issues but I have not found anything that fixes my issue.
I am running Pure Nexus with the stock kernel.
Click to expand...
Click to collapse
Need few more details. Who is your carrier? What ROM is on working phone?
I would clean flash latest factory image and see if that helps.
https://developers.google.com/android/nexus/images#shamu

Witek_M said:
Need few more details. Who is your carrier? What ROM is on working phone?
I would clean flash latest factory image and see if that helps.
https://developers.google.com/android/nexus/images#shamu
Click to expand...
Click to collapse
Straight Talk.
Pure Nexus ROM
I did a back up and tried flashing another ROM last night, CyanogenMod but I did something wrong and I ended up flashing Pure Nexus again and it restored everything from my backup (still learning I guess). But it is working fine, now that is, it was working fine before. The only thing that I thought may have caused an issues was I had Macrodroid setup to disable wifi radio when out of my homes cell tower's range. I used this all the time with my old phone and it helped a lot to save battery. But it didn't seem to work for some reason. So I turned Macrodroid off and it did help with my data issues then I even uninstalled it completely.
So bottom line, it's working now, but like I said in my original post, it was working for about 24 hours then I started having issues.

tjlmbklr said:
Straight Talk.
Pure Nexus ROM
Click to expand...
Click to collapse
Straight Talk is not a carrier. They are reseller of services provided by Big Four.

Witek_M said:
Straight Talk is not a carrier. They are reseller of services provided by Big Four.
Click to expand...
Click to collapse
I think all know this detail by now. The APN however is unique straight talk even though it is technically AT&T or (T-mobile)

I can't believe this is still an issue, totally unacceptable IMO

I've had this twice today. 100% stock, no root. Latest T-Mobile 5.1.1 with T-Mobile service. I'll take my phone out of my pocket and have a "!" next to the signal bar.
This even happens when in use. I had Spotify streaming music in my car when it cut out. When I got home, I checked the phone and again, "!" next to the signal bar.
I just did a clean flash and factory reset yesterday and set the phone up as a new device (no apps auto downloaded from previous setup) and I'm still getting this error whenever I leave the phone to sleep too long.

Same here !
Bought a N6 as my first Google phone, I thought I'd get the benefits of an always up to date phone, but instead I have to deal with that kind of issue
Hopefully that's a software issue and Google will provide us with a fix quickly... that's why I bought a Nexus !
(Orange 4G - France)

I had the same thing happen to me today. I left my phone in the car to go to a meeting, went to check it had no signal. Just turned on airplane mode for a few seconds then off, everything came back. I'm using the phone on ATT GoPhone network. I'm also using the nextgenphone apn instead of the phone apn. Maybe that's causing it.
Sent from my Nexus 6 using Tapatalk

Weird issue with no data while making phone calls

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. ?

Nexus 6, T-Mobile and MMS problem

This has been a frustrating issue. My wife and I both have Nexus 6 phones. She has the 32gb & I have the 64gb version. Hers recently started not receiving MMS messages. Anything with a large picture would simply never show up. Anything with a very small graphic or group text would show up as "Non-text content". Here are the steps we've taken to solve this:
1. TMO started by insisting it was an APN issue. So she edited her APN. Didn't help.
2. We then swapped SIMs. Hmmmm. My phone then behaved like hers while hers could then send/receive MMS.
3. TMO said ok maybe it's the SIM. They sent us a new one. SAME result. Her phone wouldn't receive MMS.
4. Out of frustration, I factory reset her phone and reset the APN info. Didn't help. (Cleaned up her phone of some trash programs though. :laugh
5. TMO engineering says they still can't find anything on their end. Elevate to tech supervisor. She tells us to go a TMO store (right near us) to try a THIRD SIM. OK, we do. SAME RESULT. We tried swapping SIMs around again and the same thing happens. My SIM in her phone, everything works. Her SIM in mine, I can't receive MMS.
6. TMO store guy suggests MAYBE (but unlikely) that there is something her account has that's stored on the SIM when its activated that causes the phone to freak. Also says it's above his pay grade .
So now we are again waiting on TMO to poke around further on their end. My question for all you smart types here is:
Has anyone ever heard of this issue? Is there anything you know of that could be causing it? I think it's a bad provisioning somewhere in the dark recesses of TMO. The ONLY change we made to our plans (which seems just coincidental) is that we moved from the 2 lines Unlimited for $100 plan to the over-55 Unlimited plan. We did this maybe 3 weeks ago. But the features are all the same on both plans.
We are both on the same Android 7.0 final OTA firmware updates from Google. NBD92G
Would there be ANY chance that a sideload firmware update would make any difference? We're getting desperate here. Any & all suggestions welcome.

I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case

Don't use old firmware... I had issues on certain custom ROMs and old firmware where MMS wouldn't work over WiFi. Never as bad as you were getting.
If you wanna stay stock, sideload the latest OTA to go to NGI55D. Anything older than that is vulnerable to Blueborne exploit, which is a HUGE security concern IMO. I can confirm MMS is working correctly (even with WiFi enabled) on bone stock NGI55D as well as custom ROM Dirty Unicorns v11.7.1 which includes September security patch.

ktmom said:
I wonder if her SIM is configured for wifi calling. There has been a conflict between wifi calling and mms for awhile. I've seen it reported several times where this T-Mobile forum post helps in that case
Click to expand...
Click to collapse
I've had this issue on most LOS roms. i ended up making a custom APN i flash when i try a rom built on LOS.

Yeah, it sure sounds like a problem with account partitioning, or something else with the account that gets associated with the SIM on initial use. What if you try the problem SIM in a phone that is not a Nexus 6? I wonder if you could get a new sim and set it up in a different phone, then transfer it to the problem phone?

OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.

RealSkier said:
OK all, finally got a TMO engineer who agreed with my assessment -- that it was a hidden provisioning problem. She nuked my wife's line and recreated it from scratch. Everything works great now. Frustrating that we had to go through about 15 phone calls and over 3 hours of phone time to get it resolved.
Click to expand...
Click to collapse
Glad they figured this out.