New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth devices (Xbox One S controller) not pairing correctly via SteamOS bluetooth settings #6756
Comments
I just encountered this bug with the Xbox One Controller. It basically renders the bluetooth ui useless and forces manually pairing the controllers. |
Confirmed on Manjaro with steam build from Jun. 4 2020 |
I have the same problem with Switch Pro controller. It connects to the controller but I cant move around in the steam UI. Can you update gameros to automatically trust all bluetooth connections? |
Same for DS4 controllers. |
I finally found a fix, you just need to set I suppose this is outside the scope of Steam, so I am closing this issue. |
Took you long enough
Regards,
Leo
253-213-8585
… On May 7, 2021, at 3:16 PM, alkazar ***@***.***> wrote:
I finally found a fix, you just need to set AlwaysPairable = true in /etc/bluetooth/main.conf under the [General] section.
I suppose this is outside the scope of Steam, so I am closing this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Your system information
Steps for reproducing this issue:
echo 1 > /sys/module/bluetooth/parameters/disable_ertm
to allow pairing of Xbox One S controller-steamos -tenfoot
options to enable Bluetooth settings in Big Picture modeExpected result:
the controller should connect and be usable
Actual result:
the controller does not connect and acts as if it is unpaired; trying to pair it again in the bluetooth configuration screen is unsuccessful. I have to run the
remove
command inbluetoothctl
before I can re-pair the device from the Steam big picture UI.Additional notes:
bluetoothctl
from the command line and following the connection instructions here (without actually installing the xpad neo driver): https://atar-axis.github.io/xpadneo/#connectiontrust
step. I tested this idea by again following thebluetoothctl
instructions linked above, but skipping thetrust
command. This resulted in the same failure as the Steam big picture configuration page. Therefore it is very likely the case that the Steam big picture bluetooth configuration page is not doing a crucial step to allow bluetooth devices to be trusted. As a result, devices are not able to reconnect after being disconnected and users must drop to the command line and usebluetoothctl
to be able to re-connect the devices again.The text was updated successfully, but these errors were encountered: