2005-09-21 16:24:38

by Roland Lezuo

[permalink] [raw]
Subject: [Bluez-users] No audio, just noise with btsco

I have the following BT headset:

Requesting information ...
BD Address: 00:09:DD:30:65:2B
Device Name: BT Headset
LMP Version: 1.1 (0x1) LMP Subversion: 0x434
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <park state> <RSSI> <channel
quality>
<SCO link> <HV2 packets> <HV3 packets> <u-law log>
<A-law log>
<CVSD> <paging scheme> <power control> <transparent SCO>


I managed to compile snd-bt-sco.ko and btsco

./btsco -v 00:09:DD:30:65:2B
btsco v0.4c
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
^^
when playing something with aplay -D plughw:Headset sound.wav btsco says

speaker volume: 12 mic volume: 1
i/o needed: connecting sco...
connected SCO channel
Done setting sco fd
recieved AT+VGS=12
Sending up speaker change 12
^^
I hear increased noise but no sound. When aborting btsco says:

speaker volume: 12 mic volume: 1
driver is not in use
disconnected SCO channel
^^

from dmesg I get:
snd-bt-sco: playback_open
snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 2000
snd-bt-sco: playback_trigger 1
snd-bt-sco: setting playback to bspcm
snd-bt-sco: playback_trigger 0
snd-bt-sco: setting playback to NULL
snd-bt-sco: Disposing of previous socket count 3
snd-bt-sco: file_count is 2 (expected 3)
^^

I found a posting on bluez-users pointing to
http://sourceforge.net/mailarchive/message.php?msg_id=11431438
(http://sourceforge.net/mailarchive/message.php?msg_id=11487825)
but this did not work for me. Anyone having any hints?

regards
roland lezuo


Attachments:
smime.p7s (3.43 kB)
S/MIME Cryptographic Signature

2005-09-22 01:14:19

by Brad Midgley

[permalink] [raw]
Subject: Re: [Bluez-users] No audio, just noise with btsco

Roland

> here is something written about SCO link cap.

Yes, the capability is there but the linux driver can't exploit it. If
you have a usb adapter, there's no pain in replacing it but if it's a
builtin adapter or on an embedded board then yes it is a real problem.

Brad


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

2005-09-21 22:09:16

by Roland Lezuo

[permalink] [raw]
Subject: Re: [Bluez-users] No audio, just noise with btsco


here is something written about SCO link cap.

sudo hciconfig hci0 features
hci0: Type: USB
BD Address: 00:0A:3A:65:83:84 ACL MTU: 377:10 SCO MTU: 16:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power
control>
<transparent SCO> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <AFH cap. slave> <AFH cap. master>


regards
roland lezuo


Attachments:
smime.p7s (3.43 kB)
S/MIME Cryptographic Signature

2005-09-21 21:56:14

by Roland Lezuo

[permalink] [raw]
Subject: Re: [Bluez-users] No audio, just noise with btsco

> As root(!) run "/usr/sbin/hciconfig hci0 revision"


hci0: Type: USB
BD Address: 00:0A:3A:65:83:84 ACL MTU: 377:10 SCO MTU: 16:0
Firmware 0.3 / 9


> it must say something like "SCO mapping: HCI". If it doesn't say
nope nothing...

...have to get another bluetooth dongle? Or firmware update?

regards
roland lezuo


Attachments:
smime.p7s (3.43 kB)
S/MIME Cryptographic Signature

2005-09-21 21:15:47

by Andreas Beck

[permalink] [raw]
Subject: Re: [Bluez-users] No audio, just noise with btsco

Roland Lezuo <[email protected]> wrote:
> I have the following BT headset:

The more interesting question might be what dongle you have.

It may sound strange, but audio transmission is not supported for all
dongles.

As root(!) run "/usr/sbin/hciconfig hci0 revision"

it must say something like "SCO mapping: HCI". If it doesn't say
anything about SCO _mapping_, the dongle is the problem. Don't get
confused with the SCO MTU that will always be displayed.

See also: http://bluetooth-alsa.sourceforge.net/ Section Discussion

> RFCOMM channel 1 connected
> ^^

Yeah - that's only control channel. Bit me, too.


CU, Andy


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users