Google recently launched the Android 5.0.1 Lollipop update for mobile devices. The first to get the update was the Nexus users. As soon as they got the update, they started complaining about some issue that was causing their phone memory to leak. What happening was that this was killing the open applications and also made the home screen of the device keep reloading constantly. This killing of applications caused the RAM to leak and the users were in trouble. They had this issue put up at the Android Issue Tracker from Google and started showing the anger and frustration that this bug was causing.
Battery drainage after android lollipop update is another problem that users have been facing. But if you are not facing these problems after updating to android lollipop then read on the android lollipop tips and tricks.
What is the bug exactly and how serious is the issue?
RAM or Random Access Memory is required by the system to run the applications. Now whenever any application is opened some part of this RAM is taken and consumed. But when this RAM is required by some other operation or application then it clears up automatically and gets available for the application or the process to be run. But what the bug is doing is that it didn’t let the RAM to get cleared up and be available for the other applications or processes that might require memory. So this made the applications get crashed and killed automatically.
The issue is really serious because what it meant is whenever a person would turn his device screen on or off the memory would leak and keep coming closer and closer to the maximum capacity of. And as it keeps on rising because of this it would finally come to a stage where there would be no memory left even for the phone’s core operations to run properly. So the issue is really serious as this meant malfunctioning of the phone.
According to some posts at the Android Issue Tracker the device is eating up as high as 1.2 GB of RAM when normally it wouldn’t be more than 500 GB without the bug. So knowing the steps to fix Android Lollipop Memory leak Issue is very important. Well Google has launched a fix for the issue and we are providing this guide to help you fix Android Lollipop Memory leak Issue. Just follow the given process step by step.
Important points to note before going ahead with the big fix
- The given fix works only for rooted Android 5.0 or 5.0.1 devices.
- The device should have the Xposed framework installed on it.
- It should be a Motorola, Nexus or Google Play edition.
- The device should have the unknown sources installed.
- This would not work if you have updated to Android 5.1.
Steps to fix Android Lollipop Memory leakage Issue
- First of all install the “Fix Memory Leak Issue”.
- You would find this in your Xposed installer application. Go to the download section of the app. In the search bar, search for fix Lollipop Memory leak and in the results just tap on the top most one. This is the one that you need to install.
- Now go to the Version tab. Now just tap the download button which is next to the recent one.
- After this, the Android Installer interface would come up. When it does, just tap on the ‘Install’ button there.
- After this process has been completed a notification will come that will say that the module is not activated and a reboot is going to be required. When this happens just hit the ‘Activate and Reboot’ button. After this the device is going to restart.
Step 2- Check the Memory usage
When the device reboots the fixes are applied on your device. The device would start running smoothly and an increase in the performance would be seen after that. But please note that this might not be because of the work that we just did. It is because of the reboot and clearing up of space from device’s RAM.
Now you will get to know if the issue has been fixed within a couple of days when you use your phone regularly. You can keep a check on the memory usage by just going into Settings > Apps and then moving to ‘running’ tab.
If the device memory doesn’t get filled up again then it means that the fix has worked on your device.