From: mirko_3 <mirko_3@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco
Date: Sat, 22 Jan 2005 15:19:59 +0100 [thread overview]
Message-ID: <20050122151959.3384d572@mirko_3> (raw)
In-Reply-To: <41F25C4B.6040709@webstuhl.net>
On Sat, 22 Jan 2005 14:59:39 +0100
Ben Pezzei <ben@webstuhl.net> wrote:
> 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 ? :)
Can't help you with the rest, but in xmms you can select the headset...
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-01-22 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 11:44 [Bluez-devel] Again: Problems with Dongle, Headset or btsco Ben Pezzei
2005-01-21 13:07 ` Lars Grunewaldt
2005-01-21 16:08 ` Ben Pezzei
2005-01-21 17:04 ` Lars Grunewaldt
2005-01-21 17:14 ` mirko_3
2005-01-22 13:59 ` Ben Pezzei
2005-01-22 14:19 ` mirko_3 [this message]
2005-01-22 14:40 ` ligi
2005-01-22 15:35 ` [Bluez-devel] " Paul Ionescu
2005-01-22 17:43 ` Ben Pezzei
2005-01-22 19:24 ` [Bluez-devel] " Paul Ionescu
2005-01-22 15:40 ` [Bluez-devel] " Sebastian Roth
2005-01-22 17:50 ` Ben Pezzei
2005-01-23 17:52 ` Lars Grunewaldt
2005-01-24 10:46 ` Ben Pezzei
2005-01-24 11:21 ` Lars Grunewaldt
2005-01-24 12:20 ` Marcel Holtmann
2005-02-02 5:00 ` [Bluez-devel] " Jesse Guardiani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050122151959.3384d572@mirko_3 \
--to=mirko_3@gmx.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.