I’ve just received my CM4 DevTerm - yes I know I’m late on the adopter curve
After a worrying period of it not starting (the CM4 module was not shoved in with enough force) I’m up and running and have updated OS and keyboard firmware from the official github repo.
The trackball is even jankier than I feared so I’m trying to get to grips with the keyboard shortcuts but I’m not finding them to work as expected/documented for the Pi:
CTRL-ALT-T launches a terminal.
CTRL-ESCAPE does NOT open the system menu, and neither does ALT-F1.
CTRL-ALT-L does NOT lock the screen.
Assuming CMD is the “Windows” key then shortcuts such as CMD-A (“Opens the application menu”) are NOT behaving as expected either.
Presumably I’m doing something stupid and would appreciate someone setting me upon the correct path.
Also my XTAR 18650 3500 mAh batteries are charging incredibly slowly.
The stock Clockworkpi images have slow charging defaults among other issues. I’ve made a updated images and fixed some of the problems with them. the only thing that doesn’t work on the DevTerm on this new image is the thermal printer right now.
I’m beginning to have a suspicion that my keyboard module might be a bit wonky:
Is the trackball (despite not being great) actually meant to be usable ? Mine is very erratic and certainly not smooth, it’s largely unresponsive to small movements but given a bit of a flick it will jerk across the screen.
Is the [Cmd] key meant to be the “Windows” key, it doesn’t seem to do anything, but if I plug an external USB keyboard then the “Windows” key performs “as expected”.
Some of the keys, especially “E” experience a double-bounce when pressed.
Thanks for the prompt responses and helping me with my teething troubles @Rex.
The track ball is just shit
I’m not sure “shit” quite does it justice, which is why I’m wondering if there may actually be a fault with my keyboard unit.
If your DevTerm is convenient could I ask you to start it up and press the [Cmd] key on the Pi OS desktop and tell me it does anything, if it is the “Windows” key then it should display the application menu … if it isn’t the “Windows” key then what is it ?
So as I suspected it is the “Windows” key and either that key on my keyboard is non-functional, or more likely we are running different keyboard firmware.
Do you know which firmware you are running ? Is it possible to query it ? In theory I installed the latest from the official github repo .
Quite surprised at this threat tbh. I mean, I’ve never seen a DevTerm, and actually only had an uConsole in my hands. But, in this unit I talk about, the keyboard is great once you get to hold it with both hands like a “Game-Boy” (I type kind of “phone fast” with it). The the trackmousithingy is amazing, once you get used to it, for sure. I quite tended to muscle-memory-learned to use the pressure as “sensitivity”, I’ll explain; just “rubbing” the surface for fast movements, and pushing it (with care, I know there’s a button but…xd) for smaller movements.
