#10 problem reconnecting to the same btsco process
Just wanted to send you a quick note to thank you for
the your work on the bluetooth-alsa project, and to
confirm that the I was able to get SCO audio working on
the Bluespoon AX in case you'd like to add it to the
list of supported devices.
The only thing that doesn't work perfectly is that a
given session of btsco will sometimes produce nothing
but noise on the incoming mike. As far as I can tell
this occurs if and only if an attempt is made to use a
given run of btsco for a second connection from the
bluetooth device (first connection works fine, second
and subsequent connections work for BT earpiece but not
headphone). The problem can be solved by starting a
new btsco process.
I'm running fedora core 3 (2.6.10-1.766smp). Output
from btsco one time that this happened is shown below.
There is nothing in /var/log/messages that helps, I
have one message from sdpd that sasy close_sock: Read
error: Connection timed out, but the microphone was
dropped more than once in the relevant interval.
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
speaker volume: 1 mic volume: 1
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=07
Sending up speaker change 7
recieved AT+VGS=08
Sending up speaker change 8
recieved AT+VGS=09
Sending up speaker change 9
recieved AT+VGS=10
Sending up speaker change 10
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=12
Sending up speaker change 12
recieved AT+VGS=13
Sending up speaker change 13
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
recieved AT+CKPD=200
disconnected SCO channel
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
I can't verify whether this occurs with other Bluetooth
headsets as I can't find my other one.
Best,
Rich
Logged In: YES
user_id=17404
btsco has a new option -c to clear up the connection. You
could experiment with that.
By the "second connection" are you talking about using your
bluetooth adapter to connect to something different like a
mouse?
Logged In: YES
user_id=17404
We are testing a change to watch for these audio problems.
I'll attach it here in case you want to try it out for us.