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

KC_LGUI and KC_RGUI not working on my ergodox EZ #423

Closed
Nixsm opened this Issue Jun 20, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@Nixsm

Nixsm commented Jun 20, 2016

Hi,
using QMK firmware, my designated key does not output KC_LGUI nor KC_RGUI, it does output any other key(KC_A, KC_O and so on). Using the Massdrop .hex file the keyboard outputs LGUI normally.
Is this a known problem?

Edit: xev does not recognize that the key is being pressed.

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented Jun 20, 2016

This might be caused by holding the the space + LGUI key when plugging the keyboard in - if you hold space + backspace, if should reset the eeprom, and restore the GUI keys.

@Nixsm

This comment has been minimized.

Nixsm commented Jun 20, 2016

Whoa, that was fast.
Tyvm.

@Nixsm Nixsm closed this Jun 20, 2016

@alexives

This comment has been minimized.

alexives commented Jun 28, 2016

@jackhumbert I'm having the same issue, but I can't seem to get this fix to work. I also tried uploading the hex file in quantum/tools with no result... I can however use GUI_T(KC_NO) just fine... any thoughts?

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented Jun 28, 2016

Are you on an EZ as well? Bootmagic may have been turned off, and if the EEPROM reset doesn't work, you can temporarily map MAGIC_UNNO_GUI somewhere on your keymap to unset that setting.

@alexives

This comment has been minimized.

alexives commented Jun 28, 2016

Perfect! Actually, I'm on an original dox. I guess that's probably why this didn't work. The MAGIC_UNNO_GUI key worked like a charm!

Thanks for the quick response!

@douglascamata

This comment has been minimized.

douglascamata commented Dec 2, 2016

Is there an easy fix for this? I have the same issue but i would like to know if it is possible to fix this without using the command line.

PS: I have the original dox, not the ez or infinity.

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented Dec 2, 2016

What keyboard are you using? The EZ implemented this functionality into the default layout shortly after this. I believe it's the grave key on the symbol layer.

@douglascamata

This comment has been minimized.

douglascamata commented Dec 2, 2016

I'm using an ergodox (vanilla, i think), bought from falbatech.pl. But I'm using the configurator from Ergodox EZ webpage. Maybe this is what I'm doing wrong. I think I should use the configurator from Massdrop, maybe?

@douglascamata

This comment has been minimized.

douglascamata commented Dec 2, 2016

BTW, it works if I configure it as Command + KEY but don't actually fill this key. But this generate crazy behavior if I type Command and decide not to pressing anything right after... it kinda stores this Command key press and combine it with the next key that I press.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment