New bluez version breaks PS3 controller pairing

[saccublenda]

Hello, I've noticed that the new bluez version 5.50-1.2~deb10u4 breaks the pairing of PS3 controller (other bluetooth controllers pair fine).
After updating bluez to the new version I tried pairing the PS3 controller in the RetroPie bluetooth menu using the standard procedure:

1. turn off the controller
2. connect the controller with a usb cable
3. select Pair and Connect to Bluetooth Device
4. unplug the controller, press the PS button and then reconnect
5. select the PS3 controller to pair
6. unplug the usb cable upon prompt

After doing this the leds on the controller keep flashing and the controller is not paired.
By downgrading bluez to 5.50-1.2~deb10u3+rpt1 version, the above procedure successfully pairs the controller.

Pi Model or other hardware: pi4 4gb
Power Supply used: USB3.0
RetroPie Version Used: 4.8.6
Built From: https://github.com/RetroPie/RetroPie-Setup/releases/download/4.8/retropie-buster-4.8-rpi4_400.img.gz
USB Devices connected: bluetooth dongle
Controller used: 8bitdo sfc30 (bluetooth), PS3 controller DualShock 3 (bluetooth)

[mitu]

Do other gamepads pairing works ? Is the bluetooth service started when attempting the pairing ?

[saccublenda]

@mitu said in New bluez version breaks PS3 controller pairing:

Do other gamepads pairing works ?

Yes.

Is the bluetooth service started when attempting the pairing ?

Didn't check, I assumed it did since pairing works for other controllers.

[lsdninja]

Had the same problem and downgrading bluez fixed it here too.

[BuZz]

For anyone else running into this issue - to downgrade the package:

sudo apt-get install bluez=5.50-1.2~deb10u3+rpt1

and to hold the package to stop it updating in the future

echo "bluez hold" | sudo dpkg --set-selections

[mitu]

We've added a configuration pin for the bluez packages so that only the RPI originated packages are installed, this way any possible Debian/upstream updates will not overwrite the package.
The pinning is active only for the RaspiOS Buster release and can also install/downgrade the right package even if it was upgraded to the 'broken' version originating from the Debian repository.

[saccublenda]

@mitu Will this work only when updating packages through retropie_setup.sh or also when using apt?

[mitu]

@saccublenda said in New bluez version breaks PS3 controller pairing:

@mitu Will this work only when updating packages through retropie_setup.sh or also when using apt?

Both. RetroPie-Setup uses apt-get to update, so any configuration applied to apt/apt-get (i.e. pinning) is automatically taken into account.

[Pakoach]

Hello,
I had the same issue and found another work around rather than reverting to the previous version.

The topic is discussed here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931

It seems that this is intentional will not be changed in future versions.
As mentionned right at the beginning of that post the workaround is the following:

1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
2. Run: systemctl restart bluetooth # or reboot

It worked for me.
Maybe its worth digging a little bit more to know what is the more suitable way of handling this new way of working of BlueZ...