There aren’t too many Android users that are actually using Lollipop just yet. Primarily it’s Nexus devices and a few Motorola devices that have received the update so far, but as we approach 2015 many more devices will receive updates to the latest Android operating system, and there’s a bit of an issue.
While Lollipop went through a fairly extensive testing and public review process, a nasty little bug has snuck through and users are starting to notice the issues. Under certain circumstances, Android 5.0 and 5.0.1 suffer a memory leak, and when the system runs out of allocatable memory, Android basically craps itself and tries to close apps to recover the memory. The problem? This doesn’t work, because it isn’t an app that’s causing the problem, it’s Android itself.
The only way to (temporarily) recover when this situation arises is to restart your phone or tablet, but that will only work until the system runs out of memory next. What we need is a more permanent fix, and it looks like Google’s onto it.
Google has agreed that this is a bug, and that it has been fixed in the source code. This doesn’t do anything to help users today, but when we see the next releases of Android 5.0 (probably as 5.0.3) the bug will be fixed, with others.
Are you running Android 5.0 / 5.0.1, and have you noticed this issue on your devices? Let us know.
