Doze

[RGeB]

Automate Documentation for Block ‘Device doze mode set state’ says:

 “This block only makes the device enter or exit ‘doze’ mode, it doesn’t enable or disable the ‘doze’ feature.

 An alternative to this block is to use the Shell command privileged, ADB shell command or Shell command superuser block to execute: dumpsys deviceidle <enable|force-idle> to activate and dumpsys battery reset to deactivate.”

 

ABD commands that start with dumpsys generally only report or change the display of values (ie reports and ‘simulations’=spoofs), but sometimes they are necessary to allow desired changes from other ADB commands, Automate blocks or Device Settings. deviceidle (doze) may be an exception. Or it may just spoof (and really need device_config put or settings put global device_idle_constants). It is hard to tell when other battery-saving Device Settings are in place; and even a spoof may deliver some of the benefits by fooling other apps.

1. Does “This block only makes the device enter or exit ‘doze’ mode, it doesn’t enable or disable the ‘doze’ feature” mean that the Automate Block (with ‘force activate’) just spoofs?

2. For me, dumpsys battery reset does not deactivate doze (or the doze spoof). I have to use deviceidle unforce (or some-such) or the Automate Block ‘Device doze mode set state’ with ‘deactivate’.

[Henrik "The Developer" Lindqvist]

1. No, the device should enter doze, not forcing it. For what i know there's no "spoofing", not unless Google has changed something. But it's all hacks so how knows how it should work.
2. It probably might not work when "forced". The block use does it another way.