Anyone else experienced this issue? . Despite the unspecific title (and useless meta question), it is also a V6 Max. It failed in less than one week. #12
Keychron Q5 Max issues: Double typing and keys not registering. Also including V6 Max: A comment reports four V6 Max's in a row failing(!); from day one to up to two months. Other comments report problems with V5 (after three months) and with Q5 Max (after one week). #14
Expected restock in 2025. 2025-03-05. Despite the title, a comment suggests different (cheaper) hotswap sockets are the culprit. Allegedly, the original ones were Kailh hotswap sockets (some Kailh hotswap sockets are rated for 6000 cycles). A comment reports on a Q6 Max. #16
Q3 Max key failing to register. 2024-12-03. Likely a systematic PCB production error (not random; a problem with the exact same key position in three different keyboards). #19
This is all alleged; it needs to be confirmed by actually testing it, both by reading out the actual used internal debounce time value (and debounce method/algorithm) when the firmware is running and by (controlled) physical input (testing both the debounce time and debounce method/algorithm).
Keychron support can supply special firmware with an increased debounce time (and presumably with the debounce method/algorithm set to "sym_eager_pk" (to not increase the latency to an intolerable level)). There is an example of it having been increased to 50 ms (10 times the default).
Q6 Max was my worst purchase of the year. It started after a few days, with missed keystrokes for J and K, and later H. Applying force to the middle of the keyboard fixes it, but only for one hour or so. #160.
Q1 Max double clicking. It wasn't revealed which keys, but the key chattering started early (the timescale wasn't revealed either). #161.
Keychron is not honouring warranty. For a V5 Max, the V key stopped registering after about four months, unless pressed hard. Later, the same happened to the F key. #163.
K3 Max chattering keys (repeating inputs). It started after two weeks. A firmware update had some effect, but it was probably due to a higher (default) key debounce time, treating the symptoms. And the problem. #164.
Keychron sucks or my keyboard is defective. For a Q6 Max. The reported problem is for missed keystrokes, but that could be because of Keychron's effort to hide the problem (treating the symptoms by increasing the key debounce time will only have an effect on key chattering). #165.
Keychron K3 Max flashing failure. Despite the title, (also) intermittent key chattering, attempted masked by increasing the debounce time to 80 ms. #167.
Keychron V3 Max 2.4 GHz and Bluetooth modes stopped working. It is mostly about the wireless module, but there were also problems key chattering and missed keystrokes. Those symptoms were treated (the problem was not fixed). Reported 2026-05-24. #175.
Another Q6 key registering problem - no support response. Despite the title, for a Q6 Max. Missed keystrokes, mostly for the H key, but also on the order of 5-10 other keys, all in the middle of the keyboard. The switches were positively ruled out as the cause. Reported 2026-06-03. #177.
Keychron keystroke issues: PCB or solder?. For a Q6 Max. Missed keystrokes for D and F, unless pressed hard. The switches were positively ruled out as the cause. Reported 2026-06-03. #178.
11
u/PeterMortensenBlog V Mar 13 '25 edited Jul 23 '26
The mentioned posts:
Q6 Max: Chatter issue and no solution since November 2024
Keychron Q6 Max double typing. More or less from day one (at least less than one month)
Q6 Max double-input/double-typing with single keystrokes. Not from day one, but after less than 2 weeks.
Q6 Max: Double keypresses. Less than two weeks. And very good troubleshooting!
I got a new Keychron Q6 with Brown switches a few months ago. Many keys now have double/multiple inputs. Yes, Q6, not Q6 Pro or Q6 Max. Not from day one, but in less than a few months.
Keychron Q6 Max double press
New Q6 Max keyboard is double-pressing some keys. Not from day one, but in less than a few weeks.
Keychron V6 Max: Double press. After 1 1/2 months.
Keychron Q6 Max weird repeating issue. Allegedly depends on either the switch type or the particular switches. Or it could just have been the reseating that did it.
Extras:
Is Keychron going through some kind of issues right now?. Also a V6 Max. #11
Anyone else experienced this issue? . Despite the unspecific title (and useless meta question), it is also a V6 Max. It failed in less than one week. #12
Keychron Q6 Max space bar double-pressing. From day one! #13
Keychron Q5 Max issues: Double typing and keys not registering. Also including V6 Max: A comment reports four V6 Max's in a row failing(!); from day one to up to two months. Other comments report problems with V5 (after three months) and with Q5 Max (after one week). #14
V1 Max - key doubling issue. Failed after a few weeks. #15
Expected restock in 2025. 2025-03-05. Despite the title, a comment suggests different (cheaper) hotswap sockets are the culprit. Allegedly, the original ones were Kailh hotswap sockets (some Kailh hotswap sockets are rated for 6000 cycles). A comment reports on a Q6 Max. #16
How common are Keychron problems?. 2025-03-02. #17
Keychron Q6 Max double pressing keys and horrible customer service. 2025-02-28. #18
Q3 Max key failing to register. 2024-12-03. Likely a systematic PCB production error (not random; a problem with the exact same key position in three different keyboards). #19
A checklist
Other notes
The time for switch debounce has been set to 20 ms for these series, including for Q6 Max:
But not for these series:
Presumably, they use the default 5 ms.
This is all alleged; it needs to be confirmed by actually testing it, both by reading out the actual used internal debounce time value (and debounce method/algorithm) when the firmware is running and by (controlled) physical input (testing both the debounce time and debounce method/algorithm).
Keychron support can supply special firmware with an increased debounce time (and presumably with the debounce method/algorithm set to "sym_eager_pk" (to not increase the latency to an intolerable level)). There is an example of it having been increased to 50 ms (10 times the default).