linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Kamens <jik@kamens.us>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: HFP/HSP Telephony profile doesn't work with Bluetooth USB dongle
Date: Fri, 15 Mar 2013 09:30:51 -0400	[thread overview]
Message-ID: <5143228B.1000405@kamens.us> (raw)
In-Reply-To: <512E15F5.4010909@kamens.us>

FYI, the folks at BlueRigger sent me BTD-300 ("Product=Broadcom Bluetooh 
3.0 Device" in usb-devices output, as opposed to "Product=BCM20702A0" 
for the BTD-400 that wasn't working with HSP/HFP), and it works with 
HSP/HFP just fine.

This means I've got one USB Bluetooth dongle (the BTD-300) that works 
with the HSP/HFP profile, and two that don't (the BTD-400 and a cheap 
Cambridge Research dongle).

In the spirit of supporting open source software, I am willing to mail 
either or both of the dongles that don't work with HSP/HFP at my expense 
to anyone on this list who is willing to commit to (a) checking whether 
this problem still exists with the most recent kernel and bluez code) 
and (b) debugging and fixing it if it does. You can keep the dongles.

If you are willing to commit to doing these things, send me your mailing 
address in private email and let me know whether you want just one of 
the dongles or both of them.

Bonus points if you're willing to specifically make sure it works with 
Fedora 19, which just went into early testing, but I won't make that a 
hard requirement for the free dongles. :-)

Thanks,

Jonathan Kamens


      reply	other threads:[~2013-03-15 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 19:39 HFP/HSP Telephony profile doesn't work with Bluetooth USB dongle Jonathan Kamens
2013-02-24  4:28 ` Jonathan Kamens
2013-02-24 14:59 ` Anderson Lizardo
2013-02-24 21:14   ` Jonathan Kamens
2013-02-25  9:25     ` Luiz Augusto von Dentz
2013-02-27 14:19       ` Jonathan Kamens
2013-03-15 13:30         ` Jonathan Kamens [this message]

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=5143228B.1000405@kamens.us \
    --to=jik@kamens.us \
    --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;
as well as URLs for NNTP newsgroup(s).