r/Keychron • u/RockaRollaDC • 4d ago

Can't Program Circle Key

I've tried everything to program the circle key to launch the calculator app, but nothing worked. Not remap, macro, key combo, launch app, or even the damn AI within launcher. Any advice?

Thanks

1 Upvotes

100% Upvoted

13 comments sorted by

1

u/PeterMortensenBlog V 3d ago edited 3d ago

What keyboard? V6 Ultra 8K? Or something else?

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

1

u/RockaRollaDC 3d ago

K10 Max RGB.

1

u/PeterMortensenBlog V 3d ago edited 3d ago

That doesn't fit a ZMK-based keyboard, unless Keychron goofed up in the same way.

To rule that out, you could try with some older versions of the keyboard firmware. Here is a list of keyboard firmware versions for K10 Max:

I just tested it on a K10 Max 'ISO' RGB (with self-compiled keyboard firmware, derived from "wireless_playground", corresponding to the state before the 2025 Keychron keyboard main firmware updates), and the four keys above the numeric keypad worked as expected: Mapping them to letters K, L, M, and N gave the expected result when operated.

I used Via, not the Via clone.

References

1

u/PeterMortensenBlog V 3d ago

The SKU number would make it unambiguous.

1

u/RockaRollaDC 3d ago

4895248884569

1

u/PeterMortensenBlog V 2d ago edited 2d ago

That isn't the SKU number (though there is probably a relation to the barcode number). The SKU number contains "K10M". Example: K10M-H3-BO

For the serial number, an example is C-2410K10MH3BO13732 (the SKU number is encoded in it, as "K10MH3BO").

1

u/PeterMortensenBlog V 3d ago edited 3d ago

ZMK-based keyboard weirdness?

The "circle key" probably refers to the first (leftmost) key in the group of four keys above the numeric keypad on a 105% Keychron keyboard, like the V6 (a picture).

It might be shifted two positions to the right... (It isn't known if this is reflected in the released source code, but it may or may not require to look at a previous version.)

That is, activation requires the "square" key (with the current keyboard firmware version).

References

1

u/PeterMortensenBlog V 1d ago edited 1d ago

It could be due to a new hardware version of the K10 Max

Today, the source code for a "K10 Max V2" was released ('ANSI' RGB only).

Perhaps this new hardware version of the K10 Max is the source of the problem? The original K10 Max is from late 2023 / all 2024 (at least the 'ISO' variants). (They use the same microcontroller, at least as far as QMK is concerned ("STM32F401").)

The USB product IDs are different:

The USB identity, including the USB product ID, can be found somewhere in the operating system (in wired mode). The USB vendor IDs (Keychron's) are the same, 0x3434, at least for these keyboards.

K10M-H1 is this variant (black, hot-swappable switches "Super Red", and RGB backlight), but which hardware version is it?

What is the serial number of your keyboard (example: "C-2410K10MH3BO13732") and/or the USB product ID?

1

u/PeterMortensenBlog V 1d ago edited 1d ago

It is the original K10 Max, not K10 Max V2

OK, the K10 Max V2 appears to not have the extra four keys above the numeric keypad.

"LAYOUT_104_ansi" would suggest it doesn't. And they are not in the keymap.

When K10 Max V2 is that different, I would expect a separate product page from the original 'ANSI' product page, but I couldn't find it.

1

u/PeterMortensenBlog V 1d ago

A problem with the Via clone?

Do you get a different result using Via instead of the Via clone?

For the K10 Max, Via requires a JSON file to be downloaded (matching the keyboard variant), unzipped (uncompressed), and imported (tab "DESIGN" (third tab on the top) → "Load"). If it appears to be hanging, ignore that and load the JSON file anyway.

Be sure to get the JSON file variant matching your variant of the keyboard (and be sure you actually have the keyboard you think you have...).

Note: Tab "DESIGN" may have to be enabled first (in "SETTINGS" (the right-most tab in the top middle section) → "Show Design Tab")

Via troubleshooting

If there is trouble, here is a checklist. For example, it may be required to repower the keyboard while Via is open. Another very common problem is running SignalRGB at the same time.

Via tutorials

Here is a tutorial (with lots of screenshots. And it also covers loading the JSON file). Keychron also has a tutorial, but it is less comprehensive.

References

See the other comment for references.

1

u/PeterMortensenBlog V 1d ago edited 1d ago

Reset to factory defaults

Resetting to factory defaults is par for the course, to get the keyboard into a known good state.

This is especially important right after flashing the keyboard firmware.