[Bluez-devel] Sony Bluetooth BD Remote Control

[Bluez-devel] Sony Bluetooth BD Remote Control

[Jelle de Jong]

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This message contains the following attachment(s):
Jelle de Jong - Installation Guide - Sony Bluetooth BD Remote Control -
2008-10-10 - v0.1.1j.txt

Hello everybody,

I bought a bluetooth remote for a bluetooth mobile system that I am
trying to built. (bluetooth remote, speakers, mouse, keyboard, headset, gps)

However I can't get the device to work out of the box... I have found
some script and some tools on the internet but this is not very
maintainable (and I could not get it to work)

I am wondering what is needed to create a good healthy maintainable
system to get the remote working out of the box after connecting to it
with bluez...? So how do we create out of the box support for bluetooth
devices?

hidd[3688]: New HID device 00:1E:3D:15:0A:4F (Sony Computer
Entertainment Inc BD Remote Control)
kernel: [18419.605288] input: Sony Computer Entertainment Inc BD Remote
Control as /class/input/input12

Any help is appreciated,

Kind regards,

Jelle de Jong
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkjx974ACgkQ1WclBW9j5Hn+owQAnGdjX0hXkCQBDO35sGmnA+U+
JjXTjkoFefNoem0b5NEeNvUUhwWF5Ogcdtd/tCyZ0YFhXn5w8NBlbWeMFMg1JX7L
o8Tnrj4wi6y6viJoZ1mk+CyIKPigEiqe7aQkahbiTB0LAC7H28/0Nz/AXGStyoE0
50yksr2u8P0gDmpiDm0=
=36g8
-----END PGP SIGNATURE-----

[-- Attachment #2: Jelle de Jong - Installation Guide - Sony Bluetooth BD Remote Control - 2008-10-10 - v0.1.1j.txt --]
[-- Type: text/plain, Size: 9060 bytes --]

#!/bin/sh # just for highlighting this is not a script

# creator: Jelle de Jong <jelledejong at powercraft dot com>

# background: information: http://www2.apebox.org/wordpress/programming/28/
# background: information: http://ant.starikov.googlepages.com/linuxdriverforsonybdremote

Simultaneously press "Start" and "Enter" buttons on the remote for about 5 seconds, to get the device in pairing mode.

sudo /etc/init.d/sysklogd start
sudo /etc/init.d/klogd start
sudo /etc/init.d/bluetooth restart
sudo tail --lines=100 --follow /var/log/syslog

------------------------------------------------------------------------
hcitool scan
    Scanning ...
        00:1E:3D:15:0A:4F   BD Remote Control

------------------------------------------------------------------------
sudo hidd --connect 00:1E:3D:15:0A:4F
    hidd: New HID device 00:1E:3D:15:0A:4F (Sony Computer Entertainment Inc BD Remote Control)
    kernel: [15926.724235] input: Sony Computer Entertainment Inc BD Remote Control as /class/input/input11

------------------------------------------------------------------------
sudo hcitool info 00:1E:3D:15:0A:4F
    Requesting information ...
        BD Address:  00:1E:3D:15:0A:4F
        Device Name: BD Remote Control
        LMP Version: 2.0 (0x3) LMP Subversion: 0x229
        Manufacturer: Broadcom Corporation (15)
        Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
            <encryption> <slot offset> <timing accuracy> <role switch>
            <sniff mode> <RSSI> <power control> <enhanced iscan>
            <interlaced iscan> <interlaced pscan> <AFH cap. slave>

------------------------------------------------------------------------
echo 'HIDD_OPTIONS="--connect 00:1E:3D:15:0A:4F --server"' | sudo tee --append /etc/default/bluetooth
cat /etc/default/bluetooth

------------------------------------------------------------------------
cat /etc/default/bluetooth
    HIDD_ENABLED=1
    HIDD_OPTIONS="--search --server"
    HIDD_OPTIONS="--connect 11:11:11:11:17:95 --server"
    HIDD_OPTIONS="--connect 00:07:61:0F:4A:60 --server"
    HIDD_OPTIONS="--connect 00:1E:3D:15:0A:4F --server"

------------------------------------------------------------------------
sdptool browse 00:1E:3D:15:0A:4F
    Browsing 00:1E:3D:15:0A:4F ...
    Service Name: BD Remote Control
    Service Description: BD Remote Control
    Service Provider: Sony Computer Entertainment Inc
    Service RecHandle: 0x10000
    Service Class ID List:
      "Human Interface Device" (0x1124)
    Protocol Descriptor List:
      "L2CAP" (0x0100)
        PSM: 17
      "HIDP" (0x0011)
    Language Base Attr List:
      code_ISO639: 0x656e
      encoding:    0x6a
      base_offset: 0x100
    Profile Descriptor List:
      "Human Interface Device" (0x1124)
        Version: 0x0100

------------------------------------------------------------------------
sudo hcitool con
    Connections:
        < ACL 00:1E:3D:15:0A:4F handle 42 state 1 lm MASTER

------------------------------------------------------------------------
udevinfo -a -p $(udevinfo -q path -n /dev/input/event11)
    Udevinfo starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.

      looking at device '/class/input/input11/event11':
        KERNEL=="event11"
        SUBSYSTEM=="input"
        DRIVER==""

      looking at parent device '/class/input/input11':
        KERNELS=="input11"
        SUBSYSTEMS=="input"
        DRIVERS==""
        ATTRS{name}=="Sony Computer Entertainment Inc BD Remote Control"
        ATTRS{phys}=="00:1B:DC:00:32:71"
        ATTRS{uniq}=="00:1E:3D:15:0A:4F"
        ATTRS{modalias}=="input:b0005v054Cp0306e0100-e0,kramlsfw"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/hci0/acl001E3D150A4F':
        KERNELS=="acl001E3D150A4F"
        SUBSYSTEMS=="bluetooth"
        DRIVERS==""
        ATTRS{type}=="ACL"
        ATTRS{address}=="00:1E:3D:15:0A:4F"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/hci0':
        KERNELS=="hci0"
        SUBSYSTEMS=="bluetooth"
        DRIVERS==""
        ATTRS{type}=="USB"
        ATTRS{name}=="BlueZ (0)"
        ATTRS{class}=="0x080100"
        ATTRS{address}=="00:1B:DC:00:32:71"
        ATTRS{features}=="0xffff8ffe9bf90080"
        ATTRS{manufacturer}=="10"
        ATTRS{hci_version}=="3"
        ATTRS{hci_revision}=="3164"
        ATTRS{inquiry_cache}=="00:1E:3D:15:0A:4F 1 2 0 0x00250c 0x294d -51 3905334"
        ATTRS{idle_timeout}=="0"
        ATTRS{sniff_max_interval}=="800"
        ATTRS{sniff_min_interval}=="80"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0':
        KERNELS=="1-2:1.0"
        SUBSYSTEMS=="usb"
        DRIVERS=="hci_usb"
        ATTRS{bInterfaceNumber}=="00"
        ATTRS{bAlternateSetting}==" 0"
        ATTRS{bNumEndpoints}=="03"
        ATTRS{bInterfaceClass}=="e0"
        ATTRS{bInterfaceSubClass}=="01"
        ATTRS{bInterfaceProtocol}=="01"
        ATTRS{modalias}=="usb:v0A12p0001d3164dcE0dsc01dp01icE0isc01ip01"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2':
        KERNELS=="1-2"
        SUBSYSTEMS=="usb"
        DRIVERS=="usb"
        ATTRS{configuration}==""
        ATTRS{bNumInterfaces}==" 2"
        ATTRS{bConfigurationValue}=="1"
        ATTRS{bmAttributes}=="80"
        ATTRS{bMaxPower}=="  0mA"
        ATTRS{urbnum}=="151688"
        ATTRS{idVendor}=="0a12"
        ATTRS{idProduct}=="0001"
        ATTRS{bcdDevice}=="3164"
        ATTRS{bDeviceClass}=="e0"
        ATTRS{bDeviceSubClass}=="01"
        ATTRS{bDeviceProtocol}=="01"
        ATTRS{bNumConfigurations}=="1"
        ATTRS{bMaxPacketSize0}=="64"
        ATTRS{speed}=="12"
        ATTRS{busnum}=="1"
        ATTRS{devnum}=="2"
        ATTRS{version}==" 2.00"
        ATTRS{maxchild}=="0"
        ATTRS{quirks}=="0x0"
        ATTRS{authorized}=="1"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1':
        KERNELS=="usb1"
        SUBSYSTEMS=="usb"
        DRIVERS=="usb"
        ATTRS{configuration}==""
        ATTRS{bNumInterfaces}==" 1"
        ATTRS{bConfigurationValue}=="1"
        ATTRS{bmAttributes}=="e0"
        ATTRS{bMaxPower}=="  0mA"
        ATTRS{urbnum}=="39"
        ATTRS{idVendor}=="1d6b"
        ATTRS{idProduct}=="0001"
        ATTRS{bcdDevice}=="0206"
        ATTRS{bDeviceClass}=="09"
        ATTRS{bDeviceSubClass}=="00"
        ATTRS{bDeviceProtocol}=="00"
        ATTRS{bNumConfigurations}=="1"
        ATTRS{bMaxPacketSize0}=="64"
        ATTRS{speed}=="12"
        ATTRS{busnum}=="1"
        ATTRS{devnum}=="1"
        ATTRS{version}==" 1.10"
        ATTRS{maxchild}=="2"
        ATTRS{quirks}=="0x0"
        ATTRS{authorized}=="1"
        ATTRS{manufacturer}=="Linux 2.6.26-1-686 uhci_hcd"
        ATTRS{product}=="UHCI Host Controller"
        ATTRS{serial}=="0000:00:1d.0"
        ATTRS{authorized_default}=="1"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0':
        KERNELS=="0000:00:1d.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="uhci_hcd"
        ATTRS{vendor}=="0x8086"
        ATTRS{device}=="0x2658"
        ATTRS{subsystem_vendor}=="0x1043"
        ATTRS{subsystem_device}=="0x82d8"
        ATTRS{class}=="0x0c0300"
        ATTRS{irq}=="23"
        ATTRS{local_cpus}=="ff"
        ATTRS{local_cpulist}=="0-7"
        ATTRS{modalias}=="pci:v00008086d00002658sv00001043sd000082D8bc0Csc03i00"
        ATTRS{broken_parity_status}=="0"
        ATTRS{msi_bus}==""

      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""

------------------------------------------------------------------------
sudo evtest /dev/input/event11

------------------------------------------------------------------------
sudo apt-get install libbluetooth-dev

cd bdremote-0.2/
make
    gcc -O3 bdremoted.c -o bdremoted -lpthread

sudo cp --verbose  bdremoted /usr/bin/bdremoted
    `bdremoted' -> `/usr/bin/bdremoted'
sudo chmod --verbose 755 /usr/bin/bdremoted
    mode of `/usr/bin/bdremoted' changed to 0755 (rwxr-xr-x)
------------------------------------------------------------------------

sudo hidd --kill 00:1E:3D:15:0A:4F
sudo hcitool con
    Connections:

bdremoted -h
sudo bdremoted -a 00:1E:3D:15:0A:4F -p 8888 -d 4 -n
    det=0, port=8888, tmout=60, rep=10, deb=4, addr=00:1E:3D:15:0A:4F
    Can't listen on HID control channel: Address already in use
    BTBD try to reconnect.
    Can't listen on HID control channel: Address already in use
    BTBD try to reconnect.

sudo /etc/init.d/lirc stop
sudo lircd -H null --connect 127.0.0.1:8888
irw
    # no output

sudo killall -9 bdremoted
sudo killall -9 lircd

sudo bdremoted -a 00:1E:3D:15:0A:4F -p 8888
    # 100% cpu load....
------------------------------------------------------------------------

[-- Attachment #3: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Sony Bluetooth BD Remote Control

[Bastien Nocera]

On Sun, 2008-10-12 at 15:12 +0200, Jelle de Jong wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
<snip>
> Hello everybody,
> 
> I bought a bluetooth remote for a bluetooth mobile system that I am
> trying to built. (bluetooth remote, speakers, mouse, keyboard, headset, gps)
> 
> However I can't get the device to work out of the box... I have found
> some script and some tools on the internet but this is not very
> maintainable (and I could not get it to work)
> 
> I am wondering what is needed to create a good healthy maintainable
> system to get the remote working out of the box after connecting to it
> with bluez...? So how do we create out of the box support for bluetooth
> devices?
> 
> hidd[3688]: New HID device 00:1E:3D:15:0A:4F (Sony Computer

There's no hidd support for the PS3 BD remote. Use bluez-{utils,libs}
3.36, or use the latest versions of bluez and bluez-gnome (and make sure
your version has that patch[1]).

And don't use that "Linux driver" horror that requires networking...

[1]:
http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commit;h=c99b105989a216dd4565228ba7dc3b2702f4a6ad


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Sony Bluetooth BD Remote Control

[Jelle de Jong]

Bastien Nocera wrote:
> On Sun, 2008-10-12 at 15:12 +0200, Jelle de Jong wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
> <snip>
>> Hello everybody,
>>
>> I bought a bluetooth remote for a bluetooth mobile system that I am
>> trying to built. (bluetooth remote, speakers, mouse, keyboard, headset, gps)
>>
>> However I can't get the device to work out of the box... I have found
>> some script and some tools on the internet but this is not very
>> maintainable (and I could not get it to work)
>>
>> I am wondering what is needed to create a good healthy maintainable
>> system to get the remote working out of the box after connecting to it
>> with bluez...? So how do we create out of the box support for bluetooth
>> devices?
>>
>> hidd[3688]: New HID device 00:1E:3D:15:0A:4F (Sony Computer
> 
> There's no hidd support for the PS3 BD remote. Use bluez-{utils,libs}
> 3.36, or use the latest versions of bluez and bluez-gnome (and make sure
> your version has that patch[1]).
> 
> And don't use that "Linux driver" horror that requires networking...
> 
> [1]:
> http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commit;h=c99b105989a216dd4565228ba7dc3b2702f4a6ad
> 

Thank you for the information,

I currently use bluez-utils_3.36-2_i386.deb and bluetooth_3.36-2_all.deb
on my debian sid system this is version 3.36 as suggested. I don't know
if the patch is applied on the package. Should the device have worked on
my system?

But I am kind of curious what is needed to get such device working in
the source code and how keys are mapped.

Kind regards,

Jelle



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Sony Bluetooth BD Remote Control

[Jelle de Jong]

[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bastien Nocera wrote:
> On Sun, 2008-10-12 at 15:12 +0200, Jelle de Jong wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
> <snip>
>> Hello everybody,
>>
>> I bought a bluetooth remote for a bluetooth mobile system that I am
>> trying to built. (bluetooth remote, speakers, mouse, keyboard, headset, gps)
>>
>> However I can't get the device to work out of the box... I have found
>> some script and some tools on the internet but this is not very
>> maintainable (and I could not get it to work)
>>
>> I am wondering what is needed to create a good healthy maintainable
>> system to get the remote working out of the box after connecting to it
>> with bluez...? So how do we create out of the box support for bluetooth
>> devices?
>>
>> hidd[3688]: New HID device 00:1E:3D:15:0A:4F (Sony Computer
> 
> There's no hidd support for the PS3 BD remote. Use bluez-{utils,libs}
> 3.36, or use the latest versions of bluez and bluez-gnome (and make sure
> your version has that patch[1]).
> 
> And don't use that "Linux driver" horror that requires networking...
> 
> [1]:
> http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commit;h=c99b105989a216dd4565228ba7dc3b2702f4a6ad
> 

I have been working hard to get the bluetooth remote working, but
without success. I build new non official debian packages of the latest
git. I installed them with success. Loaded the new daemon tried to
connect with the bluetooth-wizard but it will not pair/connect. With the
hidd system is does connect but the situation is exactly the same as
with the ordinal report.

What commands are needed to get the device working? I would like to be
able to use xbindings --key to attach commands/keybindings to the keys.

See the attachment for all the steps I did, the new trials are on the
end of the documents.

Please help,

Best regards,

Jelle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkj15z8ACgkQ1WclBW9j5HkIXAP+OilXkEYfDyJ+YPW5TD+PaywS
vTbv5C5CYtE9DQIZ4/A4WHbhuxvY6DwzsZOuksgDgYin8p+z5bzCNw4NBi8rc/Ji
AZoSvaFfZbtyJ0AaOiebCCvdR1zSyKKOlvhrZPjVHPbxcyidebv4EA8yE5+eVtkX
NsviEdWWLouppKHOHwg=
=rjia
-----END PGP SIGNATURE-----

[-- Attachment #2: Jelle de Jong - Sony Bluetooth BD Remote Control - Installation Guide - 2008-10-10 - v0.1.2j.txt --]
[-- Type: text/plain, Size: 18128 bytes --]

#!/bin/sh # just for highlighting this is not a script

# creator: Jelle de Jong <jelledejong at powercraft dot com>

# background: information: http://www2.apebox.org/wordpress/programming/28/
# background: information: http://ant.starikov.googlepages.com/linuxdriverforsonybdremote

Simultaneously press "Start" and "Enter" buttons on the remote for about 5 seconds, to get the device in pairing mode.

sudo /etc/init.d/sysklogd start
sudo /etc/init.d/klogd start
sudo /etc/init.d/bluetooth restart
sudo tail --lines=100 --follow /var/log/syslog

------------------------------------------------------------------------
hcitool scan
    Scanning ...
        00:1E:3D:15:0A:4F   BD Remote Control

------------------------------------------------------------------------
sudo hidd --connect 00:1E:3D:15:0A:4F
    hidd: New HID device 00:1E:3D:15:0A:4F (Sony Computer Entertainment Inc BD Remote Control)
    kernel: [15926.724235] input: Sony Computer Entertainment Inc BD Remote Control as /class/input/input11

------------------------------------------------------------------------
sudo hcitool info 00:1E:3D:15:0A:4F
    Requesting information ...
        BD Address:  00:1E:3D:15:0A:4F
        Device Name: BD Remote Control
        LMP Version: 2.0 (0x3) LMP Subversion: 0x229
        Manufacturer: Broadcom Corporation (15)
        Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
            <encryption> <slot offset> <timing accuracy> <role switch>
            <sniff mode> <RSSI> <power control> <enhanced iscan>
            <interlaced iscan> <interlaced pscan> <AFH cap. slave>

------------------------------------------------------------------------
echo 'HIDD_OPTIONS="--connect 00:1E:3D:15:0A:4F --server"' | sudo tee --append /etc/default/bluetooth
cat /etc/default/bluetooth

------------------------------------------------------------------------
cat /etc/default/bluetooth
    HIDD_ENABLED=1
    HIDD_OPTIONS="--search --server"
    HIDD_OPTIONS="--connect 11:11:11:11:17:95 --server"
    HIDD_OPTIONS="--connect 00:07:61:0F:4A:60 --server"
    HIDD_OPTIONS="--connect 00:1E:3D:15:0A:4F --server"

------------------------------------------------------------------------
sdptool browse 00:1E:3D:15:0A:4F
    Browsing 00:1E:3D:15:0A:4F ...
    Service Name: BD Remote Control
    Service Description: BD Remote Control
    Service Provider: Sony Computer Entertainment Inc
    Service RecHandle: 0x10000
    Service Class ID List:
      "Human Interface Device" (0x1124)
    Protocol Descriptor List:
      "L2CAP" (0x0100)
        PSM: 17
      "HIDP" (0x0011)
    Language Base Attr List:
      code_ISO639: 0x656e
      encoding:    0x6a
      base_offset: 0x100
    Profile Descriptor List:
      "Human Interface Device" (0x1124)
        Version: 0x0100

------------------------------------------------------------------------
sudo hcitool con
    Connections:
        < ACL 00:1E:3D:15:0A:4F handle 42 state 1 lm MASTER

------------------------------------------------------------------------
udevinfo -a -p $(udevinfo -q path -n /dev/input/event11)
    Udevinfo starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.

      looking at device '/class/input/input11/event11':
        KERNEL=="event11"
        SUBSYSTEM=="input"
        DRIVER==""

      looking at parent device '/class/input/input11':
        KERNELS=="input11"
        SUBSYSTEMS=="input"
        DRIVERS==""
        ATTRS{name}=="Sony Computer Entertainment Inc BD Remote Control"
        ATTRS{phys}=="00:1B:DC:00:32:71"
        ATTRS{uniq}=="00:1E:3D:15:0A:4F"
        ATTRS{modalias}=="input:b0005v054Cp0306e0100-e0,kramlsfw"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/hci0/acl001E3D150A4F':
        KERNELS=="acl001E3D150A4F"
        SUBSYSTEMS=="bluetooth"
        DRIVERS==""
        ATTRS{type}=="ACL"
        ATTRS{address}=="00:1E:3D:15:0A:4F"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/hci0':
        KERNELS=="hci0"
        SUBSYSTEMS=="bluetooth"
        DRIVERS==""
        ATTRS{type}=="USB"
        ATTRS{name}=="BlueZ (0)"
        ATTRS{class}=="0x080100"
        ATTRS{address}=="00:1B:DC:00:32:71"
        ATTRS{features}=="0xffff8ffe9bf90080"
        ATTRS{manufacturer}=="10"
        ATTRS{hci_version}=="3"
        ATTRS{hci_revision}=="3164"
        ATTRS{inquiry_cache}=="00:1E:3D:15:0A:4F 1 2 0 0x00250c 0x294d -51 3905334"
        ATTRS{idle_timeout}=="0"
        ATTRS{sniff_max_interval}=="800"
        ATTRS{sniff_min_interval}=="80"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0':
        KERNELS=="1-2:1.0"
        SUBSYSTEMS=="usb"
        DRIVERS=="hci_usb"
        ATTRS{bInterfaceNumber}=="00"
        ATTRS{bAlternateSetting}==" 0"
        ATTRS{bNumEndpoints}=="03"
        ATTRS{bInterfaceClass}=="e0"
        ATTRS{bInterfaceSubClass}=="01"
        ATTRS{bInterfaceProtocol}=="01"
        ATTRS{modalias}=="usb:v0A12p0001d3164dcE0dsc01dp01icE0isc01ip01"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1/1-2':
        KERNELS=="1-2"
        SUBSYSTEMS=="usb"
        DRIVERS=="usb"
        ATTRS{configuration}==""
        ATTRS{bNumInterfaces}==" 2"
        ATTRS{bConfigurationValue}=="1"
        ATTRS{bmAttributes}=="80"
        ATTRS{bMaxPower}=="  0mA"
        ATTRS{urbnum}=="151688"
        ATTRS{idVendor}=="0a12"
        ATTRS{idProduct}=="0001"
        ATTRS{bcdDevice}=="3164"
        ATTRS{bDeviceClass}=="e0"
        ATTRS{bDeviceSubClass}=="01"
        ATTRS{bDeviceProtocol}=="01"
        ATTRS{bNumConfigurations}=="1"
        ATTRS{bMaxPacketSize0}=="64"
        ATTRS{speed}=="12"
        ATTRS{busnum}=="1"
        ATTRS{devnum}=="2"
        ATTRS{version}==" 2.00"
        ATTRS{maxchild}=="0"
        ATTRS{quirks}=="0x0"
        ATTRS{authorized}=="1"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb1':
        KERNELS=="usb1"
        SUBSYSTEMS=="usb"
        DRIVERS=="usb"
        ATTRS{configuration}==""
        ATTRS{bNumInterfaces}==" 1"
        ATTRS{bConfigurationValue}=="1"
        ATTRS{bmAttributes}=="e0"
        ATTRS{bMaxPower}=="  0mA"
        ATTRS{urbnum}=="39"
        ATTRS{idVendor}=="1d6b"
        ATTRS{idProduct}=="0001"
        ATTRS{bcdDevice}=="0206"
        ATTRS{bDeviceClass}=="09"
        ATTRS{bDeviceSubClass}=="00"
        ATTRS{bDeviceProtocol}=="00"
        ATTRS{bNumConfigurations}=="1"
        ATTRS{bMaxPacketSize0}=="64"
        ATTRS{speed}=="12"
        ATTRS{busnum}=="1"
        ATTRS{devnum}=="1"
        ATTRS{version}==" 1.10"
        ATTRS{maxchild}=="2"
        ATTRS{quirks}=="0x0"
        ATTRS{authorized}=="1"
        ATTRS{manufacturer}=="Linux 2.6.26-1-686 uhci_hcd"
        ATTRS{product}=="UHCI Host Controller"
        ATTRS{serial}=="0000:00:1d.0"
        ATTRS{authorized_default}=="1"

      looking at parent device '/devices/pci0000:00/0000:00:1d.0':
        KERNELS=="0000:00:1d.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="uhci_hcd"
        ATTRS{vendor}=="0x8086"
        ATTRS{device}=="0x2658"
        ATTRS{subsystem_vendor}=="0x1043"
        ATTRS{subsystem_device}=="0x82d8"
        ATTRS{class}=="0x0c0300"
        ATTRS{irq}=="23"
        ATTRS{local_cpus}=="ff"
        ATTRS{local_cpulist}=="0-7"
        ATTRS{modalias}=="pci:v00008086d00002658sv00001043sd000082D8bc0Csc03i00"
        ATTRS{broken_parity_status}=="0"
        ATTRS{msi_bus}==""

      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""

------------------------------------------------------------------------
sudo evtest /dev/input/event11

------------------------------------------------------------------------
sudo apt-get install libbluetooth-dev

cd bdremote-0.2/
make
    gcc -O3 bdremoted.c -o bdremoted -lpthread

sudo cp --verbose  bdremoted /usr/bin/bdremoted
    `bdremoted' -> `/usr/bin/bdremoted'
sudo chmod --verbose 755 /usr/bin/bdremoted
    mode of `/usr/bin/bdremoted' changed to 0755 (rwxr-xr-x)
------------------------------------------------------------------------

sudo hidd --kill 00:1E:3D:15:0A:4F
sudo hcitool con
    Connections:

bdremoted -h
sudo bdremoted -a 00:1E:3D:15:0A:4F -p 8888 -d 4 -n
    det=0, port=8888, tmout=60, rep=10, deb=4, addr=00:1E:3D:15:0A:4F
    Can't listen on HID control channel: Address already in use
    BTBD try to reconnect.
    Can't listen on HID control channel: Address already in use
    BTBD try to reconnect.

sudo /etc/init.d/lirc stop
sudo lircd -H null --connect 127.0.0.1:8888
irw
    # no output

sudo killall -9 bdremoted
sudo killall -9 lircd

sudo bdremoted -a 00:1E:3D:15:0A:4F -p 8888
    # 100% cpu load....
------------------------------------------------------------------------

# svn should have been git :-p

sudo dpkg -i $HOME/bluez-utils_4.13svn_i386.deb
sudo dpkg -i $HOME/bluez-gnome_1.8svn_i386.deb
sudo ldconfig -v

------------------------------------------------------------------------

sudo /usr/sbin/bluetoothd --nodaemon --debug

sudo bluetooth-applet

------------------------------------------------------------------------

bluetoothd[14894]: Bluetooth daemon
bluetoothd[14894]: Enabling debug information
bluetoothd[14894]: parsing main.conf
bluetoothd[14894]: offmode=NoScan
bluetoothd[14894]: discovto=0
bluetoothd[14894]: pageto=8192
bluetoothd[14894]: name=%h-%d
bluetoothd[14894]: class=0x000100
bluetoothd[14894]: inqmode=0
bluetoothd[14894]: Starting SDP server
bluetoothd[14894]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[14894]: /usr/lib/bluetooth/plugins/service.so
bluetoothd[14894]: /usr/lib/bluetooth/plugins/hal.so
bluetoothd[14894]: /usr/lib/bluetooth/plugins/network.so
bluetoothd[14894]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
bluetoothd[14894]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[14894]: bridge pan0 created
bluetoothd[14894]: /usr/lib/bluetooth/plugins/serial.so
bluetoothd[14894]: /usr/lib/bluetooth/plugins/input.so
bluetoothd[14894]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
bluetoothd[14894]: /usr/lib/bluetooth/plugins/audio.so
bluetoothd[14894]: Unix socket created: 13
bluetoothd[14894]: Telephony plugin initialized
bluetoothd[14894]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[14894]: HCI dev 0 registered
bluetoothd[14894]: child 14903 forked
bluetoothd[14894]: HCI dev 0 already up
bluetoothd[14894]: service_probe: path /org/bluez/hci0
bluetoothd[14894]: Registered interface org.bluez.Service on path /org/bluez/hci0
bluetoothd[14894]: network_server_probe: path /org/bluez/hci0
bluetoothd[14894]: Adding record with handle 0x10000
bluetoothd[14894]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[14894]: register_server_record: got record id 0x10000
bluetoothd[14894]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
bluetoothd[14894]: network_server_probe: path /org/bluez/hci0
bluetoothd[14894]: Adding record with handle 0x10001
bluetoothd[14894]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001117-0000-1000-8000-00805f9
bluetoothd[14894]: register_server_record: got record id 0x10001
bluetoothd[14894]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
bluetoothd[14894]: network_server_probe: path /org/bluez/hci0
bluetoothd[14894]: Adding record with handle 0x10002
bluetoothd[14894]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001116-0000-1000-8000-00805f9
bluetoothd[14894]: register_server_record: got record id 0x10002
bluetoothd[14894]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
bluetoothd[14894]: proxy_probe: path /org/bluez/hci0
bluetoothd[14894]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
bluetoothd[14894]: headset_server_probe: path /org/bluez/hci0
bluetoothd[14894]: audio.conf: Key file does not have key 'Master'
bluetoothd[14894]: Adding record with handle 0x10003
bluetoothd[14894]: Record pattern UUID 00000003-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001108-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001112-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001203-0000-1000-8000-00805f9
bluetoothd[14894]: audio.conf: Key file does not have key 'SCORouting'
bluetoothd[14894]: a2dp_server_probe: path /org/bluez/hci0
bluetoothd[14894]: audio.conf: Key file does not have key 'Disable'
bluetoothd[14894]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[14894]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[14894]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[14894]: audio.conf: Key file does not have group 'A2DP'
bluetoothd[14894]: audio.conf: Key file does not have key 'Master'
bluetoothd[14894]: SEP 0xb9296078 registered: type:0 codec:0 seid:1
bluetoothd[14894]: Adding record with handle 0x10004
bluetoothd[14894]: Record pattern UUID 00000019-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 0000110a-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 0000110d-0000-1000-8000-00805f9
bluetoothd[14894]: avrcp_server_probe: path /org/bluez/hci0
bluetoothd[14894]: audio.conf: Key file does not have key 'Master'
bluetoothd[14894]: Adding record with handle 0x10005
bluetoothd[14894]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 0000110c-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[14894]: Adding record with handle 0x10006
bluetoothd[14894]: Record pattern UUID 00000017-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[14894]: Record pattern UUID 0000110e-0000-1000-8000-00805f9
bluetoothd[14894]: Adapter /org/bluez/hci0 has been enabled
bluetoothd[14894]: Starting security manager 0
bluetoothd[14894]: child 14903 exited
bluetoothd[14894]: Computer is classified as laptop
bluetoothd[14894]: Current device class is 0x0a010c
bluetoothd[14894]: Setting 0x00010c for major/minor device class
bluetoothd[14894]: Agent registered for hci0 at :1.42:/org/bluez/agent/hci0
bluetoothd[14894]: Discovery session 0xb9291c98 with :1.44 activated
bluetoothd[14894]: session_ref(0xb9291c98): ref=1
bluetoothd[14894]: session_unref(0xb9291c98): ref=0
bluetoothd[14894]: Discovery session 0xb9291c98 with :1.44 deactivated
bluetoothd[14894]: Stopping discovery
bluetoothd[14894]: bonding_request_new(00:1E:3D:15:0A:4F)
bluetoothd[14894]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: adapter_create_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: Creating device /org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[14894]: Temporary agent registered for hci0/00:1E:3D:15:0A:4F at :1.44:/org/bluez/agent/wizard
bluetoothd[14894]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: link_key_request (sba=00:1B:DC:00:32:71, dba=00:1E:3D:15:0A:4F)
bluetoothd[14894]: kernel auth requirements = 0x00
bluetoothd[14894]: pin_code_request (sba=00:1B:DC:00:32:71, dba=00:1E:3D:15:0A:4F)
bluetoothd[14894]: hcid_dbus_new_auth_request
bluetoothd[14894]: hcid_dbus_bonding_process_complete: status=18
bluetoothd[14894]: Releasing agent :1.44, /org/bluez/agent/wizard
bluetoothd[14894]: Removing temporary device 00:1E:3D:15:0A:4F
bluetoothd[14894]: Removing device /org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[14894]: Discovery session 0xb928f3a8 with :1.44 activated
bluetoothd[14894]: session_ref(0xb928f3a8): ref=1
bluetoothd[14894]: session_unref(0xb928f3a8): ref=0
bluetoothd[14894]: Discovery session 0xb928f3a8 with :1.44 deactivated
bluetoothd[14894]: Stopping discovery
bluetoothd[14894]: bonding_request_new(00:1E:3D:15:0A:4F)
bluetoothd[14894]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: adapter_create_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: Creating device /org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[14894]: Temporary agent registered for hci0/00:1E:3D:15:0A:4F at :1.44:/org/bluez/agent/wizard
bluetoothd[14894]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[14894]: link_key_request (sba=00:1B:DC:00:32:71, dba=00:1E:3D:15:0A:4F)
bluetoothd[14894]: kernel auth requirements = 0x00
bluetoothd[14894]: pin_code_request (sba=00:1B:DC:00:32:71, dba=00:1E:3D:15:0A:4F)
bluetoothd[14894]: hcid_dbus_new_auth_request
bluetoothd[14894]: hcid_dbus_bonding_process_complete: status=18
bluetoothd[14894]: Releasing agent :1.44, /org/bluez/agent/wizard
bluetoothd[14894]: Removing temporary device 00:1E:3D:15:0A:4F
bluetoothd[14894]: Removing device /org/bluez/hci0/dev_00_1E_3D_15_0A_4F

[-- Attachment #3: bluez-build-v0.0.2j.txt --]
[-- Type: text/plain, Size: 4538 bytes --]

#!/bin/bash # just for highlighting

# creator: Jelle de Jong <jelledejong at powercraft dot com>

cat /proc/version
Linux version 2.6.26-1-686 (Debian 2.6.26-8) (waldi@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Oct 9 15:18:09 UTC 2008

sudo apt-get remove --purge bluetooth-alsa bluez-audio bluez-gnome bluez-hcidump bluez-utils
sudo apt-get remove --purge libbluetooth2

sudo apt-get install dpkg-dev
sudo apt-get install bison flex cdbs
sudo apt-get install autotools-dev libdbus-1-dev libdbus-glib-1-dev libusb-dev libglib2.0-dev libasound2-dev

sudo apt-get install git-core automake autoconf libtool intltool

sudo apt-get install libxml-libxml-perl libgtk2.0-dev libglib2.0-dev libnotify-dev-gtk2.10 libgconf2-dev libhal-dev

------------------------------------------------------------------------

cd $HOME
sudo rm --recursive bluez
git clone git://git.kernel.org/pub/scm/bluetooth/bluez.git

cd $HOME
cd bluez
aclocal
autoheader
libtoolize
automake --add-missing
autoconf
./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --libexecdir=/lib --disable-initscripts --enable-obex --enable-cups --enable-hid2hci --disable-sdpd --enable-glib --enable-pcmciarules --enable-audio --enable-alsa --enable-hidd --enable-pand --enable-dund
make
rm --recursive $HOME/bluez-utils-svn/
mkdir $HOME/bluez-utils-svn/
make install DESTDIR=$HOME/bluez-utils-svn/

cd $HOME/bluez-utils-svn/
mkdir DEBIAN
chmod 0755 DEBIAN
echo 'Package: bluez-utils
Version: 4.13svn
Priority: optional
Architecture: i386
Maintainer: Jelle de Jong <jelledejong@tuxcrafter.net>
Depends: module-init-tools, makedev (<< 3.3.8.2-0) | udev, lsb-base (>= 3.0-3), dbus
Description: Bluez bluetooth userspace modules
 This package contains userspace modules for using Bluetooth devices.
 .
 BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source
 project distributed under GNU General Public License (GPL).' > DEBIAN/control

cd $HOME
dpkg -b $HOME/bluez-utils-svn/ $HOME/bluez-utils_4.13svn_i386.deb

sudo dpkg -i $HOME/bluez-utils_4.13svn_i386.deb
sudo ldconfig -v

------------------------------------------------------------------------

cd $HOME
sudo rm --recursive bluez-gnome
git clone git://git.kernel.org/pub/scm/bluetooth/bluez-gnome.git

cd $HOME
cd bluez-gnome
aclocal
autoheader
libtoolize
intltoolize
automake --add-missing
autoconf
./configure ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --enable-maintainer-mode --disable-mime-update --disable-desktop-update
make
mkdir $HOME/bluez-gnome-svn/
make install DESTDIR=$HOME/bluez-gnome-svn/

# note:
# ./configure --help

cd $HOME/bluez-gnome-svn/
mkdir DEBIAN
chmod 0755 DEBIAN
echo 'Package: bluez-gnome
Priority: optional
Section: admin
Installed-Size: 45
Maintainer: Jelle de Jong <jelledejong@tuxcrafter.net>
Version: 1.8svn
Architecture: i386
Depends: lsb-base, module-init-tools, dbus, udev
Description: Bluetooth tools and daemons
 This package contains tools and system daemons for using Bluetooth devices.
 .
 BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source
 project distributed under GNU General Public License (GPL).' > DEBIAN/control

cd $HOME
dpkg -b $HOME/bluez-gnome-svn/ $HOME/bluez-gnome_1.8svn_i386.deb

sudo dpkg -i $HOME/bluez-gnome_1.8svn_i386.deb
sudo ldconfig -v

------------------------------------------------------------------------

sudo dpkg --remove bluez-utils
sudo dpkg --remove bluez-gnome
sudo rm -r /var/lib/bluetooth/*

sudo hciconfig hci0 up

hcitool scan
Scanning ...
    00:0B:0D:89:5B:77   HOLUX GPSlim236
    20:07:09:15:A9:5A   Samsung WEP210
    11:11:11:11:17:95   Trust Mouse 15606
    00:07:61:0F:4A:60   Logitech Cordless Presenter
    00:53:53:FB:7E:9C   Nokia BH-801
    00:0C:55:D1:C9:78   Motorola S805
    00:0D:FD:18:6E:3C   Motorola S9
    00:18:83:10:00:92   Bluetooth Presenter
    00:1E:3D:15:0A:4F   BD Remote Control

# note:
# check that your initscripts are using the currect options as example
# ps -aux | grep hcid
# /usr/sbin/hcid -x -s

sudo /etc/init.d/dbus start
sudo /usr/sbin/bluetoothd --nodaemon --debug

sudo hciconfig hci0 up
hcitool scan
Scanning ...
    00:1E:3D:15:0A:4F   BD Remote Control

sudo hidd --connect 00:1E:3D:15:0A:4F

Oct 15 13:23:56 debian-eeepc hidd: New HID device 00:1E:3D:15:0A:4F (Sony Computer Entertainment Inc BD Remote Control)
Oct 15 13:23:56 debian-eeepc kernel: [13983.397665] input: Sony Computer Entertainment Inc BD Remote Control as /class/input/input13


[-- Attachment #4: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #5: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Sony Bluetooth BD Remote Control

[Bastien Nocera]

On Wed, 2008-10-15 at 14:51 +0200, Jelle de Jong wrote:
<snip>
> I have been working hard to get the bluetooth remote working, but
> without success. I build new non official debian packages of the latest
> git. I installed them with success. Loaded the new daemon tried to
> connect with the bluetooth-wizard but it will not pair/connect. With the
> hidd system is does connect but the situation is exactly the same as
> with the ordinal report.
> 
> What commands are needed to get the device working? I would like to be
> able to use xbindings --key to attach commands/keybindings to the keys.
> 
> See the attachment for all the steps I did, the new trials are on the
> end of the documents.

I mentioned it in the past, I'll mention it again: DO NOT USE HIDD.

It doesn't have support for the PS3 BD remote. Make sure you have the
latest git, I fixed the input event generation for the remote yesterday.

Cheers


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Sony Bluetooth BD Remote Control

[Jelle de Jong]

Bastien Nocera wrote:
> On Wed, 2008-10-15 at 14:51 +0200, Jelle de Jong wrote:
> <snip>
>> I have been working hard to get the bluetooth remote working, but
>> without success. I build new non official debian packages of the latest
>> git. I installed them with success. Loaded the new daemon tried to
>> connect with the bluetooth-wizard but it will not pair/connect. With the
>> hidd system is does connect but the situation is exactly the same as
>> with the ordinal report.
>>
>> What commands are needed to get the device working? I would like to be
>> able to use xbindings --key to attach commands/keybindings to the keys.
>>
>> See the attachment for all the steps I did, the new trials are on the
>> end of the documents.
> 
> I mentioned it in the past, I'll mention it again: DO NOT USE HIDD.
> 
> It doesn't have support for the PS3 BD remote. Make sure you have the
> latest git, I fixed the input event generation for the remote yesterday.
> 
> Cheers

I only used the hidd as extra testing after I tried the new way, I
cloned the git this morning and I saw the new commits. Can you see why
it does not want to connect? I attached all the debug log in my previous
mail, please help. (I am on a deadline to get this fully working before
the 20th 5 days remaining)

I only used hidd as extra testig and used /usr/sbin/bluetoothd with
/usr/bin/bluetooth-applet to connect to the remote but it would not
pair, please see the logs, if I can provide more or better information
please tell me how.

I can be contacted on chat.freenode.net as tuxcrafter, we can work on it
together if wanted.

Kind regards,

Jelle

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] [PATCH] Re: Sony Bluetooth BD Remote Control

[Bastien Nocera]

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Wed, 2008-10-15 at 14:54 +0100, Bastien Nocera wrote:
> On Wed, 2008-10-15 at 14:51 +0200, Jelle de Jong wrote:
> <snip>
> > I have been working hard to get the bluetooth remote working, but
> > without success. I build new non official debian packages of the latest
> > git. I installed them with success. Loaded the new daemon tried to
> > connect with the bluetooth-wizard but it will not pair/connect. With the
> > hidd system is does connect but the situation is exactly the same as
> > with the ordinal report.
> > 
> > What commands are needed to get the device working? I would like to be
> > able to use xbindings --key to attach commands/keybindings to the keys.
> > 
> > See the attachment for all the steps I did, the new trials are on the
> > end of the documents.
> 
> I mentioned it in the past, I'll mention it again: DO NOT USE HIDD.
> 
> It doesn't have support for the PS3 BD remote. Make sure you have the
> latest git, I fixed the input event generation for the remote yesterday.

As it's just the pairing that doesn't work, the bug was in the wizard.
The code to restrict the PS3 detection to a particular OUI was causing
problems.

Patch attached.

[-- Attachment #2: 0001-Add-another-OUI-for-the-PS3-BD-Remote.patch --]
[-- Type: text/x-patch, Size: 938 bytes --]

>>From f774ba3252faf2eb49374f53b6c1d3883a99f45b Mon Sep 17 00:00:00 2001
From: Bastien Nocera <hadess@hadess.net>
Date: Wed, 15 Oct 2008 16:07:38 +0100
Subject: [PATCH] Add another OUI for the PS3 BD Remote

Should fix pairing for this type of remote:
http://thread.gmane.org/gmane.linux.bluez.devel/16132/focus=16143
---
 wizard/main.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/wizard/main.c b/wizard/main.c
index 0854913..aba800b 100644
--- a/wizard/main.c
+++ b/wizard/main.c
@@ -209,7 +209,8 @@ static void prepare_callback(GtkWidget *assistant,
 			path = NULL;
 
 		/* Sony PlayStation 3 Remote Control */
-		if (g_str_has_prefix(target_address, "00:19:C1:") == TRUE &&
+		if ((g_str_has_prefix(target_address, "00:19:C1:") == TRUE ||
+		     g_str_has_prefix(target_address, "00:1E:3D:") == TRUE) &&
 					g_str_equal(target_name,
 						"BD Remote Control") == TRUE)
 			path = NULL;
-- 
1.5.5.2


[-- Attachment #3: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [PATCH] Re: Sony Bluetooth BD Remote Control

[Marcel Holtmann]

Hi Bastien,

> > > I have been working hard to get the bluetooth remote working, but
> > > without success. I build new non official debian packages of the latest
> > > git. I installed them with success. Loaded the new daemon tried to
> > > connect with the bluetooth-wizard but it will not pair/connect. With the
> > > hidd system is does connect but the situation is exactly the same as
> > > with the ordinal report.
> > > 
> > > What commands are needed to get the device working? I would like to be
> > > able to use xbindings --key to attach commands/keybindings to the keys.
> > > 
> > > See the attachment for all the steps I did, the new trials are on the
> > > end of the documents.
> > 
> > I mentioned it in the past, I'll mention it again: DO NOT USE HIDD.
> > 
> > It doesn't have support for the PS3 BD remote. Make sure you have the
> > latest git, I fixed the input event generation for the remote yesterday.
> 
> As it's just the pairing that doesn't work, the bug was in the wizard.
> The code to restrict the PS3 detection to a particular OUI was causing
> problems.

I added the extra OUI. Thanks.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [PATCH] Re: Sony Bluetooth BD Remote Control

[Jelle de Jong]

Marcel Holtmann wrote:
> Hi Bastien,
> 
>>>> I have been working hard to get the bluetooth remote working, but
>>>> without success. I build new non official debian packages of the latest
>>>> git. I installed them with success. Loaded the new daemon tried to
>>>> connect with the bluetooth-wizard but it will not pair/connect. With the
>>>> hidd system is does connect but the situation is exactly the same as
>>>> with the ordinal report.
>>>>
>>>> What commands are needed to get the device working? I would like to be
>>>> able to use xbindings --key to attach commands/keybindings to the keys.
>>>>
>>>> See the attachment for all the steps I did, the new trials are on the
>>>> end of the documents.
>>> I mentioned it in the past, I'll mention it again: DO NOT USE HIDD.
>>>
>>> It doesn't have support for the PS3 BD remote. Make sure you have the
>>> latest git, I fixed the input event generation for the remote yesterday.
>> As it's just the pairing that doesn't work, the bug was in the wizard.
>> The code to restrict the PS3 detection to a particular OUI was causing
>> problems.
> 
> I added the extra OUI. Thanks.
> 
> Regards
> 
> Marcel
> 

Thank you all for the patches and the support, after rebuilding
everything and trying things out. The bluetooth-applet wizzard system
tolled me it connected successfully. See the log below.

However how can I know actually use the device? I tried xbindings --key
to catch a key and bind it to something useful. I feel like I am back to
point one with the old hidd system...

bluetoothd[10832]: Discovery session 0xb9409040 with :1.8 activated
bluetoothd[10832]: session_ref(0xb9409040): ref=1
bluetoothd[10832]: session_unref(0xb9409040): ref=0
bluetoothd[10832]: Discovery session 0xb9409040 with :1.8 deactivated
bluetoothd[10832]: Stopping discovery
bluetoothd[10832]: create_device(00:1E:3D:15:0A:4F)
bluetoothd[10832]: Creating device /org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[10832]: adapter_get_device(00:1E:3D:15:0A:4F)
bluetoothd[10832]: Probe drivers for /org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[10832]: hid_device_probe: path
/org/bluez/hci0/dev_00_1E_3D_15_0A_4F
bluetoothd[10832]: Registered interface org.bluez.Input on path
/org/bluez/hci0/dev_00_1E_3D_15_0A_4F

Best regards,

Jelle

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] [PATCH] Re: Sony Bluetooth BD Remote Control

[Bastien Nocera]

On Wed, 2008-10-15 at 20:02 +0200, Jelle de Jong wrote:
<snip>
> Thank you all for the patches and the support, after rebuilding
> everything and trying things out. The bluetooth-applet wizzard system
> tolled me it connected successfully. See the log below.
> 
> However how can I know actually use the device? I tried xbindings --key
> to catch a key and bind it to something useful. I feel like I am back to
> point one with the old hidd system...

Then you need something that can listen to the event from the Linux
input layer device. On Fedora it will probably be through lirc, and
gnome-lirc-properties:
http://bugzilla.gnome.org/show_bug.cgi?id=555802

If your setup isn't customised, you should at least see some keys as
having keysyms under X. Launch xev and press the "Play" key.

But you'll see that something like lirc will be necessary to take full
advantage of the remote.

Cheers


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel