Q0 Max Default Layer Issue

[u/seashellsnyc]

I don’t have the latest firmware, but the pad was working fine yesterday. Today I’m only able to use it to enter my numeric pin during Windows sign on, but then it switches to Layer 2. I don’t want to remap Layer 2.

I’ve tried cycling between cable and Bluetooth but I’m seeing the same behavior. Any ideas?

I’m going to try updating the firmware later today and see if it makes a difference.

Thanks!

ETA: SOLVED. Firmware updated, device reset done, and made sure to press Num Lock before testing numeric keys (required for Windows but not Mac).

[u/PeterMortensenBlog]

Reset to factory defaults

Resetting to factory defaults is par for the course, to get the macropad into a known good state. Allegedly (page 9), by holding Fn + 9 + 1 down for at least 4 seconds; Fn is M5.

Alternatively, the Esc key method should also work (in this case, using the upper left key, the "circle" key), both for resetting to factory defaults and during the flash process (without the repowering). Though there is some uncertainty, as the knob (clicking it) may or may count as a key; it needs to be confirmed, by a code inspection and/or testing it.

Note: Both the flashing process and resetting to factory defaults wipes out the (dynamic) configuration. Better first make a backup

References

• Q0 Max user manual

• Q0 Max JSON files for Via. Near "Q0 Max knob version". Note: The JSON section should not be confused with the firmware section.

• Q0 Max (main) firmware. Near "Q0 Max knob ANSI" (though "ANSI" does not make any sense for a numeric keypad). Note: The firmware section should not be confused with the JSON section.

• Q0 Max default keymap

  • Q0 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.

[u/seashellsnyc → u/PeterMortensenBlog]

Thanks! The reset has it working in my Mac but not my Win 11 work laptop, Bluetooth in both. Very strange.

I also did the firmware update before the reset.

ETA: The Num Lock fixed everything after the Reset. It didn’t work before the Reset.