From: robert <rbscott@cadvium.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] handsfree or headset support on pc
Date: Thu, 13 Sep 2007 18:58:44 -0700 [thread overview]
Message-ID: <AE056821-FE53-4A5B-8761-81908AC41E70@cadvium.net> (raw)
In-Reply-To: <E21A90CDB9591542899EFC7FB4ED5CC90576575C@tfmail02.TFMAIL.COM>
Hello Andrey Larin,
The Headset profile has two sides to it. There is the Audio Gateway
(AG) which is typically a cell phone, and then the Hands-Free unit (HF).
I think there has been a lot of development on the Audio Gateway(AG)
side, because it is really useful to be able to play music on your
computer and have it come out of your bluetooth headphones.
As far as I can tell(and someone please correct me if I am wrong),
there are not as many projects dedicated to implementing the HF side,
this is the side one of the projects i am working on is
implementing. Essentially there are two channels, the RFCOMM channel
which essentially acts as the control channel, and then the SCO
channel which is for sending audio data back and forth. I wrote a
program to handle RFCOMM channel and service discovery in java, and
presently have a basic SCO manager (in c) for the SCO data and am
working on a way to actually play it.
I hope to put the code online soon, but right now I am trying to
learn how to use D-BUS in order to make the two parts communicate
with one another.
Hope that helps,
--robert
On Sep 13, 2007, at 6:45 PM, guoyun wrote:
> Hi andrey larin
>
>> From your description, the headset need to open visibility to be
>> found. Hope this is not your tiny mistake. :-)
>
> Cheers
>
> -Gawain.
>
>
> ________________________________
>
> From: bluez-devel-bounces@lists.sourceforge.net [mailto:bluez-
> devel-bounces@lists.sourceforge.net] On Behalf Of andrey larin
> Sent: Friday, September 14, 2007 4:49 AM
> To: BlueZ development
> Subject: Re: [Bluez-devel] handsfree or headset support on pc
>
>
> after all i see while serching
> i think this:
>
> currently software is able to handle this
> but requred some tuning
>
> but may be i wrong :)
>
> so i more interested in technical details
>
> if you could provide ... some :)
>
> or say that i wrong and there is requerd a lot of coding
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-09-14 1:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 1:45 [Bluez-devel] handsfree or headset support on pc guoyun
2007-09-14 1:58 ` robert [this message]
2007-09-14 5:17 ` andrey larin
2007-09-14 6:22 ` robert
2007-09-14 7:39 ` andrey larin
2007-09-14 16:44 ` robert
2007-09-14 17:39 ` andrey larin
2007-09-14 17:48 ` andrey larin
2007-09-14 18:01 ` robert
2007-09-14 18:31 ` andrey larin
2007-09-14 20:37 ` robert
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 19:34 andrey larin
2007-09-13 19:54 ` robert
2007-09-13 20:48 ` andrey larin
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=AE056821-FE53-4A5B-8761-81908AC41E70@cadvium.net \
--to=rbscott@cadvium.net \
--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