search

keyboardio / Chrysalis

Graphical configurator for Kaleidoscope-powered keyboards
https://github.com/keyboardio/Chrysalis#chrysalis
GNU General Public License v3.0
493 stars 65 forks source link

Modifier keys get stuck [Model100] #1340

Closed min-pascal closed 2 months ago

min-pascal commented 2 months ago

After updating to v0.92.6+116 modifier keys occasionally get stuck. Pressing them again gets them up again

obra commented 2 months ago

This sounds like there may be an EEPROM corruption issue on your keyboard, or there may be a sticky keys setting you need to toggle.

Can you attach the results of 'Report a problem' in the Chrysalis menus after connecting your keyboard?

On Sat, May 11, 2024 at 5:48 AM Michel Nielsen @.***> wrote:

After updating to v0.92.6+116 modifier keys occasionally get stuck. Pressing them again gets them up again

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1340, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2AGVXXWFCRQUXG6NBTZBYHRPAVCNFSM6AAAAABHR462U6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TAOBYGM2DMOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

min-pascal commented 2 months ago

Okay. I'm guessing it is a corrupted EEPROM then. My layouts got screwed after the update and I have had random keys light up in random colors. Do I need to factory reset the Keyboard?

obra commented 2 months ago

That's likely the fastest way to get you up and running again.

best, jesse

On Tue, May 14, 2024 at 8:52 AM Michel Nielsen @.***> wrote:

Okay. I'm guessing it is a corrupted EEPROM then. My layouts got screwed after the update and I have had random keys light up in random colors. Do I need to factory reset the Keyboard?

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1340#issuecomment-2110582047, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2BRXYYSVWOLJPXA5MLZCIXKHAVCNFSM6AAAAABHR462U6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGU4DEMBUG4 . You are receiving this because you commented.Message ID: @.***>

min-pascal commented 2 months ago

I have reset the keyboard to factory defaults with chrysalis but there are 2 things that confuse me. The firmware version 0.92.6+116 was still written in the UI after the reset and there is still misalignment with the key colors given in the software and the keys who have color.

obra commented 2 months ago

On Thu, May 16, 2024 at 12:01 PM Michel Nielsen @.***> wrote:

I have reset the keyboard to factory resets with chrysalis but there are 2 things that confuse me. The firmware version 0.92.6+116 was still written in the UI after the reset and there is still misalignment with the key colors given in the software and the keys who have color.

The firmware version doesn't get reset with a factory reset, just the data stored in the keyboard's persistent storage. Are your modifier keys now behaving? With a straight up factory reset, there shouldn't have been any hardcoded key colors. Can you tell me a bit more about what you're seeing in detail?

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1340#issuecomment-2115985402, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2FZATUUR7F4MVTBUPTZCT67PAVCNFSM6AAAAABHR462U6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVHE4DKNBQGI . You are receiving this because you modified the open/close state.Message ID: @.***>

min-pascal commented 2 months ago

I think I've narrowed down what's going on with the inconsistent colouring of keys. All keys on layer #1 insist to be red if they are not transparent. I moved my layer #1 to another layer as a workaround to get them green. Despite from that the keyboard is functioning correctly. No more sticky modifiers. I do on the other hand experience an occasional bug in chrysalis where keys suddenly change to a 6 digit hex number when editing but that is another and luckily not a breaking thing

obra commented 2 months ago

Oh. So this is a thing that will change soon, but the second layer (Layer 1) is, by default, the Numpad layer. And since the first release of the Model 01, we've had a hardcoded effect that lights the Numpad up as red. In the next firmware release or so, we're going to be moving to a more modern, flexible system, where the LED effect uses a more customizable LED overlay that you'll be able to configure.

Right now, changing what's going on with layer 1 requires compiling a new firmware "sketch" for your keyboard. Alternatively, you could skip layer 1 with your custom config and use higher layers instead.

On Sun, May 19, 2024 at 3:20 AM Michel Nielsen @.***> wrote:

I think I've narrowed down what's going on with the inconsistent colouring of keys. All keys on layer #1 https://github.com/keyboardio/Chrysalis/issues/1 insist to be red if they are not transparent. I moved my layer #1 https://github.com/keyboardio/Chrysalis/issues/1 to another layer as a workaround to get them green. Despite from that the keyboard is functioning correctly. No more sticky modifiers. I do on the other hand experience an occasional bug in chrysalis where keys suddenly change to a 6 digit hex number when editing but that is another and luckily not a breaking thing

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1340#issuecomment-2119181916, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2D3VG437U3NUHKWVCTZDB4HJAVCNFSM6AAAAABHR462U6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGE4DCOJRGY . You are receiving this because you modified the open/close state.Message ID: @.***>