[x] Steam Input (enabled by default via Steam Desktop client)
[ ] Steam Link (usually via Raspberry Pi or other micro computers)
[ ] xow (alternative driver using the Xbox dongle)
[ ] Anti-Micro (may affect button mappings)
[ ] netstick (shares input devices via network similar to Steam Link)
[ ] xboxdrv (user-space gamepad driver)
Severity / Impact
[x] I've read the docs and the bug reporting instructions
[x] I've applied the latest firmware update to the controller
[ ] It does not work at all
[ ] It used to work in a previous version
[ ] It mostly works but sometimes it doesn't
[ ] I found a work-around
[ ] I probably didn't figure it all out but it's too early to give up
[ ] I don't know how to ...
[ ] It's too complicated
[ ] Fantastic work but ...
[x] I can code and I want to help
Describe the Bug
The controller can be paired properly (it rumbles and X logo stays lit, input works in steam and when testing with evtest), but after turning it off and on again it doesn't connect anymore. I have to remove the device from paired devices and pair it again. It reconnects properly on Winndows on the same PC (with the same bluetooth controller).
Steps to Reproduce
Pair your controller
Turn off the controller
Turn it back on
Controller doesn't reconnect to the PC. Trying to manually connect it using bluetoothctl or KDE bluetooth applet doesn't work either.
Expected Behavior
Controller should automatically connect back to the PC when turned on. At least it should allow to connect manually without pairing it again.
Screenshots / GIFs / Videos
Not applicable
System Information
# uname -a
Linux <redacted> 5.13.0-30-generic #33-Ubuntu SMP Fri Feb 4 17:03:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I've tried various tweaks mentioned in different threads, like:
Enabling FastConnectable
Setting JustWorksRepairing to always
Setting Privacy to device
Disabling ERTM
Copying pairing keys from Windows
In all possible combinations. At first I wasn't able to pair my controller at all, but it started working after pairing it at least once on Windows (through bluetooth. Pairing via dongle or connecting through the USB cable didn't work, there was no firmware updates either).
I've resolved the issue recently by completely removing IdentityResolvingKey section (together with data inside this section) from /var/lib/bluetooth/adapter_mac/device_mac/info file. This issue and workaround for it is described on Arch wiki.
Version of xpadneo
v0.9-93-gcf392a7
Controller Model
Connection mode
Installed Software
Severity / Impact
Describe the Bug
The controller can be paired properly (it rumbles and X logo stays lit, input works in steam and when testing with evtest), but after turning it off and on again it doesn't connect anymore. I have to remove the device from paired devices and pair it again. It reconnects properly on Winndows on the same PC (with the same bluetooth controller).
Steps to Reproduce
Expected Behavior
Controller should automatically connect back to the PC when turned on. At least it should allow to connect manually without pairing it again.
Screenshots / GIFs / Videos
Not applicable
System Information
Controller and Bluetooth Information
xpadneo-btmon.txt (pairing process, as simple reconnect doesn't work)
xpadneo-dmesg.txt
8087:0029 Intel Corp. AX200 Bluetooth
xpadneo-lsusb.txt
Additional Context
I've tried various tweaks mentioned in different threads, like:
FastConnectable
JustWorksRepairing
toalways
Privacy
todevice
In all possible combinations. At first I wasn't able to pair my controller at all, but it started working after pairing it at least once on Windows (through bluetooth. Pairing via dongle or connecting through the USB cable didn't work, there was no firmware updates either).