Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

Lars Grunewaldt
2005-01-21T17:04:56Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Pezzei wrote:
| Hi Lars,
|
| Tnx for your reply
|
| Lars Grunewaldt schrieb:
|
| ...
|
|> 3. disconnect the headset by pressing the "connect" button of the
|> headset again. Audio stops working until you "connect" again with the
|> button.
|
|
| like i said, the rfcomm connection is fine: (output from btsco <addr>):

btsco handles rfcomm and sco connections, so...

| Device is 1:0
| Voice setting: 0x0060
| RFCOMM channel 1 connected
| recieved AT+CKPD=200
| opened hwdep
| connected SCO channel
| Setting sco fd
| Done setting sco fd

this looks good.

| after reconnecting via headset:
| disconnected SCO channel
| recieved AT+CKPD=200
| opened hwdep
| Can't connect SCO audio channel
| : Connection timed out

this does not. It should re-connect without problems, but I can't tell
whether this would be solved with mh1-patches or what might causing that
you can't reconnect to the headset.

You can try the patches out, I use them and it works well.

| I guess the Problem has to do with the SCO or ALSA Stuff

sco, not alsa I think. The alsa stuff is only needed to transmit the sco
data to the alsa functions and vice versa, so it's unlikly that the
impossibility of reconnecting on a new sco channel is the problem. More
likely the sco channel is not terminated correctly in the first place.

best regards,
~ Lars

- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8TY3QWC6DTWkDAoRAlCCAJ9CyuecdSlBzOw+WP2AOqK5G0BOoACfWSNH
P0eRv2FWV2wQNyVtdZ3+m9I=
=NCy7
-----END PGP SIGNATURE-----