# I have a single dead-ish key **URL:** \ **Category:** Typing & Ergonomics\ **Created:** [October 14, 2018, 1:13pm UTC](https://community.keyboard.io/t/i-have-a-single-dead-ish-key/2104 "2018-10-14T13:13:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\ **Post date:** [October 14, 2018, 3:32pm UTC](https://community.keyboard.io/t/i-have-a-single-dead-ish-key/2104/2 "2018-10-14T15:32:24Z")
> [@mr.fluffy](#): > > So my question is, are there any known issues (such as with the debouncing) that I can easily remedy myself? As a first step, I’d recommend trying the built-in test mode, to see if it shows an error for the mentioned key. See this post for a short HOWTO: > [@Kaleidoscope-Model01-TestMode documentation?](https://community.keyboard.io/t/kaleidoscope-model01-testmode-documentation/841/2): > > It’s mostly useful to detect hardware issues, but here’s how to use it: press PROG, LED and left Fn together at the same time to enter the test mode. First, it will test the LEDs by going through a few colors (waiting for any keypress in between): red, green, blue, then white. It will follow that with 1000 cycles of rainbow. Then it enters the matrix test mode. In this mode, when you press a key, it will aggressively check for chatter (by reducing debounce time significantly). By default, all … Then, send a mail to [help@keyboard.io](mailto:help@keyboard.io), with your original post here, and the test mode results. They’ll walk you through the possible options. Emailing that address is important - especially if the key was dead on arrival - so they can keep a tally of faults. --- _[View the full topic](https://community.keyboard.io/t/i-have-a-single-dead-ish-key/2104)._