[kobik]

Someone please help.
I managed to pair the remote one time now.
But after reboot I can't see it anymore and both

Code:

hcitool scan

and

Code:

python ps3_pair.py

finds nothing.

[peeedeee]

Not in the manual... but if finally (after 4 hours) got the remote working, after deleting the content of /var/lib/bluetooth/ and run the ps3_pair.py again.

Could some one add it to the manual, it solved more problems with blue-tooth for me in the past.


@ kobic
As far i understand uinput isn't required as kernel-module with newer kernels (mine at the moment 3.0.4 on ubuntu 10.10) ...and if you got a usb printer you probably also won't need lp in /etc/modules.
Try "hciconfig" to be sure your device is up, if not execute "hciconfig up" and try "sudo ./python ps3_pair.py" instead of "./python ps3_pair.py"

[kobik]

Thanks peeedeee.
Apparently, after so many retries the batteries just went dead and were the ones who failed on me and now it's working like a charm

[kobik]

I'm using the following input.conf file but not matter what, it seems it doesn't have any affect on my remote.
Only the default buttons are working.
Any ideas?
BTW, how can I know for sure that it was kitlaan version which was installed?

Code:

# Configuration file for the input service

# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in seconds) before the connection will
# be disconnect (defaults to 0 for no timeout)
#IdleTimeout=600



# This section contains options that are specific to a device
#[00:11:22:33:44:55]
#
# Set a custom idle timeout (in seconds) for this specific device
#IdleTimeout=30



# This section is the PS3 Remote keymap.  It is loaded when bluez starts.
# Use 'uinput.h' from bluez sources or '/usr/include/linux/input.h' for
# a list of possible KEY_* values.
#
[PS3 Remote Map]
# When the 'OverlayBuiltin' option is TRUE (the default), the keymap uses
# the built-in keymap as a starting point.  When FALSE, an empty keymap is
# the starting point.
#OverlayBuiltin = TRUE
# The mapping below is the bluez internal configuration. You'll want to
# customize it; some recommendations for XBMC are specified.
0x16 = KEY_S              # EJECT
0x64 = KEY_A              # AUDIO             (XBMC recommendation: KEY_A)
0x65 = KEY_Z              # ANGLE             (XBMC recommendation: KEY_Z)
0x63 = KEY_T              # SUBTITLE          (XBMC recommendation: KEY_T)
0x0f = KEY_DELETE         # CLEAR             (XBMC recommendation: KEY_DELETE)
0x28 = KEY_END            # TIMER             (XBMC recommendation: KEY_END)
0x00 = KEY_1              # NUM-1
0x01 = KEY_2              # NUM-2
0x02 = KEY_3              # NUM-3
0x03 = KEY_4              # NUM-4
0x04 = KEY_5              # NUM-5
0x05 = KEY_6              # NUM-6
0x06 = KEY_7              # NUM-7
0x07 = KEY_8              # NUM-8
0x08 = KEY_9              # NUM-9
0x09 = KEY_0              # NUM-0
0x81 = KEY_F7             # RED               (XBMC recommendation: KEY_F7)
0x82 = KEY_F8               # GREEN             (XBMC recommendation: KEY_F8)
0x80 = KEY_F9              # BLUE              (XBMC recommendation: KEY_F9)
0x83 = KEY_F10              # YELLOW            (XBMC recommendation: KEY_F10)
0x70 = KEY_H              # DISPLAY           (XBMC recommendation: KEY_D)
0x1a = KEY_MENU           # TOP MENU
0x40 = KEY_F11          # POP UP/MENU       (XBMC recommendation: KEY_F11)
0x0e = KEY_ESC            # RETURN
0x5c = KEY_C              # TRIANGLE/OPTIONS  (XBMC recommendation: KEY_C)
0x5d = KEY_BACKSPACE      # CIRCLE/BACK
0x5f = KEY_I              # SQUARE/VIEW       (XBMC recommendation: KEY_V)
0x5e = KEY_O              # CROSS             (XBMC recommendation: KEY_X)
0x54 = KEY_UP             # UP
0x56 = KEY_DOWN           # DOWN
0x57 = KEY_LEFT           # LEFT
0x55 = KEY_RIGHT          # RIGHT
0x0b = KEY_ENTER          # ENTER
0x5a = KEY_PAGEUP         # L1                (XBMC recommendation: KEY_F1)
0x58 = KEY_PAGEDOWN       # L2                (XBMC recommendation: KEY_F2)
0x51 = KEY_TAB              # L3                (XBMC recommendation: KEY_F3)
0x5b = KEY_HOME           # R1                (XBMC recommendation: KEY_F4)
0x59 = KEY_END            # R2                (XBMC recommendation: KEY_F5)
0x52 = KEY_H              # R3                (XBMC recommendation: KEY_F6)
0x43 = KEY_HOMEPAGE       # PS button
0x50 = KEY_Q              # SELECT            (XBMC recommendation: KEY_INSERT)
0x53 = KEY_W              # START             (XBMC recommendation: KEY_HOME)
0x33 = KEY_R              # SCAN BACK         (XBMC recommendation: KEY_R)
0x32 = KEY_PLAY           # PLAY
0x34 = KEY_F              # SCAN FORWARD      (XBMC recommendation: KEY_F)
0x30 = KEY_COMMA      # PREVIOUS          (XBMC recommendationL KEY_PAGEUP)
0x38 = KEY_STOP           # STOP
0x31 = KEY_PERIOD      # NEXT              (XBMC recommendation: KEY_PAGEDOWN)
0x60 = KEY_FRAMEBACK      # SLOW/STEP BACK    (XBMC recommendation: KEY_COMMA)
0x39 = KEY_SPACE          # PAUSE
0x61 = KEY_DOT          # SLOW/STEP FORWARD (XBMC recommendation: KEY_DOT)
0xff = KEY_MAX

[gorgeth]

For those that may have had a working 11.10 that stopped after an update recently it is due to the "unpatched" oneiric ubuntu sources leapfrogging kitlaan's ppa .. if you downgrade to his version (using synaptic/package menu force version) and then lock the version you should be back in business using customized input.conf as usual!

you may have to install synaptic manually if this was a clean install of 11.10 (sudo apt-get install synaptic or use the software center either way works)

Update: do NOT blindly allow updates from "apt-get update/upgrade" if you use this method.. as using for ex sudo apt-get update && apt-get upgrade will walk all over your "locked' versions from synaptic.. update-manager/synaptic/aptitude (terminal mode gui) all seem to support the synaptic package version force though...

[mocker]

For those that may have had a working 11.10 that stopped after an update recently it is due to the "unpatched" oneiric ubuntu sources leapfrogging kitlaan's ppa .. if you downgrade to his version (using synaptic/package menu force version) and then lock the version you should be back in business using customized input.conf as usual!

you may have to install synaptic manually if this was a clean install of 11.10 (sudo apt-get install synaptic or use the software center either way works)

Update: do NOT blindly allow updates from "apt-get update/upgrade" if you use this method.. as using for ex sudo apt-get update && apt-get upgrade will walk all over your "locked' versions from synaptic.. update-manager/synaptic/aptitude (terminal mode gui) all seem to support the synaptic package version force though...

Have you tried setting a priority on the repository? I'm not at home but something like this may work:

Code:

user@boobtube:/etc/apt/preferences.d$ pwd
/etc/apt/preferences.d
user@boobtube:/etc/apt/preferences.d$ cat bluez-pin-700
Package: *
Pin: release o=LP-PPA-kitlaan
Pin-Priority: 700
user@boobtube:/etc/apt/preferences.d$

After you setup the preference try running 'apt-cache policy bluez' to see which candidate is selected for installation.

Also on a different topic, a note for people following the instructions on Ubuntu 11.10, uinput is now compiled into the kernel, so the modprobe won't show anything.

[Trooper87]

Have you tried setting a priority on the repository? I'm not at home but something like this may work:
...
After you setup the preference try running 'apt-cache policy bluez' to see which candidate is selected for installation.

Also on a different topic, a note for people following the instructions on Ubuntu 11.10, uinput is now compiled into the kernel, so the modprobe won't show anything.

Managed to get the remote working on 11.10.
This is how I set the preferred repository:

Code:

cd /etc/apt
sudo nano preferences

Package: *
Pin: release o=LP-PPA-kitlaan
Pin-Priority: 700

The wake up time is a bit slow on this remote, takes 2-3 sec to wake up and input is registered. I might have a bad bluetooth adapter.
Is anyone experiencing a faster wake up time?

[Infinitatus]

Just paired my zacate pc with my ps3 remote. In blueman the device is present. I used bluezpatch from kitlaan. It pairs, but no button works in XBMC, I changed the input.conf like in the xbmc wiki, but no result. No even the default buttons
/usr/share/doc/bluez/examples/list-devices shows:

Name = Mypcname-0
Powered = 1
Devices = dev_00_24_33_98_EE_6B
DiscoverableTimeout = 0
PairableTimeout = 0
Discoverable = 1
Address = 00:26:83:2F:49:AD
Discovering = 0
Pairable = 1
Class = 4849920
UUIDs = 0x1000 0x1001 0x1112 0x111f 0x110a 0x110c 0x110e 0x1103
[ /org/bluez/1007/hci0/dev_00_24_33_98_EE_6B ]
Name = BD Remote Control
Paired = 0
Adapter = /org/bluez/1007/hci0
Alias = BD Remote Control
Connected = 0
UUIDs = 0x1124 0x1200
Address = 00:24:33:98:EE:6B
Services = dbus.Array([], signature=dbus.Signature('o'), variant_level=1)
Class = 0x00250c
Trusted = 1
Blocked = 0

cat /proc/bus/input/devices won't show the remote


I pairs, it is trusted, but it is not connected? Please help me. I cannot use bluesman because i used a minimal installation.

[Infinitatus]

Just paired my zacate pc with my ps3 remote. In blueman the device is present. I used bluezpatch from kitlaan. It pairs, but no button works in XBMC, I changed the input.conf like in the xbmc wiki, but no result. No even the default buttons
/usr/share/doc/bluez/examples/list-devices shows:

Name = Mypcname-0
Powered = 1
Devices = dev_00_24_33_98_EE_6B
DiscoverableTimeout = 0
PairableTimeout = 0
Discoverable = 1
Address = 00:26:83:2F:49:AD
Discovering = 0
Pairable = 1
Class = 4849920
UUIDs = 0x1000 0x1001 0x1112 0x111f 0x110a 0x110c 0x110e 0x1103
[ /org/bluez/1007/hci0/dev_00_24_33_98_EE_6B ]
Name = BD Remote Control
Paired = 0
Adapter = /org/bluez/1007/hci0
Alias = BD Remote Control
Connected = 0
UUIDs = 0x1124 0x1200
Address = 00:24:33:98:EE:6B
Services = dbus.Array([], signature=dbus.Signature('o'), variant_level=1)
Class = 0x00250c
Trusted = 1
Blocked = 0

cat /proc/bus/input/devices won't show the remote


I pairs, it is trusted, but it is not connected? Please help me. I cannot use bluesman because i used a minimal installation.

Several days have passed. I am still without remote. I can´t find the solution.

[kobik]

@Infinitatus, have you tried this?

Not in the manual... but if finally (after 4 hours) got the remote working, after deleting the content of /var/lib/bluetooth/ and run the ps3_pair.py again.

Could some one add it to the manual, it solved more problems with blue-tooth for me in the past.

BTW, how can a set a button for print screen?

[pumkinut]

You'd need to set up a button for the screenshot command in input.conf.

For example if you wanted to use the Blue button for taking screenshot it would be as such:

Code:

0x80 = KEY_PRINTSCREEN   #BLUE

That's if you're setting up the remote to send keyboard presses, since the default screenshot key is "Print Screen".

[Trooper87]

I also had problems with getting the remote working, got the remote paired but the remote would not work.
Then I tried this guide and it worked(I skipped the uinput part because 11.10 has uinput built into the kernel):
http://forum.xbmc.org/showpost.php?p=921...tcount=614

[Infinitatus]

@Infinitatus, have you tried this?



BTW, how can a set a button for print screen?

Didn´t work i deleted everything, but it says that ps3remote already exists.
@Trooper87 there is one problem with that guide: http://h00s.net/ps3bdremote.tar.gz -->403 forbidden. Unless you have that program, can you mail me that program?

[kobik]

You'd need to set up a button for the screenshot command in input.conf.

For example if you wanted to use the Blue button for taking screenshot it would be as such:

Code:

0x80 = KEY_PRINTSCREEN   #BLUE

That's if you're setting up the remote to send keyboard presses, since the default screenshot key is "Print Screen".

Thanks man!
BTW, where to xbmc saves them :S

[Infinitatus]

Didn´t work i deleted everything, but it says that ps3remote already exists.
@Trooper87 there is one problem with that guide: http://h00s.net/ps3bdremote.tar.gz -->403 forbidden. Unless you have that program, can you mail me that program?

I was almost there, today i found it:

dbus-send --system --dest=org.bluez --print-reply \
/org/bluez/.../hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Input.Connect did the job.