+ Monday December 9th, 2019

lollipop-blog
When Google first began the push of Android 5.0 source code to AOSP, understandably the first questions of when OTA’s for various Nexus devices would occur started popping up. It appears that there may be an issue with the Android 5.0 code somewhere causing what appears to be a fairly serious Wi-Fi draining bug.

The issue has been reported on the Android Developer Preview Issue tracker, where users are reporting that the ‘Miscellaneous’ process has taken up a good portion of the battery usage. The issue mainly seems to be affecting users on the Nexus 5 – one of only two devices running the Android L Dev preview – and many of them have taken time to post screenshots of the Miscellaneous process in their battery stats :

For their part, Google has merged a fair number of reports of the issue on the Issue Tracker into one – Issue 189, where Google Engineer Trevor Johns advised :

Android Engineering is aware of an issue affecting Nexus 5 users running Android 5.0 which causes significant “Miscellaneous” battery usage while WiFi is enabled. This appears to be caused by an abnormally high number of IRQ wakeup events.

We are continuing to investigate this issue.

So, Google is aware of the issue and will be working hard to resolve this as quickly as possible. This is a pretty serious bug, so it’s best off waiting for it to be resolved before OTAs roll out.

Update:
The Issue Tracker has been updated and marked as ‘Fixed’ with Google Engineer Trevor Johns advising :

This issue has been fixed in the latest builds, and this issue is now considered resolved. Thanks everyone.

Ok, it’s fixed – Roll on OTA’s! Thanks to everyone who advised of the update

Source: Android Developer Preview Issue Tracker.
Thanks: +Onel Benjamin.

Daniel Tyson  

Daniel Tyson

Daniel is a former editor of Ausdroid, and left in February 2019.

newest oldest most voted
Notify of
Martin Olminkhof
Ausdroid Reader

so, OTA’s will be out tomorrow then? 😛

Steve Offer
Guest
Steve Offer

Google sw testing & validation seems poor, probaby on par with Apple. It must have been tested on all platforms before pre release on these two? Makes OTA via Samsung, HTC, LG etc look safe & attractive.

Avon Perera
Guest
Avon Perera

Almost as bad as the qcamera daemon bug. That thing frustrated me to no end

Check Also

December update for Pixel 3 and 3a devices is causing the Pixel Launcher to crash

Yesterday Google released the latest security update for its Pixel devices and it seems that …