Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M3 and M4 keys stop working after sleep. #728

Closed
UnknownLOL opened this issue Jul 4, 2023 · 5 comments
Closed

M3 and M4 keys stop working after sleep. #728

UnknownLOL opened this issue Jul 4, 2023 · 5 comments
Labels
question Further information is requested

Comments

@UnknownLOL
Copy link

Describe the bug
M3 and M4 keys stop working after sleep \ wake up. The longer it is in sleep mode the easier it is to reproduce this behavior.

Clear scenario to Reproduce
Steps to reproduce the behavior:

  1. Leave the laptop for a while (for an hour or so, preferably) so it sleeps for some time.
  2. Wake it up.
  3. Try to use M3 \ M4 \ Fn+C - nothing happens. M1 and M2 still work though.

Expected behavior
The keys worked fine before sleep, expected them to work after sleep as well.

App Logs
log.txt

Desktop (please complete the following information):

  • OS: [Windows 11]
  • Laptop model: ROG Flow Z13 GZ301ZE

Asus software

  • Armoury crate uninstalled
  • MyASUS uninstalled
  • Asus services running: 0

Additional context
Log seems to mention "Listener stopped" and "Listener terminated" pretty consistently after "Monitor turned off" (so - entering sleep mode). Most likely this is when keys stop working, not sure why it happens though. I've set Fn+C to launch custom task (Elevated MSI Afterburner) which also stops working, of course.
Also - Z13 have these keys as follows: M1 = Fn+F2, M2 = Fn+F3, M3 = Fn+F4, M4 = Fn+Space, not sure if it's relevant.

@seerge
Copy link
Owner

seerge commented Jul 4, 2023

@UnknownLOL hello,

"Listener terminated" appears when USB device (keyboard) disconnects from the app. That's generally possible when laptop goes to sleep (even tho it doesn't happen on my devices).

But when laptop wakes up Monitor Power On even in a log, app always tries to re-establish connection with keyboard. Looks like it doesn't always happen in your case (it goes through windows, mb device itself is still sleeping).

I have added a second attempt to get in touch with keyboard on wake up (in 1 second after first one). And also added logging for case when it can't connect to anything.

Can you try this build and post a log ?
GHelper.zip

@seerge seerge added the question Further information is requested label Jul 4, 2023
@UnknownLOL
Copy link
Author

log.txt
Managed one test and everything seems to work alright.

Keyboard disconnecting makes a lot of sense as I have "USB Battery saver" option in Windows Settings turned on. It shuts off all USB devices while screen is off, I can only wake it with power button. Like you said - it probably tries to reconnect while kb is still in this shut off state.

@seerge
Copy link
Owner

seerge commented Jul 4, 2023

@UnknownLOL ok, great to hear. Please test a bit more, and if retry seemed to help, i will include this in next release

@UnknownLOL
Copy link
Author

log.txt

Did a couple more tests and in general 1s delay seems pretty reliable. However, it did fail to reconnect once (in 5 or 6 tests), here in the log:

7/5/2023 3:10:39 PM: Monitor Power Off
7/5/2023 3:11:57 PM: Listener terminated
7/5/2023 3:11:57 PM: Listener stopped
7/5/2023 3:11:58 PM: Timeout:5D-BA-C5-C4-00
7/5/2023 3:11:59 PM: Monitor Power On

It's the only time when there is a Timeout line inbetween Listener stopped and Monitor Power On. Not sure if it's coincidental.

@seerge
Copy link
Owner

seerge commented Jul 5, 2023

@UnknownLOL , even in a case you mention

7/5/2023 3:11:59 PM: Monitor Power On
7/5/2023 3:10:39 PM: Monitor Power Off
7/5/2023 3:11:57 PM: Listener terminated
7/5/2023 3:11:57 PM: Listener stopped
7/5/2023 3:11:58 PM: Timeout:5D-BA-C5-C4-00
7/5/2023 3:11:59 PM: Monitor Power On
7/5/2023 3:11:59 PM: AutoSetting for Online
7/5/2023 3:11:59 PM: Input: \\?\hid#vid_0b05&pid_18c6&mi_02&col01#7&11e16951&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

It actually managed to reconnect (Input:\ line is a USB device it connects to)

So I assume it's now "solved" for you :)

Closing as completed then

@seerge seerge closed this as completed Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants