public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] a2dp choppy sound problem
Date: Sun, 23 Dec 2007 21:26:20 -0700	[thread overview]
Message-ID: <d89ddf300712232026y32878c5x4b1e61ac0cee712c@mail.gmail.com> (raw)
In-Reply-To: <BLU117-W1270E7F77535BE008FEAF288590@phx.gbl>

Benson

> It seems no difference and chopyy as before.
> Anything else could do ?

you can try all three config changes above together.

what version of bluez-utils is this? Have you tried cvs head?

are you getting interference? If it's a 1.2 or newer bt adapter, you
could check the afh map to see if it's detecting and trying to avoid
interference:

hcitool afh 00:0D:3C:EB:53:F0

If the adapter on your computer is bt 1.2+ and the headset is older
than 1.2, afh might be another advantage to run the computer's adapter
as master.

is it running on a slow computer or an embedded computer?

-- 
Brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-12-24  4:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21  6:33 [Bluez-users] a2dp choppy sound problem Benson Dong
2007-12-21 15:52 ` Brad Midgley
2007-12-24  2:09   ` Benson Dong
2007-12-24  2:36     ` Brad Midgley
2007-12-24  3:26       ` Benson Dong
2007-12-24  4:26         ` Brad Midgley [this message]
2007-12-24  6:54           ` Benson Dong
2007-12-24 10:47             ` Marcel Holtmann

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=d89ddf300712232026y32878c5x4b1e61ac0cee712c@mail.gmail.com \
    --to=bmidgley@gmail.com \
    --cc=bluez-users@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