bluez VS steam-devices

See for yourself, it's public - https://github.com/bluez/bluez/graphs/contributors. Top contributions are from Johan Hedberg, Marcel Holtmann, and Luiz Augusto von Dentz if we're dropping names, or from Intel if we're speaking about corporations.

5.68 with the fix is out: https://github.com/bluez/bluez/releases/tag/5.68

These are some links I checked and followed: https://github.com/bluez/bluez/blob/master/test/simple-agent https://scribles.net/creating-ble-gatt-server-uart-service-on-raspberry-pi/

For more information, see https://github.com/bluez/bluez/issues/157 ```

The only issue I have is that I can't use LDAC with my bluetooth headphones (Sony WF-1000XM4). This is probably related to bluez: https://github.com/bluez/bluez/issues/313 It's fixed in bluez 5.65 which is not available in the repositories (yet). The current repository version of bluez is 5.64.

I am sorry but this is still not clear enough. I will assume that you are using a Linux based system e.g a raspberry pi and a Xbox one series x/s controller (the one with the share button). If this is the case, I have bad news for you: they still didn’t fix the problem with the Bluetooth ble inside the Bluetooth stack implementation on most Linuxes OS (Debian, Ubuntu or anything that uses BLUEZ). If the controller is not the latest BLE version, it is only a matter of updating it to a newer kernel (5.13 or higher) and the latest blues version, as there was also another problem that was solved for the older controllers. If you are in the first case where they didn’t fixed it yet. You can report it on GitHub or just follow this issue https://github.com/bluez/bluez/issues/155 to check if something new comes up, there is also the possibility to use a Bluetooth dongle and somehow “transplant” the pairing keys from a windows computer to Linux so that the controller leaves this “connection loop”. Check that GitHub issue or this https://github.com/atar-axis/xpadneo/issues/198

if you mean this ( https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules ) in /etc/udev/rules.d , yes i did

Create an udev rule for the device, you can copy the rule for your device from here.

I am attempting to play Spelunky with a controller but I am not having any luck. Spelunky has a platinum rating on protondb and runs as expected. I am in a flatpak and I did install the udev rules from valve if any of that makes a difference. My controller works fine in native games.

I solved the problem by copying the 60-steam-input.rules file to the folder: /etc/udev/rules.d

this is their Github: https://github.com/ValveSoftware/steam-devices

steam maintains udev rules for controllers that might help: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules

Here is my open PR for the hori alpha for reference: https://github.com/ValveSoftware/steam-devices/pull/42/files

To use a controller with the Steam flatpak, you need to layer the steam-devices package from RPM Fusion, or download the udev rules from upstream and install them to /etc/udev/rules.d/ (which is what I did).

> The effort you need to go through to actually use these depends on how your distribution handles the file permissions of /dev/uinput. Some of them have it as root:input, in which case you just need to usermod -a -G input and then relog to get it working. Others have it as root:root so you either need to go do some reconfigurations to change its permissions or live with running the software using it as root.

There's a trick to that. The TL;DR is "install the steam-devices package or similar" (https://github.com/ValveSoftware/steam-devices/), which adds the following udev rule (and others, but this is the relevant one):

  # Steam Controller udev write access