Welcome to the Garuda forum @druaga .
Just FYI, Windows often creates problems with Bluetooth/Linux when dual booting.
You are making things far more complicated for yourself if you dual boot with Windows. You will need to perform the following steps if you dual boot:
the default “shutdown” state of Windows is actually not fully powered off. Windows enables a “fast startup” mode, which holds on to certain resources in an effort to shave a few seconds off of the boot time. You will have to disable this feature from Windows itself to make sure Windows is completely “off” when you shut it down.
As well, you should boot into Windows and go to the advanced properties for your WiFi & Bluetooth adapters in the Windows device manager. Be sure to disable any settings for your network adapters that involve power saving.
It is also possible that MAC randomization is causing connectivity problems. Search for the terms “disable MAC Address randomization” on the forum. Disable MAC Address randomization then reboot both your computer and router.
Be sure to try refreshing the Bluetooth pairing keys in Linux & Windows.
See section 2.1of the Arch Wiki on BT, Dual boot pairing:
Bluetooth - ArchWiki
Also see:
GitHub - x2es/bt-dualboot: Sync Bluetooth for dualboot Linux and Windows
There is a lot of helpful information regarding Bluetooth connectivity on the Arch wiki:
https://wiki.archlinux.org/title/Gamepad#top-page
https://wiki.archlinux.org/title/Bluetooth
https://wiki.archlinux.org/index.php/Bluetooth#Troubleshooting
https://wiki.archlinux.org/title/Bluetooth#Discoverable_on_startup
Some other links that may be informative:
Maybe you could try removing the controller from paired devices in windows, should this be a dual boot issue…
Alright, it’s been resolved! The solution was to install bluez-git, delete /var/lib/bluetooth and, most importantly drain the power from my PC. I tried the first two steps a while back, which was detailed in a different thread. I never drained the power because most people said that their issue was resolved after the first two steps, so I figured there was no need. But I found one other person who, like me, was only able to finalize those changes after draining the power. I’m not entirely sure …
FYI, I only have to use xboxdrv. I have noticed sometimes that the driver stops working. Usually, restarting the xboxdrv service helps:
sudo systemctl stop xboxdrv.service
sudo systemctl start xboxdrv.service
I’ve also found that having both xboxdrv and xbox-generic-controller enabled causes conflicts for me.
Another possible solution is setting up the /etc/default/xboxdrv file with these settings:
[xboxdrv]
silent = true
device-name = "XBox 360 Wireless Receiver"
mimic-xpad = true
deadzone = 4000
[xboxdrv-daemon]
dbus = disabled
This works for both wired and wireless XBox360 controllers. You can use whatever string you want in device-name. I just use a wireless XBox360 controller.
Hi…there is anything but a particular connector for the Series X/S regulators for PC. The current connector turns out only great with these fresher regulators, but it is presently in extremely short stockpile. There are outsider ones accessible that do exactly the same thing.
The Xbox 360 remote regulators utilize an alternate WIFI convention, they need their own Xbox 360 remote Gaming Receiver.
Xbox One and Series X/S regulators can be associated with PC through Bluetooth, however headsets will just work with the Xbox One connector (or an outsider form), they will not work when the regulator is associated by means of BT
Bluetooth is a minefield of issues, especially when dual booting Windows. Good luck finding a resolution to your BT problems, and again welcome to the Garuda community.
2 Likes