From: amateur <ztl.post@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] USB dongle failed to pair with headset
Date: Wed, 29 Nov 2006 20:42:16 +0800 [thread overview]
Message-ID: <20061129124216.GC3364@163.com> (raw)
In-Reply-To: <12311.89646.qm@web30509.mail.mud.yahoo.com>
On Wed, Nov 29, 2006 at 01:39:46AM -0800, gary ng wrote:
> Hi,
>
> I just got a no name dongle(CSR chipset) which I
> failed to pair with my headset. I have no problem
> pairing the headset with my t68i and I have no problem
> pairing with the t68i using the dongle.
Sometime ago, I have the same problem with my headset and usb
bluetooth dongle. I solved that by force Security Mode 3 on my usb
dongle which can be reached by using
hciconfig hci0 auth
hciconfig hci0 encrypt
maybe you can try it. Or you can give the result of
hcidump -x -V
when you do
hcitool cc ...
this list has lots of expert here.
>
> I can see the headset but "hcitool info" or "hcitool
> cc" would both fail.
>
> Does the dongle(i.e. firmware on it) play a role in
> whether it can pair with a headset ?
>
> When issuing "hciconfig -a", I don't see the Audio
> service class which I have no idea if it matters or
> not.
>
--
You will soon meet a person who will play an important role in your life.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-11-29 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 9:39 [Bluez-users] USB dongle failed to pair with headset gary ng
2006-11-29 12:42 ` amateur [this message]
2006-11-30 18:50 ` Brad Midgley
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=20061129124216.GC3364@163.com \
--to=ztl.post@gmail.com \
--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