SetFlowState disable / overflow

[andy]

Hello Martin,

I use several flows which enable or disable other flows.
Currently I am fighting again strange wakelocks. Wakelock Detective shows an entry *overflow* which one increase counter each time a flow with action "set flow state disable" executes.

I could reproduces it by generate a simple flow with mentioned action. If you run flow (not only action! ) manually you can see it. In logger I cannot find strange timestamp for execution.

I use version 1.26.0

How can I avoid this overflows?

Regards

Andy

[andy]

Hello Martin,

I read another post about a similar topic. You mentioned there that Android only lists a limited number of wakelocks. The rest is called under *overflow* Searching for more infos I did not find any detailed explanation. Can you confirm that Android acts like this? If yes it would expain why some flows do not appears in Wakelock Detective.

Regards

Andy

[Martin]

Hi,

Last time I checked the limit was 30 wakelocks. When an app uses more than 30 different wake lock names, Android starts to group the wakelocks under *overflow*.
The name of the wakelock is based on the name of the flow so it's easier to track down which flow causes battery drain. Unfortunately the wakelocks of the flows you are currently executing seem to fall into the overflow group so you only see the overflow group incrementing.
You could restart the device to reset the statistics but you will see the overflow group again when ~30 different flows have been executed (a few less since Android internally uses some technical wakelocks like *vibrator* etc. and Automagic also uses some general wakelocks like AMS.. or the names of some triggers that keep the device awake).

Regards,
Martin

[andy]

Hi Martin,

In fact, Automagics statistic shows more than 30 flows since bootup on my device. Additionally there are widget refresher and so on which I can see on Wakelock Detective.

Thank you for your short explanation

Regards

Andy