Xbox Controller Won’t Autoconnect
Hey all, been having this issue with my Xbox controller since I installed bazzite about 3 weeks ago
Basically it won’t connect unless I use a keyboard and go into the Bluetooth tab in settings
It works great otherwise just can’t get it to connect without having to do this
I’ve attached a video to show you what I mean
Hoping someone can help cheers
Edit: I have updated my Xbox and Xbox accessories app and then updated both my Xbox controllers and am still getting this issue, when I was on chimera os they connected fine straight away so must be bazzite related
6 Replies
This might or might not work, I'm not running Bazzite game mode, so I cannot test this properly.
Switch to a terminal session CTRL+ALT+F2
Run
bluetoothctl paired-devices to get the mac address of your Xbox controller
Now run bluetoothctl trust 48:87:59:83:28:D2 where you replace the example mac address with the one that was returned for you. This should allow auto pairing with the device without manual intervention.
Now press CTRL+ALT+F1 to jump back into game mode. If it opens another session, try CTRL+ALT+F3, CTRL+ALT+F4 etcThanks for you response, just tried setting it to trusted still no luck.
it wont pair unless i go into the bluetooth tab or i run "bluetoothctl" and then "scan on"
This is my bluetoothctl info:
Device F4:6A:D7:60:DC:B8 (public)
Name: Xbox Wireless Controller
Alias: Xbox Wireless Controller
Appearance: 0x03c4 (964)
Icon: input-gaming
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific (00000001-5f60-4c4f-9c83-a7953298d40d)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
Modalias: usb:v045Ep0B13d0520
Battery Percentage: 0x64 (100)
if you run
bluetoothctl scan on in one command in a background tty session does it carry on working?
I'm guessing that chimera is set to always listen for bluetooth connections from startup.just ssh'd in on a fresh boot up and ran "bluetoothctl scan on" and it doesnt connect, i need to run "bluetoothctl" first and then "scan on" for it connect the controller
I should mentioned my ps5 controller doesnt have this issue its just my xbox controller
I just disabled my motherboard Bluetooth and found a Bluetooth dongle and it works!
Not sure what would be causing the motherboard Bluetooth to not auto connect
Probably some random kernal driver issue
had the same exact problem and in the end, i disabled bt on the motherboard (onboard intel one) used a usb dongle and works flawless. try that