Has anyone else noticed heavy standby drain from Android System?
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
I hope this helps someone else out that was having the same issue. I did not get a screen shoot of my battery usage before disabling the service but I have included one with it disabled.
I was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam
I spent a couple of hours digging through to find the culprit and it looks like it's actually Qualcomm's IZat location services. Even though you can disable it in the location settings it is still set to scan and report back to Qualcomm's servers via a couple of config files in /etc.
Instead of changing the config files and forgetting which ones I changed I simply disabled the service in location settings then disabled the package that IZat uses and rebooted.
I am already seeing an decrease in battery usage and I have been able to still use GPS.
You can either freeze the app with Titanium Backup or whatever you choose. I did it through adb which I believe is even possible to do without root.
com.qualcomm.location
Code:
adb shell pm disable com.qualcomm.locationI was losing 15% overnight with a kernel wakelock for the entire night that showed up as LocationManagerServiceEx through GSam
No comments:
Post a Comment