Corsair K70 (non RGB) and sleep mode

[tdp...@gmail.com]

I am sorry if this has been solved before, but I have been suffering an issue that I explain below for a long time and I have not been able to found the solution yet...

I am very grateful to the ckb-next project, and I have been using it (ckb and later ckb-next) since long time. It was working like a charm until for quite some time I have the following problem:

Normally I have the option and menu exchanged in the ckb profile to have the natural order as in an original mac (ctrl-opt-cmd).

This works perfectly but when I suspend my mac, and return the next day, when I wake up the mac from sleep mode, the keys suddenly return to the original state (alt is cmd and windows is option) and the only way I have to solve it is a script that I made to stop and reload the driver:

      #!/ bin / sh

      sudo launchctl unload -w /Library/LaunchDaemons/org.ckb-next.daemon.plist

      sudo launchctl load -w /Library/LaunchDaemons/org.ckb-next.daemon.plist

It's a bit annoying to have to do it every time I get back from sleep mode. Does anyone know why this happens and what is the solution?

FYI: I am currently using Mojave 10.14.4 (but it did not work on any version of Mojave and if I remember correctly, in the previous version of OSX either), apart from always using the latest version of git and I compile myself to check if it was solved.

Thanks in advance!

       

        Tomas

[Tasos Sahanidis]

Hello!

Try rebooting your mac first to start with a clean state.
Then, once it goes to sleep and this issue occurs, open up the user interface, and on the settings tab click the "generate report" button.

Once the report is generated, you can then restart the daemon to get your keyboard back and attach the report here. It will most likely tell us why this issue happens and we can try to fix it.

--
Tasos

--
You received this message because you are subscribed to the Google Groups "ckb-next" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ckb-next+u...@googlegroups.com.
To post to this group, send email to ckb-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tdp...@gmail.com]

Hello Tasos!

Thank you very much for your answer.

Attached you can find the generated report, i hope it will be useful.

[Tasos Sahanidis]

That's odd. There are no errors in the log.

Can you test if restarting the UI (Go to settings, click the Quit button on the bottom right and then run it again.), without running any of the launchctl commands, also fixes the issue after resuming from sleep?

[tdp...@gmail.com]

I think i've tried that before but I have ended to launchctl because is the only way that I've found that works for me.

Now to be sure, I tried it again what you say (restart ckb-next ui) and it doesn't work.  Coming back from sleep I have command in windows key, despite if I go to the GUI after I restarted it, shows the correct/expected layout.

Thank you!

El sábado, 20 de abril de 2019, 18:24:46 (UTC+2), Tasos Sahanidis escribió:

That's odd. There are no errors in the log.

Can you test if restarting the UI (Go to settings, click the Quit button on the bottom right and then run it again.), without running any of the launchctl commands, also fixes the issue after resuming from sleep?

On 20/04/2019 12.27, tdp...@gmail.com wrote:

Hello Tasos!

Thank you very much for your answer.

Attached you can find the generated report, i hope it will be useful.

El viernes, 19 de abril de 2019, 17:22:19 (UTC+2), Tasos Sahanidis escribió:

Hello!

Try rebooting your mac first to start with a clean state.
Then, once it goes to sleep and this issue occurs, open up the user interface, and on the settings tab click the "generate report" button.

Once the report is generated, you can then restart the daemon to get your keyboard back and attach the report here. It will most likely tell us why this issue happens and we can try to fix it.

--
Tasos

--
You received this message because you are subscribed to the Google Groups "ckb-next" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ckb-...@googlegroups.com.

[Tasos Sahanidis]

If you map any other functions to other keys, for example binding f1 to a macro, does that work after resuming?
I get the feeling the keyboard disconnects and reconnects during sleep, but the daemon isn't aware of it, because it doesn't send any data.

To unsubscribe from this group and stop receiving emails from it, send an email to ckb-next+u...@googlegroups.com.

[tdp...@gmail.com]

Tasos,

I assigned "Volume Down" to F12 to test, before sleep it works right as expected.  I put mac in sleep, after wake up, F12 does not work as Volume Down, like cmd-opt. (Also after wake, I tried again restarting the GUI but with no luck, as we know)

About the point you mention that the keyboard is disconnected and connects, keep in mind that the keyboard is turned off when entering sleep (the LEDs are off), and is turned on when the Mac awakens again. 

But this has always happened and it worked for me before. Some time ago I tried with old versions of ckb and ckb-next in case it was some modern change in code, I do not remember well my conclusions now, but I think that none of them worked for me (since in that case I would have keep using an old version). 

I think that maybe something of the behavior about the keyboard/usb changed in the latest revisions of OSX, but is strange that nobody noticed this, so maybe that only happens to me?

Thank you very much for your time&support!

[Tasos Sahanidis]

Could you please, after resuming from sleep, unplug and replug your keyboard, and then generate another report from the gui? ( only run the launchctl commands after generating the report.)

Then attach it here again please.

Thank you

[tdp...@gmail.com]

Tasos,

I've done exactly what you said. Attached you have the report.  Also I've tested after reconnecting the keyboard without running launchctl, and here is the behaviour I've observed if it helps to you:

Seems that unplugging keyboard and plugging it again seems that option/command keys now are as I configured in the options in ckb-next, but not working 100% because after plugging in the keyboard acts a bit weird, as if a key was pressed, like control or shift etc...

I'll try to explain you as best I can.  If I click some icon in Desktop, gets selected and I can select other icons. Also I've tried to click on Terminal icon on Dock to run my script to restore the behaviour, and if I click the icon, instead of showing me the window, a Finder window appears with Applications folder....

But I can type in Spotlight (I can show up the bar with cmd-space), and all letters appers in lowercase. Very strange :(

Thanks!

   Tomas