[TUT/DISQ] Google drains your battery
One would think that the company that actually created the OS would be the once knowing how to build the best applications for it. But this is far from true. Google's own closed sourced applications is actually the once with the largest battery draining issue. Google's Applications is also harder to locate when using analytics application to locate problematic packages because they hide behind the system processes category. Some analytic apps does not check these and others has to manually be configured to include them. Android's own list in the Battery section in Android Settings also does not include most if these processes. The once that are included is wrapped in a group containing multiple processes making it impossible to locate the actual problematic one.
The problem is that most people can't do without these packages. At least not all of them. But, it is possible to limit the amount and thereby remove a lot of your battery issues. In this thread I will tell you about the once that I found. Then maybe others can pitch in with their experience and some how we could once and for all stop Google from raping our batteries.
My first notice of this, was when Watchdog started reporting constant extensive CPU usage while the device was suppose to be sleeping. I could get multiple warnings within minutes about different kworker processes using 30% - 70% CPU usage at times where the CPU should be idle. Since kworker is a wrapper without any information about the process using it, those types are not easy to locate. However, after a few month I manages to track down the problem, which turns out to be Google Settings. The Application that it always automatically installed upon the first run after clean install. I removed this application and the problem was gone. No more alerts and battery life became better.
My second notice was a certain start of battery drain. At first this made no sense as I had not really done anything or installed anything different. All I did was update to latest nightly of CM, so I thought maybe a bug in CM. The problem however never went away and started looking into it. I found the Google Services group (One of those containing multiple processes). For some reason it was keeping wakelock's for very long periods of time, more specific 48 minutes out of little under 3 hours. It made sense since I updated the gapps package at the same time as CM. Someone in the CM10.2 thread advised me to take a look at Network Location. And sure enough, disabling this fixed the issue.
I can live without Google Settings, but Network Location? Don't know yet. However, those who can't could instead take a look at the OpenSource Version
. I have used that before, and it is working just fine.
Also, when installing gapps, you could try to minimize what you install. I stripped the package down to the list below
- NetworkLocation.apk (Which I will now remove or replace)
- Phonesky.apk (Play Store)
No Libraries or nothing
Now, others might need other packages, but if you minimize by removing what you don't need, then you will also minimize the issues brought along by Google Applications.