Kodi Community Forum
[LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: [LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS (/showthread.php?tid=50717)



- ruff - 2009-09-28

I have the same dongle
Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

i've paired it initially using blueman, and after that i'm just copying the data. I guess hcitool cannot be used in this particular case, since BD remote is not using pairing, rather registering. Bluez has special mode for this as well as blueman, but hcitool doesn't (afaik).


- flxfxp - 2009-09-28

Ok, time to skip forward. I got bluez working by first apt-getting the official bluez and then overwriting by using the 4.50 bluez version patched. I got the remote set up using blueman. However /proc/bus/input/devices doesnt list the remote.

suggestions?


- flxfxp - 2009-09-28

Here is a link to my /proc/bus/input/devices:
http://pastebin.com/f27b04b56

ruff, do you have msn of some sort?


- ruff - 2009-09-28

kubax Wrote:ok, yesterday i rebooted my mashine, and have top running while disconnection my ps3 remote, then my bluetoothd gets 99% of cpu time... i think this is what you meant...
yes, this is it, however it should not be the case while remote timed out on idle.

kubax Wrote:oh, if this matters, my system is 64bit...
Don't know yet, try to apply patches submitted to bluez, they should fix cpu load issue, and cpu load is actually blocking subsequent connections.
http://marc.info/?l=linux-bluetooth&m=125397520600513&w=2
http://marc.info/?l=linux-bluetooth&m=125397534400714&w=2
http://marc.info/?l=linux-bluetooth&m=125397547300875&w=2
http://marc.info/?l=linux-bluetooth&m=125397557100988&w=2


- flxfxp - 2009-09-28

By the way, if I go to devices and click connect to device I see in the debug window: fail (DBusException(dbus.String(u'Connection Refused (111)'),),)


- ruff - 2009-09-28

flxfxp Wrote:Ok, time to skip forward. I got bluez working by first apt-getting the official bluez and then overwriting by using the 4.50 bluez version patched. I got the remote set up using blueman. However /proc/bus/input/devices doesnt list the remote.

suggestions?

What does bluetoothd -nd tell when pressing buttons on remote?

And yes, I have msn, but I'm hardly using it. I'm always online on icq though. Also AIM is always online as well, though I don't have any contacts there %)


- flxfxp - 2009-09-28

Code:
xbmc@AurigaHD:~$ sudo bluetoothd -nd
bluetoothd[4898]: Bluetooth daemon 4.50
bluetoothd[4898]: Enabling debug information
bluetoothd[4898]: parsing main.conf
bluetoothd[4898]: discovto=0
bluetoothd[4898]: pairto=0
bluetoothd[4898]: pageto=8192
bluetoothd[4898]: name=%h-%d
bluetoothd[4898]: class=0x000100
bluetoothd[4898]: discov_interval=0
bluetoothd[4898]: Key file does not have key 'DeviceID'
bluetoothd[4898]: Unable to get on D-Bus

/etc/bluetooth/main.conf:
http://pastebin.com/f732a15c1

?


- kubax - 2009-09-28

first close your running blutooth deamon (/usr/init.d/bluetooth stop) than run bluetoothd -nd again (from the compiled directory [most /usr/local/sbin/bluetoothd -nd] )

only when bluetoothd -nd NOT atomatically closes itself, it runs (-n is for no deamon mode -d is for debug output)

Edit:
ruff, thanks will try the patches now...


- flxfxp - 2009-09-28

Thanks kubax:
Code:
xbmc@AurigaHD:~$ sudo bluetoothd -nd
bluetoothd[4957]: Bluetooth daemon 4.50
bluetoothd[4957]: Enabling debug information
bluetoothd[4957]: parsing main.conf
bluetoothd[4957]: discovto=0
bluetoothd[4957]: pairto=0
bluetoothd[4957]: pageto=8192
bluetoothd[4957]: name=%h-%d
bluetoothd[4957]: class=0x000100
bluetoothd[4957]: discov_interval=0
bluetoothd[4957]: Key file does not have key 'DeviceID'
bluetoothd[4957]: Starting SDP server
bluetoothd[4957]: Loading builtin plugins
bluetoothd[4957]: Loading audio plugin
bluetoothd[4957]: Loading input plugin
bluetoothd[4957]: Loading serial plugin
bluetoothd[4957]: Loading network plugin
bluetoothd[4957]: Loading service plugin
bluetoothd[4957]: Loading hciops plugin
bluetoothd[4957]: Loading hal plugin
bluetoothd[4957]: Loading storage plugin
bluetoothd[4957]: Loading plugins /usr/local/lib/bluetooth/plugins
bluetoothd[4957]: register_interface: path /org/bluez/4957/any
bluetoothd[4957]: Registered interface org.bluez.Service on path /org/bluez/4957/any
bluetoothd[4957]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[4957]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[4957]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4957]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4957]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4957]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[4957]: bridge pan0 created
bluetoothd[4957]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[4957]: Unix socket created: 9
bluetoothd[4957]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[4957]: audio.conf: Key file does not have key 'MaxConnected'
bluetoothd[4957]: Telephony plugin initialized
bluetoothd[4957]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[4957]: HCI dev 0 registered
bluetoothd[4957]: child 4962 forked
bluetoothd[4957]: btd_adapter_ref(0xb905fc88): ref=1
bluetoothd[4957]: Failed to open RFKILL control device
bluetoothd[4957]: Entering main loop
bluetoothd[4957]: Agent registered for hci0 at :1.18:/org/blueman/agent/adapter/hci0
bluetoothd[4957]: child 4962 exited
bluetoothd[4957]: HCI dev 0 up
bluetoothd[4957]: Starting security manager 0
bluetoothd[4957]: Changing Major/Minor class to 0x000104
bluetoothd[4957]: register_interface: path /org/bluez/4957/hci0
bluetoothd[4957]: Registered interface org.bluez.Service on path /org/bluez/4957/hci0
bluetoothd[4957]: network_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: btd_adapter_ref(0xb905fc88): ref=2
bluetoothd[4957]: Adding record with handle 0x10000
bluetoothd[4957]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[4957]: register_server_record: got record id 0x10000
bluetoothd[4957]: Registered interface org.bluez.NetworkPeer on path /org/bluez/4957/hci0
bluetoothd[4957]: network_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: Adding record with handle 0x10001
bluetoothd[4957]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[4957]: register_server_record: got record id 0x10001
bluetoothd[4957]: Registered interface org.bluez.NetworkHub on path /org/bluez/4957/hci0
bluetoothd[4957]: network_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: Adding record with handle 0x10002
bluetoothd[4957]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[4957]: register_server_record: got record id 0x10002
bluetoothd[4957]: Registered interface org.bluez.NetworkRouter on path /org/bluez/4957/hci0
bluetoothd[4957]: proxy_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: btd_adapter_ref(0xb905fc88): ref=3
bluetoothd[4957]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/4957/hci0
bluetoothd[4957]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
bluetoothd[4957]: btd_adapter_ref(0xb905fc88): ref=4
bluetoothd[4957]: headset_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: btd_adapter_ref(0xb905fc88): ref=5
bluetoothd[4957]: audio_adapter_ref(0xb90624d0): ref=1
bluetoothd[4957]: audio.conf: Key file does not have key 'Master'
bluetoothd[4957]: Adding record with handle 0x10003
bluetoothd[4957]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[4957]: audio.conf: Key file does not have key 'SCORouting'
bluetoothd[4957]: a2dp_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: audio_adapter_ref(0xb90624d0): ref=2
bluetoothd[4957]: audio.conf: Key file does not have key 'Enable'
bluetoothd[4957]: audio.conf: Key file does not have key 'Disable'
bluetoothd[4957]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[4957]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[4957]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[4957]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[4957]: audio.conf: Key file does not have key 'Master'
bluetoothd[4957]: SEP 0xb9063138 registered: type:0 codec:0 seid:1
bluetoothd[4957]: Adding record with handle 0x10004
bluetoothd[4957]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[4957]: avrcp_server_probe: path /org/bluez/4957/hci0
bluetoothd[4957]: audio_adapter_ref(0xb90624d0): ref=3
bluetoothd[4957]: audio.conf: Key file does not have key 'Master'
bluetoothd[4957]: Adding record with handle 0x10005
bluetoothd[4957]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[4957]: Adding record with handle 0x10006
bluetoothd[4957]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[4957]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[4957]: Creating device /org/bluez/4957/hci0/dev_00_1E_3D_11_53_EA
bluetoothd[4957]: btd_device_ref(0xb90641d8): ref=1
bluetoothd[4957]: Probe drivers for /org/bluez/4957/hci0/dev_00_1E_3D_11_53_EA
bluetoothd[4957]: hid_device_probe: path /org/bluez/4957/hci0/dev_00_1E_3D_11_53_EA
bluetoothd[4957]: btd_device_ref(0xb90641d8): ref=2
bluetoothd[4957]: Registered interface org.bluez.Input on path /org/bluez/4957/hci0/dev_00_1E_3D_11_53_EA
bluetoothd[4957]: Adapter /org/bluez/4957/hci0 has been enabled
bluetoothd[4957]: Computer is classified as desktop
bluetoothd[4957]: Setting 0x000104 for major/minor device class
bluetoothd[4957]: Changing service classes to 0x1a0104
bluetoothd[4957]: HCI dev 0 down
bluetoothd[4957]: Adapter /org/bluez/4957/hci0 has been disabled
bluetoothd[4957]: Stopping security manager 0
bluetoothd[4957]: Removing record with handle 0x10002
bluetoothd[4957]: Removing record with handle 0x10001
What a mess...I'm completely lost Sad


- kubax - 2009-09-28

only a guess, but did you copied the data from the old bluez (apt-get version) to the compiled version?

if not, look in /var/lib/bluetooth/ and see if there is a folder with your mac adress of the remote (and one of your card)

should look something like this...

Code:
root@kubax-vdr:/var/lib/bluetooth# tree
.
|-- 00:02:72:09:78:69
|   |-- classes
|   |-- config
|   |-- features
|   `-- lastused
`-- 11:11:11:11:11:11
    |-- classes
    |-- config
    |-- did
    |-- features
    |-- hidd
    |-- lastseen
    |-- lastused
    |-- manufacturers
    |-- names
    |-- profiles
    |-- sdp
    `-- trusts


copy it completely to /usr/lib/bluetooth (this is where the compiled version trys to find paired devices)
after this, your remote should be paired after some button presses and shows every button pressed in the bluetoothd -nd window..

btw. 11:11:11 and so on is my dongle


- flxfxp - 2009-09-28

Code:
xbmc@AurigaHD:/var/lib/bluetooth$ tree
.
`-- 00:15:83:2C:24:44
    |-- classes
    |-- config
    |-- did
    |-- features
    |-- lastseen
    |-- lastused
    |-- manufacturers
    |-- names
    |-- profiles
    |-- sdp
    `-- trusts
Code:
xbmc@AurigaHD:/usr/lib/bluetooth$ tree
.
`-- plugins
    |-- audio.so
    |-- hal.so
    |-- input.so
    |-- netlink.so
    |-- network.so
    |-- serial.so
    `-- service.so

1 directory, 7 files

the remote has 00:1E:3D:11:53:EA as mac


- kubax - 2009-09-28

so your remote isn't properly paired with your computer.. when you pair with blueman, does it ask you how to se the remote? (input device or something else)


- flxfxp - 2009-09-28

It prompts for input device or none
By the way, isnt it smarter to start all over again? The reason im asking is because i couldnt get hcitool working in the first place due to the "no device" problem, i apt-getted the official bluez and then make installed the patched one over it. This may cause some problems.
However, hcitool didnt work before i apt-getted the official, does bluez has any requirements that it might have grabbed as well?

Sorry if im talking gibberish.


- kubax - 2009-09-28

i dont see any reason to do evrything completely new...

i've also installed bluez with apt-get and then compiled it manualy.. and evrything (exept the disconnection of bluetooth) works fine...

i can offer you to try helping you if you got the posibillity to set the ssh and / or vnc port patted to your mashine.. but first of all we should stop spamming this thread ^^ i pm you my icq number..


- kubax - 2009-09-28

hmm.. the patches can't be applied to any version i've tried (4.48, 4.50, 4.52, 4.54) here are the error messages i get for the latest (4.54 version)

Code:
root@kubax-vdr:/usr/src/bluez-4.54# patch -p1 < patch1.patch
patching file input/device.c
patch: **** malformed patch at line 33: input_device *idev,

root@kubax-vdr:/usr/src/bluez-4.54# patch -p1 < patch2.patch
patching file input/fakehid.c
Hunk #2 succeeded at 211 (offset 1 line).
patch: **** malformed patch at line 47: GIOCondition cond,

root@kubax-vdr:/usr/src/bluez-4.54# patch -p1 < patch3.patch
patching file input/device.h
Hunk #1 FAILED at 55.
1 out of 1 hunk FAILED -- saving rejects to file input/device.h.rej
patching file input/fakehid.c
Hunk #1 FAILED at 209.
patch: **** malformed patch at line 56: GIOCondition cond,

root@kubax-vdr:/usr/src/bluez-4.54# patch -p1 < patch4.patch
patching file input/device.h
Hunk #1 FAILED at 29.
1 out of 1 hunk FAILED -- saving rejects to file input/device.h.rej
patching file input/fakehid.c
Hunk #1 succeeded at 92 (offset -2 lines).
Hunk #2 succeeded at 145 with fuzz 1 (offset -2 lines).
patch: **** malformed patch at line 93: fake_input *fake, GError **err)