-
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
Bluetooth class isn't changed properly #20
Comments
Interesting... It seems like the device class is reset when registering the SDP record. The Switch still connects fine for me though. I created a pull request where I set the device class after registering the SDP record. Please check if that works for you. |
I don't think this is needed since it was working in the end after enabling pairing |
@JuanPotato Sorry I think I might have a similar problem: sudo python3 ./run_controller_cli.py PRO_CONTROLLER Is this due to the same issue? How do I change the bluetooth class while it was running? Thanks! |
@Ruoruo-0v0 I had the same issue and think I just got it working. I used |
Changing the default class to 0x002508 in /etc/bluetooth/main.conf seems to be necessary to connect after the 12.0.0 update |
How do you do that exactly |
I'm also affected by this problem where joycontrol does not seem to set the |
@l0nkDev I think it's the Class setting in that file. |
At first joycontrol wouldnt work on my laptop (running an xps 13 9370) so I tried to figure out what was wrong. My phone showed a "pro controller" but with a laptop icon so I checked the class with hciconfig and it was set to
0x0c010c
for Laptop. I changed it to0x002508
for Gamepad, ran joycontrol, but joycontrol seemed to revert it back to Laptop. I ran joycontrol and changed the class while it was running which worked. The switch connected and I was able to send inputs.The text was updated successfully, but these errors were encountered: