From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth headset not working
Date: Fri, 19 Oct 2007 19:42:35 +0300 [thread overview]
Message-ID: <C8CB368F-A413-442E-99FA-CF006830DB35@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710190839510.16412@simba.math.ucla.edu>
On Oct 19, 2007, at 19:03, Jim Carter wrote:
> 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.
Actually bluetoothd-service-audio takes care of both A2DP and HSP.
Unless you specified explicitly the profile to use in your .asoundrc
(e.g. "profile a2dp") the selection process goes as such that A2DP is
used if available and otherwise HSP.
Johan
-------------------------------------------------------------------------
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:42 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
2007-10-19 16:42 ` Johan Hedberg [this message]
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=C8CB368F-A413-442E-99FA-CF006830DB35@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=bluez-devel@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