Now Tasker is setting off alarms. And Location/scanning. I have not seen so many Location related alarms in all my 6 yrs on XDA.

Anyway, if you are happy with the setup (drain is only 0.6% per hr), leave it and enjoy the device.

I will stick with the profile that turned off everything, including WiFi. That one gave me 0,31 drain during the night and 1% half an hour before wake, as I run a couple of tasks.
Overall 4% drain per hour.
But how do you know tasker is asking for location? It should not as all location related profiles are off. And actually location services in Android system is set to off, the only thing on is WiFi.

I will stick with the profile that turned off everything, including WiFi. That one gave me 0,31 drain during the night and 1% half an hour before wake, as I run a couple of tasks.
Overall 4% drain per hour.
But how do you know tasker is asking for location? It should not as all location related profiles are off. And actually location services in Android system is set to off, the only thing on is WiFi.

Regards

Enviado de meu HD1903 usando o Tapatalk

I am not saying that Tasker is setting off Location alarms. But Location alarms are very high in the dump. If Location is off, what about Scanning in Settings>Location? There is something which triggers Location.

I am not saying that Tasker is setting off Location alarms. But Location alarms are very high in the dump. If Location is off, what about Scanning in Settings>Location? There is something which triggers Location.

It is also off.
I see lots of location alarms in the format below, but they are all equal to zero:
com.google.android.gms.location.fused.SEND_LOCATIO N_IN_STATIONARY_MODE_ALARM_ALARM_XXX

All of them under Google services. I don't know if this is the normal behavior but I don't think they'll are impacting battery since the number of questions is 0.

It is also off.
I see lots of location alarms in the format below, but they are all equal to zero:
com.google.android.gms.location.fused.SEND_LOCATIO N_IN_STATIONARY_MODE_ALARM_ALARM_XXX

All of them under Google services. I don't know if this is the normal behavior but I don't think they'll are impacting battery since the number of questions is 0.

Wakelocks in the absence of subsequent (presumably undesirable) actions are not evil. Good chance Google, at the request of some other application, is asking for location but can't get it due to device config. Rinse and repeat. Maintaining network connectivity typically resolves that behavior (if you care; ask yourself why...) and probably won't increase battery consumption in any meaningful manner.

Wakelocks in the absence of subsequent (presumably undesirable) actions are not evil. Good chance Google, at the request of some other application, is asking for location but can't get it due to device config. Rinse and repeat. Maintaining network connectivity typically resolves that behavior (if you care; ask yourself why...) and probably won't increase battery consumption in any meaningful manner.

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.

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).

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

Thanks, I don't think it is Doze as my settings are similar to yours, quick and rough location.
Honestly I don't mind the location alarms during the night as my battery drainage is at 0.6% per hour, which is acceptable. And BBS is a great tool for analyzing that during the night.
My issue now is the drainage during the day and screen on. Google play services shouldn't be draining as much as the display.
How do you guys analyze that? Do you recommend another app or another form of analyzing BBS?

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service