14 DAY TRIAL // Android 5.0 Lollipop – we craved ever since Google talked about it for the first time and flashed images of Material Design before our eyes.
But as is the case with new builds, they also tend to bring about a handful of problems and issues, which are particularly annoying.
So the first device owners actually getting a new update will most likely be faced with frustrating inconveniences that will later on be fixed by further updates.
You probably remember iOS 8 caused its fair share of woes when it came out and the story is not extremely different with Android 5.0 Lollipop.
Android 5.0.1 sucks in RAM memory
And with the Android 5.0.1 update which is currently available for Nexus devices, a fair share of users are reporting a memory leak bug that will kill open apps and prompt perpetual home screen reloads on their handsets.
If you check the Google Android Issue Tracker, you’ll find a great number of Nexus users discussing this particular situation.
It seems like owners of the Nexus 7 (2013), Nexus 5 or Nexus 4 are affected. They are saying that on their device the Android system is showing as eating up 1.2GB+ of RAM when around 500MB is the correct amount.
The thread we mentioned above mostly consists of folks complaining about the issue, but one user in particular claims to have intercepted the cause of the pesky memory in “system_server” when the screen is turned on/off (frameworks/base/services/core/java/com/android/server/display/ColorFade.java)
A fix is under way, but when?
The good news is that the thread has been marked as “FutureRelease” which means the issue has been accounted for and we can expect to see an official fix for it being rolled out.
Naturally, we don’t know exactly when the medicine for this particular problem will arrive and which specific build number will take care of things. Our guess is that Android 5.0.3 will do so, since Android 5.0.2 was already spotted online and is currently available on the Nexus 7 (2012).
