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

1. First of all, a question for kitlaan - you say: "The PPA has been updated for oneiric, no need to hold the package any more; sorry about that".
I'm not sure what you mean by that? Do you mean that there are unncessary steps in my posting from "2011-12-30, 16:08", or what?

2. I've been looking at the remote control power consumption. With mine, on standby the remote control draws 0.12 mA.
Then if you press a button on the remote control it establishes the bluetooth connection and the consumption goes up to about 14 mA.
However the timeout doesn't seem to work.
The power consumption goes back to standby when you unplug the Bluetooth dongle, power down the mythbox or issue 'sudo service bluetooth stop'.
But if you press a button and just leave it, the consumption stays at 14 mA.
I set:
IdleTimeout=30
(and restarted the bluetooth service) but it doesn't time out after 30 seconds - in fact 40 minutes on it's still drawing 14 mA.
I tried running it in debug mode by issuing the following:
sudo service bluetooth stop
sudo bluetoothd -nd

The debug messages show when a key is pressed and released, but there are no timeout messages, etc.

Does anyone have any suggestions about this?

Thanks very much - Vaughan

In fact I've found the answer to my question #2 above: when I looked nearer the start of the debug output I found that it contained the following line:

bluetoothd[2351]: input/manager.c:input_manager_init() input.conf: Key file contains key 'IdleTimeout' in group 'General' which has value that cannot be interpreted.

After experimenting it appears that you need to ensure that there aren't any blank characters at the end of the 'IdleTimeout' line in /etc/bluetooth/input.conf.

Having corrected that, I found that the timeout did indeed occur after the specified number of seconds - and then the power consumption dropped back to 0.12 mA.

Evening

After much faffing about I now have this remote working, but for the life of me can't it to WOL (wake on lan). can anyone tell me if this is possible and if so what I am missing with this remote or I should be looking for something else to let me do this?

Thank you

vaughan Wrote:In fact I've found the answer to my question #2 above: when I looked nearer the start of the debug output I found that it contained the following line:

bluetoothd[2351]: input/manager.c:input_manager_init() input.conf: Key file contains key 'IdleTimeout' in group 'General' which has value that cannot be interpreted.

After experimenting it appears that you need to ensure that there aren't any blank characters at the end of the 'IdleTimeout' line in /etc/bluetooth/input.conf.
)

It seems the example input.conf in the wiki http://wiki.xbmc.org/index.php?title=HOW..._BD_Remote has several spaces after the numeric value in the IdleTimeout line. This could be a problem for anyone who cut/pastes that file.

It also says that IdleTimeout is measure in minutes. I thought it was seconds. I have IdleTimeout=30 and it definately disconnects after 30 seconds, according to the bluez list-devices script.

Is there any reason why the Revo will not be saving my edited files after I have made sure the USB00-03 are listed for Wake on Lan?. It wokes if i remote on to the machine but if I fully power down it will not WOL. Seems the unit doesn't keep the USB settings to accept wake on lan.

any ideas?

kitlaan Wrote:I don't believe that you can do a wake-up using the bluetooth remote, based on how the PC sleep cycle works. I hope someone proves me wrong, though.

Someone had posted instructions on how to wake up a suspended machine via Bluetooth.

http://forum.xbmc.org/showpost.php?p=614...tcount=516

I haven't used it myself yet but the person who posted it says it works.

Is it possible to map two keys to one button in input.conf?

I want to map ALT-F4 and ESC to the eject button.

tweaker Wrote:Is it possible to map two keys to one button in input.conf?

I want to map ALT-F4 and ESC to the eject button.

You can always use irexec to map an executable script to a button

Martin

MartinHJ Wrote:You can always use irexec to map an executable script to a button

Martin

Thanks.

I have another question.

How do I pair a PS3 Sixaxis/Dualshock controller?

I'm using kitlaans patched drivers for my BD Remote. Works perfectly but now I need a controller for emulators.

heldchen Wrote:anyone who had problems waking up through the ps3 remote from a suspended state:

Code:

sudo cat /sys/bus/usb/devices/x-y.z/power/wakeup
echo enabled | sudo tee > /sys/bus/usb/devices/x-y.z/power/wakeup

replace x-y.z with the node the bluetooth dongle is located. also make sure the usb host's power wakeup setting is enabled:

Code:

sudo cat /proc/acpi/wakeup
echo USBx | sudo tee > /proc/acpi/wakeup

replace USBx with your actual usb port name as outputted by /proc/acpi/wakeup

once that works, put the echo commands into your /etc/rc.local to have it enabled on boot.

works like a charm now for me (using a cheap usb dongle).

I've been trying to get this working, but ran into a few issues I'm hoping you can help me out with:

- lsusb output shows my bluetooth dongle connect on Bus 007 device 002, but looking at my /sys/bus/usb/devices/ folder, the closest thing I've found to this is 7-1:1.2, but there are so many other options (usb1 through usb8 among several others like 7-1, 7-1:1.0, 7-1:1.1 etc...) is there any way to tell exactly which one I want?

- sudo cat /sys/bus/usb/devices/7-1:1.2/power/wakeup returns a no such file or directory error

- echo enabled | sudo tee > /sys/bus/usb/devices/7-1:1.2/power/wakeup returns a permission denied error

I'm guessing it's more of a user error than anything, I really have no idea what these commands are doing, or if I'm even on the right track with the USB node the bluetooth dongle is connected to. Any help would be greatly appreciated!