Normally after installing blueman, will appear the bluetooth icon on the top bar of the gnome desktop, if not, you must execute the applet:

Code:

blueman-applet

Once we have the blueman applet running, we click with the secondary mouse button on the bluetooth icon and select "Configure new device".
While the remote is in discovery mode (pressing enter + start for 5 secconds) we will see our remote on the device list, click on it and click "next", the wizard will offer 3 options "random key", "my own key", and "not pairing", we select "not pairing" and click next. On the next screen will see 2 options "input service" and "don't connect", we select "input service and click next.
Now we have the remote paired permanently with the PC, to check it, open "devices" right clicking on the bluetooth icon, and will see the "BD Remote Control" paired, on the right it will show the signal strength. On the devices list there is a button to trust on a device, we must trust on "BD Remote Control", it will show a little yellow star on the icon.
This has created a input device, to see it execute:

Code:

cat /proc/bus/input/devices

this will show the actual input devices on your system and will have something like this

The last line include the name of the input device that was created on the previous step, in my case "/dev/input/event6"

Then restart LIRC

Code:

sudo /etc/init.d/lirc restart

4.- Learn the remote codes of the PS3 BD Remote

You may record your own codes with the command:

Code:

sudo irrecord --device=/dev/input/event6 --driver=devinput PS3.rem

Where "/dev/input/event6" is your input device. And follow the instructions.

NOTE: The PS3 remote send one event when you press a key, and another event when you release it, so when irrecord needs a key pressed we must press many times different keys.

Or use the one I created

Code:

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.4a(devinput) on Sun May 3 19:43:29 2009
#
# contributed by
#
# brand: PS3
# model no. of remote control:
# devices being controlled by this remote:
#

After adding uinput to /etc/modules, installing bluetoothd and disabling network security, I got it working. Now on reboot, lirc exists since it doesn't find the device created by blueman yet. How did you solve that problem? Also it seems I have to configure blueman all over again at each reboot.

freezy Wrote:Another thing: Pressing a button for a longer time doesn't repeat the button (like scrolling down a list). Did you notice that too?

Yes, I notice, b_balthasar is right, the PS3 remote sends a event when a key is pressed, and another one when it's released, but I don't know the way to configure LIRC to repeat until another event occurs

freezy Wrote:After adding uinput to /etc/modules, installing bluetoothd and disabling network security, I got it working. Now on reboot, lirc exists since it doesn't find the device created by blueman yet. How did you solve that problem? Also it seems I have to configure blueman all over again at each reboot.

When I wrote the howto it worked fine for me, after a reboot when I press a key on the remote automaticly reconnects, but now I tried to use the remote with another computer with another BT dongle, and I am in the same situation than you, I have to "connnect input device" every reboot, and I don't know how to solve it :confused2: now I am working on it.

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="false"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""

This solution would work much better for me if it would timeout after 30 or 60 seconds so as not to burn through batteries as quickly. I know I can hold the PS logo button for 6-8 seconds and it will disconnect... but I'll forget and leave it connected until the batteries are dead.