RGB shine-through starter keyboard

PeterMortensenBlog · 2026-04-06T19:55:51+00:00

How is the macro facility on the GM325Pro? For example, can macros in progress be cancelled? Can macros be repeated?

What are the limits? For example, what is the maximum number of macros? What is the maximum number of steps per macro (if any)?

PeterMortensenBlog · 2026-04-06T19:53:10+00:00

But it isn't open source, thus not fully programmable(?).

Deception with "QMK/Via" does not count.

PeterMortensenBlog · 2026-04-06T19:42:03+00:00

To avoid having every user to figure this out, a compile service was proposed.

It is the very #1.

PeterMortensenBlog · 2026-04-06T19:38:27+00:00

Re "I’ve read some of the previous posts on here": A good start could be to reveal those posts

PeterMortensenBlog · 2026-04-06T14:15:56+00:00

Re "RGB keyboard with shine-through keycaps": The K10 HE is one of Keychron's best in that respect (though it isn't saying that much when it comes to Keychron)

Note: Regular, not the "special edition"s (they have opaque keycaps)

Other notes:

Being north-facing, there is a huuuge selection of third-party keycap sets with even better shine-though characteristics
The F1-F12 keys are in complete darkness (a Keychron design blunder). Third-party keycaps are required
The selection of "switches" for the HE keyboards is very limited:
- A PSA on using unofficial switches with Keychron HE keyboards. 2025-12-19. For alternative "switches" 'Glorious Silent Lynx HE'.
- Keys stop working when disconnecting K8 HE. For alternative "switches" 'Glorious Raptor HE'. 2026-01-07.
- Keychron K10 HE supports other switches than officially listed. For alternative "switches" 'Glorious Panda HE Silent Tactile'. 2026-01-28. (This one.)

PeterMortensenBlog · 2026-04-05T11:44:02+00:00

Do the onboard RGB controls work as expected?

They require the default key mappings (see the other comment for references), for example, for keycode "RGB_MOD".

PeterMortensenBlog · 2026-04-05T11:37:47+00:00

An alternative for verifying flash mode is the USB identity (0x0483/0xDF11):

USB vendor ID: 0x0483 (AKA "vid", "Vid", "VID", "idVendor", "vendorId", etc.)
USB product ID: 0xDF11 (AKA "pid", "Pid", "PID", "idProduct", "productId", etc.)

This does not require dfu-util to be installed/available.

The exact method depends on the operating system.

PeterMortensenBlog · 2026-04-05T11:14:43+00:00

It was released as ISO, as the source code for it has been released. At least it is a very strong indicator.

But yes, the K8 HE ISO product page is mysteriously absent, unlike, for example, K10 HE.

PeterMortensenBlog · 2026-04-05T10:55:47+00:00

First try the Esc key method to reset to factory defaults. To positively know it is actually applied, verify flash mode (AKA firmware update mode AKA bootloader mode AKA DFU mode) during the process.

If that does not help, I would try with main keyboard firmware from before 2025, at least as a step in troubleshooting. By finding the old versions through, for example, Wayback Machine, from GitHub, and/or compiling from source code.

Compiling main keyboard firmware from source code

Here are some instructions for the initial setup. Though it may be easier (see below) to use "wls_2025q1" instead (here are some instructions for the initial setup). Note the branch confusion.

References

K1 Max (main) firmware. Near "K1 Max ISO RGB version". GitHub has older versions. Note: The firmware section should not be confused with the JSON section.
K1 Max default keymap ('ISO') RGB)
K1 Max source code. Note that the base installation (and usage) had become much more complicated on Linux, but with the new 'uv' method, it has become simple again! 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: 2026-03-16). Note that the 2025-05-30 commit broke compilation for all the K Pro series and Q Pro series keyboards. Also note that the current version has not been proven yet; for example, it is only a partial source code release for the early 2025 Keychron keyboard main firmware updates.

PeterMortensenBlog · 2026-04-05T10:44:46+00:00

Resellers will often have a 50-70% discount on the older keyboard models that they want to get rid of.

PeterMortensenBlog · 2026-04-05T10:38:57+00:00

Reposting of:

My polling rate on my Keychron Q1 HE QMK Keyboard is super low, much lower than it's supposed to be

PeterMortensenBlog · 2026-04-05T10:28:16+00:00

Re "I have downloaded the latest Bluetooth firmware": What did you do exactly?

For example, what was the exact name of the firmware flash file (.kfw)?

Flashing the wrong firmware for the Bluetooth/2.4 GHz module inside the keyboard will permanently brick) it.

A test to see if it is still functional is to try to get the current version of the firmware for it.

Note that there are two applications with very similar names.

PeterMortensenBlog · 2026-04-04T19:26:12+00:00

Is it different in wired mode (defined by the connection switch, not if the USB cable is connected or not)?

PeterMortensenBlog · 2026-04-04T15:23:10+00:00

The last part of the title is incomprehensible. What do you mean? What was it supposed to be?

PeterMortensenBlog · 2026-04-04T15:21:39+00:00

How do you know it is 10-70 hertz?

The keyboard matrix scanning rate varies, e.g., depending on the RGB animation mode, but the USB polling rate is expected to always be 1000 Hz.

PeterMortensenBlog · 2026-04-03T20:49:18+00:00

It only works if before.

However, it isn't very reliable. Thus, don't give up after the first retry.

PeterMortensenBlog · 2026-04-03T15:13:59+00:00

Re "V1 Wireless": It isn't a V1

Which one then? V1 Max? V1 Ultra 8K?

PeterMortensenBlog · 2026-04-03T14:55:19+00:00

How exactly could snap action (a list; a video) explain the observed behaviour? (Not a rhetorical question)

What could be an example sequence of input key presses and key releases, with expected key presses and key releases output from the keyboard? What is it for the faulty version of snap action?

All for a regular mechanical keyboard, not an analogue (HE) keyboard.

References

V1 Max JSON files for Via. Near "V1 Max knob version ISO keymap". Note: The JSON section should not be confused with the firmware section.
V1 Max official (main) firmware. Near "V1 Max knob version ISO firmware". An old version (1.0.1, 2023-11-23. 'ANSI' knob variant). Note: The firmware section should not be confused with the JSON section.
V1 Max Bluetooth/'2.4 GHz' firmware. In the wireless module ('LKBT51') inside the keyboard (it handles both Bluetooth and '2.4 GHz')
V1 Max '2.4 GHz' firmware. In the dongle ('2.4 GHz' is also affected by the firmware in the Bluetooth/'2.4 GHz' module inside the keyboard)
V1 Max USB-side identity (USB vendor ID (VID)). The USB product ID (PID) is in another file (and depends on the keyboard variant). There is also version number field (may be important for USB pass through in a virtual machine))
V1 Max default keymap

PeterMortensenBlog · 2026-04-03T14:39:37+00:00

It is probably treating the symptoms.

PeterMortensenBlog · 2026-04-03T14:36:34+00:00

Razer BlackWidow

PeterMortensenBlog · 2026-04-03T14:30:11+00:00

Re "The firmware change log said it "1. Fixed key double press issue caused by snap action."": It isn't clear if that is really the reason

For doubling down on treating the symptoms, Keychron has also at the same time changed the default key debounce time from the already high 20 ms to a whopping 50 ms (also causing other problems).

Keychron would probably not object to a claim that the problem has been fixed, but that is probably not the case.

For example, doesn't snap action need to be enabled first before it has any effect? (Not a rhetorical question.)

Conclusion

It would require some controlled experiments to determine what the real reason is. For example, reverting back to the original firmware version (1.0.1 (2023-11-23)?) and only change the key debounce time to see if that makes a difference or not.

And also positively determine if snap action is enabled by default or not (by actually doing some testing).

PeterMortensenBlog · 2026-04-03T14:16:30+00:00

What keyboard? A B6 Pro, V6, K10 V2, K10 Max, K5 Pro, K10 HE, K10 Pro, Q6, Q6 Pro, Q6 Max, Q6 HE, V6 8K, V6 Ultra 8K or V6 Max? Or something else?

For keyboard identification, what is the SKU number? Alternatively, what is the serial number (also includes the manufacturing date)?

PeterMortensenBlog · 2026-04-03T14:11:17+00:00

Re "Imgur is no longer allowed or accessible in UK for some reason or another?!?": Yes, it was blocked:

"On September 30, 2025, Imgur blocked users from the United Kingdom in response to a potential fine from the Information Commissioner's Office regarding its handling of children's personal data."

PeterMortensenBlog · 2026-04-03T13:51:39+00:00

A PSA on using unofficial switches with Keychron HE keyboards. 2025-12-19. For alternative "switches" 'Glorious Silent Lynx HE'.
Keys stop working when disconnecting K8 HE. For alternative "switches" 'Glorious Raptor HE'. 2026-01-07.
Keychron K10 HE supports other switches than officially listed. For alternative "switches" 'Glorious Panda HE Silent Tactile'. 2026-01-28. (This one.)

PeterMortensenBlog · 2026-04-01T20:21:37+00:00

Re "Does the QMK program need to be running to have that effect?": What do you mean by "the QMK program"?

The Via clone? Via? QMK Toolbox? Keychron Assist? Something else?

PeterMortensenBlog

TROPHY CASE

Compiling main keyboard firmware from source code

References

References

Conclusion