08:22 Fri 29 Aug, jayjwa wrote:
> 
> 
> On Thu, 28 Aug 2008, pramod gurav wrote:
> 
> -> Send the output  of
> -> $ hcitool conn
> -> It should show both SCO and ACL connections.
root@darkstar:/etc/bluetooth# hcitool conn
Connections:
:/
For the first time, when I was pair my devices, all was normal.
> -> 
> -> 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> &

It had a crashing after power on headset:
# ps
..
/usr/lib/bluetooth/add-passkey 00:16:8F:DA:83:75
..

after power on headset proccess 'add-passkey' is down and in
/var/log/syslog appears:

Sep  2 22:42:53 darkstar audio[6044]: Access denied: Authorization agent
does not exist
Sep  2 22:42:54 darkstar hcid[6031]: Got NameOwnerChanged signal for
:1.29 which has no listeners

> 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 &
Is it the same 'register-passkeys'? Yes, it running.
> 
> 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.
> 
From documentation to headset: "Bluetooth 2.0 supporting headset and
hands-free profile", dongle support BT 2.0 too.

-- 
Murat D. Kadirov