5.0.1 for Nexus 6?

[radicchio]

I've been following your thread with Google, Benjamin, and I'm glad you've managed (with the help of others) to finally get their attention. I haven't been able to get a phone yet from Google or Motorola (which is another issue), so obviously have nothing to contribute. I also can't post there anyway because I don't have a Google + account and don't want one.

Anyway, in reading all the comments here and on the Google thread I had a thought. If Google is so eager to help and wants to get to the bottom of this, why don't they offer to overnight an identical new phone to someone who has been experiencing the random reboots and then have them send their phone back to Google? Instead of listening to a bunch of reports and trying to reproduce it at their end, they could actually see the problem in action. Another thought is, assuming there is a unique identifying number for each phone, would one of those numbers reveal whether these phones are coming from certain production runs? Might that help identify if there is a specific hardware issue?

Again, I don't have a phone yet, but as a potential buyer I'm keeping a close eye on this issue and how it gets resolved. As I said before, good for you for being persistent and making Google take notice!

 

[dkeven]

Back on track. Got update OTA it downloaded, did not reboot said up to date. Nothing appeared to change same version and build as before. Says up to date.??

Posted via the Android Central App

 

[VW Maverick]

The build number is actually different.
First one is LRX210, new one is LRX22C

Fixes/Enhancements:
Android update to assure all Google applications can be installed properly.
Enhancements to device call stability.
Fixes an application install issue.
Fixes modem issue.
Software version: LRX22C

Mav.

 

[dkeven]

Mine still 210 and 5.0 says up to date

Posted via the Android Central App

 

[VW Maverick]

Patience.
OTA updates can take days to get to everyone.

Mav.

 

[Vinnie Boom Batz]

Back on track. Got update OTA it downloaded, did not reboot said up to date. Nothing appeared to change same version and build as before. Says up to date.??

Posted via the Android Central App

Exact same thing for me. I'm on AT&T, FWIW.

 

[slave]

I have an AT&T SIM, nought it on T-Mobile, got a notification last night that it was available, charged phone, went to download, it is blank be, won't update

 

[quailman421]

Something with AT&T and Nexus devices

 

[Dubbayoo]

If you're rooted with chainfire I take it you have to unroot and lock bootloader, etc? Will re-rooting wipe data again? If so, then I'll just as soon wait for a more significant update before applying.

 

[dkeven]

I too am AT&T but purchased from Moto directly, guess AT&T back to their usual games as far as updates, will probably resurface with their bloatware attached, so much for a clean phone.

 

[slave]

Wait, because we are on AT&T, we won't get the updates?

 

[dmlv]

I do not believe AT&T has anything to do with the Motorola or Google Play unlock devices.
No bloatware or anything ever installed on mine.

Posted via the Android Central App

 

[Adranalyne]

Anyone who is complaining about the update fleeing them really needs to learn how to flash factory images or sideload OTAs. It's like buying a WRX sTi and asking for an automatic transmission. Should you have to learn? Probably not. Should you anyways? Yes.

Posted via the Android Central App

 

[agentlossing]

Woah, just tested the camera out after the update and taking photos with HDR on is much faster now.

That's a good fix! I hope my AT&T model gets the update soon. The camera has irked me.

 

[Benjamin_NYC]

Yeah second time you've replied to me saying it's not a third party app.... I've had Apps that caused my phone to have issues and once deleted the phone went back to normal...No clue what is causing you and a handful of people to have this issue.... Could be anything.... But you are pretty dang sure it's not an app... No way I could say definitively it wasn't an app.... But who knows.... Delete all your apps and take the next six weeks to add one at a time and wait for it to happen again.... (Joking with you as it was a suggestion from the Google Nexus Forum suggestion... Since there is no sarcasm "I'm joking" font to use.)

The only thing every single user that experiences the reboots has in common is the N6, Lollipop and Google Apps. The fault lies with one of those three. It's not a third party app.

Posted via the Android Central App

 

[Benjamin_NYC]

I've been following your thread with Google, Benjamin, and I'm glad you've managed (with the help of others) to finally get their attention. I haven't been able to get a phone yet from Google or Motorola (which is another issue), so obviously have nothing to contribute. I also can't post there anyway because I don't have a Google + account and don't want one.

Anyway, in reading all the comments here and on the Google thread I had a thought. If Google is so eager to help and wants to get to the bottom of this, why don't they offer to overnight an identical new phone to someone who has been experiencing the random reboots and then have them send their phone back to Google? Instead of listening to a bunch of reports and trying to reproduce it at their end, they could actually see the problem in action. Another thought is, assuming there is a unique identifying number for each phone, would one of those numbers reveal whether these phones are coming from certain production runs? Might that help identify if there is a specific hardware issue?

Again, I don't have a phone yet, but as a potential buyer I'm keeping a close eye on this issue and how it gets resolved. As I said before, good for you for being persistent and making Google take notice!

My guess is they know it's a hardware issue, are scrambling to patch it with software, and stringing us along in the meantime with this third party apps and Safe Mode suggestion crap.

Posted via the Android Central App

 

[radicchio]

I don't know a lot about smartphones, just trying to learn. However, if it is a hardware issue, how do you correct that with software? Also, if there are a significant number of people with the same problem, but not everyone is affected, does that point to specific production runs with defective parts? Or could it be random issue with the assembly of hardware on some of the phones that have been built over time? Obviously, right now no one knows for sure what it is (or they're not telling), but I'm trying to make some sense of this.

 

[Benjamin_NYC]

I don't know a lot about smartphones, just trying to learn. However, if it is a hardware issue, how do you correct that with software? Also, if there are a significant number of people with the same problem, but not everyone is affected, does that point to specific production runs with defective parts? Or could it be random issue with the assembly of hardware on some of the phones that have been built over time? Obviously, right now no one knows for sure what it is (or they're not telling), but I'm trying to make some sense of this.

Who knows. I have an idea:

Maybe the reason that this OTA was essentially pulled mid release was that Google discovered the reboot bug (or realized how to fix it) and pulled the update to add this fix to the change log. Wishful thinking, but my thread on Product Forums is getting a lot of Google attention now, and it would be some coincidence that the upgrade was pulled right as this issue got traction. I could end up being the reason everyone's phone got fixed this week. I am awesome.

Posted via the Android Central App

 

[radicchio]

Who knows. I have an idea:

Maybe the reason that this OTA was essentially pulled mid release was that Google discovered the reboot bug (or realized how to fix it) and pulled the update to add this fix to the change log. Wishful thinking, but my thread on Product Forums is getting a lot of Google attention now, and it would be some coincidence that the upgrade was pulled right as this issue got traction. I could end up being the reason everyone's phone got fixed this week. I am awesome.

Posted via the Android Central App

And yet so modest, too! Nevertheless, I'm glad you were so tenacious in getting Google's attention. It would be nice to know this has been resolved sooner rather than later.

 

[Premium1]

I don't know a lot about smartphones, just trying to learn. However, if it is a hardware issue, how do you correct that with software? Also, if there are a significant number of people with the same problem, but not everyone is affected, does that point to specific production runs with defective parts? Or could it be random issue with the assembly of hardware on some of the phones that have been built over time? Obviously, right now no one knows for sure what it is (or they're not telling), but I'm trying to make some sense of this.

Usually if its random reboots that is software issue. although it can be a hardware issue. I am sure it also could be some defective units, because there are always some that are defective. That being said, I am glad I was unable to order a nexus when it first launched and will wait and see if these issues get fixed in the coming months.