Apps are easily the biggest draw of owning a smartphone, but unfortunately, they can also be what hinders the performance of our devices, too. AVG anonymously collected data from over 1 million smartphone and tablet users to measure just which apps drained battery the fastest and used up the most storage space, and the results are pretty interesting.
A recently uncovered bug in Chrome showed that Google’s browser was unnecessarily using too much battery on laptop computers due to the way Chrome handled PC processors when it was idling. Chrome sets the processor tick rate at 1 millisecond, even when it’s just sitting in the background not doing anything, which can cause up to an extra 25% battery drain on some hardware. Other browsers, like Microsoft’s Internet Explorer, keep the CPU tick rate at the default 15.625 milliseconds when it isn’t doing intensive tasks.
Experiencing some excessive battery drain? Hangouts may be the culprit. With the 2.1 version of Hangouts, users have been noticing the app is really punishing battery life. On the Google Product Forums, people have started chatting about it and Google is listening. The engineers reportedly found a potential fix for the bug. When any fix will be issued, no one knows. But hopefully they do so before mass riots ensue. Damn you, Hangouts.
Source: Google Product Forums
We all understand there are things we do on our phones that will drain the battery faster. Streaming video, playing games, and using the GPS all cause the juice to flow out faster than we’d like. When we put our phone to sleep though, we expect the battery to drain very slowly. Software glitches can ruin that dream, sometimes emptying the battery in as little as a few hours. Researchers at Purdue have decided enough is enough, and set out to try to identify and mitigate the problems the bugs cause.
Read about what they found, and how they plan to fix it, after the break.
Android users on the T-mobile network may be in for a shock, as a sudden and violent drop in battery life appears to be sweeping across the board. There is a thread on the T-mobile forums addressing the issue, but employees seem to be at a loss. There is a suspicion that changes to the 2G/3G data modes may be the culprit, though T-mobile needs any and all input from users experiencing issues. If this is, in fact, an issue with the network, it may be some time before T-mobile sees a resolution. If you’re one of the unlucky few, let us know in the comments below!