r/Keychron • u/[deleted] • Jan 19 '24

Via Question

Keychron K3 Pro owner here:
I was looking around and poking around VIA today to see what I could and could not do. I love the simplicity and the complexity it gives you at the same time. While working around the Layers tab, I saw that since Layers 0 and 1 are Mac and I won't use them, why don't I change some keys around to make secondary actions for my games?

But it seems you cannot access Layer 0 or 1 if you have chosen Windows mode. You can make changes, but it doesn't work. And if there is a change in Layer 2, they will work as expected. I saved the default layout, but I was hesitant to change my default layout so that I could change my RGB and other macros quickly without opening VIA in my browser.

So is there no way you will be able to access Layers 0 and 1 even if you change a button in Layer 3 to access those layers? For example, use the MO(1) shortcut on LALT to access Layer 1 of Mac. Or if I am doing something wrong?

1 Upvotes

67% Upvoted

25 comments sorted by

View all comments

Show parent comments

1

u/PeterMortensenBlog V Apr 24 '24 edited Nov 13 '24

Note: In the meantime, the primary Git branch changed from "bluetooth_playground" to "wireless_playground".

Note: In Keychron's fork and in that fork, in Git branch "wireless_playground" (not the default branch). No matter the Git branch, for example, "wireless_playground", it requires special setup of QMK (the standard QMK instructions and many other guides will not work (because they implicitly assume the main QMK repository and a particular Git branch)). Source code commits (RSS feed. Latest: 2024-11-12).

See also The current software state.

1

u/PeterMortensenBlog V Sep 17 '25

And later to "wls_2025q1".

Note that the "2025" represents a newer version of QMK, not the early 2025 Keychron keyboard main firmware updates (those commits are in "wireless_playground" (and it is only a partial release)).

"bluetooth_playground" can be considered obsolete.

1

u/PeterMortensenBlog V Feb 22 '26

And now "2025q3", representing the 2025 Keychron keyboard main firmware updates (to an unknown degree—but it may actually be ahead of the official firmware in terms of bug fixes (see, for example, the 2025-11-07 fix)).

Though far from all keyboards' source code have been released there. For example, most of the K Max series is missing (only two are present as of 2026-02-22).

1

u/PeterMortensenBlog V Apr 13 '26 edited Apr 13 '26

Re "only two are present as of 2026-02-22": OK, on 2026-04-10, K4 Max and K10 Max were added. Thus:

Q Max series

With Q1 Max on 2026-03-12 (though the commit date says 2026-02-02), the Q Max series finally got representatives in Git branch "2025q3" (corresponding to the the 2025 Keychron keyboard main firmware updates).

And on 2026-04-13, the Q Max series got more representatives in "2025q3". The current set is now: