Slashdot Mirror
Google Lollipop Bricking Nexus 5 and Nexus 7 Devices
First time accepted submitter Zape (303550) writes The Lollipop update has turned sour for me and several other Nexus 7, Gen 2 (and Nexus 5) owners. It seems that I'm not alone in having my tablet boot to the Google Logo since a couple of days after updating to Android 5.0.2. Now Nexus 5 owners are reporting a reboot loop in Android 5.1. My device, like many others, is a couple of months out of warranty, but worked great until the latest OTA update from Google. They branded it, and they updated it, but Google claims it is between the buyers and ASUS, the manufacturer.
Boot Loop does not equal brick.
If they let people upgrade their own phones this wouldn't happen
Google takes 6-9 months to release updates to their devices. It took 5 weeks for my nexus 7 to get the update.
Google should ask apple how to transmit updates to lots of users at once.
i thought once I was found, but it was only a dream.
My Nexus 5 went into a reboot loop, after a lot of research online (and taking the phone apart to see if the power switch was damaged (it appeared to be working fine with a good "click" when pressed) -- I managed to get to boot by repeatedly and rapidly hitting the power button while it was booting, then quickly unlocked the phone and rebooted into safe mode by holding down the power button.
After it booted into safe mode, I left it in the charger overnight, and in the morning, rebooted back into normal mode and it was fine. Mostly. It was no longer in the reboot loop, but kept powering itself off throughout the day.
I replaced it with a new phone, moved my SIM over, and then the Nexus appeared to be fine, no more poweroffs, no reboot loops, I used it as a Wifi-only tablet for a day and then it got a Lolipop 5.1 OTA upgrade, so I upgraded. It's been over a week since then, and it's still working fine as a wifi-only tablet, I haven't tried moving the SIM back
I still have no idea what was wrong with the phone, maybe it was a hardware problem with the switch, or maybe it was a software problem. My Nexus 7 tablet (also running lollipop) is fine.
I replaced my Nexus 5 with a Samsung Galaxy S5 -- I really like the S5 (and removable SIM), but I hate Samsung's Touchwiz interface. I really wanted to stick with the Nexus line, but am not willing to pay $700 for a 64GB Nexus 6 when the S5 cost about half that and I wasn't going to buy another Nexus 5 after what happened to this one.
5.0.1 totally killed the battery in my Nexus 5, but I replaced it (thanks, Amazon for the battery and iFixit for the spudgers) and stuck with 4.4.4 until 5.1 came out. I'm running 5.1 now with no issues. I'm not saying that there are no problems, but this is probably a configuration-dependent issue, so a factory reset ought to fix it.
But that's the provider's problem, isn't it?
Google can't force providers to use AOSP, and unlocked bootloaders, and all that...
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
1. Can't connect to camera error often.
2. Play Music simply won't play music.
These are new on my Nexus 5 on 5.1.
And the one issue I hoped 5.1 would fix:
3. Play Music skipping on Bluetooth
Didn't go away.
This lollipop sucks.
The whole point of the Nexus branded devices is that they are a plain vanilla version of Android directly from Google, and yes these plain vanilla versions call home directly to Google for updates. Carriers are not supposed to alter the OS at all other than the standard provisioning info. Google designed the specs for the device and then contracted each one with a manufacturer.
It takes a few weeks for the various devices to get the update as Google does a staggered release by device. Not sure on the exact order but it does seem to be somewhat by the device's original release date.
So what would be if you buy a PC and then Microsoft won't sell you or let you update to any new version?
I guess that's why he suggested Google ask Apple how they handle it. The article is specifically talking about Google branded phones (which are only available from Google, not through carriers, no?), not Samsungs running Android or something. If you get an iPhone from AT&T, Vodaphone or Ethiopia Tel, Apple takes responsibility for updates to that phone. They absolutely can "go on to the Verizon/T-mobile/AT&T/Sprint network and update your phone. It's called the Internet. It's a good system that works well.
I have a Nexus 5, with Lollipop 5.1 on it. No boot loop issues. Coworkers with Nexus 5 aren't reporting this, either. /shrug/
I have a hard and fast rule at work: unless it's a real lab device, never ever ever install anything that has been out less than 6 months and is not on its 3rd patch.
It doesn't matter how much a customer wants (read: is willing to pay for) a feature that's out in the next release, if the product version is X.0 or even X.4.0 - if the last number is a not a 3 - I'm not installing it unless I've had it in the lab for 6 months and have thrown everything I can think of at it, including production size load & stress testing. Normally when they find out how much that lab costs they back down. The lab I have cannot provide a production sized load so its basically useless beyond functioning as a classroom for new features.
I have a Nexus 7 (tilapia) and it got Android 4.4.4 loaded in January. It's actually ParanoidAndroid 4.6 beta 6, which I read as 4.6.6. That beta was released on Nov 3rd, it was the 6th patch so I only waited 3 months. Before that I was running their stable release 4.45, which I installed 1 month after its release. Before that I was stock.
I own many nexus devices, the phones all bought directly from google (about have the price of buying them from my carrier). Current gen I can put a sim in and work on every major us carrier CMDA or GSM with one phone. Hell my carrier (ting) is working on phones that are on the GSM and CDMA networks and roam freely between them. The radio does get updates from the carrier PRL updates and the like.
Google figured out that the carriers were a barrier so they went around them.
No sir I dont like it.
Not sure why you're confused. The post clearly begins with "The whole point of the Nexus branded devices." Yes, this is true for Nexus branded hardware. It's Google's Android OS with no carrier bloatware. The updates come straight from Google. I own a Nexus 7 2013. I've updated many times - comes straight from Google.
Here's the link on Google's support site to confirm it: Click on the "Nexus Devices" to expand to see the below text.
https://support.google.com/nex...
Nexus 4, Nexus 5, Nexus 6, Nexus 7, Nexus 9, and Nexus 10 devices receive the latest version of Android directly from Google. Once an update is available, it can take up to two weeks for it to reach your device. Based on your carrier, it may take longer than two weeks after release to get an update.
Nexus devices may not receive the latest version of Android if they fall outside of the update window, which is usually around 18 months after a device has been released.
Wrong. Many people, including myself, bought their device directly from Google, and Google themselves create and release the updates for these devices. You can install factory images directly from Google or wait for the over-thr-air updates.
I believe there are also carriers modified versions. For example, I think T-Mo has Nexus devices with proprietary WiFi calling added. In those cases then yes, the carrier must manage the update. Nexus program guidelines suggest how quickly carriers must release such updates.
Nevertheless, many people are on the Google-direct update train.
Google are really hit and miss with updates. They don't offer pre-releases to enthusiasts like they ought to (a pre-5.0 build was an exception and that's only because they were changing the runtime out and literally had to do it for dev support). They announce releases then don't roll them out to their most popular devices for weeks/months, and they release fix versions that don't address some of the worst bugs.
I like Android but my biggest gripe is not being in control of my own updates. When Apple announces a new OS everyone can get it. When Google announces a new OS you better pray you can get it a month later, and that the bug fix version won't be three months behind. That's if your device manufacturer even supports the update.
Ah. No worries. In your defense, Google has not been very good about advertising this unique aspect of the Nexus line of products. Other than Apple, it's not exactly the norm for how devices are updated either. Still, it's unique in that, apparently, Google is pushing some of the support to the hardware manufacturers instead of handling it themselves (though I could be mistaken). I find this disheartening as it's Google's flagship name and I believe Google should handle any issues unless there's a hardware malfunction rather than a software glitch - possibly caused by Google's update.
Basically, Google chooses a specific manufacturer and works with them to develop a model that has its requirements, labels the product a "Nexus" , then supports the OS directly. They even sell Nexus items straight from Google rather than through a carrier. Nexus phones can typically switch carriers as long as the phone supports the proper tech and frequencies - same for the tablets. My Nexus 7 is made by ASUS, but I knew buying it that I'd be supported by Google - which is why I got it instead of a similar ASUS tablet with a standard USB port (Nexus products are notorious for not having expansion ports - Google thinks you should use them and the cloud for everything). I'd rather have the assurance that my hardware will be supported by the latest Android (so many manufacturers sell you a device, then don't bother updating it) than to have a few extra features.
I could be wrong, but last I checked, Nexus 5 had the proper tech to run on Verizon's network, but Verizon won't approve it - I suspect because the don't like that it's not locked down. They already hate that the iPhone doesn't have their bloatware and artificial restrictions.
But, yeah, if you see the name Nexus, that's Google's flagship product line and they'll update it first and directly while all other Android devices will take you months to get an update - if ever.
It's probably unrelated but my Nexus 9 went into a terminal boot loop this week (it was lagging severely and taking 10 minutes to boot beforehand so I suspect a memory or CPU issue). I just find it amusing that Google are putting this on the manufacturer because when I complained to HTC they told me to go talk to Google instead. Fortunately since it's fairly new and UK law is very clear about responsibility I can go to the retailer instead of playing customer support ping-pong.
And behold, a command prompt and he who sat upon it, his name was shutdown and -h 3:11 followed with him
Google figured out that the carriers were a barrier so they went around them.
Google didn't, Apple did. Not one iPhone ever sold has ever been touched by a carrier before getting into the hands of the final user, where the vast majority of Android devices get crapped by carriers before they get sold.
Apple said: Carriers are crap, let's protect all of our phones (and thus users) from them.
Google said: Carriers are crap, we're going to provide users that care with phones that are untouched by them.
As always, Apple forced their views on everyone while Google offered a choice. I think Apple was right on this one.
Write boring code, not shiny code!
If you bought your device in the UK, then you entered into a contract under laws such as the Sale of Goods Act 1979 with the retailer (not the manufacturer). In my case I bought my N5 from the Google Play store, so my contract is with Google, not with LG and as such Google are solely responsible for providing a replacement, repair or refund. Alternatively, because these devices cost more than £100, if the item was either partially or fully purchased on a credit card you benefit from an additional right to seek compensation from the credit card company under Section 75 of the Consumer Credit Act as well as the manufacturer.
Sadly this "go to the manufacturer" response is so common from customer service staff (and their managers) in the UK who haven't been correctly trained.
Apple limited carrier choice for a very long time, that whole 5 year exclusive to AT&T.
No sir I dont like it.
Apple "limited choice" because other carriers weren't willing to allow Apple to update phones directly and wanted to put carrier crap on it. Apple went to Verizon first.
Hindsight being what it is, which was the better choice? Allowing carriers to put their own crap on the phone and to control updates or to force their hand?
I own a Nexus 7 2013 (Non-cellular, WiFi only) unit.
Two weeks after accepting the latest OTA update, my tablet froze on the lock screen and would refuse to accept any key presses on-screen. Forced a reset via the power button, and got the described symptoms (Boot loop). None of the bootloader options allowed me to get it to boot all the way.
I guess that I must have been a little frustrated at this point, because I held the tablet so hard that it gave slightly (held in Portrait with my hands on each side and fingers pushing from back to front gently, but enough to cause mild screen distortion). After doing this a final restart allowed the device to boot normally. I have since carried out the same procedure with three other examples of the same model of tablet (OK, so one of them was the LTE variant) and seen it resolve the same symptoms in each case without any adverse affect (other than a look of mild horror on one of the owners' faces until I handed it back working!).
The only thing I can think of (and I haven't bothered to crack the case to check, so this is literally just a guess) is that the touchscreen connector may not be as sturdy as it could be, and that the device will fail to boot if it doesn't detect a properly working touchscreen connection.
I'm not suggesting that everyone should try this, but if you're going to crack the case to replace the motherboard anyway, try re-seating the connectors (particularly the screen) and reassembling it first before going as far as replacing any parts and see if it sorts the issue out for you!
Just my $0.03 (At current exchange rates, my £0.02 is worth more than your $0.02)
Man, those RAZRs were awesome. I'm actually looking for something similar now for my father who is just now learning to text - he has a flip phone now and a slide-out keyboard would be best. It's getting more difficult to find one that doesn't require a data plan. Verizon charges for data based on the type of phone - doesn't matter if you actually intend to use the data or not :-/