From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Cannot pair A2DP speakers with Belkin Bluetooth adapter
Date: Mon, 4 Aug 2008 11:47:11 +0300 [thread overview]
Message-ID: <77F88439-8777-40C9-BECA-CFF500EE7DEA@gmail.com> (raw)
In-Reply-To: <792645.64581.qm@web52903.mail.re2.yahoo.com>
Hi,
On Aug 4, 2008, at 2:39, Chris Rankin wrote:
> and I cannot pair it with a set of bluetooth A2DP speakers. These
> same speakers work fine with my laptop, which has an internal
> bluetooth device 0x0a5c:0x2110. But whenever I try to pair the
> Belkin device using the commands
>
> $ hcitool cc <bdaddr>
> $ hcitool auth <bdaddr>
>
> then the connection drops after only a few seconds and the pairing
> fails.
For those two low-level test commands the behavior you describe is
perfectly normal and expected. However, they certainly aren't a proper
way to initiate pairing. Where did you get the idea that this is the
right way to do pairing? If it was in some BlueZ documentation we
should fix it ASAP. You might want to check the bluez wiki for some
ways to perform pairing (hint: search for "CreateBonding"):
http://wiki.bluez.org/wiki/HOWTO/Bonding
> Can anyone suggest anything to try in order to keep the BT
> connection up, please? I have already tried adding the flags
> HCI_RESET | HCI_WRONG_SCO_MTU without any effect.
This is not specific in any way to your adapter. You would have gotten
the same behavior with any other adapter as well.
Johan
next prev parent reply other threads:[~2008-08-04 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 23:39 Cannot pair A2DP speakers with Belkin Bluetooth adapter Chris Rankin
2008-08-04 8:47 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-25 20:50 Chris Rankin
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=77F88439-8777-40C9-BECA-CFF500EE7DEA@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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