It is probably not enabled on the firmware. As it is not enabled by default. So it probably has to be rebuild with via enabled for it to work. Maybe @olly can tell us if it es enabled?
oh i can see in the repo that it is not
rules.mk
POINTING_DEVICE_DRIVER = custom
SRC += timeout.c rate_meter.c glider.c trackball.c
is missing this line
VIA_ENABLE = yes
1 Like
if the firmware does not flash from stock, you can edit maple_upload and set the delay to 1500
uh, slow pointer, it’s unusual, I hope I’ll get used to it.
Hey everyone! 
I’ve been spending some quality time re-working the QMK firmware for the uConsole. Since our input devices are so central to the whole experience, I wanted to see if I could make things feel a bit more polished and responsive.
I’ve made a ton of under-the-hood improvements—specifically fine-tuning the trackball movement to make it smoother and more intuitive.
Get Started
-
Source & Info: qmk-uconsole, instructions, guides and DON’T PANIC is in one place.
-
Downloads: Grab the latest firmware from the Releases tab. Latest is always at the top.
-
Web Key Tester: I’ve also included a web-based tester in the repo so you can visualize the keyboard behavior and layout. uConsole Keyboard Tester
I’d love for you to try it out! Let me know what you think or if you have any feedback. Any bugs, it would be ideal creating an issue on GitHub, or if you don’t have an account, I will followup here.
Enjoy! 
5 Likes
First of all: Thank you! I am really interested in trying your firmware. I have done some work on the stock firmware myself lately and have grown just a little bit tired of flashing 
As external connectivity is very important to me, I wanted to ask how your version handles plugging in external USB devices before I give it a go. Does the keyboard stay in DFU mode after voltage dips?
Edit: The web-based tester is really cool! Just a little heads up: At least for me, the game buttons register slightly swapped. Y registers as Y, but B registers as X, X registers as A and A registers as B.
Edit 2: This “bug” only applies to the stock firmware. I just flashed your version and it feels great! Also: Connecting USB devices works!
1 Like
I don’t mean to spam, but I’ve created a PR that implements scrolling with Select as it seems wildly popular in uConsole community 
Thank you for your work!
Thank you for the comments and testing the firmware. I agree that shift select works better with two hands and FN is too far away from the pointer position. I will test it and merge it later today.
The web tester is coded against the key code in this firmware, so it could be slightly different with other firmware - most importantly it shows keys are registering.
the trackball movement is optimized for the 5 inch screen & resolution. Hope it makes a much more enjoyable - I initially thinking about changing trackball to touchpad, but it seems not necessary now!
Regarding USB power issues, I saw these report - I am sure there is a power brownout issue that triggers QMK going into DFU mode - because the main board is designed for cm3. I tried to reproduce it by plugin all sorts of my common usb devices (thunderbolt nvm, iPhone, usb drives, iPod.. they all seem to be fine for me - via hacker-gadgets usb & usb-c ports) at least I can’t reproduce it for the moments.
I am sorry, I meant to type Select instead of Shift. Scrolling with the Select key is way more comfy when using the uConsole with two hands!
1 Like
Yes! And it’s closer to L&R mouse clicks too.
Thanks for the PR, I have made recommended changes and released it.
2 Likes
I believe this is triggered from the main board’s USB-A port. This blackout has happened to me a few times before. (On the flipside, I find it to be a convenient way to induce the keyboard to DFU mode for updates.) Perhaps this behavior does not occur on the expansion port for some arcane reason.
1 Like
I tested via the built-in internal USB-A port (still waiting for my AIOv2) and so far, I haven’t had any issues. Tried with a USB flash drive, external SSD, FTDI232 and a mouse.
1 Like
It is possible - there might be a workaround by disabling bootmagic for qmk but it will be really not convenient. I can’t confirm until I can reproduce the brownout.
A brownout happened to me today. I caught the respective kernel messages and opened an issue on GitHub.
I found a workaround to restore the bootloader behaviour.
In case of power surge, the keyboard would move to bootloading mode, if no firmware uploading happens to it then it will verify, load the firmware as usual. I have tested with my ethernet cable with 100% backlight on, it restores the keyboard behaviour after power surge (see lights off & back on shortly - and it looks kinda cool as well!), no need to reboot or flashing the firmware now.
Here is the release.
2 Likes
I just tested 1.5 and I can confirm: Works like a charm! Thank you!
Awesome, thank you for confirming!
Tested QMK for the first time.
it seems to work well. the trackball feels little smoother in motion. i have since removed my “mousekeys” hack.
Question though, the original firmware has the YXBA keys mapped to 288,289,290 and 291.
what are these keys mapped to now?
Use the tester to check the JoyCon mapping, bottom of the tester will show the joycon numbers (use tester with the QMK firmware)
1 Like