From: Jim Carter <jimc@math.ucla.edu>
To: Kevin Fenzi <kevin@scrye.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth headset not working
Date: Fri, 19 Oct 2007 09:03:43 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710190839510.16412@simba.math.ucla.edu> (raw)
In-Reply-To: <20071018124830.58d558be@ghistelwchlohm.scrye.com>
On Thu, 18 Oct 2007, Kevin Fenzi wrote:
> On Thu, 18 Oct 2007 10:59:50 -0700 (PDT)
> Jim Carter <jimc@math.ucla.edu> wrote:
> > 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.
The ones with 2 earpieces and a mass of about 100 grams invariably (?) do
A2DP which transmits stereo at 44100 Hz or 48000 Hz, compressed with the
SBC codec. The single-ear ones with a mass of about 20 grams invariably
(?) do HSP/HFP, monaural at 8000 Hz, I think uncompressed. That would be
your Jabra BT 250v. Some but not all of the music headsets can switch
protocols and have call control buttons for HFP; these are advertised as
"works with Skype".
So the Jabra is capable of doing the HSP protocol, and when the message
says the protocol is "not available", the problem is likely not in the
headset. Not likely that the headset is broken or has buggy firmware, but
just for paranoia, it would be a good data point if the same message were
seen with a different headset.
I've seen a similar message when I didn't have bluetoothd-service-audio
configured to autostart and forgot to start it manually. Do you have the
corresponding protocol/profile daemon running? I don't have my laptop
handy to look up the name of this daemon but I think it's
bluetoothd-service-sco. This is in bluez-utils-3.19 (3.20 is latest;
probably came in at 3.16.)
Unfortunately that's about the limit of my expertise, since I haven't
messed with the HSP/HFP feature of the Motorola HT-820 that I have.
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: jimc@math.ucla.edu http://www.math.ucla.edu/~jimc (q.v. for PGP key)
-------------------------------------------------------------------------
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/
_______________________________________________
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-19 16:03 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
2007-10-19 16:03 ` Jim Carter [this message]
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=Pine.LNX.4.64.0710190839510.16412@simba.math.ucla.edu \
--to=jimc@math.ucla.edu \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kevin@scrye.com \
/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