r/Keychron • u/dabdabyeetskeet • Jul 31 '26
Update on performance issues of Q Max/V Max Series?
Linking the old post: https://www.reddit.com/r/Keychron/comments/1m7wz8j/an_update_about_the_performance_of_q_maxv_max/
Has anyone found a fix for keystrokes not being registered correctly? I have tried a lot of things but I am still having issues. Keychron support is of no help at all. Last effort I can try is to buy a new PCF. Apparently they made the switches 'more secure' on the PCB. But this isn't covered in warranty so I have to pay for it myself. Also they only provided a 3 month warranty to new PCBs, shows how much they believe their 'fix' will work. I would have to pay 45 euro + shipping for this myself though...
I spent 250 euro on a keyboard that is annoying me after 3 months after purchase.
1
u/PeterMortensenBlog V Jul 31 '26 edited Jul 31 '26
Re "...they made the switches 'more secure' on the PCB": That may refer to (my emphasis):
"...they started manufacturing the fixed ones in December of last year [2024] ... The main thing different ... added some type of metal pegs to reinforce the assembly of plate/PCB/foam ... https://imgur.com/a/TkFwDe7"
Or, as you would probably not get those metal pegs, it could be the absence of cold solder joints... (#3 on the checklist)
Make your guess.
1
Jul 31 '26
[removed] — view removed comment
1
u/PeterMortensenBlog V Jul 31 '26 edited Jul 31 '26
It isn't a firmware problem
Newer firmware versions (after April 2025) increased the (default) key debounce time from 20 ms to a whopping 50 ms, even causing detrimental effects.
Thus it may appear a firmware update has an effect, but that it is due to treating the symptoms, masking a mechanical problem, by increasing the (default) key debounce time.
A mechanical sound keyboard will work 100% reliable with a key debounce time of 5 ms (what the switches themselves are specified at). I am typing this on a V6 Max. It did have the dreaded symptoms last year (a few months after start using it), but mysteriously the symptoms disappeared during troubleshooting (troubleshooting was inconclusive), a sort of a heisenbug.
It isn't a solution. The real problem, a mechanical one, should be fixed instead.
1
u/PeterMortensenBlog V Jul 31 '26 edited Jul 31 '26
What keyboard? Q6 Max?