-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
MacOS Ventura 13.2.1 BLE connection issues #473
Comments
Have you ensured the second profile is cleared? Sometimes there is residual pairing data in the second profile and a clear is required, even if it shows as open. On the default windows keymap it's mod+win |
@ReFil I had never used any of the other profiles, but since you mentioned it, here's what I did:
|
If it's successfully pairing on other devices then it seems like there's something up with your mac, what model is it? |
@ReFil It's a custom-built intel-based PC running MacOS Ventura. I've been using this computer for 5+ years without Bluetooth issues. I'm currently paired with a Logitech MX Master mouse and ad-hoc usage of Sony headphones, also over Bluetooth... It seems this could be some corner case incompatibility between the controller/firmware on the keyboard and the controller/firmware on my BT adapter. Hence why I came to Github... |
What bluetooth adapter are you using? There was a known bug with intel AX2xx adapters but that's been addressed. Is your mouse the original MX master or one of the newer versions, The 3 uses BLE but i'm not sure about the older versions |
@ReFil I'm using BCM_20703A1: |
I'm sorry! I missed some of your questions. |
Hello!
Let me start by stating that I've been using the latest firmware without any major issues with my M2 MacBook Pro running Sonoma.
Now the issue I'm trying to solve is connecting that same keyboard to my desktop Mac, running Ventura (13.2.1): It won't connect.
I switched the bt profile on the keyboard to 2 (blue LED), and they keyboard was discovered as expected.
When trying to connect, the spinner goes on for quite a while, and then stops. The "connect" button changes label to "disconnect", but the keyboard is still showing on the "found devices" list, and never moved the the list of "paired devices"
Trying to debug this I little further, I've collected some debug logs for the bluetooth subsystem:
This command is grep'ed for readability. The log is available on this pastebin
Any help is appreciated.
The text was updated successfully, but these errors were encountered: