Hi all,
Iv just got my new uConsole, but the trackball registers only minimal cursor movement and is barely usable. I’ve gone through pretty much every fix I could find on here and it hasn’t shifted, so before I conclude the sensor module is faulty I wanted to ask if there’s anything I’ve missed.
Setup
- uConsole with Raspberry Pi CM5 Lite
- HackerGadgets AIO V2 board, booting from NVMe
- OS: ClockworkPi Bookworm 6.12.67
j1n6’s web keyboard tester: in j1n6’s web keyboard tester (which reads the trackball’s raw output straight from the firmware, before the OS), rolling the ball shows only minimal movement. So the weak signal is there at the firmware level, not an OS/driver thing.
What I’ve already tried (no change with any of it):
- Both trackballs that came in the kit have identical poor result with each.
- Stock factory firmware (uconsole_keyboard.ino.bin) AND j1n6’s tuned QMK firmware (clockworkpi_uconsole_default.bin) same on both.
- Cleaned the balls with isopropyl
- Confirmed the ball spins completely freely in a clean socket, no stiction, glue, or debris
- Added a shim to remove the module’s play/rattle in the case
- Bumped pointer speed + acceleration in labwc
- Checked it’s not stuck in Precision/reduced-movement mode
Given the minimal movement shows up on stock firmware, with a freely-spinning ball in a clean socket, and is visible in the raw firmware-level tester, is there anything else worth trying? Or does this point to a faulty/poor trackball sensor module?
And if it is the module: is the trackball/sensor available as a spare part anywhere, or is it just worth doing a trackpad upgrade