public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dp, sco and kernel version
Date: Tue, 31 Jul 2007 10:31:46 +0200	[thread overview]
Message-ID: <1185870706.27218.43.camel@ubuntu.mpl.access-company.com> (raw)
In-Reply-To: <46AE7340.4010603@gmail.com>

Hi,

>  I got a much more improved 
> quality audio when using a2dp. Now I really get sound in HiFi.

The nokia guys at indt fixed the sbc codec to get good quality.

> even a2dpd works awfully no, it sounds crappy and 
> disconnects from the headset all the time. 

I'm annoyed by this bug. Several people have been reporting it.
It looks like they all uses kernel 2.6.21 and higher.

A patch has been proposed that you can try by appending
--enable-retrypatch=yes at configure command line. I have not made this
patch default yet because I think it hides the problem.

Now technical question :
A2DPD tries to send each sbc packet at the correct date for playback. To
do this, it uses gettimeofday at the beginning of the stream and if it
is too early to send a packet it will wait for the calculated date.

Sometimes, after a few seconds of playing, the  send() returns EAGAIN.
As if all data were not sent but enqueued, and the queue was full. But
if I send the packet at right date, this queue should not be full.
Most probable is the date of packet sending is bad, but I have checked,
and why would it work with earlier kernels.
Without the patch, a2dpd will disconnect instead of resending the data.
This is because if the packet is not sent at right date, the stream is
interrupted so no matter.

Any advice is welcome...

Frederic


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2007-07-31  8:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 23:24 [Bluez-devel] a2dp, sco and kernel version Manuel Naranjo
2007-07-31  0:26 ` Brad Midgley
2007-07-31  0:34   ` Manuel Naranjo
2007-07-31  8:31 ` Frederic Dalleau [this message]
2007-07-31  8:52   ` Frederic Dalleau
2007-07-31 11:19     ` Manuel Naranjo
2007-07-31 16:29       ` Luiz Augusto von Dentz
2007-07-31 18:22         ` Manuel Naranjo
2007-08-01  7:38           ` Frederic Dalleau
2007-08-01 12:44             ` Manuel Naranjo
2007-08-02  3:22               ` Luiz Augusto von Dentz
2007-08-02  4:02                 ` Manuel Naranjo
2007-08-02 13:04                   ` Frederic Dalleau
2007-08-02 13:05                     ` Frederic Dalleau
2007-08-02 15:18                       ` Manuel Naranjo
2007-08-02 18:53                         ` [Bluez-devel] a2dp, sco and kernel version [Possible Solution] Manuel Naranjo
2007-08-02 19:12                           ` Brad Midgley
2007-08-02 19:24                             ` Manuel Naranjo

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=1185870706.27218.43.camel@ubuntu.mpl.access-company.com \
    --to=frederic.dalleau@access-company.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox