Keychron Bluetooth Not Working on Linux: Fix BlueZ Pairing and Bond Removal

Published on 2026-11-08 ยท 9 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your Keychron keyboard is not broken โ€” Linux's BlueZ stack is holding a corrupted bond entry that prevents clean re-pairing. Keychron K-series and Q-series keyboards store pairing credentials in onboard flash across three device slots (Fn+1, Fn+2, Fn+3), and when BlueZ on the host side caches a mismatched Link Key or IRK, the keyboard and host talk past each other at the HCI layer. The fix is a full bond removal on both ends, a ControllerMode correction in /etc/bluetooth/main.conf, and in some kernel versions an explicit HID quirk flag.

Diagnose the Actual BlueZ State Before Touching Anything

Open a terminal and run bluetoothctl. At the [bluetooth]# prompt type devices. If your Keychron appears as a paired device but the status column reads Connected: no even when the keyboard is in pairing mode (blue LED flashing rapidly), you have a stale bond. If the device does not appear at all, you have a scan or controller mode problem. These are two different failure paths.

Check your Bluetooth controller mode first:

  1. Run cat /etc/bluetooth/main.conf and locate the [Policy] section.
  2. Find the ControllerMode line. If it is set to bredr or is commented out entirely, BlueZ will not negotiate BLE. Keychron keyboards use Bluetooth 5.1 and default to BLE mode on Linux.
  3. Set it to dual and restart the service: sudo systemctl restart bluetooth.

Also confirm your adapter supports BLE: hciconfig hci0 should show RUNNING and hcitool lescan should return results without erroring out. Intel AX200/AX210 and Realtek RTL8852AE adapters are the two most common adapters in Linux laptops and both support dual mode without extra firmware beyond what linux-firmware provides.

Remove Stale Bonds on Both the Keyboard and the Host

This is the step most guides skip, and it is the reason people spend hours re-pairing and getting nowhere. You must clear the bond on the keyboard side first, then on the BlueZ side.

  1. On the Keychron, hold the slot key you want to clear โ€” for example Fn+2 โ€” for four seconds until the LED flashes three times rapidly. That wipes the stored pairing credential from onboard flash for that slot.
  2. Back in bluetoothctl, run devices again and note the MAC address of your Keychron (format: XX:XX:XX:XX:XX:XX).
  3. Run remove XX:XX:XX:XX:XX:XX using the actual MAC. BlueZ will delete the bond file from /var/lib/bluetooth/<adapter-mac>/<device-mac>/.
  4. Verify deletion: ls /var/lib/bluetooth/ and navigate into your adapter folder. The Keychron device folder should be gone.
  5. Restart Bluetooth: sudo systemctl restart bluetooth.

Now put the Keychron into pairing mode on the cleared slot (Fn+slot held until LED flashes rapidly), run scan on in bluetoothctl, wait for the device to appear, then pair XX:XX:XX:XX:XX:XX followed by trust XX:XX:XX:XX:XX:XX and connect XX:XX:XX:XX:XX:XX.

Once connected, use the Keyboard Test tool to verify every key registers correctly before you close the terminal session.

Fix Keychron Function Keys Not Working on Linux

Keychron keyboard function keys not working on Linux is a separate issue from pairing. The keyboard ships in multimedia key mode by default, meaning F1โ€“F12 send media commands unless you hold Fn. On Linux you fix this two ways depending on whether you want a firmware-level change or a kernel module parameter.

Firmware-level (persistent across all OS): Press Fn+X+L for four seconds. The keyboard toggles into function key priority mode and stores that in onboard flash. The LED will blink twice to confirm. This works on K2, K6, K8, K10, Q1, Q2, Q3, and Q5 models.

Kernel module parameter (Linux-only, does not affect Windows/macOS pairing slots):

  1. Create the file /etc/modprobe.d/keychron.conf.
  2. Add the line: options hid_apple fnmode=2
  3. Run sudo update-initramfs -u on Debian/Ubuntu, or sudo dracut --force on Fedora/RHEL.
  4. Reboot.

The hid_apple module applies to Keychron keyboards because they report an Apple HID vendor descriptor. fnmode=2 makes F-keys primary; fnmode=0 disables the Fn layer entirely; fnmode=1 is the default multimedia-first behavior.

Keychron Bluetooth Mode Comparison: K-Series vs Q-Series on Linux

ModelBluetooth ChipBLE VersionLinux Pairing Slot CountUSB-C Wired Fallbackhid_apple Module Needed
K2 v2Broadcom BCM20730BT 5.13YesYes
K6 ProBroadcom BCM20730BT 5.13YesYes
K8 ProBroadcom BCM20730BT 5.13YesYes
Q1 ProBroadcom BCM20730BT 5.13YesYes
K3 v2Broadcom BCM20730BT 5.13YesYes

All current Keychron Bluetooth models use the same Broadcom BCM20730 module. The pairing behavior and BlueZ bond management is identical across the lineup, so this guide applies regardless of which K or Q model you own.

If you want to confirm the keyboard is actually sending keystrokes after pairing, the Keyboard Test page will show you live key output with no software install required. For checking that modifier keys like Fn and the layer-toggle combinations register properly, run the test immediately after pairing before you change any module parameters.

Kernel Version-Specific HID Quirks

On kernels 5.17 through 6.1, some Keychron keyboards fail to enumerate correctly over BLE because the HID report descriptor exceeds the default BlueZ ATT MTU negotiation window. Symptoms are: pairing succeeds, device shows as connected, but zero keystrokes register in any application.

To apply the quirk manually without recompiling the kernel:

  1. Find your Keychron's vendor and product ID: bluetoothctl info XX:XX:XX:XX:XX:XX โ€” look for the Modalias line, typically usb:v3434p.... Keychron's USB vendor ID is 0x3434.
  2. Add a udev rule in /etc/udev/rules.d/99-keychron.rules:
    SUBSYSTEM=="input", ATTRS{idVendor}=="3434", RUN+="/usr/bin/setkeycodes 0x70 0"
  3. Reload udev: sudo udevadm control --reload-rules && sudo udevadm trigger.

On kernel 6.2 and later this is largely resolved. Run uname -r to confirm your kernel version before spending time on quirk patches.

After any kernel-level change, re-run the Mac Keyboard Test if you are dual-booting, since macOS uses a separate pairing slot and the udev rule will not affect it.

Frequently Asked Questions

Why does my Keychron keep disconnecting after a few seconds on Linux?

BlueZ's auto-suspend is putting the Bluetooth adapter into low-power mode. Run sudo systemctl edit bluetooth and add ExecStartPost=/usr/bin/hciconfig hci0 sspmode 1 under [Service]. Also check /etc/bluetooth/main.conf for AutoEnable=true under [Policy] and confirm it is set. USB adapter users should also disable USB autosuspend for the specific device via a udev rule targeting the adapter's idVendor.

My Keychron shows as paired but the keyboard test shows no input โ€” what is wrong?

The bond is cached but the HID profile did not complete. In bluetoothctl run disconnect then connect on the device MAC. If keystrokes still do not appear in the Keyboard Test, remove the bond entirely and re-pair from scratch following the steps in the bond removal section above.

Does switching between Bluetooth slots on the Keychron require re-pairing on Linux every time?

No. Once each slot is paired and trusted in BlueZ, switching slots with Fn+1, Fn+2, or Fn+3 reconnects automatically within three to five seconds as long as the host Bluetooth adapter is powered on and the bond file in /var/lib/bluetooth/ is intact.

Why are my Keychron function keys not working on Linux even after setting fnmode=2?

If the keyboard is still in multimedia mode after setting the kernel parameter, the firmware-level toggle takes priority. Hold Fn+X+L for four seconds to switch the keyboard's internal mode to function key priority. The hid_apple fnmode=2 parameter only works when the keyboard firmware is in its default auto mode.

Can I use Keychron Linux Bluetooth and wired USB simultaneously?

No. The keyboard's internal switch (the three-position slider on the side: Off, BT, Cable) is hardware-level. In Cable position the Bluetooth radio is powered down entirely. You cannot have both active at once, which is a hardware design decision on the BCM20730 module, not a Linux limitation.

Which BlueZ version is required for stable Keychron pairing on Linux?

BlueZ 5.65 or later. Earlier versions have a known bug in the LE SMP bonding state machine that causes the IRK to be stored incorrectly, producing exactly the stale bond symptom described in this article. Run bluetoothd --version to check. Ubuntu 22.04 ships 5.64 โ€” upgrade via the upstream PPA if needed.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester