public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Pezzei <ben@webstuhl.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco
Date: Sat, 22 Jan 2005 18:50:44 +0100	[thread overview]
Message-ID: <41F29274.3020909@webstuhl.net> (raw)
In-Reply-To: <csts46$p5n$1@sea.gmane.org>

Hi Sebastian,

Sebastian Roth schrieb:

>> 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
> 
> For older versions of arecord this is the usual behaviour. Update 
> alsa-tools or try the commandline switch '-d' (man arecord).

Well, I'll give it a last try: I'll patch the kernel
with the mh1 patch from bluez and the latest alsa libs.
(currently installed arecord version is 1.0.7 - latest is 1.0.8),
although i doubt this will finally work :)

One very last Question (BT specific):

I upgraded the Dongle on a win xp box to BT 1.2. After reading
the docs, 1.2 has some changes in it regarding Audio which imho
affects the SCO part, right? Does it make sense to downgrade the
dongle to 1.1 (if possible)?

finally, tnx all for your replies & tips

greetings
ben



-------------------------------------------------------
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

  reply	other threads:[~2005-01-22 17:50 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
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 [this message]
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=41F29274.3020909@webstuhl.net \
    --to=ben@webstuhl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox