Open duckyz5 opened 2 years ago
Hi I also have this issue for my MW65
Did you try the fix?
Sorry which fix?
Hi I also have this issue for my MW65
Did you try the fix?
Sorry which fix?
earlier in the thread I outlined a possible fix, please try that and let me know if it works
Same issue here with a 980mini...
Same issue (still) here with a Keychron Q1.
First of all kudos @LilithWasTaken, you seem to have put a lot of work into researching this issue. Sad the devs apparently haven't picked up on it yet.
@AoXNeR I think I am at the exact point where you were, have you found any hotfix that works for you by now? I tried all 3 config files from here on both VIA 1.3.1 and 1.2.6.
For via fix, you need to load in the previous version of sinc-rev2.json before plugging in the board B/c revert of bad pull request hasn’t been merged in yet
@LilithWasTaken, you said something about a revert of a bad PR not having been merged yet? Is that public? I already have problems finding information about the compilation process overall. I would love to just fork a repository, do the changes myself and compile a hotfixed version if that's possible, and I'm looking to save some time on research :wink:
For via fix, you need to load in the previous version of sinc-rev2.json before plugging in the board B/c revert of bad pull request hasn’t been merged in yet
@LilithWasTaken, you said something about a revert of a bad PR not having been merged yet? Is that public? I already have problems finding information about the compilation process overall. I would love to just fork a repository, do the changes myself and compile a hotfixed version if that's possible, and I'm looking to save some time on research 😉
Hey sorry for not being in here as of late, I appreciate the props. It took a hot minute to find that fix. As far as I know there is not a repo to fork from, I ended up buying a Q1 to see if I could replicate the issue and I'm getting the same thing on the lighting tab, for now im using the keymapping to control the lighting but I will see if I can find a work around for y'all
thanks for sticking around!
The new Keychron Q3 has the exact same problem as its predecessors, and worse, there are no other .json revisions to try, it's first one is bad right out of the gate. Plus, there is not a Q3 folder in the VIA GH repo yet, or even in the QMK GH, either. Sarcastic WOOHOO. And here I thought being able to use VIA was going to be advantageous. That's what I get for jumping in to buying a new board too quickly.
This is what worked for me on the Q1 I just received. Not a full solution but at least it got me working
1) Followed the steps to reset firmware (https://www.keychron.com/blogs/archived/how-to-reset-your-keychron-q1-to-factory-settings) and used the provided 'Q1 Non Knob Ansi Firmware'
2) After firmware reset was complete I quit QMK toolbox
3) Downloaded the JSON file (https://www.keychron.com/pages/how-to-use-via-to-pair-with-keychron-q-series-keyboard) for Non-Knob JSON file for ANSI, which is my version keyboard
4) Disconnected the keyboard and launched VIA
5) I clicked on the 'Via' menu in the upper left hand corner and clicked on 'Import Keymap' and chose the JSON file I downloaded which happened to be v 1.03 based on file name and loaded that up. **The JSON file link that you're provided in the steps to reset firmware didn't work I had to download this file from the URL I proved in step 3
6) After the file was loaded, I plugged in the keyboard and was able to load lighting and make changes. However every time I launch VIA I have to load that JSON file to avoid blank screen.
Damn they literally didn't update huh. I've been waiting all this time lol.
Q2 Iso non Knob. Firmware latest 1.05 Issue still present. Via is not able to start/Reconize the board.
Any update on this? I'm not able to use the lighting tab for an air40 I just got.