public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "andrey larin" <ubergitler@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] handsfree or headset support on pc
Date: Thu, 13 Sep 2007 20:48:41 +0000	[thread overview]
Message-ID: <b5fcf2320709131348q162f3edcg728bfe99348694f@mail.gmail.com> (raw)
In-Reply-To: <8F372D8E-8EC4-40E1-9DD6-B95C41EBDB37@cadvium.net>


[-- Attachment #1.1: Type: text/plain, Size: 1384 bytes --]

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

2007/9/13, robert <rbscott@cadvium.net>:
>
> I am working on a project to implement the handsfree profile on a
> pc.  It is still pretty early on, but it is getting there.  A lot of
> the code is written in java, and some of the SCO connection
> management is written in C.  Let me know if you are interested in
> something like that.
>
> cheers,
> --robert
>
>
> On Sep 13, 2007, at 12:34 PM, andrey larin wrote:
>
> > hi i done a lot searching but don't find anything
> > about handsfree or headset profile support on pc ( moble phone uses pc
> > speaker and microphone (so named answer machine ) )
> > so you are the bluez developers
> > maybe you can answer me it is curently possible or not
> >
>
> -------------------------------------------------------------------------
> 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
>

[-- Attachment #1.2: Type: text/html, Size: 2295 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-09-13 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:34 [Bluez-devel] handsfree or headset support on pc andrey larin
2007-09-13 19:54 ` robert
2007-09-13 20:48   ` andrey larin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-14  1:45 guoyun
2007-09-14  1:58 ` robert
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

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=b5fcf2320709131348q162f3edcg728bfe99348694f@mail.gmail.com \
    --to=ubergitler@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