Closed AccaliaDeElementia closed 4 weeks ago
From your description, it first sounds like a udev issue. But looking at the logs, this is more likely an issue with bluez. This was most likely fixed in the later firmware versions but your version is up to date. So probably something isn't handled properly for your Bluetooth chipset in bluez.
Please check the troubleshooting for bluez and adjust some settings, to see if it helps: https://github.com/atar-axis/xpadneo/blob/master/docs/TROUBLESHOOTING.md (do not use the ERTM work-around on modern kernels).
Also, lately I've discovered that my original Xbox XB1S controller doesn't automatically reconnect. Press and hold 1 second on the connect button fixes that and it connects.
Hmm....
looks like on arch, or with recent enough versions of bluez the JustWorksRepairing setting is required to properly load xpadneo after a reboot.
after... i honestly lost track of how many reboots it took, but here's the bluetooth config that appears to reliably work, at least with my bluetooth controller:
█▓▒░accalia@Alexis░▒▓██▓▒░ Thu Jun 06 11:18:08
~/ grep -e '^[^#]' /etc/bluetooth/main.conf
[General]
JustWorksRepairing = always
[BR]
[LE]
[GATT]
[CSIS]
[AVDTP]
[Policy]
[AdvMon]
█▓▒░accalia@Alexis░▒▓██▓▒░ Thu Jun 06 11:18:24
~/
Pairing an Xbox Elite (1) controller or an Xbox Series X controller via the KDE control panel with xpadneo install works flawlessly.... until i reboot my system. After reboot the controller will connect via bluetooth, but xpadneo does not pick either model of controller up.
Version of xpadneo
0.9.6 - via AUR package xpadneo-dkms
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
Pairing an Xbox Elite (1) controller or an Xbox Series X controller via the KDE control panel with xpadneo install works flawlessly.... until i reboot my system. After reboot the controller will connect via bluetooth, but xpadneo does not pick either model of controller up.
Forgetting the controller and re-pairing will cause the controller to be picked up again and work flawlessly, until the next reboot.
Steps to Reproduce
Pair controller using KDE system config, observe that the controller works flawlessly, including power cycling the controller and reconnecting.
Reboot the host machine, observe that while the controller will automatically connect, it is not detected as a joystick and xpadneo is not attaching to the device. No lines appear in dmesg when connecting.
Forget the controller in the KDE control panel and re-pair, observe that it is connected successfully and dmesg shows xpadneo grabbing the device
Expected Behavior
Connecting the controller after reboot works.
I'm not sure if this is a bluez issue or an xpadneo issue, but i cannot seem to figure it out, and attempting the various fixes suggested when googling or reading the docs/issues result in either breaking the bluetooth pairing process entirely or no change in behavior.
Screenshots / GIFs / Videos
System Information
Without xpadneo detecting the controller
With xpadneo detecting the controller after fresh pairing
Controller and Bluetooth Information
xpadneo-reconnect-btmon.txt and xpadneo-reconnect-dmesg.txt are after a fresh boot and connecting the controller and resulted in no detected controller
xpadneo-new-pairing-btmon.txt and xpadneo-new-pairing-dmesg.txt are after forgetting the controller and initiating a pair and resulted in a detected and working controller
xpadneo-lsusb.txt xpadneo-reconnect-btmon.txt xpadneo-reconnect-dmesg.txt xpadneo-new-pairing-btmon.txt xpadneo-new-pairing-dmesg.txt
Additional Context