From: Kevin Fenzi <kevin@scrye.com>
To: Jim Carter <jimc@math.ucla.edu>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth headset not working
Date: Thu, 18 Oct 2007 12:48:30 -0600 [thread overview]
Message-ID: <20071018124830.58d558be@ghistelwchlohm.scrye.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710181052500.28683@simba.math.ucla.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
On Thu, 18 Oct 2007 10:59:50 -0700 (PDT)
Jim Carter <jimc@math.ucla.edu> wrote:
> On Thu, 18 Oct 2007, Kevin Fenzi wrote:
>
> > I have setup my ~/.asoundrc.
> > I can play audio to my headset via mplayer or aplay fine.
> > When I try and set twinkle to use the ALSA bluetooth device it seems
> > like it opens the headset, and then it spits out:
> >
> > ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
> > available (92)
>
> aplay or mplayer are talking to the ALSA device that uses the A2DP
> profile. The phone app needs to use the device with the HFP profile.
Humm... do all headsets do A2DP? I thought mine did not.
> It looks like you got that set up in .asoundrc since a plausible
> subroutine is reporting the error. Next question: does your headset
> do HFP, or is it purely a music headset (A2DP)? Some headsets,
> including the Motorola HT820, will auto-switch, but I think not every
> music headset will do so. Hope this helps!
I am using a jabra BT 250v headset.
It's not a music headset.
I have a few more headsets I can dig up here to test with if you think
it's something with the jabra.
kevin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 17:45 [Bluez-devel] bluetooth headset not working Kevin Fenzi
2007-10-18 17:59 ` Jim Carter
2007-10-18 18:48 ` Kevin Fenzi [this message]
2007-10-19 16:03 ` Jim Carter
2007-10-19 16:42 ` Johan Hedberg
2007-10-19 19:23 ` Kevin Fenzi
-- strict thread matches above, loose matches on Subject: below --
2007-10-20 2:10 KyoYin
2007-10-20 12:45 ` Johan Hedberg
2007-10-23 7:13 ` Johan Hedberg
2007-10-23 7:53 ` KyoYin
2007-10-23 10:02 ` Johan Hedberg
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=20071018124830.58d558be@ghistelwchlohm.scrye.com \
--to=kevin@scrye.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jimc@math.ucla.edu \
/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