-
Notifications
You must be signed in to change notification settings - Fork 276
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
changed order of device class setting #21
Conversation
My class still does not change with this patch |
@JuanPotato Can you open bluetoothctl, run the joycontrol script and send me the output of bluetoothctl? |
Oh I've just noticed something, I had bluetoothctl open when I had the switch connect successfully. In both master and this branch, the class is not reflected as changed when I run hciconfig to check it. In both branches, no connection is made regardless if I change the class manually, until I open bluetoothctl. This is really weird. bluetoothctl
joycontrol when I have bluetoothctl running
joycontrol when I dont have bluetoothctl running
This may be an issue just because of the way I have things set up on my laptop. I don't use bluetooth that much and am running i3 as my window manager. I'll check if this works while I'm running in gnome. |
Same issue happens in gnome, switch refuses to recognize me until I open bluetoothctl or gnome bluetooth settings. If I run joycontrol without bluetoothctl, wait, and then open bluetoothctl, it connects and this is blueoothctl's output
which makes me think joycontrol isn't making the device pairable? |
This is indeed strange... I don't see why it would make a difference to have bluetoothctl running. I think I have to check back at a later date. It's getting pretty late here. Sorry I couldn't be of any help as of now. |
Since you paired initially paired with the Switch you can use the reconnect option. Maybe you can at least avoid the issue this way for now. |
Check out my patch, I'm not sure if disabling Pairable is needed but it works for me. |
Pull request to fix #20
Registering the Bluetooth SDP record seems to cause the device class to be reset to 0x000c010c.
Should further investigate why that happens...
Hotfix: Changed the order of setting the device class to after registering the SDP record.