# Installing the Keyboard OS firmware

**URL:** <https://forum.clockworkpi.com/t/installing-the-keyboard-os-firmware/20943>\
**Category:** PicoCalc\
**Created:** [January 4, 2026, 5:47pm UTC](https://forum.clockworkpi.com/t/installing-the-keyboard-os-firmware/20943 "2026-01-04T17:47:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![maple](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/maple/32/12677_2.png) [@maple](https://forum.clockworkpi.com/u/maple)\
**Post date:** [January 5, 2026, 6:47am UTC](https://forum.clockworkpi.com/t/installing-the-keyboard-os-firmware/20943/3 "2026-01-05T06:47:44Z")

</div>

i genuinely think the problem is threefold:

- the physical switches (the interaction between the rubber and the clicky switches, which themselves are not great since the click feedback is not 100% of the time in sync with there being an actual closed electrical connection)
- the keyboard firmware (i have not used the official firmware beyond like day 2, in my experience Jack Carter Smith’s works a lot better with optimisations)
- whatever software you use not handling the keyboard FIFO robustly enough to avoid dropped keys, or worse, buffering keys in a way that you get old key presses instead (this happened on my own firmwares until i implemented some fixes)

with proper keyboard firmware, and pico software that handles the I2C better, i _have_ noticed a significant decrease in typing issues. that does _not_ mean it fixes the physical issues with the keyboard switches which also cause drops

that said, i can’t speak to your issues upgrading the firmware, sorry

---

_[View the full topic](https://forum.clockworkpi.com/t/installing-the-keyboard-os-firmware/20943)._