From: Zhu Yanhai <zhu.yanhai@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
pulseaudio-discuss@mail.0pointer.de, vivian.zhang@intel.com,
guannan.ou@intel.com, Zheng Huan <huan.zheng@intel.com>,
Zhu Yanhai <yanhai.zhu@linux.intel.com>,
"Zhu, Yanhai" <yanhai.zhu@intel.com>
Subject: Re: Is hsp code in BlueZ and pulseaudio broken?
Date: Tue, 13 Apr 2010 15:52:19 +0800 [thread overview]
Message-ID: <p2o977a2be21004130052y6dc9af81n344d91dc8aecd9d8@mail.gmail.com> (raw)
In-Reply-To: <h2i2d5a2c101004090532o6c7e33a4k7563fe8f628f3d6f@mail.gmail.com>
Hi,
I think this bug is caused by the buggy implement of eSCO on the Dell
BH200 headset. After echo 'Y' > /sys/module/sco/parameters/disable_esco,
everything is OK then.
Thanks,
Zhu Yanhai
2010/4/9 Luiz Augusto von Dentz <luiz.dentz@gmail.com>:
> Hi,
>
> On Fri, Apr 9, 2010 at 11:35 AM, Zhu Yanhai <zhu.yanhai@gmail.com> wrote:
>> 'hcitool con' reported there was no connections after that, and the
>> headset was power off automatically. And of course I can't see this
>> headset by
>> 'ilst-cards' or 'list-sinks' in pacmd.
>>
>> Is it because there is anything broken in the latest BlueZ +
>> Pulseaudio, or am I doing something wrong?
>
> It seems ok in bluetoothd size, maybe it is the suspend logic that
> disconnect sco after a few seconds when idle, but it doesn't seems to
> be the case here as also rfcomm connection is dropped somehow.
>
> --
> Luiz Augusto von Dentz
> Computer Engineer
>
prev parent reply other threads:[~2010-04-13 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 8:35 Is hsp code in BlueZ and pulseaudio broken? Zhu Yanhai
2010-04-09 12:32 ` Luiz Augusto von Dentz
2010-04-13 7:52 ` Zhu Yanhai [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=p2o977a2be21004130052y6dc9af81n344d91dc8aecd9d8@mail.gmail.com \
--to=zhu.yanhai@gmail.com \
--cc=guannan.ou@intel.com \
--cc=huan.zheng@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pulseaudio-discuss@mail.0pointer.de \
--cc=vivian.zhang@intel.com \
--cc=yanhai.zhu@intel.com \
--cc=yanhai.zhu@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).