- Apr 25, 2013
- 5,355
On Monday Google announced the launch of Android 5.0 Lollipop. The company is known for its gradual roll-outs, but with no Nexus 4, 5, 7 or 9 yet to update the frustration has been growing. Now we know why: Lollipop has problems.
Android Police got wind earlier today that a WiFi bug in the final build of Lollipop is dramatically impacting battery life. This was backed up by mass reports of the problem in the official Android Developer Forum which were quickly fused into a single thread that is now over 800 posts long.
Google Android Senior Developer Trevor Johns ultimately chimed inconfirming that:
“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.”
Update: Google has officially marked the bug as ‘Fixed‘ on its Android Developer Forum. Android Senior Developer Trevor Johns stated: “This issue has been fixed in the latest builds, and this issue is now considered resolved. Thanks everyone.” The thread has also been locked to stop further comments (which were mostly requests to speed up the roll-out!). There was no mention of how or if it would delay the roll-out of Android to existing Nexus devices.
Full Article
Android Police got wind earlier today that a WiFi bug in the final build of Lollipop is dramatically impacting battery life. This was backed up by mass reports of the problem in the official Android Developer Forum which were quickly fused into a single thread that is now over 800 posts long.
Google Android Senior Developer Trevor Johns ultimately chimed inconfirming that:
“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.”
Update: Google has officially marked the bug as ‘Fixed‘ on its Android Developer Forum. Android Senior Developer Trevor Johns stated: “This issue has been fixed in the latest builds, and this issue is now considered resolved. Thanks everyone.” The thread has also been locked to stop further comments (which were mostly requests to speed up the roll-out!). There was no mention of how or if it would delay the roll-out of Android to existing Nexus devices.
Full Article
