Well I fell down the custom keyboard world.
- Thread starter davetherave2
- Start date
Associate
I've only got opticals, which I wouldn't want to lube as I imagine it'd end up under the switch in the path of the optical sensors.
I've got mechanical ones (K1 Pro) so curious what's possible.
Although I'm also having issues with the K1 and VIA. Keychron have advised me to do a factory reset and use QMK. So, that's fun.
I'm curious what the issue is with Via, what's happening, or not as the case may be?
I'm using the JSON file provided by Keychron, trying to load it and getting an error message. VIA tells me 'object should have required property, lighting' and I can't do anything.
The keyboard works fine, it's just not mapped correctly out of the box.
I assume you have the correct RGB vs White json file? There's also RGB vs White firmware too.
On my Q1s I had to fire up QMK Toolbox and update drivers before the via configs would work or I could update the firmware. Just wondering if you need to do the same?
Link for QMK if you don't already have it:
K1 Pro Factory Reset and Firmware Flash
Keychron designs and produces custom and wireless productive computer peripherals for Mac, Windows, iPhone and Android.
www.keychron.com
Last edited:
They did suggest that, yes. I tried last night and it's not working, QMK is suggesting there is no driver when I try. I've emailed Keychron back with a snapshot of the QMK screen. Hopefully it's something obvious I'm doing wrong.I assume you have the correct RGB vs White json file? There's also RGB vs White firmware too.
On my Q1s I had to fire up QMK Toolbox and update drivers before the via configs would work or I could update the firmware. Just wondering if you need to do the same?
Link for QMK if you don't already have it:
K1 Pro Factory Reset and Firmware Flash
Keychron designs and produces custom and wireless productive computer peripherals for Mac, Windows, iPhone and Android.
Ah ok fair enough. I know when I used QMK Toolbox it "didn't work" at first and I had the "no driver" message too but don't recall if I needed to fire up QMK and then plug in the board or have the board already in. I also tried a reset first too. Anyhow, I had to play about a bit and then one time it fired up and updated drivers, only then could I install the firmware and get Via working properly.
Not sure why but I am convinced you have the same issue as I did, feels exactly the same......
Not sure why but I am convinced you have the same issue as I did, feels exactly the same......
Last edited:
They've responded with what seems like a simple fix I need to do, so will see. Agree though, it feels like a similar issue. I'll see if I can get it fixed later!
So, I 'fixed' the issue (loaded drivers via QMK and then flashed the keeb per Keychron instruction) and can load the JSON file into VIA but, only using VIA online and not through the desktop app (I still have the same error there).
I can configure the layout I want and save it then load it (I get confirmation layout has loaded). However, it's not working. The keys are still as they were, not as they have been mapped.
I can configure the layout I want and save it then load it (I get confirmation layout has loaded). However, it's not working. The keys are still as they were, not as they have been mapped.
Associate
Remember to use Layer 2/3 if you're on a PC. The others are for Macs.
Last edited:
That's exactly the issue, thanks!!
Although i still can't get '\' to map correctly on any layer. It comes up as '#' when I press the key no matter where I try to map it to.
It's like I have an ANSI key layout that's mapped as ISO. Even '@' is where it should be and not on the number 2.
Associate
I've had that issue on non-QMK keyboards, but not on Keychron. In those cases I created a macro with ALT+92.
Does VIA show the keyboard as an ISO version?
Does VIA show the keyboard as an ISO version?
Use NUBS for backslash and use NUHS for the #
Edit - NUBS is non US backslash and NUHS is non us hash for info....
2nd edit - QMK/VIA will show all as ANSI (hence the use of NUBS and NUHS) and the @ is where it should be due to having UK keyboard set in the OS.
Last edited:
Just pick NUBS from the special section and NUHS too for that matter.
Last edited:
Associate
I'm really loving these keycaps. Brand "Jaketsai", not that expensive, 173 keys and have a really premium silky feel. They remind me of a 1980s BBC Micro, especially the font. If you like SA profile (I do) then I'd reccommend them.
Also I experimented with cardboard modding the Q1 (layer of foam then a slice of cardboard directly under the PCB). Sounds like a tape mod on steroids, only disadvantage is losing most of the gasket movement. Sound beats gasket for me though...
Also I experimented with cardboard modding the Q1 (layer of foam then a slice of cardboard directly under the PCB). Sounds like a tape mod on steroids, only disadvantage is losing most of the gasket movement. Sound beats gasket for me though...
Associate
I'm coming to the conclusion that if you're a tactile lover, then linears just don't cut it. I splashed out on some Oil Kings and don't get me wrong, they're nice and all, sound good, and are truly super smooth, albeit more wobbly than I expected, but they still feel super light to my (terrible) typing technique.
So a question to linear lovers- can you reccommend any available/in-stock linears with a satisfying heavy feel?
So a question to linear lovers- can you reccommend any available/in-stock linears with a satisfying heavy feel?