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: Fri, 14 Sep 2007 21:39:37 +0400 [thread overview]
Message-ID: <b5fcf2320709141039mebf6c84vc07e53dee647d8d9@mail.gmail.com> (raw)
In-Reply-To: <6D0501F2-3D13-4229-98A2-D710C0D5B085@cadvium.net>
[-- Attachment #1.1: Type: text/plain, Size: 1775 bytes --]
well
what i do..
in gentoo and testing 2 phones SonyEricsson-w800 and Nokia 5200
install bluez
registered HF service using sdptool
using hcitool and sdptool
finding phone and it rfcomm channel
on phone i set that my pc is can always connect to phone
binding using rfcomm to /dev/rfcomm0
and just using minicom
i even make a stupid script in bash to connect to rfcomm on phone
when the ring comes i try at command to request audio channel
but nothing
maybe same thing foget to tell
2007/9/14, robert <rbscott@cadvium.net>:
>
> Hello Andrey,
>
> let me back up for a second and ask how you are trying to access the
> handsfree?
>
> Is the phone paired with your computer?
> Is the phone paired with your computer as a Handsfree device?
> What kind of phone are you using?
> For your RFCOMM channel, are you connecting to the channel channel
> are you connecting to on the phone?
> How are you handing the RFCOMM processing?
>
> I left out some steps about Service Discovery and Pairing that I
> assumed you already completed.
>
> --robert
>
> On Sep 14, 2007, at 12:39 AM, andrey larin wrote:
>
> > i try to do something similar but
> > last time a wrote programs was wery long ago so
> > i don't understud your code in proper :((
> > but i tried to do as you say
> >
> > and nothing happens
> >
> > coud you explain what your code exactly do ?
> >
> >
>
>
> -------------------------------------------------------------------------
> 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: 2467 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
next prev parent reply other threads:[~2007-09-14 17:39 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
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 [this message]
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=b5fcf2320709141039mebf6c84vc07e53dee647d8d9@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