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
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 would rather Google ask users if they really want to download an update that's going to completely screw up their tablet.
The first Lollipop update made my Nexus 7 unusable until I turned off a lot of the services that made the Nexus 7 useful to begin with. Every subsequent update has made things a little bit worse. At the moment, my Nexus 7 is barely usable as a media player, and only because I've had to learn more about hidden settings and turning off services than I ever wanted to.
I loved my Nexus 7 just the way it was. If you're going to push out an OS update, please first make sure to do no harm.
You are welcome on my lawn.
Apple limited carrier choice for a very long time, that whole 5 year exclusive to AT&T.
No sir I dont like it.