Android
Nexus Android 5.0 Lollipop Problem Fix Confirmed
Google’s new Android 5.0 Lollipop operating system delivered tons of new features to Nexus smartphone and tablet users. However, it also delivered a number of Android 5.0 Lollipop issues to owners of the Nexus 4, Nexus 5, Nexus 6, Nexus 9, Nexus 10, and Nexus 7, Lollipop problems that Google’s been trying to iron out over the last month and a half.
In early November, after a lengthy stint as a developer preview, Google’s new Android 5.0 Lollipop operating system started rolling out to owners of Google’s Nexus smartphones and tablets. The update, as expected, delivered numerous changes to Android including the company’s all new Material Design, improved notifications, a changed lock screen, and more.
The Android 5.0 update also delivered Lollipop problems to owners of Google’s Nexus 5, Nexus 4, Nexus 6, Nexus 10, Nexus 9, and Nexus 7. Nexus users have complained about an array of Android 5.0 Lollipop problems in the days, and weeks, after the release of Android 5.0 Lollipop. Fortunately, Google has responded in the form of two bug fix updates, Android 5.0.2 Lollipop and Android 5.0.1 Lollipop.
While those two updates fixed several of the Android 5.0 Lollipop problems plaguing Nexus users, they did not wipe them all out and it appears that at least one major Lollipop issue is still on board the software.
Nexus users have reported app crashes after getting the Android 5.0 Lollipop on board their device. According to Google’s Issue Tracker, the issue is being caused by a memory leak on board the operating system. The bug, it seems, prevents the operating system from clearling memory as intended. This unfortunately has lead to a number of app crashes post-Android 5.0 Lollipop release. We’ve heard about the problem affecting Nexus 7 and Nexus 5 users though it looks like the issue is widespread.
It appears that this issue has been affecting Android 5.0 Lollipop users since November and that it persists inside Google’s latest Android 5.0 Lollipop updates including the Android 5.0.1 bug fixer that Google pushed out several weeks ago.
Google says that the fix will be coming in a future Android update though the company unsurprisingly fails to confirm which update that will be. Rumors have pointed to an Android 5.1 Lollipop release in early 2015 but that remains unconfirmed. It’s also entirely possible that Google rolls out another bug fixer dubbed Android 5.0.3 at some point in the future. Android 5.0.2 Lollipop appears to be a Nexus 7-centric update.
The company still owes Android 5.0 Lollipop updates to the cellular versions of the Nexus 7 so we could also see Google push out a new Android update that coincides with those two roll outs. The company has yet to confirm a release date for those two updates leaving Nexus 7 2012 and Nexus 7 2013 users in the dark.
Android 5.0.1 Lollipop and Android 5.0.2 Lollipop both tackled some of the more serious issues on board the Android 5.0 Lollipop software though as we’ve pointed out, they both come equipped with problems of their own. A majority of the complaints come from owners on Android 5.0.1 Lollipop, the large bug fixer that Google pushed out to Nexus 4, Nexus 5, Nexus 6, Nexus 7 2013, Nexus 9, and Nexus 10 users. Android 5.0.1 Lollipop problems range from battery drain to issues with Wi-Fi to the random crashes on the Nexus 5.
It’s clear that Google is making an effort to get rid of these Android 5.0 Lollipop bugs as quickly as possible though for some Nexus users, a bug fix won’t come soon enough. We’ve put together a list of potential fixes for Android 5.0 Lollipop problems that Nexus users will want to consult before the arrival of Google’s next Android update.
Google’s bug fix releases are extremely unpredictable and while there is a ton of demand for another update, it could take several weeks, or several months, for another update to arrive.
![](https://www.gottabemobile.com/wp-content/uploads/2020/10/GottaBeMobile-GBM-Logo_wht_381-90.png)
Les Moor
12/30/2014 at 8:18 pm
I had no problems with either 5 nor 5.0.1 on an N5. Oh boy.
Mike Johnson
12/31/2014 at 12:13 am
I made the terrible mistake of installing lollipop over a month ago. Since that time my Nexus 7 has only been useful for two things. As a paperweight or a doorstop. Google should be absolutely ashamed of themselves. Would i ever buy anything from Google again. NO, NO, A THOUSAND TIMES NO!
Chris Aguilar
12/31/2014 at 10:23 am
Lollipop 5.0.1 has been working great on my two Nexus 7’s (2013).
pov
01/01/2015 at 11:10 am
I still haven’t received lollipop on my nexus 5…….. Running 4.4.4 KitKat??? Anyone else?
anthony
01/01/2015 at 2:26 pm
I haven’t received the update for the nexus 7 2013
Krish
01/01/2015 at 9:02 pm
The latest lollipop 5.0.1 is awesome in terms of battery on my nexus 7 2nd gen. though there are few minor bugs like power control widget behaving/appearing improperly, hangs once or twice a month(but restarting device solves it). The biggest bug is video recording with low frame rates and auto focus not working properly.
masud ahmed
01/02/2015 at 12:04 am
why i am not get update? when i will get it.
Shelley Neth
01/02/2015 at 6:44 am
I have not received the update on my Nexus 7 2013 as of 1-2-2015.
Angel
01/02/2015 at 7:37 am
I had the 5.0 update sent to my nexus 7 2013 a few weeks ago.I didn’t load it immediately, and when I went back a few days later to update it was no longer there??? Its still KitKat and says I’m up to date.
David Levin
01/03/2015 at 1:16 pm
Personally I don’t like the visual changes in the 5.0 OS and how they look on large tablets (in landscape view). I feel it’s a big step backwards and plan to keep my Nexus 10 on version 4.4.
Lee s
01/23/2015 at 1:02 am
The 5.0 update killed my nexus 7 2012. It now won’t charge or turn on. After less than 2 years it’s dead. Thanks Google. I’m reluctant to trust any updates on my nexus 5 now.
onetruefriend
02/24/2015 at 3:31 pm
I will think carefully before buying Nexus again.
Update 5.0.2 wrecked my beautiful system and left
BBC radio sound playing as if it was running at the wrong speed.
Beware this update.