From: "Dave Schile" <dave@schile.com>
To: linux-bluetooth@vger.kernel.org
Subject: incoming connection conflicting with alsa?
Date: Thu, 1 Jan 2009 12:38:09 -0700 (MST) [thread overview]
Message-ID: <60689.209.216.239.242.1230838689.squirrel@webmail.ipns.com> (raw)
Hello,
I think I'm having a conflict between alsa and my headset device making
its own connection. If there is no connection, programs that are set to
use the alsa bluetooth device connect fine. If I have press the button
on the headset before alsa can connect to it, te device makes its own ACL
connection and alsa becomes unable to get the device.
If alsa makes the connection first then press the button on the headset
the incoming connection takes the place of the alsa connection and alsa
loses the device.
How can I solve this? I've tried a number of hciconfig settings, but the
button press always creates a connection, breaking the alsa one.
Thank you
Dave
next reply other threads:[~2009-01-01 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 19:38 Dave Schile [this message]
2009-01-01 21:25 ` incoming connection conflicting with alsa? Johan Hedberg
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=60689.209.216.239.242.1230838689.squirrel@webmail.ipns.com \
--to=dave@schile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox