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

[Ben Pezzei <ben@webstuhl.net>]

Hi Lars,

Lars Grunewaldt schrieb:
> | 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.

ok. Is it possible that the SCO Part of this dongle is somehow broken?
Obviously the RFCOMM Part is working fine.

Since the hwdep module is part of the alsa-libs it looks like
the dongle can't be re-initialized (as a soundcard) after a
disconnect.

Question: when connected via btsco and trying to play
some sound with:
aplay -D plughw:Headset soundfile
Does soundfile need to have the correct samplerate,frequency,etc
as the Headset?
I am also able to set speaker and capture volume of the Headset
with alsamixer -c 1

unfortunately
arecord -D plughw:Headset z1.out
Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono

only creates a 44 Byte big file z1.out with the header but
no content

Last Question: Which are other methods to send/receive
data from/to the headset beside aplay / arecord?

eg cat /dev/snd/pcmC1D0c > z1.out ? :)

greetings
b





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel