Hi Dave,
On Jan 1, 2009, at 21:38, Dave Schile wrote:
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.
It shouldn't matter if the headset is already connected or if
bluetoothd needs to create the connection on-demand (when needed by an
alsa application). In both cases the alsa application should be able
to pick up the bluetooth audio stream just fine. Could you post the
output of hcidump -XV when the headset creates a connection to you and
also when you try to use it with alsa after this (which fails)? Any
debug output from bluetoothd when this happens could also help.
One potential cause that comes to my mind is that this headset might
have a buggy HSP implementation (I assume you've got HFP disabled
based on your other email about the AnswerRequested signal which is
only available for HSP connections). Maybe the headset tries to
connect HFP, fails (since you don't have it enabled) but stops there
even though the correct behavior would be to continue trying to
connect HSP instead. Which headset model is this btw?
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
