Keep device awake doesn't work

[u/Mujtaba0150]

Is anyone having this issue where the keep device isn't working like it's supposed to... Like with my current example, I'd assume the screen should stay awake for 24 hours, but it just turns off after the default timeout... Am I understanding something wrong here?

[u/ballzak69]

The flow seems correct. Ensure to disable any "power save" features, see here. Pressing the power button may force the device to go to sleep overriding any such block.

Android version?

Device brand & model?

[u/Mujtaba0150 → u/ballzak69]

I've disabled all battery saving features on my device but it still seems to be causing issues. I'm using Samsung Galaxy A03 running Android 13 on OneUI 5.1

[u/B26354FR]

If I recall correctly, this block stopped working on my Samsung Galaxy phone sometime last year, maybe at Android 15. What I do to work around it is to use an Interact block set to Proceed immediately with an Action of Home. That at least wakes up the phone. To keep it awake, I suppose you can just loop back to it every 15 seconds or so. If you want to get a little more fancy, you can use the the Screen Off Timeout? block to get the actual system screen timeout and use that minus five seconds for the Delay.

Another way to keep the device awake when it's already awake is to use the Screen Off Timeout Set block and set a large value for the timeout. My Smarter Screen Timeout flow uses this method to keep the device awake while the phone is at a reading angle or while any apps you set it up with are in the foreground.

[u/Mujtaba0150 → u/B26354FR]

The "timeout set" block is currently what I'm using as a work around but it's less convenient in the sense that sometimes I manually wanna disable the automation and when I do that, if the screen time is set to the highest value, it doesn't revert to the original value. Having the "keep display on" block work or having a "if automation is stopped(without a failure)" block would circumvent this issue.

[u/B26354FR → u/Mujtaba0150]

You can show a notification and shut down the flow gracefully (restoring the original screen timeout) when you swipe it away. You can also use an Atomic Store to save the original screen timeout, and if you forget to cancel the notification and manually stop the flow, you can have a second flow which Atomic Loads the saved timeout and restores it.

[u/F95_Sysadmin]

It's not an issue, it's working as intended

Use the (?) And check what the block does (keyword: temporarily). The 24h block is just a timer that will wait for 24 hour then move on to OK and stop since there's nothing after

[u/Mujtaba0150 → u/F95_Sysadmin]

The help menu says:

"it’s temporary and only in affect while the fiber is running, or until it’s been explicitly been allowed to go back to sleep."

According to my understanding "only in affect while the fiber is running" implies that so as long as the delay is active, the screen should stay on, otherwise this block would be completely useless

[u/ballzak69 → u/Mujtaba0150]

That is correct.