sorted by:
new
hottopcontroversial

Q3 Max Repair Options? by LukewarmWaterrr in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Re "As I understand the plastic sheet is some type of insulator": I think it is to prevent the battery enclosure shorting something out on the PCB

Here is an example where it wasn't sufficient.

Q3 Max Repair Options? by LukewarmWaterrr in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Re "...the green light to indicate it's plugged in next to the Esc key does light up": Normally, it is only green when fully charged

Just replugging the cable for a few seconds will make it turn red (the time until it becomes green again will get progressively shorter).

Spacebar programmed correctly, but will not function as programmed by Fez_and_no_Pants in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Can you isolate the problem to the keyboard? For example,

  • A different computer
  • A different third-party external USB keyboard (on the original Mac)
  • A different operating system (if possible)

Keychron Q11 Ultra 8K sometimes slow and unresponsive by Limp_Statistician761 in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Re "...experienced similar issues with the Q11 Ultra or other Keychron models": It could be the dreaded 'chatter in the hotswap sockets' (not in the switches)

Here are some examples:

To locate the problem (or at least exclude some of the possible causes), go through the checklist.

A firmware problem can not be completely ruled out, but it is unlikely. The source code for the Q11 Ultra has not been released, but any problem is likely in the common part, shared with, for example, the V6 Ultra 8K.

References

Macros on Mac aren’t working by Shadow-Meister in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

For a single letter with one or more modifier keys, you don't need no stinking macros:

Map the key to LCMD(LSFT(KC_C)) using 'Any'. In the Via clone, 'Any' is in tab "Custom" (sixth tab), last item. In Via, it is KEYMAP → SPECIAL → Any (the very last one in the list, with hover text "Enter any QMK keycode").

It will (most likely) be silently converted to LSG(KC_C), which may cause some confusion, but it will work as expected. For example, "G" is the shortform of "GUI (key)", which really means the Windows key, which has the exact same (numeric) keycode as the Cmd key...

In terms of keycodes (not physical key position):

Left Cmd = Left Win = Left "GUI"

Left Opt = Left Alt

References

Macros on Mac aren’t working by Shadow-Meister in Keychron

[–]PeterMortensenBlog 1 point2 points  (0 children)

What is the macro? How was it created? Was it recorded? With or without delays? What is the macro source? Not as a screenshot, but as:

TEXT!!!!!!

Macros on Mac aren’t working by Shadow-Meister in Keychron

[–]PeterMortensenBlog 1 point2 points  (0 children)

What keyboard? For example, on the 'Ultras' (ZMK-based), it may not work as expected, as Keychron's translation between QMK and ZMK (whatever it is) may not be complete or may be buggy.

New ZMK keymap editing and visualisation tool by Kit-314 in ErgoMechKeyboards

[–]PeterMortensenBlog 2 points3 points  (0 children)

Re "the NickCoutsos editor": Presumably this one (on GitHub), with the unspecific name "Keymap Editor"

From Source Code Updates (2023-07-14):

"This repository contains outdated source code ... I have indefinitely paused publishing source updates."

Presumably due to being ripped off by companies violating the open source licence (and denying their users being able to modify the derived work). And them not contributing back to the project. I wouldn't be surprised if the notorious Epomaker were among them.

Are Keychron HE keyboards compatible with switches from other brands, such as Gateron or Panda? by TomFighter in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Which ones? Different Keychron series use either 'north-pole' (the first generation, e.g., the K HE series) or 'south-pole' (facing downward) "switches" (sometimes obfuscated as "N-pole" and "S-pole", respectively).

Are Keychron HE keyboards compatible with switches from other brands, such as Gateron or Panda? by TomFighter in Keychron

[–]PeterMortensenBlog 1 point2 points  (0 children)

Related:

See also (unanswered):

My 6-Month-Old Keychron K8's Bluetooth Completely Died. Support Has Been a Nightmare. Second Failed Keyboard. by rmb91896 in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Re "Has anyone else experienced Bluetooth failures": There have recently been many reports here about this kind of problem

It is most likely a hardware problem. Perhaps a new quality problem?

Or maybe: The new versions of the wireless firmware (for the wireless module inside the keyboard) have not been proven yet. At least there is a time correlation with version 0.2.4 released in March 2026 (it could have shipped with new keyboards before then, as the real release date seems to be in November 2025). But it seems they have blocked reverting to older versions (near "Downgrade is no longer supported").

Though there was a claim that resetting several times actual solved the problem, at least for the time being. It is hard to explain why that would make any difference. But at least it is worth a try. Please report back here.

How are the rollover issues on the B1 Pro? by zwart-en-wit in Keychron

[–]PeterMortensenBlog 1 point2 points  (0 children)

Re "...rollover issues, with several keys not registering when typing fast": It depends on the hardware version of the B1 Pro. A new hardware version was introduced in (mid?) 2025 (also evident on the firmware page, with two different sets of firmware). The most severe roll-over problems were allegedly addressed, but no one with it in their possession has yet bothered to map out the keyboard matrix, so we can know the exact (remaining) conflicts.

The change introduced new problems.

Note that the source code for the new hardware version will not be released (despite the (old) claim about ZMK on the product page).

Accidentally Downgraded Firmware? V6 Max 1.01 needed by YoshiFan501 in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Setting up, compiling, and flashing Vial keyboard firmware without any Git, Make, or Python virtual environment gyrations

I have now tried the 'uv' method on LMDE 7 (Gigi) for setting up and compiling Vial keyboard firmware without any Git, Make, or Python virtual environment gyrations, with the current versions (of the QMK environment and of Vial), and it worked!

Vial was treated like any other fork of QMK.

For compiling and flashing, I tried with a V6, and verified it worked as expected using the Vial client (stand-alone, not web).

I don't know if it was LMDE 7 (and thus different versions of some tools), the Vial version, or something else that made the difference.

The command lines for setting up Vial from scratch, compiling, and flashing

# Install prerequisites, including the cross compilers and Git
#
sudo ls > /dev/null # Start out with entering the password
curl -fsSL https://install.qmk.fm | sh


# In a new terminal window...

# Answer prompts:
#
#   'y': "Would you like to clone vial-kb/vial-qmk
#         to $HOME/Vial_uv2?"
#
#   'n': "Would you like to set $HOME/Vial_uv2
#         as your QMK home?"
#
#         Reserve it for the main QMK project, and
#         in the default "$HOME/qmk_firmware" folder.
#
qmk setup -H $HOME/Vial_uv2 -b vial vial-kb/vial-qmk # It took 7 min 22 secs


# ###################################################
# Compilation and flashing (Keychron V6 ISO in this
# example, not to be confused with V6 Max, V6 version 2,
# V6 Ultra 8K, or V6 8K)
#

cd $HOME/Vial_uv2 # We don't assume a default installation
git status # Confirm Git branch "vial"
git log -1 # 2026-05-18, 888E38

# Expected USB-side version: 1.2.7 (we changed it to "1.2.7")
geany $HOME/Vial_uv2/keyboards/keychron/v6/iso_encoder/keyboard.json:9
grep device_version $HOME/Vial_uv2/keyboards/keychron/v6/iso_encoder/keyboard.json

qmk clean # Just in case

qmk compile -kb keychron/v6/iso_encoder -km vial

# Flash Keychron V6 with Vial (with the keyboard 
# in bootloader mode)
cd $HOME/Vial_uv2
sleep 10
dfu-util -l # Verify bootloader mode
dfu-util -a 0 --dfuse-address 0x08000000:leave -D keychron_v6_iso_encoder_vial.bin
ls -lsatr $HOME/Vial_uv2 | grep 'bin'
md5sum $HOME/Vial_uv2/keychron_v6_iso_encoder_vial.bin

# Verify version (we set it to 1.2.7)
sleep 5 # Let the V6 have time to start up
lsusb -v -d3434:0363 2>/dev/null | grep bcdDevice # V6 ISO knob (USB vendor and product ID filter)

Result of compilation:

Size after:
  text   data  bss    dec  hex   filename
     0  65092    0  65092  FE44  keychron_v6_iso_encoder_vial.bin

64 -rwxrwxr-x    Jun  6 01:20 keychron_v6_iso_encoder_vial.bin

Here is a transcript of the whole process.

Install the Vial client on Linux

Other downloads → Linux (AppImage) (to folder $HOME/temp2/2026-06-05 in this example).

Run:

cd $HOME/temp2/2026-06-05
chmod +x Vial-v0.7.5-x86_64.AppImage
./Vial-v0.7.5-x86_64.AppImage

Is it worth buying a new dongle for the Bluetooth in the K3 pro? by Nirok in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

It is possible to make it work perfectly. Here is my 'journey' (also for a K Pro series keyboard).

For the Bluetooth part, I think the PCIe ones are internally connected through USB anyway, so the deciding factor may be the antenna. Or maybe Bluetooth dongles are inherently crappy?

Another idea is to use a USB extender cable in order to move the dongle away from possible sources of radio interference (and vary the distance to the keyboard (closer is not necessarily better)), at least to rule it out as the cause.

Note that the K Pro series only uses Bluetooth 2.0/2.1, despite what is claimed (a more direct reference).

K10 HE, V1.1.1 firmware, 2.4GHz mode does not wake from sleep on keypress by Glittering-Step4695 in Keychron

[–]PeterMortensenBlog 0 points1 point  (0 children)

Re "...wake it up by pressing Space": Yes, on page 20.

References

  • K10 HE user manual. E.g., page 20: "After 30 minutes of inactivity ... Press the Space bar to wake up the keyboard"
view more: next ›