DS3 SIXAXIS Not working via Bluetooth

Libretro Lakka
#1

Hello Everyone, Thanks for the great work on Lakka to allow us play our favourite retro games. I have installed both Lakka-Generic.x86_64-devel-20160921135800-r21588-gd33310f.img and Lakka-Generic.x86_64-devel-20161002103858-r21593-g03241bf.img in the past couple of days. The installation works fine and my DS3 Sixaxis controller works perfectly with a cable and is autoconfigured.

However, I CAN’T seem to get the DS3 controller to connect / pair / work via bluetooth. After enabling BT via the GUI, plugging the usb cable, unplugging and pressing the PS button without a successful BT connection, I tried ssh.

Following instructions from www.lakka.tv/doc/Wireless-Dualshock/ and https://wiki.gentoo.org/wiki/Sony_DualShock I go through the steps, to the point i’m supposed to get the Authorize (yes/no) prompt, and I DON’T get the authorize prompt. [ul] [li]plugged and unplugged the usb cable at different times while trying to connect / pair, no success[/li][li]Trusted the DS3 controller MAC, tried to pair and connect, no success[/li][li]Controller i’m 99% sure is a genuine one, dmesg, lsusb output seem to confirm this[/li][li]hciconfig shows up and running for the bluez controller[/li][li]systemctl status bluetooth shows up and running with an error / warning[/li][li]bluez.conf file appears to be empty in nano[/li][li]I DON’T own a playstation, bought this controller solely for PC use. It works fine via DS3 tool on my laptop (Been playing GTA :D) with the same dongle i have plugged into the micro pc for Lakka[/li][li]I have tried to pair (DS3 controller and BT dongle) from the laptop using DS3 Tool, BetterDS3 tool and then transfer to the lakka system, no success[/li][li]After days online, trying to solve this, appears plugging and unplugging is supposed to call sixpair/sixad or a fork of it? I’m not a linux wiz unfortunately. I am able to get the lakka pc online via wifi, tried to use apt to install sixpair manually and pair. But NO working apt-get on lakka[/li][li]Tried to compile sixpair from another source, no gcc on Lakka[/li][/ul] I am now stuck and would appreciate all the help I can get to have this controller work via BT dongle. Could the BT support have been broken in these more recent releases? is there a known release with the BT / DS3 / Sixpair /Sixad working that I can try?

Attaching some screen shots from the pairing attempts, dmesg, hciconfig, systemctl,bluez.conf

Thanks in advance!

hciconfig.jpg1368×329 45.3 KB

noauthprompt.jpg1366×765 66.3 KB

dmesg1.jpg1167×646 86.4 KB

dmesg2.jpg1075×601 90.8 KB

bluezconf.jpg1372×770 45 KB

#2

It seems you don’t have a genuine ps3 controller.

#3

Thanks for responding. I was starting to think along those lines as well. However, if its a clone, it appears to be quite a good one. Is there a way to know for certain if its a clone? The dmesg and lsusb outputs look quite similar to the genuine ones i’ve seen on Lakka forums. It would be good to tell for certain before I go out to get another controller and also to ensure I don’t get another clone. I’ve come across network device MAC addresses within ranges for specific manufacturers. Is there anything like that for Sony’s DS3 controller? Also, please remember that this particular controller plus dongle work both with cable and wireless on my laptop right now with no issues whatsoever. Thanks!

#4

[QUOTE=litaninja;50168]Thanks for responding. I was starting to think along those lines as well. However, if its a clone, it appears to be quite a good one. Is there a way to know for certain if its a clone? The dmesg and lsusb outputs look quite similar to the genuine ones i’ve seen on Lakka forums. It would be good to tell for certain before I go out to get another controller and also to ensure I don’t get another clone. I’ve come across network device MAC addresses within ranges for specific manufacturers. Is there anything like that for Sony’s DS3 controller? Also, please remember that this particular controller plus dongle work both with cable and wireless on my laptop right now with no issues whatsoever. Thanks![/QUOTE]

I have the same issues too. (See thread right here: http://libretro.com/forums/showthread.php?t=6440) And mine is definitely not a clone as it was part of my PS3 bundle.

My suspicion is that it’s an issue with the dongle - but I wasn’t able to work it out as of yet…

#5

Just to add a quicknote, I had to issue the command pair “ma.ca.dd.re.ss.” between “authorize service…” and connect “ma.ca.dd.re.ss”, or else my controller didn’t connect properly. Hope it helps,

#6

@litaninja : What is your bt dongle ? Can you try to give the output of lsusb (You need to access Lakka command line interface) ?

#7

Here is the output from lsusb

Lakka:~ # lsusbBus 001 Device 004: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 004: ID 054c:0268 Sony Corp. Batoh Device / PlayStation 3 Controller
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Part Output from dmesg

[ 6460.632885] input: SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:0268.0003/input/input16[ 6460.635306] sony 0003:054C:0268.0003: input,hiddev0,hidraw2: USB HID v1.11 Joystick [SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller] on usb-0000:00:1d.0-1/input0
[ 6460.641528] sony 0003:054C:0268.0003: can't set operational mode: step 3, ignoring
[ 6540.960145] usb 2-1: USB disconnect, device number 4
[ 7364.472070] usb 2-1: new full-speed USB device number 5 using uhci_hcd
[ 7364.636364] input: SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:0268.0004/input/input17
[ 7364.639264] sony 0003:054C:0268.0004: input,hiddev0,hidraw2: USB HID v1.11 Joystick [SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller] on usb-0000:00:1d.0-1/input0
[ 7364.645059] sony 0003:054C:0268.0004: can't set operational mode: step 3, ignoring
Lakka:~ #

@hermanchunky : Regarding the dongle, i’m not so certain it may be the issue here, it works perfectly with the same DS3 on my other Windows 8.1 Pro computer. Again both with the cable and BT

@HiScoreBob: Thats the funny thing here. I don’t get the authorize prompt at all. I used just the “agent on”, when that didnt work I have tried the other agent capabilities as well. i.e. along the lines of DisplayYesNo, KeyboardOnly, NoInputNoOutput, etc. None are working

Same dongle from Lakka however pairs instantly with my Samsung S5, LG TV, e.t.c. This has me puzzled!

#8

@litaninja : can you try this little setup ? It seems not easy to make it work on Linux.

#9

I guess you’re talking about

Might need same fix as Belkin : add "blacklist hci_usb" to /etc/modprobe.d/blacklist.conf, and add "hci_usb reset=1" to /etc/modules

described in the first link?

I just tried that and added the blacklist line to blacklist.conf successfully But when i try to add hci_usb reset=1 to /etc/modules i get a “read-only filesystem” error Please is there a way to work around this?

Thanks.

#10

You need to add the configuration in /storage/.config/modprobe.d and /storage/.config/modules-load.d.

#11

So I was able to run to create the “modules” file

Lakka:~ # touch /storage/.config/modules-load.d/modules

Added the

hci_usb reset=1

Is that the correct file / procedure?

And then went on to

Lakka:~ # hciconfighci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:15:83:15:A3:10  ACL MTU: 672:3  SCO MTU: 128:2
        UP RUNNING PSCAN
        RX bytes:2988 acl:4 sco:0 events:187 errors:0
        TX bytes:1685 acl:13 sco:0 commands:123 errors:0


Lakka:~ # hciconfig hci0 down
Lakka:~ # hciconfig hci0 up

Restarted the bluetooth;

Lakka:~ # systemctl stop bluetoothLakka:~ # systemctl start bluetooth
Lakka:~ # systemctl status bluetooth
â bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2016-11-04 11:05:09 UTC; 5s ago
 Main PID: 750 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           ââ750 /usr/lib/bluetooth/bluetoothd


Nov 04 11:05:09 Lakka systemd[1]: Started Bluetooth service.
Nov 04 11:05:09 Lakka bluetoothd[750]: Bluetooth daemon 5.37
Nov 04 11:05:09 Lakka bluetoothd[750]: Starting SDP server
Nov 04 11:05:09 Lakka bluetoothd[750]: Failed to open RFKILL control device
Nov 04 11:05:09 Lakka bluetoothd[750]: Bluetooth management interface 1.12 initialized
Nov 04 11:05:09 Lakka bluetoothd[750]: Failed to obtain handles for "Service Changed" characteristic






[bluetooth]# show
Controller 00:15:83:15:A3:10
        Name: BlueZ 5.37
        Alias: BlueZ 5.37
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: yes
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0525
        Discovering: no
[bluetooth]# power on
[CHG] Controller 00:15:83:15:A3:10 Class: 0x000104
Changing power on succeeded
[CHG] Controller 00:15:83:15:A3:10 Powered: yes

Bluetoothctl

[bluetooth]# agent onAgent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 00:15:83:15:A3:10 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:15:83:15:A3:10 Discovering: yes
[NEW] Device 00:C2:C6:3D:5C:E7 DAPOWALE

Plugged in the controller via usb

[NEW] Device 00:32:00:DE:FD:A1 PLAYSTATION(R)3 Controller

Unplugged the usb, no agent authorization still; Manually tried to pair;

[bluetooth]# pair 00:32:00:DE:FD:A1Attempting to pair with 00:32:00:DE:FD:A1
[bluetooth]# connect 00:32:00:DE:FD:A1
Attempting to connect to 00:32:00:DE:FD:A1
Failed to connect: org.bluez.Error.Failed
[CHG] Controller 00:15:83:15:A3:10 Discoverable: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# pair 00:32:00:DE:FD:A1
Attempting to pair with 00:32:00:DE:FD:A1
Failed to pair: org.bluez.Error.InProgress
Failed to pair: org.bluez.Error.AuthenticationCanceled

Still not working :frowning:

Now, on closer look at the dmesg output, I believe that you are right about the DS3 controler being a chinese clone

[ 6460.632885] input: SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:0268.0003/input/input16[ 6460.635306] sony 0003:054C:0268.0003: input,hiddev0,hidraw2: USB HID v1.11 Joystick [SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller] on usb-0000:00:1d.0-1/input0

I think this means one needs to find a way to get CHINESE / CLONE DS3 controllers working / pairing via bluetooth. I came across QTsixa / Sixad for manually pairing / changind the BD master and a patch for openelec that supports clone controllers via BT… Would it be possible to get something similar working in Lakka? Thanks for your time.

#12

Did you try this setup ?

#13

You you mean the “Shanwan/Gasia controllers patch” or re-installing Lakka all over?

I did try re-installing Lakka before the first post I made. I installed both Lakka-Generic.x86_64-devel-20160921135800-r21588-gd33310f.img and Lakka-Generic.x86_64-devel-20161002103858-r21593-g03241bf.img thinking maybe the latest version had a bug or something. I followed the setup from Lakka setup guide which had the "power on included. The bluetooth status reported “running”

#14

Something like :


systemctl enable bluetooth
touch /storage/.cache/services/bluez.conf
systemctl start bluetooth
systemctl status bluetooth
Lakka:~ # bluetoothctl
[bluetooth]# power on
#15

Exactly. I did that immediately after the first install. After that didn’t work and i looked through different forums and setup guides, I tried another release from Lakka site. That didn’t work either, I then posted for help on this forum. So, I’m still stuck :frowning:

[QUOTE=gouchi;50274]Something like :


systemctl enable bluetooth
touch /storage/.cache/services/bluez.conf
systemctl start bluetooth
systemctl status bluetooth
Lakka:~ # bluetoothctl
[bluetooth]# power on

[/QUOTE]

#16

Hi there… Any help on this please? I wouldn’t mind even a manual workaround of sorts to get this chinese clone controller working. Thanks.

[QUOTE=gouchi;50274]Something like :


systemctl enable bluetooth
touch /storage/.cache/services/bluez.conf
systemctl start bluetooth
systemctl status bluetooth
Lakka:~ # bluetoothctl
[bluetooth]# power on

[/QUOTE]

[ODROID-XU4] PS3 Dualshock connecting/disconnecting via bluetooth
Bluetooth troubles
#17

ds3 tool help to connect controller with PlayStation 3 but a lot of people reported that ds3 tool not working for them. On the other hand, a lot of modern consoles like to use USB ports to connect their controllers. So, best suggestion is to move on this method instead to use ds2 tool.