spams connect/disconnect when connecting via bluetooth.

[jgilmore]

Version of xpadneo

cgilmore@Marnie:~/xpadneo$ git status On branch master Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

as of filing this bug report. Where does it show the version number?

Controller Model

Unknown

Connection mode

• [ ] Bluetooth connection

Installed Software

• [ ] Steam Input (enabled by default via Steam Desktop client)

Protocol Information

Bluetooth

Please describe how it is failing below in the next sections.

Severity / Impact

• [????where docs???? ] I've read the docs and the bug reporting instructions
• [NO ] I've applied the latest firmware update to the controller
• [ NO] I've tried disabling or running without above mentioned software
• [ YES] It does not work at all
• [NO ] It used to work in a previous version
• [ NO] It mostly works but sometimes it doesn't
• [ NO] I found a work-around

Describe the Bug

Pairing, trusting, and connecting from the command line succeeds, but it then immediately disconnects.

If I connect using the "blueman applet" it connects, and then starts spamming connect/disconnect notifications. This continues until the controller's "flash quickly" mode times out.

Controller never rumbles, and remains at "flashes quickly" until it would have timed out anyway (as far as I can tell.)

System Information

Linux Marnie 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

# xxd -c20 -g1 /sys/module/hid_xpadneo/drivers/hid:xpadneo/0005:045E:*/report_descriptor | tee >(cksum)
Does not exist

Controller and Bluetooth Information

Additional Context

lsusb output is from when connected via USB. xpadneo-btmon.txt xpadneo-dmesg.txt xpadneo-lsusb.txt

[kakra]

= Index Info: 80:00:0B:44:04:57 (Intel Corp.) [hci0] 0.064844

This Bluetooth chipset is known to not work at all with the older Xbox controller firmwares, and with the newer firmware it still shows instabilities.

See https://github.com/atar-axis/xpadneo/blob/master/docs/BT_DONGLES.md and https://github.com/atar-axis/xpadneo/blob/master/docs/TROUBLESHOOTING.md

[guoyunhe]

I have similar issue with Bluetooth. But I found it only happens with Steam games, with or without xpadneo. So I think it is probably not a bug of xpadneo, but something wrong with Steam.

[guoyunhe]

Found a confirmed issue with Steam/Proton that can cause controller disconnect https://github.com/ValveSoftware/Proton/issues/7952

[kakra]

There are several situations which can cause such issues:

• buggy controller firmware (dmesg will log if a known buggy version is detected, upgrade your controller firmware, this information only works reliable for genuine Microsoft controllers)
• incompatible Bluetooth chipset or buggy chipset firmware (try downgrading the chipset firmware package if it worked previously, otherwise get a supported chipset, there's a list in the docs folder)
• incompatible bluez settings or old bluez version (upgrade bluez, check our troublshooting docs)
• incompatible device flags as artifacts in the bluez device database (stop bluez, remove the device MAC from /var/lib/bluetooth/HOST-MAC/DEVICE-MAC, then reboot, pair the controller again)
• too busy air time of the bluetooth connection (we found that kdeconnect and derivatives can cause a lot of BT discovery spamming and destabilize the connection, it's probably still the controller firmware not handling this correctly but stopping kdeconnect can help, turning off other bluetooth devices, e.g. some TVs may also fix this)
• too fast sending of rumble commands causes a crash/race condition in the Xbox controller firmware (the controller supports up to 100 hz of HID commands but we found that rumble should stay below 50 hz or even 20 hz, this is an issue partially with how ff-memless works, partially with games using hidraw, SDL ships with a protection when using hidraw, xpadneo ships with a protection when using ff-memless, future xpadneo version will bypass ff-memless)

Please also check our troubleshooting docs in additional to all issues collected under https://github.com/users/atar-axis/projects/2. Unfortunately, Github migrated all the issues to the wrong categories but it is still helpful.