From: Johan Hedberg <johan.hedberg@nokia.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Disconnect eSCO link from Command line
Date: Wed, 28 Jan 2009 13:25:04 +0200 [thread overview]
Message-ID: <20090128112504.GA22536@localhost> (raw)
In-Reply-To: <c2a31c480901280142n2cb0c2bbh9eb3a96075d21f21@mail.gmail.com>
On Wed, Jan 28, 2009, sreevani medhahal wrote:
> > On Wed, Jan 28, 2009, sreevani medhahal wrote:
> >> After the headset has created the eSCO link. The Profile Tuning
> >> Suite asks for Closing the Audio Connection from AG. Is there any
> >> command line utiility to disable the eSCO link & not the service level
> >> connection(ACL).[The eSCO link is visible on giving hcitool con ]
> >
> > You can do that by calling the Stop D-Bus method call on the
> > org.bluez.Headset interface of the corresponding device object. You can
> > e.g. use the test/test-telephony python script for this:
> > ./test-telephony stop <remote address>
> >
> The above method does not close the eSCO link ,because the
> sco_connect_cb has reported connection timed out. but the hcitool con
> still lists the eSCO link.
> I have another query bluez4.2x is compatible with which linux kernel
> version. does it have any strict requirement that it works best only
> if the kernel version is >= 2.6.27 .
You might want to try Marcel's bluetooth-testing tree. I think that
issue might be fixed by the following patch:
http://git.kernel.org/?p=linux/kernel/git/holtmann/bluetooth-testing.git;a=commitdiff;h=d7461bfbd48bb76a1126a4f05bb16e4bb0187d31
Johan
next prev parent reply other threads:[~2009-01-28 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 5:16 Disconnect eSCO link from Command line sreevani medhahal
2009-01-28 5:39 ` Marcel Holtmann
2009-01-28 9:37 ` sreevani medhahal
2009-01-28 9:57 ` Marcel Holtmann
2009-01-28 8:23 ` Johan Hedberg
2009-01-28 9:42 ` sreevani medhahal
2009-01-28 11:25 ` Johan Hedberg [this message]
2009-01-30 9:57 ` sreevani medhahal
2009-01-30 12:18 ` sreevani medhahal
2009-02-01 16:57 ` Marcel Holtmann
2009-02-01 16:56 ` Marcel Holtmann
2009-02-03 6:04 ` sreevani medhahal
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=20090128112504.GA22536@localhost \
--to=johan.hedberg@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.