• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Nexus 6 randomly turns off

steveu694

steveu694

Android Enthusiast
Not even a week old and my phone has shut down twice for no reason, and not restarted without me turning it back on. I'm stock, no root, barely any aftermarket apps installed. I had a similar issue with my N5. Should I return it for another one in my 14 day window? Or is this common on the nexus platforms?
 
I'm not seeing it. Never had a Nexus that randomly shut down. (forgetting to charge the battery isn't random :oops: )

Unless there is an odd app that effected both, or there is some really wacky EM interference in your area, I'd think you might want to see if they will swap it out.
 
The night I bought it, it got an android 5.0 build update to LRX21O from the previous build number it came with. Not sure why. As for the post above me, that makes me hopeful in doing a reset. I'm just worried about my time frame. I'd hate to return it if a reset fixes the issue. Only thing is this - I bought it Wednesday, it updated Wednesday night, it turned itself off Thursday afternoon, then turned itself off today (Tuesday). So it hasn't happened much, but I don't want it to happen at all. And if I do a reset, I'm relying on time, which I don't have a lot of (14 days), to test a reset being the resolve. My question is, why would this issue even exist?
 
steveu694 said:
The night I bought it, it got an android 5.0 build update to LRX21O from the previous build number it came with. Not sure why. As for the post above me, that makes me hopeful in doing a reset. I'm just worried about my time frame. I'd hate to return it if a reset fixes the issue. Only thing is this - I bought it Wednesday, it updated Wednesday night, it turned itself off Thursday afternoon, then turned itself off today (Tuesday). So it hasn't happened much, but I don't want it to happen at all. And if I do a reset, I'm relying on time, which I don't have a lot of (14 days), to test a reset being the resolve. My question is, why would this issue even exist?
Click to expand...

The update was a patch to bugs not discovered before release. This happens a lot of the time with new devices.

As for why its happening, its hard to tell. The factory reset is really the only way to know for sure whether or not its the device or some bit of conflicting software. If you return it you're going to have to do a factory reset anyway, so might as well do it ASAP and watch for the issue.

Depending on where you bought it from, you might even consider starting the RMA process but not going through with it until the deadline approaches. If buying from google play this isnt an issue since they are VERY fast with the RMA process.
 
Thanks, man. I got it at T-Mobile.

Just did a factory reset. I will update this thread within the next 8 days for results. Thank you, everyone!
 
Last edited by a moderator:
Mine did it once within the first two hours. Did a factory reset that resolved it. Now about twenty seven hours of screen time later, it's as though it never happened.

Had this same one time experience with my Nexus 5 last year. Once reset it's been fine ever since.
 
Well I have had this happened twice in the last 3 days. I am on the phone now doing an exchange, no issues. This last time it happened after I did a factory reset with no additional apps installed. It seems to be very sporadic.
 
Rxpert83 said:
Bad hardware then. Hopefully the new one is unaffected :)
Click to expand...
Oddly enough they are shipping out the replacement tomorrow. I guess they have plenty of inventory but are keeping some for exchanges.

I THINK my issue is tied to phone calls. Each time it shuts off I will have missed a call by the time I turn it back on. I use Ooma for my home phone and have it do a simul-call to my Google Voice number that is forwarded to my cell (holy crap). Each time it shuts off I will have a voice mail through Ooma with no missed calls on my phone. That means the phone call came through while my phone was turned off.

It doesn't matter now as my replacement phone will be here today. That and my new LG watch. We'll see if I like it more than the 360.
 
Last edited by a moderator:
This entire discussion is silly, im having all kindsa glitchy things happening I have watched many reviews on youtube everyone is having issues with the nexus 6 freezing up or resetting and taking back the phone is not going to fix this problem. You can reset it all you want but its lollipop that is doing this and nothing else. I myself did a reset, actually serveral resets through recovery as well trying and fix mine, sure it works for a week but then last night my N6 randomly reset after a week of working fine so anyhow GL with sending it back you will run into this problem again I assure you.
 
My N6 has not crashed or rebooted once. At all. 44 hours uptime right now since I last rebooted it trying to diagnose moto360 issues.

Solid as a rock.
 
I'm not ready to lay this all on Lollipop either. There were reports of N6's shipping with some strange version of Kitkat on them and mass returns of N6's due to a "firmware issue" (same issue?). In any case, just like Dave, mine hasn't shown any glitchiness or had any problems.

I have no doubt that you are experiencing these things along with all the others who've complained, but considering the number of units already shipped along with all the other devices going to lollipop, if it were and OS problem, i think it would be much more widespread.
 
There were reports of different N6 units having various chips for RAM and storage. I just checked mine, so maybe we can compare and narrow down the root of this issue.

As stated, I haven't experienced anything out of the ordinary. My device has been solid, and performs extremely well, even with encryption on. No lagginess. My hardware has:

Samsung 32GB for storage
Hynix S8 for RAM

You can check this by booting in to the bootloader. Shut down the phone. Then hold volume down and power. This will boot you to bootloader and display hardware information.
 
Mine is:

CPU: APQ8084 ES1.1
eMMC: 64GB Hynix RV=07 PV=03 TY=57
DRAM: 3072MB Samsung S8 SDRAM DIE=6Gb

Have had a couple of instances where the OS hangs for a few seconds, but I'm attributing this to the full system encryption. Haven't bothered removing the encryption at this point even though I'm unlocked, rooted, and running a custom recovery. Just doesn't bother me too much to bother at this point. Haven't had any instances of the phone rebooting.
 
Mine is:
CPU: APQ8084 ES 1.1
eMMC: 64G Hynix
DRAM: 3072MB Hynix

I have had zero issues. No lag to speak of. It seems just as smooth as my Nexus 5 and 7.
 
I have only had my new N6 for a week but no issues so far. With the last one I had several problems a week. I ensured that the same apps were installed on the new phone (for comparison reasons) and ensured that it too was unlocked and rooted. I can only assume that my phone was one in one of the reported bad batches.
 
You must log in or register to reply here.
Back
Top Bottom