Via glitch BLANK SCREENING on LIGHTING TAB

[duckyz5]

[duckyz5]

issue is still here

[duckyz5]

I flashed the latest firmware nothing changed, please fix.

[BigChen520jyp]

have the same issue

[Olivier-tl]

I have the same issue on macOS 12.0.1 (M1) with a Keychron Q2 keyboard!

[ShortCircuitGuy]

I have the same issue on Windows 10 with a
Keychron Q1 QMK Custom Mechanical Keyboard Knob Version.

[duckyz5]

looks like many people have the same issue I hope they fix this soon

[LilithWasTaken]

yes i am also having this issue
windows 10

[cryzereye]

also having this issue with ramonimbao_mona v1 on startup and Lily58 Glow when going to the RGB tab

[LilithWasTaken]

when i have the keyboard unplugged the app opens fine but as soon as I plug the keebio sinc in the screen goes blank

[LilithWasTaken]

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

[LilithWasTaken]

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.

[ShortCircuitGuy]

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.

[duckyz5]

hope more people will come out and comment on this so it'll get noticed by Via

[LilithWasTaken]

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

[xRealNeon]

Same issue with the Q1

[ShortCircuitGuy]

Are the Developer from VIA alive ? It's really annoying that this issue is still open.

[duckyz5]

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 :(

[profpuffypants]

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.

[LilithWasTaken]

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.

[LilithWasTaken]

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.

[LilithWasTaken]

here is the .json for the lily58
https://github.com/the-via/keyboards/tree/master/src/lily58

[LilithWasTaken]

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

[LilithWasTaken]

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!

[profpuffypants]

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 <#153 (comment)>, 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: ***@***.***>

[LilithWasTaken]

I dont work for via I just do alot of research lol

[ShortCircuitGuy]

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 ?

[LilithWasTaken]

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?

[duckyz5]

Can't find the load draft definition. I only have this.

[duckyz5]

damn I wish they could really fix this so it isn't that hard of a task to open the lighting tab xd

[duckyz5]

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.

[ShortCircuitGuy]

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

Q1_knob_ISO_VIA_keymap_V2.0.11.txt

[LilithWasTaken]

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

Q1_knob_ISO_VIA_keymap_V2.0.11.txt

https://github.com/the-via/keyboards/tree/master/src/keychron/q1

please try this .json from the via github

[LilithWasTaken]

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

[AoXNeR]

Instant60 (tsangan) by CannonKeys, still crashes lighting tab with the workaround.

[LilithWasTaken]

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

[AoXNeR]

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!

• Unplugging board -> Launching VIA -> Pressing Design Tab -> Load Draft Definition -> Choose Instant60.json -> Plugging board -> Configure -> Lighting Tab
• After loading draft definition:
  
• After going into lighting tab, blank blue screen as known.

Thanks for your response friend!

[LilithWasTaken]

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?

[AoXNeR]

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.

[LilithWasTaken]

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

[AoXNeR]

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.

[ghost]

Have you all tried using Vial instead?

[AoXNeR]

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. 😟

[ghost]

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.

[wasabaeee]

Hi I also have this issue for my MW65

[LilithWasTaken]

Hi I also have this issue for my MW65

Did you try the fix?

[wasabaeee]

Hi I also have this issue for my MW65

Did you try the fix?

Sorry which fix?

[LilithWasTaken]

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

[vinzenz-muser]

Same issue here with a 980mini...

[MangelWare]

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.

[MangelWare]

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 😉

[LilithWasTaken]

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!

[ttmwebdesign]

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.

[kurosake]

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.

[duckyz1]

Damn they literally didn't update huh. I've been waiting all this time lol.

[erretter]

Q2 Iso non Knob.
Firmware latest 1.05
Issue still present.
Via is not able to start/Reconize the board.

[estbndlt]

Any update on this? I'm not able to use the lighting tab for an air40 I just got.

https://www.aliexpress.us/item/3256803187062587.html?spm=a2g0o.order_list.order_list_main.5.3d521802p3AGo9&gatewayAdapt=glo2usa&_randl_shipto=US