SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP
-
@Wolfman100
yes they are already included. -
@luetzel This is what I get as my bluetooth service output,which now indicates the correct version 5.39:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─local.conf
Active: active (running) since Tue 2016-05-17 13:56:43 BST; 36min ago
Docs: man:bluetoothd(8)
Main PID: 629 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─629 /usr/libexec/bluetooth/bluetoothdMay 17 13:56:43 osmc bluetoothd[629]: Bluetooth daemon 5.39
May 17 13:56:43 osmc bluetoothd[629]: Starting SDP server
May 17 13:56:43 osmc bluetoothd[629]: Bluetooth management interface 1.10 i...edWarning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
Hint: Some lines were ellipsized, use -l to sh
w in full. -
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
This is now what I get when I run sixpair:
root@osmc:/# sudo sixpair
Current Bluetooth master: ff:00:03:c6:9e:66
Unable to retrieve local bd_addr fromhcitool dev
.
Please enable Bluetooth or specify an address manually.When you tried sixpair before, it seemed to work:
I have now installed QtSixA and have run Sixpair:
root@osmc:/# sudo ./sixpair
Current Bluetooth master: b8:27:eb:a1:9b:7f
Setting master bd_addr to b8:27:eb:a1:9b:7fI don't understand what's going on ..
-
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─local.conf
Active: inactive (dead)
Docs: man:bluetoothd(8)Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
-
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─local.conf
Active: inactive (dead)
Docs: man:bluetoothd(8)Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
And why it is no running anymore? Try
sudo systemctl daemon-reload
sudo service bluetooth restartand lets see if it helps.
-
@luetzel OK cool....that seems to have got bluetooth running again!
-
@luetzel sixpair and bluetoothctl don't seem to be seeing the bluetooth controller now however:
root@osmc:/# sudo sixpair
Current Bluetooth master: ff:00:03:c6:9e:66
Unable to retrieve local bd_addr fromhcitool dev
.
Please enable Bluetooth or specify an address manually.
root@osmc:/# b;uetoothctl
bash: b: command not found
bash: uetoothctl: command not found
root@osmc:/# bluetoothctl
[bluetooth]# devices
[bluetooth]# scan on
No default controller available
[bluetooth]# -
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
@luetzel sixpair and bluetoothctl don't seem to be seeing the bluetooth controller now however:
No default controller available
[bluetooth]#did you try:
hcitool devhere it shows:
Devices:
hci0 00:1B:10:00:2A:ECwhich is the hardware address of my BT dongle. Perhaps you have to unplug/replug it to be recognized.
IMHO the linux kernel should be responsible to register hci0, not bluez. Perhaps you have to shutdown/power off
and reboot your pi. -
@luetzel to confirm it is active:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
└─local.conf
Active: active (running) since Tue 2016-05-17 14:51:59 BST; 11min ago
Docs: man:bluetoothd(8)
Main PID: 842 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─842 /usr/libexec/bluetooth/bluetoothdMay 17 14:51:59 osmc bluetoothd[842]: Bluetooth daemon 5.39
May 17 14:51:59 osmc bluetoothd[842]: Starting SDP server
May 17 14:51:59 osmc bluetoothd[842]: Bluetooth management interface 1.10 i...ed
Hint: Some lines were ellipsized, use -l to show in full. -
My BT dongle is built in,it is a Pi3.
-
@luetzel said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
hcitool dev
hcitool shows no devices!
root@osmc:/# hcitool dev
Devices: -
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
@luetzel said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
hcitool dev
hcitool shows no devices!
root@osmc:/# hcitool dev
Devices:@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
My BT dongle is built in,it is a Pi3.
Ah, I see. This might be the problem. I have seen another thread in this forum that there is some trouble with the BT device on Pi3.
https://retropie.org.uk/forum/topic/842/pi-3-ps3-bluetooth-controller-freeze-fix-updated/1What distribution are you using on your Pi3? Was it osmc? My RetroPie runs on Rasbian/Pi2.
Just give me a minute, I'll try to replicate this behaviour on my Pi3 with osmc.
-
@luetzel thank you so much for your dedication to solving this.Your a true gent!
It seems that I mistakenly just presumed your whole article was about Pi3 as a lot of people seem to be having issues with this!
-
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
@luetzel thank you so much for your dedication to solving this.Your a true gent!
It seems that I mistakenly just presumed your whole article was about Pi3 as a lot of people seem to be having issues with this!
But it is not related to the Pi version. So far only genuine Sony PS3 controllers were supported by bluez. The cloned controllers are supported by the sixad daemon, but it interferes with other BT devices, such as keyboards or mice. I would be happy to see support PS3 support via bluez in the next version of RetroPie. Thats why I'm interested in your problem. It is so annoying, that PS3 isn't properly supported by bluez ...
-
@luetzel Indeed it is!I'm on this journey because I watched some YouTube Vids about RetroPie and for everybody else it seemed as easy as installing RetroPie, hitting PS button connecting and off you go!
This has now led me on this journey where nearly two months later I still haven't got the thing working and was in no way expecting to delve so far down the rabbit-hole in terms of coding etc!Having never even seen linux before,nevermind use it I've learned a hell of a lot....Shame I still can't play any f'in games though!
-
@luetzel there is definetly something amiss now though as bluetoothctl freezes,I'm assuming because it can't find the Bluetooth Device
-
@Wolfman100 said in SHANWAN / PS3 CONTROLLER Pi3 RETROPIE 3.6 BLUETOOTH SETUP:
@luetzel Indeed it is!I'm on this journey because I watched some YouTube Vids about RetroPie and for everybody else it seemed as easy as installing RetroPie, hitting PS button connecting and off you go!
This has now led me on this journey where nearly two months later I still haven't got the thing working and was in no way expecting to delve so far down the rabbit-hole in terms of coding etc!Having never even seen linux before,nevermind use it I've learned a hell of a lot....Shame I still can't play any f'in games though!
Ok, I see - the problem is that bluez doesn't recognize the vendor id/device id of the fake PS3 controllers. I also didn't know it, when I ordered a pair from Aliexpress. But I still think that it will be possible to pair your controller.
Just finished to compile it on osmc, will try sixpair now, so stay tuned ...
-
@luetzel Cool.
Her is my root,so you can see where evrything is etc:
root@osmc:/# ls
bin media sixpair
bluez mnt sixpair.c
boot opt srv
compilation_sid.patch pi-bluetooth_0.1.0_armhf.deb sys
dev proc tmp
etc QtSixA-1.5.1 usr
home root var
lib run vendor
lib64 sbin walkthrough_completed
lost+found selinux -
@Wolfman100
ok, I'm able to pair the PS3 controller on a Pi3 with OSMC and patched bluez:osmc@osmc:~/install/qtsixa-1.5.0/utils/bins$ hcitool dev
Devices:
hci0 B8:27:EB:9F:44:68
osmc@osmc:~/install/qtsixa-1.5.0/utils/bins$ sudo ./sixpair
Current Bluetooth master: b8:27:eb:9f:44:68
Setting master bd_addr to b8:27:eb:9f:44:68
osmc@osmc:~/install/qtsixa-1.5.0/utils/bins$ sudo bluetoothctl
[NEW] Controller B8:27:EB:9F:44:68 osmc [default]
[NEW] Device 01:B6:52:85:63:25 PLAYSTATION(R)3 Controller
[NEW] Device 20:73:AB:91:DD:6F Bluetooth V3.0 Keyboard
[NEW] Device 00:1D:D8:97:9A:F6 Microsoft Blueto
[CHG] Device 01:B6:52:85:63:25 Class: 0x000540
[CHG] Device 01:B6:52:85:63:25 Icon: input-keyboard
[CHG] Device 01:B6:52:85:63:25 Connected: yes
[PLAYSTATION(R)3 Controller]#Your problem must be related to something else. It's not the Pi3 which makes trouble. Did you update/upgrade your osmc to the latest kernel?
my 'uname -a' shows:Linux osmc 4.4.8-3-osmc #1 SMP PREEMPT Sun May 1 18:57:43 UTC 2016 armv7l GNU/Linux
Think it doesn't harm to upgrade to the latest OSMC. If you do so, you probably have to reinstall bluez from source, because the
deb for OSMC was updated on 1st of May. -
I am currently on OSMC 4.4.6-3
I would upgrade,but it is telling me that their is insufficient space for the upgrade.I think this has to do with it being a dual boot system with Raspian,and Raspian has expanded to take all the remaining space on the 32GB SD.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.