Root needed for Set Power Save, CPU, Doze?

[RGeB]

Thank you for all the work on Automate. It is a great app.

I am using a non-rooted Lenovo M8 (gen 2, Android 10), with Developer options > USB debugging on.

I installed Automate 1.50.0 from Playstore, and legacy extension from Llama.

I am using a flow to automate connection of my car OBD reader (OBDLink SX). That works well (thanks again).

I am also using an OTG Y cable for simultaneous power in and data out. With 15 kohms between microUSB pins 4 & % that also works well. But the M8 retains 'Plugged In' status, even when the external power is disconnected. The screen still 'sleeps' as usual.

So to get back to low battery usage while the screen sleeps, I am trying to use any of Automate Blocks:

Power save mode set state (Enable)

CPU speed set (On demand) or

Device doze mode et state (Activate)

I have set the required permissions (priveleged or full (superuser) access to device features and storage is available via Device Settings > Apps > Automate > Permissions > Additional permissions; even though the device is not rooted). Automate reports that start method is 'None'. I have even tried Automate > Settings > Priveleges > execute shell commands; and Workarounds > Power save mode workaround > Priveleged service (no solution for me).

I have not been asked for (nor sent) any ADB command from PC.

I tested each block alone (Flow beginning > Test Block). In each case, I get: 

Failed to start priveleged service.

java.lang.UnsupportedOperationException: Priveleged service disabled, see settings

java.util.concurrent. TimeoutException: Service startup timeout

Does this mean it needs a rooted device? Or an abd command from PC? 

It is not explicit in the Block documentation.

[Henrik "The Developer" Lindqvist]

You need to setup a "Privileged service start method" in Automate settings.

[RGeB]

Thanks.

 I choose Android Debug Bridge (ADB) as Privileged service start method (device is not rooted). There was a popup notification but no further on-screen instruction.

 I connected the device to PC, executed the shell command adb tcpip 5555,  disconnected the USB cable, restarted Automate, allowed Automate and adb to pair (in a pop-up box) and set the Default/Select USB configuration to No data transfer in system Developer settings.

 WIFI is off in the device.

 Now starting the flow gives: android system:Errnoexception: open failed: EACCES (Permission denied).

 Then I rebooted the device and restarted Automate (had to resend adb tcpip5555 from the PC). Error as above.

 Do I need to do something else?

[RGeB]

Checked further, CPU speed set gives that error, but Power save mode set Doze set now work!

Thanks again for the lead, I can survive without CPU speed set if Power save does the job.

[RGeB]

Alas, Automate Power save mode set state (Enable) does nothing when the M8 thinks it is plugged in.

I suspect that Automate Device doze mode set state (Activate)will also do nothing then.

Any ideas on how to get CPU speed set (On demand) working?

[мJ Zкxy]

I may be a feature that require Privileged service both and root service and differ to each phone the developer need to test it manually.

[RGeB]

Thank you for the feedback. 

It sounds like I may be out of luck with Automate CPU set in a non-rooted Lenovo M8.

I will try another "Y" cable and experiment with resistance values between micro-USB pins 4 & 5 to see if there is a hardware solution to the underlying "Plugged In" problem.

I am not too hopeful though, it may be a Lenovo quirk.

[Henrik "The Developer" Lindqvist]

The popup notification shows the instructions. But "Wireless debugging", which it relies on, only works on Android 11 and higher.

The CPU block will probably not works without root, but the Power mode set state and Device doze mode set state blocks should.

[RGeB]

In case it helps, in Android 10 I got a popup notification saying I should follow the on-screen instructions, but n there were no further instructions.

I just used adb as usual (as described above) and that seems to have worked (in Android 10).

I can confirm you advice about which blocks work (for me) without root.

Thanks again.

[Henrik "The Developer" Lindqvist]

On Android 10 and lower it should instruct the user to enable "Developer options", the "USB debugging" option, execute adb tcpip 5555, then try to pair.

[RGeB]

That did not happen (on screen), but the instructions under Documentation > ADB were fine.

[RGeB]

I could not solve the Lenovo "Plugged In" problem with hardware, so I looked again at Automate.

Although Doze normally does not work when "plugged In", it looks like the Automate Block does (at least with "Force Doze") based on checking with the "Device doze mode active?" Block. Is that right?

I could also make the device "think" it was unplugged from power (which it was) using the "ABD shell command" Block (after "pair with this device" to give it a keychain alias) with command dumpsys battery unplug (followed on re-powering by command dumpsys battery reset). This did not seem necessary for Automate force Doze, but it has other uses. Wow, amazing for a non-rooted device. Thanks again.

[мJ Zкxy]

If you could already doze device run a flow that un-doze it too because some service can become non responsive or not work instantly.

[Henrik "The Developer" Lindqvist]

Indeed, Doze probably doesn't activate while the device is connected to power. But how it works exactly is difficult to tell since device manufacturers usually break how it supposed to work, see: https://developer.android.com/training/monitoring-device-state/doze-standby

[RGeB]

Thanks Both. Automate Force Doze does work in the Lenovo M8 while the device is reporting "Plugged In". Confirmed using both Automate "Is device dozing" and adb shell mState report from connected PC.

Battery use is almost nil overnight with Doze on.

I do disable Doze when power is really reconnected, for the reason mentioned by mJ Zkxy.

I now use Privileged shell command instead of ADB shell command (as recommended by Automate documentation). Previously I got an error trying Privileged shell command because I used ADB shell at the start of the command.

Automate is really impressive (and I am but a novice). Thanks again for the guidance.

[RGeB]

In case anyone comes to this thread later:

Sadly, even using Flight Mode and everything in the Lenovo tab M8 device Settings that seemed likely to reduce battery drain when asleep, there was about 32% device battery use per day with the Y cable in. This dropped to <2% per day without the Y cable. It is a Lenovo quirk that cannot be overcome using Automate or ADB commands. I could not find a real hardware or software solution. 

I was mistaken before about low power use.  This was because with dumpsys battery unplugged, the battery still charges and discharges; it just fails to report. Correct charge display then needs dumpsys battery reset.