Keychron mechanical keyboards unofficial support

236 readers

1 users here now

Facebook : https://www.facebook.com/groups/Keychronlinux

founded 1 year ago

MODERATORS

TheOnlyFab@lemmy.ca

Q3 firmware update broke Karabiner Elements (lemmy.world)

submitted 4 months ago* (last edited 4 months ago) by lepinkainen@lemmy.world to c/keychron@lemmy.ca

6 comments fedilink hide all child comments

Keyboard: Keychron Q3 ISO KNOB

I had a working system with Karabiner Elements, I had mapped caps lock to be a hyper-key on macOS. Everything worked perfectly.

Then I was stupid and updated to the latest firmware on the keyboard to 1.0.5 because it's the new shiny.

Now I can't override the capslock key with Karabiner any more.

I can see it's being pressed in the event viewer, but I can't capture the event. How on earth is the firmware bypassing Karabiner and how can I make it stop short of remapping capslock to a key that CAN be overwritten in firmware?

Pretty much every other key can be overwritten at least from the dozen or so I tested already, it's just CAPS LOCK being special.

you are viewing a single comment's thread
view the rest of the comments

[–] dubyakay@lemmy.ca 1 points 4 months ago* (last edited 4 months ago)

Here, I'll quote your post:

Q3 firmware update broke Karabiner Elements Keyboard: Keychron Q3 ISO KNOB I had a working system with Karabiner Elements, I had mapped caps lock to be a hyper-key on macOS. Everything worked perfectly. Then I was stupid and updated to the latest firmware on the keyboard to 1.0.5 because it's the new shiny.

My solution to use VIA to remap pertains to your Keychron Q3 ISO.

To add: every QMK/VIA capable keyboard has its own on board memory that you can configure INDIVIDUALLY and INDEPENDENTLY of the device it is connected to. If you have a Q3, doesn't matter what device you connect it to, if you had mapped the key that has a keycap with caps lock printed on it to Hyper, it will always act as hyper/Ctrl depending on the OS of the device you are connecting it to.