Originally Posted by lucfig
That makes sense. Right now I have no idea what is causing that behavior. The location settings does not show any app different than the ones I expected.
But it is not causing much overnight drain. During the day is a different story as Google play services is consuming almost as much battery as the display.
let me prefix the following with the caveat its all random unproven and untested thoughts, based on thinly veiled info made to look like actual knowledge. So prefix everything statement below with "possibly" or "maybe", and post fix it with "I dont know"
In regards to location, one unidentifiable source of location search/attainment not allocated to a specific app is a part of doze. In the config of doze there are two parameters that relate to location.
1. locating_to = LOCATING_TIMEOUT which is the max time it waits to get a location before allowing the phone to enter idle modes.
2. location_accuracy = LOCATION_ACCURACY which is the accuracy of the location before it is accepted as a valid location before allowing the phone to enter an idle mode.
I have edited my doze parameters such that the timeout is minimal and the location accuracy is very rough.
As for the playstore being a culprit,I have not done it myself, but I have seen code that removes googles vending from the whitelist (I am guessing for doze and/or battery optimisation).
EDIT:Just read my post after posting, and I notice there is a location related item in the code above
sed -i '/<allow-in-power-save package="com.google.android.gms"/d' /system/etc/sysconfig/google.xml
sed -i '/<allow-in-data-usage-save package="com.google.android.gms"/d' /system/etc/sysconfig/google.xml
sed -i '/<allow-unthrottled-location package="com.google.android.gms"/d' /system/etc/sysconfig/google.xml