From: Chris Carlin <carlin@jlab.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth-audio and bug in a2dpd (Patch included)
Date: Sat, 26 May 2007 19:32:37 -0400 [thread overview]
Message-ID: <4658C395.6010908@jlab.org> (raw)
In-Reply-To: <20070526171539.GA16843@kobayashi-maru.wspse.de>
Matthias Hensler wrote:
> Hi!
>
> Playing with the current plugz from CVS and a2dpd I experienced a lot of
> choppy audio with a BW-HF02 bluetooth audio receiver. I tracked down the
> problem to the transmit loop in a2dpd_output_a2dp.c. My receiver has an
> own buffer which runs full after around 3-4 seconds. In that case the
> write will fail with EAGAIN. The loop should take care of that and
> retry, however errno gets lost in the current implementation, so no
> single retry is made.
Great!
This modification made my Motorola S805 headphones usable and my
Creative CB2530 headphones almost so (neither was usable at all before).
I had a feeling it was something sort of small but I was on the wrong
track with finding the cause for the EAGAIN.
~Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-26 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 17:15 [Bluez-devel] bluetooth-audio and bug in a2dpd (Patch included) Matthias Hensler
2007-05-26 23:32 ` Chris Carlin [this message]
2007-05-28 7:44 ` Frederic Dalleau
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=4658C395.6010908@jlab.org \
--to=carlin@jlab.org \
--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.