qmk_firmware VS qmk_toolbox

It is in Keychron fork of QMK, not in QMK proper. And note that it is in the branch "bluetooth_playground".

It's essentially the same layout as the Q1 Pro, which is on Keychron's QMK Github repo, but considering this is the first one with 2.4GHz support I'm not sure if this is a good way to go. There's also the same layout on OnePlus 81 Pro, also on Github, but this seems like a replication of the original Q1 Pro firmware.

It may have to be created from the source code.

https://github.com/Keychron/qmk_firmware/blob/master/keyboar...

...you just need to map keys. It was very easy, so now fn-arrow and fn-return work as a mouse on anything I've attached it to so far. I got an rpi recently, only connected this, and was able to navigate the startup ui with no mouse.

Doing a little more digging, I found that these source files are in fact in Keychron's own fork of QMK, and is located in a separate branch : https://github.com/Keychron/qmk_firmware/tree/bluetooth_playground/keyboards/keychron

The source code is located at https://github.com/Keychron/qmk_firmware/tree/playground. The keychron specific bits are located in keyboards/keychron folder. Keychron supports QMK. But, it doesn't support you modifying the code. You have to figure it out yourself. There is a qmk documnetation site at https://docs.qmk.fm/#/ but it is likely to overwhelm you with information. This information is from the Keychron V1 web pages and using google seatch for qmk documentation.

Github repo for Bluetooth Keychron Keyboard : link. Note that Bluetooth keyboards are in the "bluetooth_playground" branch and not in the master. So, when you fork the qmk_firmware repo, make sure to select include all branches and not only the master. Then, when using the QMK MSYS CLI, make sure to switch to the bluetooth_playground branch.

git clone https://github.com/Keychron/qmk_firmware.git

https://docs.qmk.fm/#/feature_layers?id=switching-and-toggling-layers

Flashing custom firmware - the current version QMK tool off the website won't work. You'll most likely get a "USB device connected (NO DRIVER): WB Device in DFU Mode " and not be able to flash anything. You will need the beta version that supports WB32 flashing utility. I grabbed mine from the GMMK guide QMK tool from GMMK

You first have to download QMK toolbox https://github.com/qmk/qmk_toolbox/releases/download/0.2.2/qmk_toolbox.exe. Once downloaded, download this bin file https://github.com/GHv4/Sense75-CAPSLOCK-UNDERGLOW/blob/main/sense75-CAPSLOCK%20UNDERGLOW.bin. Open the QMK toolbox exe file, then hit the open button. Locate the .bin file. Hold Right FN+BACKSPACE until it pops up in QMK Toolbox. Hit flash and wait for it to finish flashing. Via and Vial compatible. YOU'RE WELCOME FRIENDS!!

Flash it with qmk toolbox: https://github.com/qmk/qmk_toolbox/releases

I got things working by using the https://github.com/qmk/qmk_toolbox project, and the firmware file you linked. As you said, my pad now works with Vial, and has 12 layers. Though the layer selector still only traverses between layers 0 through 3.

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

I am currently using the QMK online configurator tool to do the compilation and download the resulting .bin file, and then the QMK Toolbox to flash it onto the keyboard.

Check out this site: http://kpchn.com/s/PoHJ. I found it from the AliExpress page and it leads to all the VIA/VIAL configs for the KPRepublic boards. Go into CSTC75 and you'll see a .hex file, that's the firmware. You should be able to use the QMK toolbox: https://github.com/qmk/qmk_toolbox to flash the firmware.

Tool needed to flash your keyboard (QMK Toolbox) can be downloaded here: https://github.com/qmk/qmk_toolbox/releases/tag/0.2.2

When I first plugged them in, my Mac (running 13.1 Ventura) recognized them as a USB storage device. I was trying to use the QMK toolbox to flash the firmware onto them, not realizing that I needed to drag and drop a .uf2 file instead of trying to flash a .hex file.