Google recently announced Android 5.0, as previous stated by Samsung Update in our news section. Although Google is popular for its slow rollouts, there have been rampant frustrations without an update to its Nexus 4, 5.7 and 7. There could be a hundred and one reasons behind this delay, but according to leaked reports, Lollipop has major problems.
Android Police acquired some information earlier that a Wi-Fi connectivity issue in the final version of Android 5.0 Lollipop is drastically affecting battery life. Such assertions can be backed-up by massive complaints of the same on the Android Developer forum. These were promptly joined into a thread that currently features more than 800 posts. Google’s senior developer in charge of Android, Trevor James, readily confirmed these reports. Trevor said that his team was aware of a problem affecting Nexus 5 users running Android Lollipop. In his own words, this issue ‘causes significant “Miscellaneous” battery usage while Wi-Fi is enabled.’ He further confirmed that this problem is likely caused by an unusually high number of IRQ wakeup events. Currently, the company is continuing investigations deeper into the issue.
DID YOU KNOW? Updato offers seamless and guaranteed phone unlocking for any device, carrier and region! It's quick and easy - try it now.
The fact that Google even acknowledges this problem exists means that the tech giant doesn’t have a fix at this moment in time. Users who have tested Android Lollipop have shared screenshots of full batteries lasting less than 4 hours. At the same time, testers have also discovered that turning Wi-Fi off seems to solve the problem, but this is no solution for a mass release of Android 5.0 Lollipop.
These developments are contrary to Google’s attempt to drastically boost battery life, as part of its ‘Project Volta’ scheme. However, this problem appears to stick with the latest build of Lollipop. Earlier builds in fact seem to increase battery life by more than a third compared to Android 4.4 KitKat.
Although the company is yet to announce the extent of this bug, it’s unlikely it’ll be long before they find an effective solution.
And as always, we end with an invite: don't be a stranger and join our community - be a part of the conversation where we help each other out, discuss the latest and greatest, and make the best of our tech.
Similar / posts
February 09 2015
January 26 2015