From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dpd: audio connection breaks every 300 seconds
Date: Mon, 15 Jan 2007 11:29:58 -0700 [thread overview]
Message-ID: <45ABC826.10404@xmission.com> (raw)
In-Reply-To: <200701151909.39305.bluez-devel@huitl.de>
Robert
> On the other hand, why is a scan able to interfere with communication? Is this
> behavior by design (because the hardware can only either scan or send/receive
> data)?
a scan hijacks the radio briefly and I believe there is no way around it.
there's one unrelated thing you could try. Do you have any other
bluetooth devices? I had to force my computer to be master in hcid.conf:
lm accept,master;
lp hold,sniff,park;
otherwise moving the bluetooth mouse or using bluetooth dun would
interrupt a2dp.
brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-15 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 1:57 [Bluez-devel] a2dpd: audio connection breaks every 300 seconds Robert Huitl
2007-01-15 7:03 ` [Bluez-devel] RE : " Frederic Dalleau
2007-01-15 10:24 ` [Bluez-devel] " Frédéric DALLEAU
2007-01-15 18:09 ` Robert Huitl
2007-01-15 18:29 ` Brad Midgley [this message]
2007-01-15 18:51 ` Andrew Kohlsmith
2007-01-15 19:01 ` Brad Midgley
2007-01-15 19:23 ` Robert Huitl
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=45ABC826.10404@xmission.com \
--to=bmidgley@xmission.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