Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modifier keys set in wired mode not preserved in wireless #262

Open
amartyaksinha-UC opened this issue Aug 5, 2024 · 1 comment
Open

Comments

@amartyaksinha-UC
Copy link

amartyaksinha-UC commented Aug 5, 2024

Hi all,
I'm facing a frustrating issue which is likely related to firmware, but could also be a bug with VIA which is why I thought I'll put it here. I have a Shortcut Studio Bridge75 Plus which is on VIA Firmware Protocol 12 (as per the diagnostic message).

So, in layer 1, I have changed the function of a few keys using the G modifier QMK code, which presses the GUI/Command key while pressing another key.

I have G(KC_DOT), G(KC_UP) and G(KC_LEFT) bound to a few keys in layer 1. While these functions work as programmed in wired mode, it does not work over both Bluetooth or 2.4ghz connections.

So pressing MO(1) + G(KC_DOT) in wired mode brings up the emoji menu as expected, but the same combination of MO(1) + G(KC_DOT) only inputs dots in wireless modes (same issue with other keys coded with G modifier). To get around this issue, I had to add macros to make them work in wireless modes. So, instead of using the "Any" key function to assign G(KC_DOT) to a key, I instead have to add a macro as below and assign that instead:
{+KC_LGUI}{+KC_DOT}{10}{-KC_LGUI}{-KC_DOT}

I tried looking up a solution but the closest I could find was this Reddit thread for a Keychron keyboard facing a similar predicament: https://www.reddit.com/r/Keychron/comments/11y1l2c/one_specific_via_macro_isnt_working_over/
However, there doesn't seem to exist any such issues in QMK's or VIA's Github repos (at least none that I could find).

Can someone else with a dual/tri mode VIA board try the above and let me know if you also encounter this? I don't mind using macros to achieve this but this seems like a bug or error on either VIA or SCS's part, and I want to see if there's anything that can be done.

So far, I've done the following with no luck:

  • Changing layer for keys with G codes
  • Trying out various keys assigned as MO(1) instead of the default Fn key and the Caps Lock key that I was using as the Fn/Mo(1) key via tap dance [coded as LT(1,KC_CAPS)] using the "Any" key option
  • Reset the board
  • Reflashed the firmware
  • Adding the G modifier commands manually in VIA; and by loading a layout with those functions already defined

Anything else I can try?
Would have tried downgrading the firmware but Shortcut Studio's website doesn't have older firmware available to download; and in any case only the latest firmware supports sleep mode which is essential for me as someone who intends to use the keyboard wirelessly.

If it helps, it seems that the bug is specifically with how VIA/the board's firmware currently handles (stores?) QMK's modifiers keycodes once it exits wired mode. Not sure if this issue also exists with other keycodes, but I also tested the LSG/SGUI modifier which has the same issue as the LGUI/G modifier.

this was not an issue till today morning. I was using the same layout for at least 3 days (when I initially set it up), and all layer 1 keys worked as they should. Which is why I'm not sure if this is a VIA or a Shortcut thing, and I asked if others with a tri mode VIA PCB could check. Thanks.

@zenador
Copy link

zenador commented Dec 10, 2024

This might not be a problem with VIA. Have you tried using the latest firmware v1.19 from here? It says it Fixed support for the ANY key in wireless mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants