Keychron Q5 Pro Not Supported? about releases HOT 8 OPEN

Just for some troubleshooting steps: first, try the steps laid out here. I would try the steps regarding supplying VIA with a json file first (ctrl+f, If VIA still doesn’t pair, go from there), then if that fails try the reflashing steps from the top of the page.

Also, I'll say that my issue was that Win mode uses layers 3,4. I was using 1,2 (the Mac mode layers).

from releases.

have you tried updating the firmware to support VIA V3?
https://www.caniusevia.com/docs/download_firmware

from releases.

I'm also currently on the Q5 Pro, the firmware I downloaded from the via page (keychron_q5_ansi_encoder_via.bin) is busted (numpad lighting is mis-mapped, no keys respond). I'm guessing this is likely because that firmware is made for the Q5 Max, not Pro. In order to restore functionality, I had to install keychron's firmware here (1.01 ansi) and factory reset (fn+j+z 4 seconds) before it becomes usable again, but back at square one.

from releases.

sorry I did not realize but it is not in the QMK firmware project. you need to open a issue with keychron here for them to submit a pull request to the parent project to add the support.
https://github.com/Keychron/qmk_firmware/tree/master

from releases.

Opened an issue over there, thanks!

from releases.

Just for some troubleshooting steps: first, try the steps laid out here. I would try the steps regarding supplying VIA with a json file first (ctrl+f, If VIA still doesn’t pair, go from there), then if that fails try the reflashing steps from the top of the page.

Also, I'll say that my issue was that Win mode uses layers 3,4. I was using 1,2 (the Mac mode layers).

keychron is developing in a secondary branch called bluetooth_playground. or at least that is where most of there new keyboards are at. they are 3676 commits behind qmk master in that branch that has the code for the Q5 pro.

I'm not sure what commit in QMK is responsible for the VIA 3.0 implementation that they can cherry pick. but thats kind of there problem. that is why I said to go open a issue in the keychron fork of QMK.

from releases.

also, since you closed the issue over there... Keychron/qmk_firmware#238

why don't you close this issue?

from releases.

why don't you close this issue?

well i'm good, hence the closed issue over there, and I'm probably gonna unsubscribe from this issue. @HarbingeroHotSauce is the owner here, we just happened to run into what looked like the same issue so I hopped in.

from releases.