public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: BlueZ 4.26 : headset profile
Date: Tue, 13 Jan 2009 10:03:25 +0100	[thread overview]
Message-ID: <59B9EB12-3290-4428-A7BF-04E115C9B55D@gmail.com> (raw)
In-Reply-To: <e6fea9c20901130025w21145356yacf4a4d051033e76@mail.gmail.com>

Hi,

On Jan 13, 2009, at 9:25, Thierry Pierret wrote:
> I wish my computer to play the role of a headset, with the aim to play
> music from my bluetooth-capable player onto the computer soundcard.

That's not implemented right now so it won't work. There's an  
experimental patch available (with the misleading subject "Gateway  
profile") on this list which hasn't been accepted upstream yet (since  
there are just too many issues with it).

> First I had to enable the "Gateway" option in the "audio.conf" file in
> order to get the Headset service exposed. By the same way, you must
> enable the "Headset" option in order to be an audio gateway). It
> sounds already weird to me.

Yeah, I know it's a little bit counterintuitive. The reason is mainly  
historical. What the option is referring to is which D-Bus interfaces  
should be enabled for remote devices objects. I.e. "Headset" enables  
support for the org.bluez.Headset interface on remote device objects  
(i.e. allows remote devices that support the Headset/Handsfree role to  
be used).

Johan

      reply	other threads:[~2009-01-13  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  8:25 BlueZ 4.26 : headset profile Thierry Pierret
2009-01-13  9:03 ` Johan Hedberg [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=59B9EB12-3290-4428-A7BF-04E115C9B55D@gmail.com \
    --to=johan.hedberg@gmail.com \
    --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