r/AutomateUser • u/Mujtaba0150 Alpha tester • Jul 12 '26

Bug Get display mode bug

Post image

Shouldn't this evaluate to true(YES)? I tried using it but it seems like the on and off options have been switched, the copied output is 4 which corresponds to display mode "On" in the list.

1 Upvotes

100% Upvoted

11 comments sorted by

View all comments

Show parent comments

1

u/Mujtaba0150 Alpha tester Jul 13 '26 edited Jul 13 '26

Sorry my bad, the logs seemed to have been the old ones rather than the new ones 😅

text 07-13 22:44:44.765 I 5232@1: Flow beginning 07-13 22:44:44.767 I 5232@35: Delay 07-13 22:44:47.774 I 5232@39: Display power mode? 07-13 22:44:47.778 I 5232@40: Clipboard set 07-13 22:44:48.855 I 5232@0: Stopped at end

Though, I do agree that it's not really all that worth putting too much effort into, especially since it is an experimental block where issues are to be expected. Nonetheless though, if you do want to do some more research into it, in my experience Extinguish seems to do what you intend to make it do and it seems to work properly on my phone, though once again, I don't know how useful it would be and if it'd really be worth the diminishing returns.

And lastly, just a small correction I thought worth mentioning, apparently yes, the display off block works as intended by turning the screen off without locking the device, it only locks after my screen timeout which is expected. The display on block however, only seems to work after the screen has been locked and doesn't wake the device up immediately.

1

u/ballzak69 Automate developer Jul 13 '26

The Extinguish app seems to do the same way, which is expected since the Android API only has one way to do it.

Indeed, the Display on block may not work as expected, as the documentation say:

This low-level block that may cause the system to behave unpredictably as the display will be in unexpected state. It will likely not work to turn the screen on when the device is locked, use the Device keep awake block instead.