public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] HFP Status?
Date: Fri, 29 Feb 2008 10:51:51 +0200	[thread overview]
Message-ID: <C3910953-F3FF-4854-971C-9B47AC8C852B@gmail.com> (raw)
In-Reply-To: <b535981e0802290028s22a771bcubbbc9a9fb993d1a7@mail.gmail.com>


On Feb 29, 2008, at 10:28, Jon wrote:
> The end goal of my project is to get some amount of bluetooth  
> handsfree calling built into a carputer (a topic that I'm sure has  
> come up before).  It will be a legal requirement (Shortly) in my  
> state to use hands free while driving.  Really all I need is to be  
> able to answer & end the call - and of course be able to hear/speak  
> to the party.  I'm not sure what would be classified as an  
> "Advanced" feature, but I think I get the gist of it.

Just so we get this clear, do you need the Audio Gateway (AG) or the  
Handsfree (HF) role of HFP? Because what is currently implemented in  
BlueZ is only the AG side (which is the most useful out of the two for  
a PC type device). There are placeholders  for the HF role in the code  
but nothing has been implemented yet (simply because it hasn't been a  
high priority for the developers compared to other Bluetooth audio  
features).

Johan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2008-02-29  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29  5:42 [Bluez-users] HFP Status? Jon
2008-02-29  7:40 ` Johan Hedberg
2008-02-29  8:28   ` Jon
2008-02-29  8:51     ` 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=C3910953-F3FF-4854-971C-9B47AC8C852B@gmail.com \
    --to=johan.hedberg@gmail.com \
    --cc=bluez-users@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