From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO connection timed out issue
Date: Thu, 18 Oct 2007 11:26:02 -0600 [thread overview]
Message-ID: <d89ddf300710181026y23897b7eqb542f3adf7bfd35f@mail.gmail.com> (raw)
In-Reply-To: <BAY117-W3751B12FFAA024B30DE551C09E0@phx.gbl>
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
next prev parent reply other threads:[~2007-10-18 17:26 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 [this message]
2007-10-19 2:24 ` dong yan
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=d89ddf300710181026y23897b7eqb542f3adf7bfd35f@mail.gmail.com \
--to=bmidgley@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