While most of us are still using the Android Jellybean or KitKat , some people are already enjoying the new flavor of Android, especially the owners of the Nexus or GPE line devices. However, there is a price to pay for this early access to the new version of the system – Bug . Although the Android 5.0 has been through a long series of tests and still have relied on previous version available four months prior to developers, unfortunately, it is normal to have errors.
Since the original release of 5.0, Google has published at least two updates. The first, Android 5.0.1, was released for the Nexus 6, 9 Nexus, Nexus 5, Nexus 4 and Nexus 7. The second, Android 5.0.2, was released for the Nexus 7 (2012) , which was not an upgrade to 5.0.1.
As a result most Lollipop users are using Android 5.0.1, but the problem is that this version has a bug. In fact, any software engineer will tell you that the Android 5.0.1 has many bugs. However, this particular one seems to be very serious.
According to comments posted on Android Bug Reporter, 5.0.1 users are getting quite annoyed with the memory leak problem, and when the leak in a critical condition, then the Android tries necessarily compensate closing applications to free up resources. What Lollipop resource manager can not identify is that much memory is “dead” without any use for the system .
A memory leak occurs when a piece of Android allocates system memory to a task and then not release it again. This means that, over time more and more megabytes to allocate and never returned. Even with 2 or 3GB of RAM, eventually, the system will run out of memory, and that’s nothing interesting.
The list of complaints on the Android Error Reporting is already very long, and still do not know if Google or system developers are already working on a solution. However, it appears that Google has not yet recognized this problem as a bug , and that it is linked to the source code.
The problem is that all manufacturers are working in their updates are currently attached to this bug. While Google does not admit the problem and releases a patch with the Android 5.0.3 Lollipop , we will continue with a system that can not use the available RAM intelligently.
now, the only solution is to restart your smartphone when the memory is full, because the more blocks are not allocated accumulating, slower your smartphone will be and this is a very annoying problem that needs to be corrected as soon as possible.
No comments:
Post a Comment