Positive news: since the April 2025 firmware update I haven’t seen any keyboard freezes.
Occasionally I still have an issue where I can’t enter the decryption password at boot although the OLED menu is working.
The workaround that works there for me is:
HYPER+ENTER R (reset keyboard)HYPER+ENTER (hold until keyboard backlight comes back on)Thanks for the feedback! It’s very interesting that resetting the keyboard helps here.
For what it’s worth, I used to have this problem which was exacerbated by the accelerometer hack and by plugging and unplugging power. Newer keyboard firmware fixed it for me for the most part. I still have occasional times where the keyboard and trackball inputs are not being registered, and I almost universally go for the new option in the OLED to reset USB instead - works every time pretty much instantly, and you don’t have to convince the keyboard that you’ve already turned the device on after resetting it.
To be clear: with the full freezes I encountered earlier during normal operation, resetting wasn’t possible because the OLED menu was also unresponsive. The reset workaround only works when the keyboard is unresponsive at boot when entering the encryption password
I’d like to try this as well but running the script tells me that -s is illegal on which and that the dependecies can’t be found. picotool and reform-tools, etc. are all installed. I am running Debian stable and I think this is why. But if I could get this script working for the sys and keyboard controller I think it might fix the issues I am having as well.
edit: @josch was able to help me with this because the dude is a serious rock star. Basically the -s option used with which in the scripts doesn’t work due to a which being a different version on Debian stable. After removing it the script works beautifully. I really suspect that this may fix the keyboard resetting and disconnecting.
I see the same behavior with FW 20251118. Last thing I can see before the hangup are repeats of the last touched key. Then trackball and keyboard become unresponsive. I can attach a mouse to shut down the device. USB and keyboard reset may bring back life, but sometimes it takes several reboots.
Hi @habasud
There is a similar discussion here ( Pocket Reform Keyboard disconnects and crashes ).
My take so far is that is mostly an incorrectly seated cable or a faulty keyboard. Mine still has this problem once in a while depending on how I wiggle the pocket and the hinges position. Also tends to go away for a bit if I open and re-seat the cables.
An easy test is also to check if the keyboard drives the OLED menu cleanly but you can´t type in the system. Which, as far as I understand, mostly means the Keyboard is alive and well but the USB connection failed.
As mentioned over there, for some reason cleaning the trackball helps. I don’t know how these two things are connected but I’ve seen it multiple times now:
My guess is that a dirty trackball/sensor somehow causes an issue in the firmware that controls both the trackball and keyboard and leads to the observed keyboard problems, but I’m not able to diagnose these things on the firmware level. I know it sounds weird, but my observations strongly point towards this.
I investigated that closing and reopening the lid just brought keyboard and trackball back to life. However when I move the lid while writing this, no malfunction occurs. So maybe that was unrelated and I have to observe it. USB connectors on both sides -keyboard and motherboard- are plugged in tightly. The OLED Display is accessable anytime.
Then @habasud seems you have exactly the same problem I have.
Sometimes it works, sometimes it doesn’t and I can’t tell you if it’s related to what @selfawaresoup points to, or to what i think is a cable malfunction or pinching or whatever is going on there.
I have no solution for you 
I ordered a replacement some time ago just in case it was a hardware malfunction but I did not get to the bottom of it.
I also started to experience the unresponsive keyboard and trackball issue just recently (running the latest firmware). I have the suspicion that it happens somewhat related to the position or movement of the lid, maybe the cable passing next to the hinge is somewhat related? I am not sure. I don’t have this issue too often for it to become annoying 
Btw.: I made a FW-”update” to the latest version from the mnt homepage that turned out to be a downgrade (20251118 to 20251030).
fwupd should update your keyboard and system controller firmware to the latest official version, if that is more convenient to you.
I’ve been having this happen recently (as well as keyboard resets in a loop), and while it’s been hard to pin down I feel like you might be right about it being related to the position of the lid. It didn’t occur to me until reading it in this thread but I think I have had the keyboard issues improve when slightly adjusting the lid position.
I just was editing some audio in audacity when trackball and keyboard froze in.
I first did a keyboard reset that didn’t help. After that an USB reset which also had no effect.
I left the room and the Pocket was untouched. When I came back, trackball and keyboard had come back to life and audacity was playing audio…
I have had this problem, but recently, I replaced my display. Normally I would have this issue at least once a day, but it hasn’t shown up in two days.
Perhaps I moved a cable and that fixed it?
Ok, it seems to be happening again. I can generally fix it by resetting USB and the keyboard. But it would nice to fix it?
are you on the newest system controller and newest system image?
I am also still (sort of regularly) experiencing issues with unresponsive keyboard and trackball. I’m on the latest firmware. The keyboard goes unresponsive, sometimes it is fixable by going into the oled menu and resetting keyboard or usb. But sometimes it doesn’t work, or the oled menu is also unresponsive. And when it goes very unresponsive, sometimes I get a rainbow on the keyboard leds (different colors light up on different keys) 
We had lots of issues with the RP2040 controller in the keyboards, and I replaced many of them. It could be that the chip itself is failing. The chip is very cheap and can be replaced in about 15 minutes if you have access to equipment, maybe xhain has the equipment needed (heatpump, hot plate, soldering iron, microscope)? What firmware does the keyboard you have report?