@classicgmr
AFAIK RPi 3B+ has new BT chipset with flow control where RPi 3B doesn't.
This feature limits the BT errors that generate random events.
cf https://github.com/raspberrypi/linux/issues/2264

So it's possible that the problem is not with your DS3.
You could try to connect your white DS3 to the RPI 3B (not +) to verify this.

@mitu perfect, thank you for the reply. I will check out the link and see what I can figure out. The audio devices don't need pins.

Thank you

Update

For anyone else trying this, I tried many different combinations of drivers and commands/scenarios. Including cycling through all the pairing modes. The best I seemed to get it was by pairing it into "Android B" mode, and from emulation station I was able to get it to recognize as a keyboard, but it only recognized a single button. Strange.

Hello and thanks for reply.
Yes, it's Bluetooth.

I've tried to pair it via Bluetooth pairing procedure.
It's recognized by Raspberry, but when I go to PAIR it, I got a Timeout error.

Same error I receive pairing controller with my Mac (I can pair ORIGINAL PS3 Wireless controller).

I think I'll trash out the controller and use an Xbox 360 wireless controller.

@icvaalmall84 I can get the controller to connect via bluetooth, but once connected it doesnt map or work. any ideas?

@majere How are you checking the status ? A normal lsusb should list the USB adapter. If you run dmesg | tail immediately after plugging it in, you should see if it's detected, something like this should be printed:

[ 2.305588] usb 1-1.2: new full-speed USB device number 4 using dwc_otg [ 2.450005] usb 1-1.2: New USB device found, idVendor=0a12, idProduct=0001 [ 2.450023] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 2.450031] usb 1-1.2: Product: CSR8510 A10 ... [ 3.595425] Bluetooth: Core ver 2.22 [ 3.595760] NET: Registered protocol family 31 [ 3.595767] Bluetooth: HCI device and connection manager initialized [ 3.595794] Bluetooth: HCI socket layer initialized [ 3.595810] Bluetooth: L2CAP socket layer initialized [ 3.595851] Bluetooth: SCO socket layer initialized [ 3.657289] usbcore: registered new interface driver btusb

If this is the product you're using, it should work without problems.

@Impman66 how you set up your speedlink controller? I have SL-6566-BK xeox pro analog gamepad-wireless-black, retropie detected it but when i press&hold A to set up nothing happened.. please help

@wihaedud

I have this exact same issue. However the fix doesn't work for me. The bluetooth disconnects after 5 seconds as it should but then never connects back to the pie and wont until the pie is rebooted. Any ideas or anything I can check using ssh to ensure the bluetooth service has restarted?? I am a bit of Linux noob but can find my way around a putty window :)

@mitu - I've done some more digging. The GameStick doesn't seem to be recognized properly by the evdev system. Found some fun log messages via dmesg:

[ 15.328485] hid-generic 0005:0F0D:1011.0003: unknown main item tag 0x0 [ 15.328963] input: GameStick Controller as /devices/platform/soc/3f201000.uart/tty/ttyAMA0/hci0/hci0:11/0005:0F0D:1011.0003/input/input2 [ 15.330713] hid-generic 0005:0F0D:1011.0003: input.hidraw2: BLUETOOTH HID v7.07 Keyboard [GameStick Controller] on b8:27:eb:03:bd:7f

It appears that the "unknown main item tag" error (which, googling around, seems to be a bug), is causing the controller to be detected by evdev as a "Keyboard". Which, obviously, doesn't work so hot for controller stuff, since the various buttons don't seem to map to anything ES's controller setup recognizes as a button or axis.

I'm going to see if there's any kind of config option or something I can pass to allow this to work...

@lodan-zark have you tried the test image

https://retropie.org.uk/forum/topic/16307/retropie-4-3-11-stretch-images-for-testing

yes the controller was updated with win10 and ertm is disabled - the conroller works in emulation station perfectly - inclusive the "select" button and the "round x box one" button. But in the retroarch GUI it does not work any longer.

@meleu thanks so much for making this script! I would be screwed without it! This should be added to the Retropie main builds! It's so useful!

It's to bad that the original SNES30 / SFC30 have been discontinued.

Would love to see a Bluetooth version of the new SF30 2.4G / SN30 2.4G models or a new production run of the original models.

@mitu Cool, good to know multiplayer shouldn't be a hassle. I figured Dualshock 4 would work on Bluetooth as well but I only have two of those, and my wife ever so occasionally games with me. Seeing as I have three PS3 controllers and I haven't used the PS3 in ages, especially in co-op, I'd rather use two PS3 controllers than the PS4 ones, even if I do think that the PS4 controller feels better (not as good as the Switch Pro controller, but that's neither here nor there). So if Bluetooth works without a bad lag then I'll probably stick with the PS3 controllers simply because I already have enough of those lying around. If Bluetooth isn't good enough then I'll either get a Bluetooth dongle, or a wired Switch Hori Pad.

@dceric
Turn off your wifi and you will get Bt working fine with both controllers

Hi mitu,
I´m sorry. Yes they do work individually in Emulationstation outside of games and also inside. But only the first 4 controllers which I connect work simultaniously. The fifth won´t connect via bluetooth (lights are flashing constantly).

@chaska04
It works on w10 normally

I did a little edit. Seems to be an issue with the 8bitdo FC30 Arcade Stick in bluetooth mode - but not in USB mode.