Any confirmed nexus 5 OTA drops for lollipop?

I agree, but you should not have to download anything or use a PC etc. Pressing the "check for updates" button on the phone should initiate the update immediately. Google can stagger it for the punters. Most of them have probably not even heard about Android Lollipop/5.0 and couldn't care less if it takes a few weeks. Anybody keen enough to push the button should get it asap.

As I have said countless times, Google are a generally good company that do some fantastic things but there are aspects of how they operate which completely baffle me. Most particularly their deliberately clandestine communication about what and when they release stuff.

Oh no I completely agree that's what I meant you should be able to hit a button on your phone and install it all on the device. Google is terrible at the updates. It shouldn't need this asinine process of adb and downloading crap on a computer. You don't want it rolling out to everyone fine but at least give the people who care an easy option to download your software.

Posted via God
 
Oh no I completely agree that's what I meant you should be able to hit a button on your phone and install it all on the device. Google is terrible at the updates. It shouldn't need this asinine process of adb and downloading crap on a computer. You don't want it rolling out to everyone fine but at least give the people who care an easy option to download your software.

Posted via God

agreed. or put a "secret" button hidden in Developer Options that basically says "Force OTA OS Update".
 
Well my Nexus 5 hasn't seen lollipop yet. This is a very long roll out it seems.

Sent from my Nexus 5
 
Oh no I completely agree that's what I meant you should be able to hit a button on your phone and install it all on the device. Google is terrible at the updates. It shouldn't need this asinine process of adb and downloading crap on a computer. You don't want it rolling out to everyone fine but at least give the people who care an easy option to download your software.

Posted via God

I often wonder what Google's thinking on the way they release updates is , why go through this protracted update process?

I can understand that they are worried about releasing a bug to the masses only to have to release another update to squash that bug, but they have released plenty of iterations of Android with a bug or bugs, even while using this protracted update process.

Bugs are a part of life in the software world and it would seem the method Google has chosen to employ is no better at preventing the release of buggy software than the more normative method of releasing software to the masses all at once.

What in my opinion makes it worse is Google's poor communication skills and they seem to get away with it, as nobody brings them to task. I have always been shocked that the tech news industry has never pressed Google harder on their inability to communicate effectively and more over ask the questions that we the end users would like to know.

Granted, I do not much about the journalism industry, but I have to imagine asking questions is part of the job and yet I have never once seen an article stating we asked Google these questions and got these specific answer, instead we get a lot of what I called controlled information and how to's which are nice but do not really get answers.

Dan

Posted via Android Central App
 
… why go through this protracted update process?
A number of other companies do the same thing, for example Canonical with its daily updates.

One reason is, as you surmised, to catch missed serious bugs before they hit too many people. No matter how well you try to test, there's always going to be something that slips past the testers.

The other reason to prevent them from being overwhelmed. Even when the servers can cope (I imagine that Google's can), there is a risk of being inundated with support calls. Spreading it over a week divides the peak by 7.

I don't know why Google does it like this, but this is probably why.
 
Historically, It can take a couple weeks for an ota roll out.

So I tried again doing the OTA manually. ADB did push the OTA through, but I got an error aborted message (status 7) on my Nexus 5. What does that mean?
 
I often wonder what Google's thinking on the way they release updates is , why go through this protracted update process?

I can understand that they are worried about releasing a bug to the masses only to have to release another update to squash that bug, but they have released plenty of iterations of Android with a bug or bugs, even while using this protracted update process.

Apple unlike Android that only has a handful of phone models that are very similar devices that are much easier to test pre-release. Android has more than a dozens independent phone manufactures that use about five or six computer chip manufactures of unique CPU and GPU chips that covers about 86% of the world's smart phones. Rolling out updates of Android are far more difficult than Apple or Microsoft phone updates. In the last major release of 4.4.1 had to be stopped three days into the roll out to correct a problem that was fixed in 4.4.2. Granted this roll out is targeting only selected Nexus devices at this time but the code for non-Nexus devices have to be in the 5.0 release or any code added for a Moto X or LG G3 that gets the roll out as the next OTA devices could corrupt the Nexus release.

I don't understand why some people can't wait a week for a update since Lollypop is just a improvement on what we have have now with a phone that works. My year old N5 works great now with 4.4.4 and the changes in 5.0 will only improve my experiences as long as it doesn't cause harm. Agreed everything has bugs in software but some bugs you can't live with. Lollypop has only gone OTA on a Nexus 5 for three days. Provided there are no major issues we will all have it this week. Google's controlled roll out is the smart way for sending out a update that has the least chance of causing issues to the masses.
 
OK I tried manual flash through CWM Touch Recovery. The status 7 error said the OTA thought I was on 4.4.3 but both WugFresh and my system info screen on my Nexus 5 confirm that I am on 4.4.4 (KTU84P). WTF?? That explains why the OTA refuses to start but why would the OTA think I am on an older build????
 
Apple unlike Android that only has a handful of phone models that are very similar devices that are much easier to test pre-release.

We are talking about the Nexus 5 here, not the entire universe of android phones. Google certainly has a couple of them lying around to test over the last many months.

Android has more than a dozens independent phone manufactures that use about five or six computer chip manufactures of unique CPU and GPU chips that covers about 86% of the world's smart phones.

Exactly. Let those manufacturers deal with the update as they see fit. Its not Google's issue, nor are those phones the subject of this thread.

I don't understand why some people can't wait a week for a update since Lollypop is just a improvement on what we have have now with a phone that works.

You are missing the point completely. It is not "waiting a week" that is the concern, it is the random staggered rollout for THE EXACT SAME DEVICE that has feathers ruffled here. Sure Apple has only a few handsets as you note above, but once the update is available, ANYBODY can run the update on demand.

Prior posters are right - Google should allow the option people who want it to update on demand and let everyone else get the staggered rollout.

Google's controlled roll out is the smart way for sending out a update that has the least chance of causing issues to the masses.

This is absolute utter nonsense. The best way to catch bugs is to allow the power users and tech types to get the update on demand as they are most likely to find and report the bugs timely because they are the ones most likely to use all the enhancements.
 
Is there anything known about the order of delivery of the OTA update? It's not countrywise. Could it be, that they deliver in order of purchase? Earlier bought, earlier updated? Or are they just delivering to the phones in order of the IMEI number ascending?

Just interested. I am waiting yet.
 
Waiting both Nexus 5 and 10, usually by now many have posted that they got their update. Is Google having another problem they haven't told us about.
 
Completely ready to sideload my N5, but, the OTA file continually stops downloading @ 50% (239MB). Pretty frustrating.
 
I gave up waiting and sideloaded, don't know why I bothered waiting at all.

Posted via the Android Central App

Lol! Most people say this once they realize how simple it is.

Side loaded my N5 and N7. Played with my N5 since Friday and back to my OPO.

Posted via my OnePlus One!
 

Trending Posts

Members online

Forum statistics

Threads
956,900
Messages
6,970,516
Members
3,163,643
Latest member
stonefruit