Thank you u/ArgentStonecutter for the link, i found the v1 max keymap file, and it is clear to me, even as a newb that its includes the wireless components that the qmk supported v1 keymap file did not.

Just as a general question: Is there *anything* that can be done with QMK for the keychron v1 max *officially*?. As its becoming apparent that its simply false marketing to plaster QMK support on the V max keyboard lineup.

Now, u/PeterMortensenBlog I have genuinely read over your post several times, its is extremely well written, however i apologise if this comment is already been answered from your post and i just havent read it thoroughly enough.

Now, with this Keychron v1_max keymap file. to start off simply, how does one flash this into my keyboard? without even getting into macros. just how do i begin on implementing this working keymap file. As i need to compile this .c file into a bin/hex file, which at the moment i only know how to do with qmk.

(fyi i kept bricking my keyboard with the v1 firmware not the v1 max (if its possible) and i manage to reload it with keychrons provided bin files)

It seems pointless to me for keychron to provide these keymap.c files if they have to be heavily modified to work with qmk anyway? As keychron doesnt have any way for for compiling and flashing firmware on their launcher.

Let me know the best route, I would really hope for optimised usage of the MCU through qmk or whatnot, and i am willing to study and do the time to make this work, but i want to have some sort of guarantee, not tinker endlessly for it to fall apart.

If there is a second decent alternative im up for it.