Don't. It's made my tablet virtually unusable. Already this morning I've typed an email with it being about a second behind what I typed, sent it three times because it wouldn't respond to a tap on the send button for ~30 seconds, and then tried to log into a guest session to see if that was any more responsive and ended up turning the tablet off after looking at a totally blank blue screen for about 5-6 minutes.

 

Seriously considering flashing this backwards just to make it usable, 4.4.4 wasn't much better so might have to go for an even older build until I find one that doesn't run like crap and then perhaps let my daughter have it for Christmas.

 

+1 even with the cache cleared mine still randomly slows down and regularly hangs.

 

Totally crashed last night using Chrome and rebooted itself which is a PITA since 5.0 takes about 5min to come back up.

 

I've seen lots of people saying it because if the number of apps they have (150+), I only have about 20 installed.

 

Hmmm I think it could be quite appealing to roll back to 4.2 and get flash back.

Gac,

Enable developer mode and restrict to 2 processes

Open the G app and disable the Now app under the settings.

Reboot and you should be as good as kitkat without the need to format or downgrade

 

Nope. Don't do that. Google Now is (apparently) an account-level setting, not a device-level setting. So disabling it on my tablet has (without making it at all clear) also disabled it on my phone where I do use it, and reset everything to factory default so probably undone any of the learning that it's been doing. Not a good solution, sadly.

 

I have limited the background processes though, will see how that goes. Personally I think it's likely to get more frustrating as it's now far more likely that I'll have to start an app from scratch instead of just being able to restore its state from RAM (I'm perfectly happy with RAM being used for caching, empty RAM is wasted RAM...)

BTW Encryption isn't on by default with 5.0 even if you have PIN or other code.

 

Was playing around last night and turned it on. Took an hour or so to go through the motions.

 

No noticeable difference in performance after so far. Plenty of stuff still crashing though even after a bunch of updates for apps.

Maybe it is a good thing that by the time EE get around to releasing it for the Galaxy S4 it will have been "bug tested" for about 6 months by other people.

Maybe it is a good thing that by the time EE get around to releasing it for the Galaxy S4 it will have been "bug tested" for about 6 months by other people.

 

My thoughts too. Have seen videos on youtube of people running it on S4 working fast and smooth. When Samsung push out for the S4 'in early 2015' I hope it is fairly sorted, never had a problem with update issues on S2 or S4 so far, touch wood.

My thoughts too. Have seen videos on youtube of people running it on S4 working fast and smooth. When Samsung push out for the S4 'in early 2015' I hope it is fairly sorted, never had a problem with update issues on S2 or S4 so far, touch wood.

Wish I could say the same - the last update to 4.4.2 caused my S4 to have fairly major issues (restarting approx every 30 mins when in my front pocket - only since the update so pretty much guaranteed to be firmware related) . Currently with EE to be repaired (if the repair doesn't work I will be asking for replacement) or early upgrade.

The play services 6.5 update is being pumped out.

If you have it, location based smart unlock is now possible. Will work within 100 meters of the GPS location you store.

Maybe it is a good thing that by the time EE get around to releasing it for the Galaxy S4 it will have been "bug tested" for about 6 months by other people.

 

Problem with that is that carriers pretty much never release anything ahead of Google (since it's Google's own source code tree). If I have LPX21P or whatever build on my Nexus devices then you'll almost certainly never be ahead of that - if you're lucky then Samsung will have pulled the repository far enough behind that my bugs aren't introduced, if you're not then you'll have the same builds we have and likely the same issues.

 

Location based smart unlock sounds good, would be useful at home (I tried the Bluetooth pairing so that when it can see my desktop/laptop switched on, it'd disable the pattern, but it never connects reliably enough for some reason).

Wish I could say the same - the last update to 4.4.2 caused my S4 to have fairly major issues (restarting approx every 30 mins when in my front pocket - only since the update so pretty much guaranteed to be firmware related) . Currently with EE to be repaired (if the repair doesn't work I will be asking for replacement) or early upgrade.

Update on the 4.4.2 update knackering the phone - it was sent off for repair and came back with the sim/SD card slots replaced, new cable to these, resoldered and new case as well as a software fix! So not a minor issue.

 

Now 3 days on and (touch wood) no issues apparent.

 

Problem with that is that carriers pretty much never release anything ahead of Google (since it's Google's own source code tree). If I have LPX21P or whatever build on my Nexus devices then you'll almost certainly never be ahead of that - if you're lucky then Samsung will have pulled the repository far enough behind that my bugs aren't introduced, if you're not then you'll have the same builds we have and likely the same issues.

 

Location based smart unlock sounds good, would be useful at home (I tried the Bluetooth pairing so that when it can see my desktop/laptop switched on, it'd disable the pattern, but it never connects reliably enough for some reason).

I can only hope that Samsung (and then EE) will include bug fixes for anything that becomes apparent. They should be able to seeing as they are always amongst the last to produce and distribute a build.

I haven't got this update yet - should it have been "pushed" to my devices or can I manually install from somewhere?

 

Nexus 7 and HTC One S, both on the previous version on Android (jellybean??)

You'll be waiting for HTC for their version.

The update for Nexus devices is apparently on hold. Certainly for the v1 nexus 7 it has been stopped and their is rumours that a custom version is being made for it

You'll be waiting for HTC for their version.

The update for Nexus devices is apparently on hold. Certainly for the v1 nexus 7 it has been stopped and their is rumours that a custom version is being made for it

 

 

Interesting. The trade press has been saying they've not seen any connections from 5.01 devices testing in the same way they've seen after earlier android updates. Unless Google is testing in stealth the opinion was that there won't be any fixes any time soon.

 

I wouldn't say my own 2012 Nexus 7 is bricked but it's certainly hobbled and I'm seriously looking at non-droid tabs in the near future.

Most slow issues are down to apps.

Facebook, soundhound and WhatsApp were all causing issues but I believe they're all updated now.

Main advice is either try removing apps until you find the culprit or if there's nothing important on it factory reset it.

Factory images have been updated to 5.0.1 for some devices now.

Facebook is certainly a prime culprit.

 

there is a memory leak somewhere I think. I have a memory cleaner app that clears processes and it is clearing much more than it used to.

I have recently had the updater specificially for L from Motorola for my Moto G, so am expecting to get it around Xmas ( either just before  or immed after ).

 

If it is a painless as Kit Kat was then will be chuffed ( unlike SWMBOS  update to v8 on iPad she was ready to throw it away with frustartion)

Facebook is certainly a prime culprit.

 

there is a memory leak somewhere I think. I have a memory cleaner app that clears processes and it is clearing much more than it used to.

I wouldn't bother with memory cleaners, personally - free RAM is wasted RAM; Android does a good job (from what I've seen) of handing back RAM from cached processes when it's required, and if it's not required then it might as well hold some background apps so they return to service quicker. I find the obsession with free memory (on all platforms, not just Android) bizarre - RAM usage isn't something to be afraid of as long as it's used sensibly, which on Android seems to be the case.

 

As opposed to my colleagues Windows 8.1 PC which today has the "Credential Manager" service spiking at 50% CPU usage and several gigabytes of RAM for no discernible reason, which is causing Windows to kill his active apps because this background service has spiked, and then about 5 seconds later it releases it all again meaning that his work has been interrupted for no good reason. That approach to things can sod off, I've never had an Android app be erroneously killed...

It does usually improve things for a while.

Havent got it on my Nexus 7(2012) yet....

Havent got it on my Nexus 7(2012) yet....

 

Unless you shop/bank on it I'd strongly suggest you avoid the update.

Havent got it on my Nexus 7(2012) yet....

Google seem to have pulled the update for these, I haven't had it either despite having the 5.0.1 update on my Nexus 5 for nearly 2 weeks now.

My wifes LG G3 updated a couple of days ago and she is happy with it. 

Mrs is hoping to see her Moto G updated in the next week or so.

My wifes LG G3 updated a couple of days ago and she is happy with it.

Ooh, wonder if my G2 will do the same soon.

HTC's 90 day promise rollout's clock started on November the 4 for the One M7 and the One M8

Edited 23 December, 201411 yr by milspectees