Bluetooth mouse in Dapper

[Matthew Kuiken]

Matthew Kuiken wrote:
> Sorry to re-post, but I found an error in my previous mail.
>
> Matthew Kuiken wrote:
>> In a terminal, try:
>>
>> sudo hcitool scan
>>
>> While the command is running, press the "Connect" button on your 
>> mouse  (My mouse is a logitech, yours might have a different name for 
>> the button.)
>>
>> The command should output something like this:
>>
>> Scanning ...
>>        00:13:70:4F:83:3B       Nokia HS-26W
>>
>>
>> The set of numbers is the Bluetooth Device Address, bd_addr for short.
>>
>> Running the command:
>>
>> sudo hidd --connect <bd_addr>
>>
>> should connect the mouse to the computer, and allow the mouse to work.
>>
>> If this works, and you want it to do this on power-on, change the 
>> /etc/default/bluez-utils file by:
>>
>> Change:
>> HIDD_ENABLED=0
>> To:
>> HIDD_ENABLED=1
>>
>> Add a line:
>> HIDD_OPTIONS="-i AA:BB:CC:DD:EE:FF --server"
>> with AA:BB:CC:DD:EE:FF being your bd_addr
>
> This should have said:
> Add a line:
> HIDD_OPTIONS="--connect AA:BB:CC:DD:EE:FF --server"
> with AA:BB:CC:DD:EE:FF being your bd_addr
>
>>
>> If the hidd --connect command does not work, it may be the pairing of 
>> your computer with the mouse.  I had already paired the mouse with 
>> the computer in that other OS, so I'm not entirely certain how to 
>> pull it off in Linux.  In theory, the following commands:
>>
>> sudo hcitool cc <bd_addr>
>> sudo hcitool auth <bd_addr>
>>
>> and putting in the pin that the mouse asks for in its documentation 
>> (probably 0000) should pair the devices.
>>
>> I say in theory because I am currently trying to do just that with a 
>> Bluetooth headset, and I am having very little luck.  I have read 
>> that the pin entry in Gnome might be broken, but I cannot find an up 
>> to date source of information.  I am currently trying the KBluetoothD 
>> stuff under Gnome to see if that will do it.
>>
>> I will post back here again once I figure out the pairing.  I may 
>> even try setting up a wiki how-to if the process is sufficiently 
>> difficult to figure out.

I almost feel bad about replying to myself twice, but I did promise to 
post if I figured out the pairing, and I think this is a good thing for 
people to be able to search for...

I had been using the standard hcid.conf file that comes with Dapper, but 
every time I would try the 'sudo hcitools auth <bd_addr>' command to 
pair my headset, I would get the error:
HCI authentication request failed: Input/output error

I believe that this was occurring because of the bluez-pin program, but 
when I would run said program from the command line it worked fine...
I changed the line in the /etc/bluetooth/hcid.conf file from:
       pin_helper /usr/bin/pinwrapper;
to:
        pin_helper /usr/bin/bluepin;

I then ran:
sudo /etc/init.d/bluez-utils stop
sudo /etc/init.d/bluez-utils start

and when I next ran:
sudo hcitool auth <bd_addr>

The pin dialog popped up, and the pairing occurred properly.  My 
bluetooth headset finally works properly, and I am using it with Ekiga.  
It is worth noting that the device that is being auth'd must be 
connected to auth.  Connecting is accomplished by 'sudo hcitool cc 
<bd_addr>'.

Just for completeness, getting the headset to work with Ekiga also 
involves installing the 'bluez-btsco' package, and running:
sudo btsco <bd_addr> <channel>

The command:
sdptool search --bdaddr <baddr> 0x1108

will show what <channel> to use. (under the RFCOMM protocol)

There was another thread named "[OT] wireless headset for it-telephony" 
that this information would be useful for, but I do not believe that the 
information needs to be posted twice.  If people disagree, I will 
re-post it to that thread. 

It's getting pretty late here at the moment, so I won't be doing any 
more with this tonight, but I may make a wiki out of this tomorrow.  
Please let me know if there is any other information that should be 
added to a page of such intent.  Comments about formatting and 
organizing information to make it less confusing are also welcomed.

-Matt