Open duckyz5 opened 2 years ago
issue is still here
I flashed the latest firmware nothing changed, please fix.
have the same issue
I have the same issue on macOS 12.0.1 (M1) with a Keychron Q2 keyboard!
I have the same issue on Windows 10 with a Keychron Q1 QMK Custom Mechanical Keyboard Knob Version.
looks like many people have the same issue I hope they fix this soon
yes i am also having this issue windows 10
also having this issue with ramonimbao_mona v1 on startup and Lily58 Glow when going to the RGB tab
when i have the keyboard unplugged the app opens fine but as soon as I plug the keebio sinc in the screen goes blank
in addition I have tried all versions back to 1.2.6 however it is only happening with the sinc rev2, the quefrency that i have is not having this issue it seems that as soon as the keymap is changed on the main page the gui crashes, is this a possibility? I hope to see this issue resolved and will keep you updated
these are the images for reference, the gui also doesnt come back after the original keyboard is plugged in. the app has to be forced closed in task manager and reopened for the gui to come back.
I think that's a really big issue because there is still an open issue since 6 month #115 with the same problem. Please fix this a soon as possible.
hope more people will come out and comment on this so it'll get noticed by Via
not only 115 but also 128 which I'm not going to lie is getting to be a bit of an issue. at this point, there are three threads about almost an identical issue. I have noticed that this issue is predominantly effecting newer boards, the Q2, lily58, sinc rev2, and the q1 are all newer boards that say that they have out-of-box support through via but via doesn't seem to be supporting them. this is clearly not an issue from the manufacturers as at that point keychron,keebio, and whoever makes the liliy58 would all be making the same issue during the manufacturing process
at this point, since my board is having issues with QMK and via is the only next step I hope this issue gets resolved quickly. if I had to guess it would be that these newer boards haven't been added to via since it hasn't been updated for almost 9 months. these boards are crashing the gui as the program doesn't know how to handle it.
I'm not a programmer and it seems that VIA has been all but abandoned in the last nine months. there are no responses when it comes to the issues that users are facing and there have been no updates. This seems to be a great loss to me
Same issue with the Q1
Are the Developer from VIA alive ? It's really annoying that this issue is still open.
Are the Developer from VIA alive ? It's really annoying that this issue is still open.
really sad if they don't fix this I have an acrylic kb I wanna do some cool lighting with it :(
Hello, just made an account to ask if this has been fixed or what the issue is. I'm having this issue with a bm40 pcb but I do not have this issue with my bakeneko65. I just flashed the bm40 with qmk toolbox with a .hex file "bm40hsrgb" that I got from caniusevia.com . Via is now working as in I can see the keyboard layout under "configure" but the lighting tab brings the blank screen. Im new, and these are my first two boards.
as far as I understand I found a workaround for my board. I found that if you preload the layout with this .json https://raw.githubusercontent.com/the-via/keyboards/16eac088f127d35846266a88fc3837cd165036a2/src/keebio/sinc/sinc-rev2.json
it fixed the issues. the way that this was described to me was this
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
so a work around might work as follows.
before you load via you need to have the keyboard unplugged
you need to find the .json that corresponds to your board for the layout
click this load button and then load the .json layout file and then plug in the keyboard
and the keyboard layout shouldnt crash the gui once the keyboard is plugged in.
like so. If you give me some time I will try and find the keyboard layouts that correspond to the boards that are not working. please try this method to see if it fixes the issue for you.
https://github.com/the-via/keyboards/tree/master/src/keychron/q1
this is the repository for the .json files for the q1, please use the json that is appropriate to your board.
here is the .json for the lily58 https://github.com/the-via/keyboards/tree/master/src/lily58
https://github.com/the-via/keyboards/tree/master/src/kprepublic
the BM40 .json is in here
https://github.com/the-via/keyboards/tree/master/src/bakeneko65rev2
bakeneko65 rev2
https://github.com/the-via/keyboards/tree/master/src/bakeneko65rev3
bakeneko65 rev3
these should be the .json that you are looking for
for every one that has a Q2 I could not find a .json file for that board. I dont know when it will be added but when it is it will be here https://github.com/the-via/keyboards/tree/master/src
this should also resolve any issues associated with this particular problem. I look forward to hearing from everyone and see if I could resolve any issues here. Thank you all for your time and patience. Just remember have fun ya'll!
Wow thank you so much! Do you work for via? I will try this when I get home.
On Thu, Feb 3, 2022 at 9:59 PM LilithWasTaken @.***> wrote:
for every one that has a Q2 I could not find a .json file for that board. I dont know when it will be added but when it is it will be here https://github.com/the-via/keyboards/tree/master/src
this should also resolve any issues associated with this particular problem. I look forward to hearing from everyone and see if I could resolve any issues here. Thank you all for your time and patience. Just remember have fun ya'll!
— Reply to this email directly, view it on GitHub https://github.com/the-via/releases/issues/153#issuecomment-1029684453, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXSRHGLFERRUQHOSGLHTI43UZNTNDANCNFSM5MAPXCGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
I dont work for via I just do alot of research lol
https://github.com/the-via/keyboards/tree/master/src/keychron/q1
this is the repository for the .json files for the q1, please use the json that is appropriate to your board.
Work this also for the q1 knob version ?
https://github.com/the-via/keyboards/tree/master/src/keychron/q1 this is the repository for the .json files for the q1, please use the json that is appropriate to your board.
Work this also for the q1 knob version ?
I believe that you have to change the knob in QMK but the board layout should work
After loading the sinc-rev.2 my correct layout showed but even after closing via, unplugging my keyboard, and loading the .json for the bm40 that you linked and trying another one I found from caniusevia.com I still get the blank screen on the lighting tab however the rest of the board has full functionality.
On Fri, Feb 4, 2022 at 4:33 PM LilithWasTaken @.***> wrote:
https://github.com/the-via/keyboards/tree/master/src/keychron/q1 this is the repository for the .json files for the q1, please use the json that is appropriate to your board.
Work this also for the q1 knob version ?
I believe that you have to change the knob in QMK but the board layout should work
— Reply to this email directly, view it on GitHub https://github.com/the-via/releases/issues/153#issuecomment-1030463517, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXSRHGKCXRXS6MTYJPKRB6TUZRV4JANCNFSM5MAPXCGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
as far as I understand I found a workaround for my board. I found that if you preload the layout with this .json https://raw.githubusercontent.com/the-via/keyboards/16eac088f127d35846266a88fc3837cd165036a2/src/keebio/sinc/sinc-rev2.json
it fixed the issues. the way that this was described to me was this
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
so a work around might work as follows.
before you load via you need to have the keyboard unplugged
you need to find the .json that corresponds to your board for the layout
click this load button and then load the .json layout file and then plug in the keyboard
and the keyboard layout shouldnt crash the gui once the keyboard is plugged in.
like so. If you give me some time I will try and find the keyboard layouts that correspond to the boards that are not working. please try this method to see if it fixes the issue for you.
eek do you have one for mw75?
as far as I understand I found a workaround for my board. I found that if you preload the layout with this .json https://raw.githubusercontent.com/the-via/keyboards/16eac088f127d35846266a88fc3837cd165036a2/src/keebio/sinc/sinc-rev2.json it fixed the issues. the way that this was described to me was this 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 so a work around might work as follows. before you load via you need to have the keyboard unplugged you need to find the .json that corresponds to your board for the layout click this load button and then load the .json layout file and then plug in the keyboard and the keyboard layout shouldnt crash the gui once the keyboard is plugged in. like so. If you give me some time I will try and find the keyboard layouts that correspond to the boards that are not working. please try this method to see if it fixes the issue for you.
eek do you have one for mw75?
https://github.com/the-via/keyboards/tree/master/src
you would find your specific keyboard here,
For the Keychron SQ1 Knob version the issue is still there :/
For the Keychron SQ1 Knob version the issue is still there :/
what keymap are you using for the SQ1? I just want to know to see if a different keymap will solve the issue?
Can't find the load draft definition. I only have this.
damn I wish they could really fix this so it isn't that hard of a task to open the lighting tab xd
Can't find the load draft definition. I only have this.
nvm found it :)
edit:
still doesn't work for me :(
I did it exactly as you told me guess I'm better off waiting for an update.
For the Keychron SQ1 Knob version the issue is still there :/
what keymap are you using for the SQ1? I just want to know to see if a different keymap will solve the issue?
I used this code in a .json file from the offical website. https://www.keychron.com/products/keychron-q1-qmk-custom-mechanical-keyboard-knob-version
the file should be saved as a .json not .txt but also you should use this map https://github.com/the-via/keyboards/tree/master/src/keychron/q1 from the via github, please let me know how this
For the Keychron SQ1 Knob version the issue is still there :/
what keymap are you using for the SQ1? I just want to know to see if a different keymap will solve the issue?
I used this code in a .json file from the offical website. https://www.keychron.com/products/keychron-q1-qmk-custom-mechanical-keyboard-knob-version
https://github.com/the-via/keyboards/tree/master/src/keychron/q1
please try this .json from the via github
Can't find the load draft definition. I only have this.
nvm found it :)
edit:
still doesn't work for me :(
I did it exactly as you told me guess I'm better off waiting for an update.
you have to enable this tab in the settings for the design tab
Instant60 (tsangan) by CannonKeys, still crashes lighting tab with the workaround.
Instant60 (tsangan) by CannonKeys, still crashes lighting tab with the workaround.
could you please show me your process or the via window before you plug in your keyboard
Instant60 (tsangan) by CannonKeys, still crashes lighting tab with the workaround.
could you please show me your process or the via window before you plug in your keyboard
With love!
Thanks for your response friend!
Thank you so much, could you try launching via as an admin? I would like to see if that affects the issue at all. also do you know what version of via you have?
Thank you so much, could you try launching via as an admin? I would like to see if that affects the issue at all. also do you know what version of via you have?
Sadly it did not help. Latest version, 1.3.1 if im not mistaken.
Thank you so much, could you try launching via as an admin? I would like to see if that affects the issue at all. also do you know what version of via you have?
Sadly it did not help. Latest version, 1.3.1 if im not mistaken.
could you please try in version 1.2.6 I want to see if that affects the issue at all. Here is the link for that https://github.com/the-via/releases/releases/tag/v1.2.6
Thank you so much, could you try launching via as an admin? I would like to see if that affects the issue at all. also do you know what version of via you have?
Sadly it did not help. Latest version, 1.3.1 if im not mistaken.
could you please try in version 1.2.6 I want to see if that affects the issue at all. Here is the link for that https://github.com/the-via/releases/releases/tag/v1.2.6
Of course! I'm down to try any idea, if you try and help me, why would I deny you? 😄 Unfortunately though, it did not help as well. Same thing.
Have you all tried using Vial instead?
Have you all tried using Vial instead? Vial is even worse, won't detect my board and 'download VIA definitions' seems "not programmed" just plain text. 😟
Downloading the definitions and then controlling a VIA board works fine on my system - you can also compile Vial firmware for your board and flash that rather than using the VIA firmware with Vial.
Hi I also have this issue for my MW65
Hi I also have this issue for my MW65
Did you try the fix?