-
Notifications
You must be signed in to change notification settings - Fork 322
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
no stroke recognition / flashing problem? #15
Comments
It sounds like it isn't paired correctly. If you had it paired before and your previous build didn't have mouse-keys enabled, then you will need to re-set the pairing: 1. Forget bluetooth device on windows, 2. clear bluetooth connection on the 360, 3. re-pair (This is necessary the first time you are enabling mouse keys, because the OS needs to change the driver from keyboard to keyboard + mouse) |
unfortunately, still not working. maybe for some reason, my OS doesnt get to do |
I just realised: it works when plugged in! it's a bluetooth thing. |
Another thing you could try if you haven't gotten Bluetooth to work yet: https://zmk.dev/blog/2023/04/06/zephyr-3-2#known-issues Afaik the official Kinesis firmware is still running on zephyr 3.0. That's why this steps may gut be necessary |
Oh! you just made me realise: when trying to BT_CLR I pressed the default 360-macro being So when thinking of reset, I actually did not. ... Edit: |
I have leds disabled in my main branch. For the layout see the image in the readme. |
What exactly do you mean by that? |
I think I successfully flashed the firmware, or so I thought.
My keyboard is being recognised but upon typing I don't see any output, alas. I'm wondering what could have gone wrong here
The text was updated successfully, but these errors were encountered: