From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dpd: audio connection breaks every 300 seconds
Date: Mon, 15 Jan 2007 11:24:57 +0100 [thread overview]
Message-ID: <45AB5679.8050606@palmsource.com> (raw)
In-Reply-To: <200701150257.21542.bluez-devel@huitl.de>
Robert,
> A2DPD[155.135]: a2dp_transfer_raw: Wrote -1 not 603 bytes.
The write call returned EAGAIN, so we should resend the data after a while.
> I attached the complete logfile. It was created by a slightly =
modified version
> of a2dpd that tries to resend the data several times (with 1/10/20 us
> delay) - to no avail.
It should succeed if you wait long enough. Set the delay to 2000 and do =
more tries (like 1000). Unfortunately, waiting too much will lead to =
gaps in the sound when this happen.
I think the cause is elsewhere, could you send us the hcidump -V log?
Do you have another program using BlueZ? Another headset to try?
You could try a shorter bitpool (say 32) if your headset supports it to =
save some bandwith.
Fr=E9d=E9ric
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-15 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 1:57 [Bluez-devel] a2dpd: audio connection breaks every 300 seconds Robert Huitl
2007-01-15 7:03 ` [Bluez-devel] RE : " Frederic Dalleau
2007-01-15 10:24 ` Frédéric DALLEAU [this message]
2007-01-15 18:09 ` [Bluez-devel] " Robert Huitl
2007-01-15 18:29 ` Brad Midgley
2007-01-15 18:51 ` Andrew Kohlsmith
2007-01-15 19:01 ` Brad Midgley
2007-01-15 19:23 ` Robert Huitl
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=45AB5679.8050606@palmsource.com \
--to=frederic.dalleau@palmsource.com \
--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.