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

Lollipop is the worst update EVER!

bjacks12 said:
I've been running Marshmallow on my Nexus 9 for months. It works just fine. I've been too busy to flash it on my Nexus 6, however.

Also....sentences man. Try using them. Kind of hard to read your posts.
Click to expand...
Nexus devices always gets the updates first sorry u don't understand my grammer
 
I find Kitkat 4.4.4 works better on the Note 4 than Lollipop 5.0.1. after the upgrade, the phone is a tad slower, & there is this lag every once in a while. t was blazing fast for me on kitkat...
 
Did you do a Wipe Cache Partition (deletimg only temporary files) after the upgrade? "Lag" is almost always associated with that need.

... Thom
 
The s3 shouldn't have received lollipop .KitKat was the last update for it. S4 got 5.0.1 which had issue's all across board.. Samsung doesn't do well with updates after 18 months in my experience. Having owned the s3 I had issues with kitkat and so did my note 3
Several friends I know have s4 and note 3 and lollipop update caused numerous issues...
 
lel4mayor said:
I have had the galaxy s3, s4, and s5 and absolutely loved it until this latest update. Hate is an understatement when it comes to this update and I have officially given up on android for this. I had a lot of issues with iphones which made me move to samsung, but compared to Google's decision to force this update on us as android owners, I will be switching back to iPhones. :mad:
Click to expand...
Late joining the party here !
I should have kept my old Galaxy S2 .... now this NEW S5 (Lollipop) won't even keep the BT connection to my car (same car) and I have to pair EACH time I get in and go to work/travel/errands.
As soon as I turned the car OFF the darn thing looses the automatic BT reconnection.
Go figure!
 
I have Lollipop 5.01 on my S4 and it works perfectly. Not had any issues. I do prefer it over KitKat as SD cards now have a bit more use:)
 
The problem seems to be confined to the S5/Lollipop v. 5.0 and this is a known issue.
There is a fix though, especially in relation with my car (a Subaru 2013).
JP
 
True enough with this Lollipop "update"/"upgrade" ... one would think that Android developers be smarter than the phones (and other Android devices) they work on.

For me: good news ... I have found a way (not my original idea found elsewhere) to have the phone automatically BT-connect to the car, finally.
The trick: using the voice commands via the steering wheel buttons of the car rather than via the "head console" buttons.
Now the S5 automatically connects to the car each time I get in range.

JP
 
kpvipin said:
Lots of issues in Lollipop. The latest being a security issue in lock screen with password protected lock.
Click to expand...

It bears mentioning that this 'vulnerability' is actually mitigated in many devices by the fact that there's no paste facility in the lockscreen password entry dialogue, so anyone attempting to use it would require lots of time (and patience) to manually enter the tens of thousands of characters needed. If they have physical access to the device for that length of time then most security is moot.

Fwiw my old Sony Xperia Z has been running 5.0.2 for several months with great success. I'll be installing the newly-released 5.1.1. update at the weekend, once I've downloaded the requisite kernel to ensure I retain root. Not all OEMs have made a mess of Lollipop. :)
 
You must log in or register to reply here.
Back
Top Bottom