app VS qmk_firmware

Why doesn't usevia.app support these features? Is there something about them that makes them hard to code? Maybe the issues will have relevant threads

Maybe Because Olivia is one of the main developers behind Via?

Over at the VIA Github, the devs seem kinda mad at the Keychron guys for using the older V2 standard instead of V3...

Via is part of QMK and offers a GUI to edit keymap on the fly. You are effectively reprogramming part of the firmware, without the need to compile it from scratch. Via has not as many options to customize your firmware as pure QMK and has bugs sometimes (https://github.com/the-via/app/issues/82)

We have added the GPL v3 license to all VIA repositories in https://github.com/the-via.

Thanks for the bug report quantumlocke! We've filed an issue and will be looking into it.

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