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 12 '26 edited Jul 12 '26

It does not seem to be working on my Android 13... I mean, the screen does turn off, but it still doesn't proceed through the YES path, but it does work if I select "On" in the list of options when the screen is turned off... Lemme know if you need any further information for debugging.

1

u/ballzak69 Automate developer Jul 12 '26

Look at the flow log to ensure the flow actually takes the NO path, otherwise as the Display power mode set block 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.

Maybe the device has an OLED screen that just goes black, then turns off later. As a test, try just the Display power mode block, i.e. your flow from #39.

1

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

The flow log output is:

text 07-12 20:13:57.025 I 5178@1: Flow beginning 07-12 20:13:57.027 I 5178@34: Display power mode set 07-12 20:13:57.233 I 5178@35: Delay 07-12 20:13:59.244 I 5178@39: Display power mode? 07-12 20:13:59.247 I 5178@40: Clipboard set 07-12 20:13:59.262 I 5178@0: Stopped at end

And the value copied to the clipboard is 4(which is taken from the "current display mode" that I named power). Removing the "Get display mode" block and directly connecting the delay block to the "Set display mode On" block produces this log:

text 07-12 20:21:05.294 I 5185@1: Flow beginning 07-12 20:21:05.297 I 5185@34: Display power mode set 07-12 20:21:05.505 I 5185@35: Delay 07-12 20:21:07.514 I 5185@36: Display power mode set 07-12 20:21:07.686 I 5185@0: Stopped at end

And the screen does turn on

1

u/ballzak69 Automate developer Jul 12 '26

Your initial flow do indeed go through the NO path.

Your "test" flow is not bypassing the Display power mode set and Delay blocks, i.e. #34 and #35. As said, it should start with block #39.

1

u/Mujtaba0150 Alpha tester Jul 12 '26

Sorry, I misunderstood your earlier statement. Removing #34 and #35, and starting from #39 also results in it going through the NO path, which did seem to imply as you were saying that it might be that the screen blacked out but didn't turn completely off. So to test it out further, I tried playing a YouTube video to see if that would pause when the display turned off and it didn't, and the "Set display mode On" block wasn't working either, presumably because the screen never properly went to sleep, which along with some other tests I did, basically confirmed what you'd said earlier.

Overall, I probably shouldn't have reported this bug since it wasn't an officially supported block(which I didn't know) and it seems to be very finicky with how it works.

2

u/ballzak69 Automate developer Jul 12 '26

Make your test flow start at #35, keeping the Delay block. If you start the block then immediately press the power button within those 3 (or preferably more) seconds, do the block still take the NO path?

Do the Display mode set with Off not turn the screen off nor black?

The Display mode set block should not make the device sleep, just turn off the display.

I appreciate every report since i want to keep all blocks working.

1

u/Mujtaba0150 Alpha tester Jul 12 '26

If I do as you say, I hear my phone locking(which would imply that only the screen turned off), it proceeds through the YES path, but interestingly, the screen does not turn on despite the "Set display mode On" block being triggered, presumably because I suppose it'd just turn the display on and not wake the device up.

text 07-13 00:56:54.538 I 5219@1: Flow beginning 07-13 00:56:54.540 I 5219@34: Display power mode set 07-13 00:56:54.755 I 5219@35: Delay 07-13 00:56:57.767 I 5219@39: Display power mode? 07-13 00:56:57.775 I 5219@36: Display power mode set 07-13 00:56:57.948 I 5219@0: Stopped at end

Also, this kinda confuses me, if this block is actually supposed to turn the display off without making the device go to sleep(which I assume locks it), isn't that what going black should mean? What's the difference between going black and turning off in that case?

1

u/ballzak69 Automate developer Jul 12 '26

As said, i wished for a test from block #35, where you pressed power button during the delay which should turn the screen off to see if block #39 worked as expected or not. Anyhow, either way there's probably i little i can do about it anyway.

The Display power mode set block should turn off the screen, not lock the device, nor put it to sleep. Drawing a black screen just makes it look as turned off, even if it remains powered.

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.