Anyway. Do you have other debugging ideas I can help you with?
I didn’t know that but i think qmk version is more convenient
1 Like
Is this a general issue folks are seeing, am curious if the newest firmware is good to go?
I have installed the 20250725 revision of the firmware, jumping from stock. According to wev(1) all keys are working except for the volume key, which may just be an issue with my configuration.
On my machine, the upgrade’s added (by my rough estimate) a half-second of lag between trackball motion and input. It’s jarring - the upgrade has also made the trackball motion significantly less jittery, so whereas before I needed to just keep trying if I wanted to land my cursor on a specific pixel, now I only need to move slowly, and have no harder time.
The keyboard backlight is also a little wonky. Before, when Fn+Space were chorded, the backlight would cycle through the appearances of 0%, 50%, and 100% brightness. Now it takes an additional keypress to go from 0% to 50%, so it loops through 0%, 0%, 50%, and 100%. A late edit: the backlight at 50% is modulated now and noticeably flickers.
Still, I really love being able to scroll now.
For the volume key try
Vol = volume down
Shift+vol = volume up
Fn+vol = mute
I’m still on 20240922 so I don’t know if it changed in the recent update.
I am too experiencing keyboard disconnection upon plugging a device to the USB port with QMK 20250725.
What is the current solution besides reverting back to the stock firmware? You, who do not have this issue, are you using some previous version QMK fw?
This issue (where the keyboard won’t connect after USB state has changed) just hit me for the first time as I went to write a reply, which made me have had to plug a keyboard in. I’ve noticed that the supplied USB power seems to fluctuate when USB devices are plugged in; keeping the keyboard light on and plugging in a keyboard and mouse causes the light to flash before dying. Take this unskilled speculation with a grain of salt but it almost looks to me like the device is trying to supply more current than it can.
I have found the tried and true method of “turning it off and turning it back on” is an excellent, free solution to this problem.
1 Like
seems like it possible to programmatically reset usb device from host system: How do you reset a USB device from the command line? - Ask Ubuntu
so someone can write a daemon which will check if keyboard is connected and if not – reset it’s state.
Tried different solutions from askubuntu forum post shared by white-round-square:
usbresetfrom usbutils package:
sudo usbreset 1eaf:0003
Resetting Maple 003 ... ok- unbind-rebind:
echo 1-1.1 | sudo tee /sys/bus/usb/drivers/usb/unbind
sleep 1
echo 1-1.1 | sudo tee /sys/bus/usb/drivers/usb/bind - toggle authorized flag:
sudo sh -c "echo 0 > /sys/bus/usb/devices/1-1.1/authorized"
sudo sh -c "echo 1 > /sys/bus/usb/devices/1-1.1/authorized"
Nothing worked. It just resets the keyboard in bootloader or some other state:
Bus 001 Device 005: ID 1eaf:0003 Leaflabs Maple DFU interface
Could we install a capacitor (or similar hardware mod) on the keyboard’s USB power line to smooth out brief voltage dips?
3 Likes
Hello I’m new to the uConsole, and first off thank you for this QMK keyboard firmware, it’s wonderful. However forgive me if I’ve missed it, but:
Is there any documentation somewhere listing all the default uConsole function keybinds (other than the orange Fn overlays on the actual physical keyboard), and/or the QMK firmware custom keybinds? I see some spread across posts in this thread, but would love to have a complete list. Thanks!
uConsole/Code/uconsole_keyboard/keymaps.ino at master · clockworkpi/uConsole · GitHub ?
on the last official version you can also do fn + ball to scroll vertically
2 Likes
So, I had the stupid idea of messing with something that works just fine and wanted to update the firmware on my keyboard. I had flashed the QMK back at the beginning of this thread but still have the stuck space problem so I grabbed the latest firmware, clockworkpi_uconsole_default.20250725.bin, and ran the command sudo dfu-util -w -d 1eaf:0003 -a 2 -D clockworkpi_uconsole_default.20250725.bin -R (both on the uConsole and through ssh), but when it it reached “Waiting for the device,” hitting fn-esc or LAlt-RAlt-Start did nothing. I would have to remove the batteries to get the keyboard to work again. Am I missing something?
I had the same problem, it seemed frozen after hitting fn-esc. I plugged in my external keyboard to see if I could ctrl-c it from there and plugging it in seemed to kick start it and it worked!