From: Remy Bosch <reboli@hccnet.nl>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Audio gaps with bcm2035 and Hama receiver
Date: Fri, 26 Oct 2007 22:26:38 +0200 [thread overview]
Message-ID: <47224D7E.3080901@hccnet.nl> (raw)
In-Reply-To: <d89ddf300710261035r613fee0pe09aa130f348398c@mail.gmail.com>
Brad Midgley wrote:
> Remy
>
> Is this last attempt using v3.22?
>
Just tested and the package builds. The gaps on the other hand are still
there. I can't determine what causes the gaps. I just notice that for a
few seconds the sound is gone though the clock keeps ticking. So, for
some time the sound appears to go to /dev/null.
The patch for 2.6.23 kernel does not help either. It got even worse, but
I'll stick to the current setup which is 2.6.22.
As mentioned before, I have a USB based BCM2035.
The receiver
- Bluetooth class 1: max. range: 100 m
- Bluetooth standard V1.2 (supports stereo profile A2DP)
Any thoughts?
Thanks!
Remy
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-10-26 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 16:46 [Bluez-users] Audio gaps with bcm2035 and Hama receiver Remy Bosch
2007-10-25 22:48 ` Marcel Holtmann
2007-10-26 12:53 ` Remy Bosch
2007-10-26 16:20 ` Remy Bosch
2007-10-26 17:35 ` Brad Midgley
2007-10-26 20:26 ` Remy Bosch [this message]
2007-10-26 21:46 ` Brad Midgley
2007-10-26 23:40 ` Remy Bosch
2007-10-30 11:29 ` Brad Midgley
2007-10-30 11:49 ` Remy Bosch
2007-10-30 6:25 ` Sumeet VERMA
2007-10-30 10:22 ` Remy Bosch
2007-10-30 10:23 ` Sumeet VERMA
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=47224D7E.3080901@hccnet.nl \
--to=reboli@hccnet.nl \
--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 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.