From: "Peter Hurley" <phurley@charter.net>
To: "'Colin Beckingham'" <colbec@start.ca>,
<linux-bluetooth@vger.kernel.org>
Subject: RE: Bluetooth headsets fail to trigger pulseaudio consistently (Long)
Date: Mon, 16 Nov 2009 13:35:15 -0500 [thread overview]
Message-ID: <007001ca66eb$8c664220$a532c660$@net> (raw)
In-Reply-To: <4B0190D5.8090406@start.ca>
Hi Colin,
> # hcidump -t -X -V
This dump looks truncated. Is this all the output or did the trace
start generating tons of SCO packets that you snipped? There might be
BT commands/replies in the mass of SCO packets that got snipped too.
Also, you need to set the already-running bluetooth daemon into debug
output mode. You can do this with:
sudo kill -SIGUSR2 [pid of bluetoothd]
Then the daemon log will be way more useful - please repost that daemon
log. Also, there's no need to include pulseaudio output because I
virtually guarantee it's just "the messenger".
I noticed the time stamps in the trace and log aren't for the same
interval. The hcidump trace and the daemon log should be for the same
events/time interval, ok?
Regards,
Peter Hurley
next prev parent reply other threads:[~2009-11-16 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 17:50 Bluetooth headsets fail to trigger pulseaudio consistently (Long) Colin Beckingham
2009-11-16 18:35 ` Peter Hurley [this message]
2009-11-17 10:51 ` Colin Beckingham
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='007001ca66eb$8c664220$a532c660$@net' \
--to=phurley@charter.net \
--cc=colbec@start.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox