Re: Does not work BT headset

On Thu, 28 Aug 2008, pramod gurav wrote:

-> Send the output  of
-> $ hcitool conn
-> It should show both SCO and ACL connections.
-> 
-> and have you run 
-> $ passkey-agent --default 0000 &
-> try running this. This is way to set the PIN for authentication.
->  And how do you connect before running mplayer?
-> When you run mplayer it will automatically establish connection. So no need to do it manually if you are doing so.

The audio player should make the connection itself, I think. Also, he seems to 
have the passkey-agent:

-> Aug 27 19:08:10 darkstar hcid[5728]: Default passkey agent (:1.43,
-> /org/bluez/passkey_agent_5737) registered


I've always used it like so:

passkey-agent --default 0000 <bt address of remote device> &


Does it work with no remote address specified (could be)?


I think it's the auth-agent that is not running. It may be needed. I always 
start this too.

auth-agent &

Here:

-> Aug 27 19:12:13 darkstar audio[5741]: Access denied: Authorization agent
-> does not exist


Is the headset an older Bluetooth 1.* device, or the newer 2.*? If it's 1.*, 
then it won't work without patching the kernel.




-------------------------------------------------------------------------
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=/