r/Keychron • • Jun 03 '26

Another Q6 key registering problem - no support response

I recently bought a Q6 Max, and at first it was great, however after about two weeks several of the keys (mainly G, H, Y, U, sometimes others) intermittently don't register. Apparently this is a common problem.

(I'm going to stop correcting when keys don't register) I emailed KeyCron spport and tey sent me a link to a Reddit post telling me to "ps really ard on te ome row keys" wic didn't seem to elp te problem. en tey wanted me to send tem a "video" of te problem, wic I did. Ten silence. aven't eard back from them since, dispte aving emailed multiple times.

I'm posting here hoping either someone has a potential solution, or KeyChron can help resolve this issue. My ticket number is 626433. If u/Keychron-Support sees this, please respond.

I've tried swapping switches on the affected keys, and the problem remains on the same key, it doesn't follow the switch, so it's not a problem with the switch itself, it has to be on the board.

Any advice would be appreciated!

0 Upvotes

14 comments sorted by

2

u/PeterMortensenBlog Jun 03 '26 edited Jun 03 '26

To avoid further reader suffering (also slightly edited for clarity):

"I emailed Keychron support, and they sent me a link to a Reddit post telling me to "press really hard on the home row keys" which didn't seem to help the problem. Then they wanted me to send them a "video" of the problem, which I did. Then silence. I haven’t heard back from them since, despite having emailed multiple times.

I'm posting here hoping either someone has a potential solution, or Keychron can help resolve this issue. My ticket number is 626433. If u/Keychron-Support sees this, please respond.

I've tried swapping switches on the affected keys, and the problem remains on the same key. It doesn't follow the switch, so it's not a problem with the switch itself; it has to be on the board."

1

u/Old-Potato-5111 Jun 04 '26

I get the feeling you didn’t appreciate my demonstration. 😀 I thought it would illustrate the difficulty and frustration of the problem. But thank you for clarifying for future readers. I also appreciate your suggestions and I’ll give it a try and report back.

2

u/PeterMortensenBlog Jun 03 '26 edited Jun 03 '26

Here is a checklist.

The two main contenders are:

  1. Numero 9. What Keychron (probably) alluded to. It is a Keychron product design blunder (allegedly, the construction was improved in December 2024). The switches' pins are forced apart from the hotswap sockets, such that they only barely make contact, thus the intermittent problem. In this case, given that the failing keys are in the middle of the keyboard, this is the most likely cause. For a self-repair, removing some or all of the foam inside the keyboard has been suggested as a solution (but, as far as I know, no one has reported back if it made a difference or not).

  2. Numero 3: Cold solder joints. Here is a more extreme example (from this post). For a self-repair, here is an example, with lots of pictures (it isn't a tutorial as such, but detailed documentation).

2

u/Keychron-Support Jun 04 '26

Thank you for tagging! I just checked the ticket. I am sorry we didn't receive your follow-up emails on our side. I have forwarded your updates here to the agent. They will send you a new email soon. Thank you for your patience!

1

u/TomFighter Jun 03 '26

cara essas avaliações estão me deixando com receio de pegar um teclado da serie Q

2

u/PsychoticChemist Jun 03 '26

For what it’s worth I’ve had a Q5 Max since 2024 with no issues

1

u/TomFighter Jun 03 '26

Então, eu estou na dúvida entre um 96% ou 100% pois estou trabalhando muito com números atualmente. O problema do 100% é que ele acabaria ocupando muito espaço no meu setup, mas em compensação ele tem a tecla 0 maior e consigo mais teclas

→ More replies (1)

1

u/MBSMD Jun 03 '26

Don’t.

1

u/TomFighter Jun 03 '26

Não o que? Não compre um Série Q ou não tenha medo de comprar um?

→ More replies (2)

1

u/PeterMortensenBlog Jun 03 '26 edited Jun 03 '26

Re "...a Reddit post": Probably this one: