Android 5.1 Lollipop Update For Moto X (2013), Moto X (2014) Begins: Is Your Moto X Getting It Too
Android 5.1 Lollipop Update For Moto X (2013), Moto X (2014) Begins: Is Your Moto X Getting It TooFacebook / Android 5.0 Lollipop

It has been a miserable experience for some Android users suffering from the notorious memory leak bug in Lollipop for the past several weeks. But it seems that Google is finally coming to rescue as the long-standing ticket has finally been marked closed in the Android issue tracker.

There are no doubts Google won millions of hearts with the major overhaul in the Android 5.0 Lollipop. The Material Design UI, improved camera, better battery saver, updated notifications among other features kept Android users busy exploring the new OS.

Like every other software, Android 5.0 Lollipop came with errors, which Google has constantly been trying to fix. Smartphone users reported various issues in Lollipop in the AOSP issue tracker forum, where Google directly acknowledges issues and offers a resolution.

For a long time, the memory leak bug in Lollipop was left unattended. The ticket received over 1,800 stars from users facing the problem. The bug in the OS stopped the RAM from clearing itself and letting the background apps build memory. As a result, the apps crashed or force-closed automatically. The performance of the system was totally ruined and the most affected users reported the problems on Nexus 5 or 7 among other devices.

The bug mainly affected the apps that run in the background like Play Music and the launch process. Users had to restart the device every time the crash occurred for the app to work properly, at least for the next couple of hours before the RAM usage shot up the roof.

According to Android Police, just before Google closed the ticket, it was the most-starred unresolved issue in the tracker. The current status of the ticket shows "Future Release," which means Google is working on a fix and will be dispatched soon.

There is no exact date on the release of the fix, but we can expect the next Android update (5.0.3?) to come with a permanent solution.

Quick Links