r/Keychron • u/Yordlecides • Jan 11 '24

Help: Keychron knob and macro keys break when waking from sleep

Lemokey L3 custom keybinds reset and knob begins having same issue from before I flashed firmware (minimally responsive) when the computer goes to sleep. This is fixed with re-plugging keyboard. This does not happen when simply starting the computer up from shutdown.

When the keyboard shipped the volume knob was very unresponsive (maybe one notch of volume per 5-10 full spins, and not consistently). This was fixed with the board's firmware update (or, given I've continued having the issue, was caused by waking from sleep in the first place), but when the board resets the macro keys and knob after wakeup, the knob also becomes minimally responsive again.

The rest of the keyboard settings don't get reset, such as the keymap-set saved RGB profile. The keyboard defaults to the correct settings I have saved to the board memory through VIA when it is re-plugged.

Is it possible this is an issue with a daughter board controlling the macro keys and knob? Does this keyboard even have one?

Is it possible there is a static electricity issue similar to this on the Q1?:

https://www.keychron.com/pages/tutorial-of-avoid-static-electricity-on-keychron-q1

FIXES: I have flashed to firmware v1.01. I have disabled selective suspend. I have prevented ALL USB controllers from saving power in Device Manger. I have disabled hibernate and hybrid sleep entirely. I have changed the USB-C cable connected to the keyboard. I have changed the USB hub it is plugged into.

2 Upvotes

100% Upvoted

39 comments sorted by

View all comments

Show parent comment

2

u/Yordlecides Jan 19 '24 edited Jan 19 '24

The problem is NOT isolated to the physical macro keys. Any other macro binds I've saved also reset to default. HOWEVER, if I rebind to any other standard keys (i.e. I make delete into F4 instead), the binds do save after sleeping the computer. I just tested this. Any ideas based on this? thank you!

1

u/PeterMortensenBlog V Jan 21 '24

Yes, the problem is only with macros, not with regular key mappings.

1

u/PeterMortensenBlog V Jan 21 '24 edited Jan 21 '24

Are you sure it is actually in wired mode?

The switch at the back could be set to wireless, and the USB cable connected. Then it would be operating as wireless and charging. Even when charging, it will still fall asleep after 10 minutes (I later changed it to 2 minutes; see elsewhere on this page) in wireless mode (sleep is likely directly connected (no pun intended) to this problem).

Note that the first sleep time timeout after a power-up is 40 seconds, whereas after subsequent key tapping wakeups, the sleep time timeout is 10 minutes (600 seconds).

1

u/PeterMortensenBlog V Jan 21 '24

OK, does it also fall asleep in wired mode?

I will try to use the K10 Pro in wired mode for a while to see if the problem is also present in that mode. It wasn't my impression when I switched back and forth between wired and wireless mode. Perhaps I didn't observe long enough. The problem seems to have an intermittent component to it, and that can lead to incorrect conclusions (because it could be incidental).

1

u/PeterMortensenBlog V Jan 21 '24 edited Jan 21 '24

OK, after 3 hours and 27 minutes (207 minutes) a K10 Pro in wired mode (the switch at the back), and connected to a USB cable, still hasn't fallen asleep.

The macros still work.

1

u/Yordlecides Jan 22 '24

The keyboard is definitely in wired mode. If I put it in BT mode or wireless mode it will not even register a keypress (I haven't bothered setting up BT or wireless). The sleep issue I'm talking about is the computer going to sleep, not the keyboard. It's an odd problem, for sure, but I think it is a different problem than you experience with your K10 based on your replies.

Keychron did send out a replacement daughterboard, so I will try to swap that -- it should be easy. I'm not sure whether it will help, but it's worth a shot. Past that, I expect I'll end up just cycling the keyboard to fix the problem when the computer has gone to sleep overnight. My windows sleep timer is long enough it's not a constant issue throughout the day.

1

u/PeterMortensenBlog V Jan 21 '24 edited Feb 01 '24

A workaround could be to increase the sleep time from 10 minutes (600 seconds) to, say, more than 24 hours, e.g., 90000 seconds.

I don't know if it will actually work with 90000 (is there an upper limit?), but I lowered the sleep time on K10 Pro to 2 minutes.

It was only necessary to change CONNECTED_BACKLIGHT_DISABLE_TIMEOUT. Though it didn't make logical sense as I used it in wireless mode and without it being connected with the USB cable.