2009-07-16, 22:32
Wow. Great progress. I've been trying for months with different programs and scripts meant to work with this remote with no joy. This is the first thing that's worked.
I'm using kubuntu karmic/9.10 alpha, and MythTV trunk. The jaunty build of blueman seems to work fine on karmic, and my remote reconnects automatically, even after a reboot.
That doesn't mean everything is solved yet, however! If I disconnect and re-connect the remote, it will connect using a new event hander.
Each time I disconnect, a new handler will be created. Not catastrophic in and of itself, because lirc can be started to look for the device name... and this seems to find the new hander okay, although I haven't tested it extensively yet.
Note: the spaces in the device name break the /etc/init.d/lirc script.... I had to hack out of some of the intelligence of the script and feed the arguments in directly:
From /etc/init.d/lirc
Note: when it the remote does reconnect, you have to re-start the lirc daemon. So it only helps with the pain of trying to figure out what event hander to connect it to.
Now, why disconnect the remote when everything is working so well? I noticed in blueman that the remote never seems to disconnect on it's own.... so I presume I'll lose battery in a day or so. What's needed is some wait for the remote to time out after a while, as it does with the PS3. Ideally, when it comes back blueman would also connect it to the same input/event handler as well.... or you just get more and more event handlers being creates (not sure what the limit would be.)
My lircd.conf:
I think the re-connect issues might require some specific enhancements to blueman.... but I'd be thrilled if anyone has another solution.
I'm using kubuntu karmic/9.10 alpha, and MythTV trunk. The jaunty build of blueman seems to work fine on karmic, and my remote reconnects automatically, even after a reboot.
That doesn't mean everything is solved yet, however! If I disconnect and re-connect the remote, it will connect using a new event hander.
Code:
I: Bus=0005 Vendor=054c Product=0306 Version=0000
N: Name="PS3 Remote Controller"
P: Phys=
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=8000000000000000 7000001083c100 8c00ea00000000 6bc0000000000001 8000 1102c0000801 80168000000000 10000ffe
I: Bus=0005 Vendor=054c Product=0306 Version=0000
N: Name="PS3 Remote Controller"
P: Phys=
S: Sysfs=/devices/virtual/input/input8
U: Uniq=
H: Handlers=kbd event7
B: EV=3
B: KEY=8000000000000000 7000001083c100 8c00ea00000000 6bc0000000000001 8000 1102c0000801 80168000000000 10000ffeEach time I disconnect, a new handler will be created. Not catastrophic in and of itself, because lirc can be started to look for the device name... and this seems to find the new hander okay, although I haven't tested it extensively yet.
Code:
lircd --device=name='PS3 Remote Controller' --driver=devinputNote: the spaces in the device name break the /etc/init.d/lirc script.... I had to hack out of some of the intelligence of the script and feed the arguments in directly:
From /etc/init.d/lirc
Code:
start-stop-daemon --start --quiet --exec /usr/sbin/lircd -- --device="$REMOTE_DEVICE" --driver=devinput < /dev/nullNote: when it the remote does reconnect, you have to re-start the lirc daemon. So it only helps with the pain of trying to figure out what event hander to connect it to.
Now, why disconnect the remote when everything is working so well? I noticed in blueman that the remote never seems to disconnect on it's own.... so I presume I'll lose battery in a day or so. What's needed is some wait for the remote to time out after a while, as it does with the PS3. Ideally, when it comes back blueman would also connect it to the same input/event handler as well.... or you just get more and more event handlers being creates (not sure what the limit would be.)
My lircd.conf:
Code:
# Please make this file available to others
# by sending it to <[email protected]>
#
# 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:
#
begin remote
name SonyBDRemote
bits 32
eps 30
aeps 100
one 0 0
zero 0 0
gap 102974
toggle_bit_mask 0x8001019C
begin codes
num1 0x80010002
num2 0x80010003
num3 0x80010004
num4 0x80010005
num5 0x80010006
num6 0x80010007
num7 0x80010008
num8 0x80010009
num9 0x8001000A
num0 0x8001000B
eject 0x800100A1
audio 0x80010188
angle 0x80010173
subtitle 0x80010172
clear 0x80010163
time 0x80010167
red 0x8001018E
green 0x8001018F
blue 0x80010191
yellow 0x80010190
display 0x80010166
top_menu 0x8001008B
menu 0x800101B6
return 0x80010001
options 0x80010165
back 0x8001009E
view 0x80010177
x 0x80010100
enter 0x8001001C
up 0x80010067
down 0x8001006C
left 0x80010069
right 0x8001006A
l1 0x80010136
l2 0x80010138
l3 0x8001013D
r1 0x80010137
r2 0x80010139
r3 0x8001013E
select 0x80010161
start 0x8001013B
ps 0x800100AC
rew 0x800100A8
play 0x800100CF
ffw 0x8001009F
prev 0x8001019C
stop 0x80010080
next 0x80010197
slow_rew 0x800101B4
pause 0x80010077
slow_ffw 0x800101B5
end codes
end remoteI think the re-connect issues might require some specific enhancements to blueman.... but I'd be thrilled if anyone has another solution.
