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

5.0 Lollipop

If I had to guess, since the Note 4 is the new flagship, it'll get it first. If not, it won't be very far behind the S5.
 
The Note 4 is the current flagship. It will receive 5.0 (and more). Samsung needs to TouchWiz it up and carriers need to push it. These things take time; patience. ;)
 
I don't want it. I find most of the improvements have more to do with starting with a fresh device and not L. My Note 4 works great AS IS. More times than not, updates screw a device up and then only the placebo susceptible "see" an improvement.

The Note 4 has good signal reception, great performance and battery life NOW, so why rock the boat? Not to mention lose about 20% of storage space and break some apps.

If there is any way to stop the update I will.
 
For what its worth, the developer preview for lollipop has been out since June, and ART for developers since way before then.

As a result of these sneak peeks, I haven't had a single app I used in KitKat not work on 5.0
 
My concern is more to do with the complete update that also impacts hardware. Radios in particular. I see no value since my device already performs great. What I will notice is a need to remove apps due to the loss of storage.

I have 2.4gb free. That means I will need to remove at least 2GB of apps and likely 2gb more, depending on the current compression of my apps.

IMO not worth it since no issues with my N4 as is.
 
I wonder how much the Note 4 S-Pen (read: stylus) contributes to delays in getting Android 5.0 Lollipop. There is a LOT of custom software on the Note 4 which makes an upgrade (I assume) a much more difficult task, especially if they're wanting to material-design it up at all.

I'd love to see it sooner rather than later, but as others have said, maybe it's better to get to this race a little late.
 
5.0 is super buggy atm. Better to have them wait and make sure one of the bad bugs doesn't get into their FW than rush it. If that were too happen, who's to say how long you'd have to deal with it, especially if you got a carrier branded phone?
 
jaj324 said:
5.0 isn't buggy at all on my N6 or N7.
Click to expand...
Android 5.0 is widely known to have contained a number of show-stopping bugs since released, so your anecdotal evidence doesn't really say much. The issues with it are widely known and widely reported.

AT&T are recalling all of their Nexus 6 stock back to Motorola because of software bugs. Are they just holding it wrong?
 
AnonGuy said:
AT&T are recalling all of their Nexus 6 stock back to Motorola because of software bugs. Are they just holding it wrong?
Click to expand...
Firmware bug - specific to a small number of ATT's nexus 6 and moto already claimed responsibility.

Not really anything to do with googles 5.0.
 
Rxpert83 said:
Firmware bug - specific to a small number of ATT's nexus 6 and moto already claimed responsibility.

Not really anything to do with googles 5.0.
Click to expand...
https://bgr.com/2014/11/19/android-5-0-lollipop-sms-bug/
http://www.phonearena.com/news/Andr...o-affect-both-the-Nexus-5-and-Nexus-4_id62975
http://www.cnet.com/news/google-squashes-android-5-0-lollipop-battery-drain-bug/#!

There are about 5 other different ones that are serious bugs that either just got fixed or are still there. I won't litter the thread with links. But 5.0 is pretty buggy right now. The issues people have been having with it, even on non-Motorola Nexus devices are pretty well documented at this point.
 
AnonGuy said:
https://bgr.com/2014/11/19/android-5-0-lollipop-sms-bug/
http://www.phonearena.com/news/Andr...o-affect-both-the-Nexus-5-and-Nexus-4_id62975
http://www.cnet.com/news/google-squashes-android-5-0-lollipop-battery-drain-bug/#!

There are about 5 other different ones that are serious bugs that either just got fixed or are still there. I won't litter the thread with links. But 5.0 is pretty buggy right now. The issues people have been having with it, even on non-Motorola Nexus devices are pretty well documented at this point.
Click to expand...
First one- Bug in the developer release, patched before the official release/OTA

Second one only occurs if you leave the flashlight on for several minutes and is solved by a simple reboot.

Sure, any new release is going contain small bugs, I'm not denying that... But calling anything so far show stopping is a little much.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom