Howdy All,
Is anyone else having issues with their GMMK Pro chattering (ie. sending two keypresses instead of one?)
About 10-15 times a day my GMMK Pro will send multiple letters. It is random on which keys it is doing it for. I am using Kailh Jades and at first I was replacing the keys that did it, but it wasn’t always the same letter(s).
Ideas? I have being updating it regularly to the latest firmware.
hmmm, i cant say i have experienced this! i have everglide aqua kings in my pro board and its been nothing but amazing so far!
@raoulrod I have been having the same issue. Like you, its been random and I started replacing switches to see if it was the switches but still happens. I’m using Gateron black ink v2.
I would shoot our support team a ticket, either through chat or email here (Product Guides) as they may have come across this issue before and be better able to troubleshoot it or replace your board if necessary.
The support had me reset the keyboard (fn+esc+f1+f3+f5). I then went back in and remapped my keys (I switch the caps lock and the control, because that is the way it should be!).
Will see if that fixes it for a bit. It wasn’t part of the suggestion, but I also changed my polling rate to 250 instead of 1000.
Thanks for the update! Keep us posted if that seems like a solid fix, I’m trying to increase my ability to troubleshoot these types of issues for you guys without sending you to support 
I’ll give this a try. Right now its the “P” and “spacebar” that is coming out double. Thank you for this info!!
I had this issue on my original GMMK Pro pretty badly. It was double pressing all the time. I submitted a video and got a replacement. The replacement has been alright but it will double press intermittently. Which is depressing in gaming, typing, or all around use. I haven’t submitted another ticket because I didn’t want to receive a non VIA chip replacement. However, now they’ve said that there will be enough chips.
I’ve been wondering if it’s the board as it’s quite a few characters but very intermittent. I keep hoping it’s actually just a firmware issue that affects everyone and will get addressed. Also wondering if it’s a gateron issue or just an inherent issue with hotswappable switches. I’ve swapped out so many without improvement though.
I noticed the same behavior on mine after updating to the latest FW a couple weeks ago. I changed the latency to the 8ms option (Fn+D+3) and it seemed to clear up. Previously had it set to 2ms. I don’t know if that was the actual solution though as I also did the full keyboard reset a couple times before changing the latency.
I also noticed my profile/layers were wonky after updating Glorious core sw as well. Kept reverting to the default key layout or seemed to be changing layers on its own. That too seemed to clear up eventually. Working fine for the past week or so now though.
So, did a factory reset to out of the box firmware and have NOT let the software do an update to the board. I also reduced the polling rate.
The problem is still there, but not as bad now.
I wouldn’t be opposed to a replacement, it happens a couple times a day, but it is not at the hair pulling out stage.
I have tried Kalih Navy, Pinks, and Jades. All seem to have the same amount of chatter.
This seems to help by switching to 8ms from 2ms. I haven’t seen a double keypress yet at 8ms. However, I don’t like the idea that the keyboard is struggling to operate at 2ms. When it’s supposed to work at that rate.
Yeah I agree. If it’s advertised as working at a certain rate, it should work at that rate. Just seems like something a future firmware could address though. Before I updated my FW a couple weeks ago, the keyboard had been working perfectly since I got it earlier in the summer.
Yeah, mine started chattering after the FW update a while back as well.
The impression that I get from reading around on Reddit is that the latency setting also changes the debounce time, so yes, you are getting lower latency, but you are also more prone to double presses. IMO, these should really be separate settings. There is no reason for debounce to be tied to input latency as input latency is about the first press, not the subsequent erroneous ones. So you’ll probably need to have your latency set no lower than 8 ms for now if you want to avoid problems. Hopefully this changes in the future.
Well, it still happened when the latency was reduced. They RMAed the board. The replacement board had the “We put all the lube in the universe on the stabilizer so now it sticks” problem. Took the board apart per the instructions and cleaned off the metric ton of lube and it is working well now
Right, you want to increase the latency to get rid of it. 8 ms is probably the minimum usable latency on the GMMK Pro right now, but you might even need to use 16 ms.
Sorry, I should have been more clear. I dropped the refresh rate (increasing latency).
It may not have been that at all, it looks like the chattering was dependent on how hard I pressed the key. If I pressed it harder once it bottomed out it would give me double characters for some of the keys
Maybe I should be more clear, then 
There’s a polling rate setting where dropping it increases the latency to some extent (settings above 250 Hz won’t have much appreciable difference, though), which sounds like what you are talking about, but there’s also an input latency setting (measured in ms, not Hz) and you want to increase that setting to get rid of the double presses. That setting was added fairly recently. And it absolutely makes sense that pressing harder would trigger the double presses more easily. The harder you press, the more likely the switch contacts are to “bounce” and trigger a second (or third or fourth) input. This is why Cherry’s minimum recommended spec is 5 ms of debounce time, so the input latency setting decreasing the debounce time below that is… unhelpful to say the least. This is why I say you shouldn’t be using an input latency setting of lower than 8 ms.
Aside from the heavy amount of lube issue, glad to hear the board is working well now. Let me know if it starts happening again and sorry for the trouble!
So, in the issue of clarity ( 
) it seemed to be related to the “flex” on the board, not necessarily the initial press of the key. After the key was down (but before the system would auto-repeat keys) if I pressed harder I could feel the board flex just a touch and then the double/triple/etc keypress would be registered.
I can see how a separate latency to adjust the debounce would be helpful. Also, for those keeping track at home, 8ms = 125 Hertz 