From: "dong yan" <semiydsemiyd@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO connection timed out issue
Date: Fri, 19 Oct 2007 10:24:58 +0800 [thread overview]
Message-ID: <194c6ea30710181924x2de24e87i7df6352a7114f5b9@mail.gmail.com> (raw)
In-Reply-To: <d89ddf300710181026y23897b7eqb542f3adf7bfd35f@mail.gmail.com>
Hi Brad:
You are right.I launched passkey-agent with the command
"passkey-agent --default 8888 &". After that ,i deleted the headset
related linkcode in the /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/pincodes.
Now hcid looks for the linkcode from passkey-agent.
Here:
hcid[306]: link_key_request (sba=00:80:E1:00:AB:BA,
dba=00:0D:3C:EB:53:F0) hcid[306]: pin_code_request
(sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0) hcid[306]: Calling
PasskeyAgent.Request: name=:1.3, path=/org/bluez/passkey_agent_328
Passkey request for device 00:0D:3C:EB:53:F0
hcid[306]: link_key_notify (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
hcid[306]: link_key_request (sba=00:80:E1:00:AB:BA,
dba=00:0D:3C:EB:53:F0) The pairing procedure to the headset is now
handled by passkey-agent. Seems like hcid will search the linkcode
firstly in that 'pincodes' file. If he didn't find one ,he will turn
to the passkey-agent and ask for the code.
thanks
semiyd
2007/10/19, Brad Midgley <bmidgley@gmail.com>:
> semiyd,
>
> fyi you get unpredictable behavior if you change stuff in
> /var/lib/bluetooth manually.
>
> brad
>
> On 10/18/07, semiyd@hotmail.com <semiyd@hotmail.com> wrote:
> >
> > Hi Brad:
> > No , i didn't start up the passkey agent:)
> > In /etc/bluetooth/hcid.conf ,my configuration is "security auto;"
> > I manually created a file named 'pincodes' in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/ and put the linkcode
> > in it . So that hcid will find the linkcode when requested by the headset.
> >
> > thanks
> >
> > semiyd
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-19 2:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 1:36 [Bluez-devel] SCO connection timed out issue \x11
2007-10-18 1:49 ` Brad Midgley
2007-10-18 2:46 ` \x11
2007-10-18 3:14 ` \x11
2007-10-18 13:24 ` Brad Midgley
2007-10-18 13:46 ` \x11
2007-10-18 17:26 ` Brad Midgley
2007-10-19 2:24 ` dong yan [this message]
2007-10-18 10:31 ` Fabien Chevalier
2007-10-18 12:13 ` \x11
2007-10-18 12:33 ` \x11
2007-10-18 13:08 ` Fabien Chevalier
2007-10-19 3:16 ` \x11
2007-10-19 5:55 ` \x11
2007-10-20 8:05 ` \x11
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=194c6ea30710181924x2de24e87i7df6352a7114f5b9@mail.gmail.com \
--to=semiydsemiyd@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox