qmk_firmware VS Adv360-Pro-ZMK

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

Turned out there is a bug. See https://github.com/KinesisCorporation/Adv360-Pro-ZMK/issues/143

You could always just replicate the miryoku layout yourself. As for instructions see https://github.com/KinesisCorporation/Adv360-Pro-ZMK.

Kinesis' web-based GUI for zmk makes configuring your keys very easy: https://kinesiscorporation.github.io/Adv360-Pro-GUI. You'll have to first fork https://github.com/KinesisCorporation/Adv360-Pro-ZMK to your own GitHub account. And, flashing the keyboards has been quite straightforward for Windows, just drag and drop, but I can see how involved it could be for other operating systems.

Kinesis's Docker-powered setup for the KA360 is well-contained and easy to modify: https://github.com/KinesisCorporation/Adv360-Pro-ZMK

Just received my Adv360 to upgrade my Adv2 but feeling a bit depressed by how challenging I am finding to just configure and duplicate my Dvorak Programmer layout with ZMK. I've been programming for a long time but I do not find any of it very intuitive even using the GUI helper after forking https://github.com/KinesisCorporation/Adv360-Pro-ZMK. After trying a few settings with basics I realized that I do not even understand how to create a basic keypress consisting of shift modifiers. ie. Dollar sign and tilde with shift press. After seeing ZMK for the first time, it's clear that it's a great decision by Kinesis and love the customizations possible but it would be nice if they added a bit more than a few lines of instructions in the manual. Would appreciate any help/guidance.

I edited my west.yml in my 360-pro-zmk fork of Kinesis and now have: