[Awake] interval timer starts when setting it instead of after last input

[Rool-IO]

Microsoft PowerToys version

0.80.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

Awake

Steps to reproduce

Set Awake to the interval mode, set whatever. Use computer.

✔️ Expected Behavior

Awake to (re)start its interval timer only after last input

❌ Actual Behavior

Awake starts its timer at time of setting it and will ignore inputs thus rendering the feature useless

Other Software

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• "Keep awake for time interval" ends instantly (#32463), similarity score: 0.79

Closed similar issues:

• Awake won't revert to off after waking up screen following set interval in Awake (#27910), similarity score: 0.80
• keep awake interval not working properly (#30052), similarity score: 0.79
• [Awake]Should switch setting to use the system configuration after interval or limit time has passed (Brought in a regression?) (#27831), similarity score: 0.77
• Awake not working (#12326), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[htcfreek]

@Rool-IO
I don't understand exactly what you mean. Can you please describe the problem a bit more precise. Does awake restart the timer every day or does it start to early or what do you mean?

/bugreport

[Rool-IO]

@Rool-IO I don't understand exactly what you mean. Can you please describe the problem a bit more precise. Does awake restart the timer every day or does it start to early or what do you mean?

/bugreport

I'll try to phrase it a bit more explicitly.
Basically it comes down to Awake not matching Windows native screen off/stand by timer behavior :

Awake interval mode seems to start its (user set or preset) timer when it is selected either by clicking any of the three preset ones in the Awake's tray icon right click menu or in PT's Awake settings page and selecting a time.
If Awake is off and interval mode was the last used one, turning Awake on will have interval mode starting its timer at that activation moment. So far so good since it should indeed start when it's set.

But whatever time is set, the timer will never restart upon each user input as expected, be it a key press, mouse movement, whatever HID interaction.

Maybe it's designed this way but if so I don't get the point of it and then a simple option to have timer as an "absolute" - from the enabling moment only - or a "relative" - from last user input - would be more than nice to have.

Hi there!We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!

No need to reproduce on my end with a bug report, it's as easy as enabling the feature to 1 minute and see that after 1 minute of active use (with user inputs), Awake reverts to off.

In #27831 , I only tested the fixes but since I had gotten used to manually switching Awake between always on and off to workaround it, it took me a while to notice the behavior of the present issue.

[htcfreek]

Okay. So the timer does not start after enabling Awake. Instead it starts elapsing directly when setting it. Correct?

[Rool-IO]

Okay. So the timer does not start after enabling Awake. Instead it starts elapsing directly when setting it. Correct?

No, the timer starts in both cases. My point being it does not restart after user input events.