From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] failed PIN Code Request
Date: Mon, 11 Feb 2008 16:00:40 -0200 [thread overview]
Message-ID: <47B08D48.7020202@aircable.net> (raw)
In-Reply-To: <200802111731.m1BHVQ9I009663@alumnus.caltech.edu>
Russell A. Bell escribi=F3:
> Quoth Manuel Naranjo:
> 'If I'm not wrong it's not your headset the one that closes the
> connection, but rather the kernel.
> Solution:
> ADDR=3D<SOMETHING> hcitootl cc $ADDR; hcitool auth $ADDR
> Still not the preferred way but it works.'
> I interpret the contents of hcidump to indicate that the
> kernel closes the connection. I wonder why. What you proposed
> doesn't work for me.
> =
Russel is it much asking that you don't break the threads? It's hard to
track your mails.
If this doesn't work, then you have something else going on, maybe
you're missing the passkey agent or something.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-11 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 17:31 [Bluez-users] failed PIN Code Request Russell A. Bell
2008-02-11 18:00 ` Manuel Naranjo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 17:31 Russell A. Bell
2008-02-09 3:47 [Bluez-users] failed PIN Code Request (Marcel Holtmann) Russell A. Bell
2008-02-09 5:02 ` [Bluez-users] failed PIN Code Request jayjwa
2008-02-09 12:13 ` Manuel Naranjo
2008-02-09 20:52 ` Brian Sammon
2008-02-05 21:08 Russell A. Bell
2008-02-06 9:24 ` Marcel Holtmann
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=47B08D48.7020202@aircable.net \
--to=manuel@aircable.net \
--cc=bluez-users@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