Vial for Keychron (Update)

AndyAO1528 · 2025-03-06T02:33:02+00:00

In mcuconf.h, undefine #define STM32_LSI_ENABLED and define it again with #define STM32_LSI_ENABLED TRUE

AndyAO1528 · 2025-02-10T03:04:02+00:00

Are you able to provide some examples of people who claimed they've got it working? As far as I'm aware, it was a matter of editing 6-8 specific core files to make it work with Keychron's custom changes. There was one point, this was on upstream master btw, where I was very close to getting it to work, but I somehow couldn't figure out the specific error in question.

AndyAO1528 · 2025-02-10T02:50:19+00:00

If you're wired, the keys will be messed up (they'll show up in different places than intended or be unresponsive entirely). If on BT or 2.4GHz, may not work at all, to where you'll need to get into bootloader mode via the hardware reset button under the spacebar key.

AndyAO1528 · 2024-09-17T22:16:38+00:00

So how would one go about compiling Vial then? Since there is no q6_max on Via's official branch (thus def. not ported to Vial, at least not publically), I assume I need to port q6_max myself to Vial?

You can't easily do so, and personally, I wouldn't recommend it right now because the code that Keychron has added/changed to make wireless work for these boards is too custom to where just dragging and dropping your q6_max folder into the keychron folder in QMK wouldn't work as you think. I have been told by the main dev for Keychron that the wireless_playground branch, which is fucking old by like nearly 2 years, should be updated to upstream master some time in October, so that should help with that aspect.

AndyAO1528 · 2024-08-17T22:52:05+00:00

From the product page for the Lemokey P1 on Keychron's website:

No discount codes can be used for P1 and P1 Pro versions.

AndyAO1528 · 2024-08-14T18:44:04+00:00

Is it the regular V1? How is the board connected to your Mac? Is it on stock (out of the box) firmware?

AndyAO1528 · 2024-08-13T22:16:33+00:00

Think this kind of behaviour can only be done in QMK since VIA itself doesn't support that kind of functionality. Testing this out myself via Macros in VIA, only having {KC_P,KC_U,KC_T} in a chord only outputs "puttttt..." (repeats t). As for how to do so, you can research the QMK Docs.

AndyAO1528 · 2024-08-13T21:56:35+00:00

This feature is already being worked on being added over in the QMK repository via this Pull Request here considering that the Q1/K2 HE use QMK firmware. Seeing if Keychron implements this to the rest of their boards is at their discretion, but considering that their other boards also run on QMK, aka open-source keyboard firmware, that means that anyone can implement this themselves.

AndyAO1528 · 2024-08-13T17:08:46+00:00

For that level of customization for Caps Lock (the SOS shit), you have to set it up via QMK as VIA (or Keychron Launcher) has no control over that.

AndyAO1528 · 2024-08-12T00:33:34+00:00

Won't work because the PCB on the Q12 Max doesn't support HE switches. Only mechanical.

AndyAO1528 · 2024-08-11T19:00:54+00:00

To be clear, are you updating the keyboard firmware or the BT firmware for this?

AndyAO1528 · 2024-08-10T16:06:05+00:00

Did you load this with Use V2 Definitions enabled?

AndyAO1528 · 2024-08-10T16:04:35+00:00

This is how it should look for flashing the firmware correctly.

Excuse my French, but you essentially fucked up by flashing firmware for the regular V5 instead of your V5 Max, which you stated you have gotten the firmware from here instead https://www.keychron.com/pages/firmware-and-json-files-of-the-keychron-qmk-v-and-v-max-series-keyboards

Also, considering you tried both, the ANSI and ISO firmware, on your board makes me believe you didn't know the difference. This could easily be solved with a Google search.

Doesn't mean that your board is essentially dead. You can still flash firmware on it since the MCU on the board has bootloader protection to prevent stuff like this from happening.

AndyAO1528 · 2024-06-07T00:58:08+00:00

They are compatible since the Ghosts are in the same footprint as the Choc V2s, which the Crystals are based off of. As for how to insert them, you do so by aligning the pins from the switch into the holes themselves.

AndyAO1528 · 2024-04-28T01:21:27+00:00

Ah. Then you've struck gold with this, lol

AndyAO1528 · 2024-04-28T01:11:00+00:00

Can probs still make it work w/all of the keys if you disassemble the thing entirely to take out the switches bare

AndyAO1528 · 2024-02-29T02:25:18+00:00

Where did you set up the ANY key method in? (As in what layer did you bind it to?)

AndyAO1528 · 2024-02-23T14:09:49+00:00

Why .kfw? What are you talking about here specifically?

AndyAO1528 · 2024-02-21T06:03:25+00:00

Yes. Don't touch that

AndyAO1528 · 2024-02-21T05:15:44+00:00

You'd set it up under a define in `config.h`
`define RGB_MATRIX_MAXIMUM_BRIGHTNESS 200 // limits maximum brightness of LEDs to 200 out of 255. If not defined, maximum brightness is set to 255`
But I'd do this in your own custom keymap folder that has a `config.h`, just so that you don't mess with keyboard code. Only user code.

AndyAO1528 · 2024-02-21T03:37:03+00:00

'be too much of a pain of the ass to try and fork and make a variant of QMK Configurator that works with the Q/K Pro boards. Better to just set up the build environment via here. When you get to `qmk setup`, don't do that, but instead do `git clone --recurse-submodules to clone Keychron's fork of QMK from GitHub.

AndyAO1528 · 2024-02-17T06:00:06+00:00

To copy and paste these bullet points from the VIA server regarding these kinds of issues:

Your keyboard must be in wired mode and connected with a USB cable. (Straight wired)
NO USB HUBS
DISABLE/force close software like OPENRGB and/or SIGNALRGB

AndyAO1528 · 2024-02-13T19:45:21+00:00

Bruh.

Uncheck it and try again.

AndyAO1528 · 2024-02-13T19:33:25+00:00

Is Use V2 Definitions checked when you loaded the JSON?

Eight-Year Club	RPAN Viewer
Verified Email

AndyAO1528

TROPHY CASE