You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last week ago ckb still worked flawless on OS X (for the first time for me even!). I believe after the new Firmware came out (2.04) it's bugged though.
Let's say I (force-)kill the ckb-daemon service... It doesn't matter whether ckb itself is running or not: Key presses only work for the first couple seconds! I noticed that the keyboard stops responding as soon as ckb shows the detected keyboard (using the graphical representation).
If however I switch the polling rate on the keyboard's back side right after the ckb-daemon starts up it works completely again without breaking. Interestingly the ckb app show's the keyboard as undetected then.
Tell me if you need to know any specs from my PC, the keyboard, or if you need to run any tests. 😊
The text was updated successfully, but these errors were encountered:
Last week ago ckb still worked flawless on OS X (for the first time for me even!). I believe after the new Firmware came out (2.04) it's bugged though.
Let's say I (force-)kill the ckb-daemon service... It doesn't matter whether ckb itself is running or not: Key presses only work for the first couple seconds! I noticed that the keyboard stops responding as soon as ckb shows the detected keyboard (using the graphical representation).
If however I switch the polling rate on the keyboard's back side right after the ckb-daemon starts up it works completely again without breaking. Interestingly the ckb app show's the keyboard as undetected then.
Tell me if you need to know any specs from my PC, the keyboard, or if you need to run any tests. 😊
The text was updated successfully, but these errors were encountered: