From: "Henryk Plötz" <henryk@ploetzli.ch>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO stuck on a Netgear WGT634U (mips)
Date: Mon, 6 Mar 2006 09:01:40 +0100 [thread overview]
Message-ID: <20060306090140.e1e882d5.henryk@ploetzli.ch> (raw)
In-Reply-To: <440BE81C.5040902@porthome.nl>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
Moin,
Am Mon, 06 Mar 2006 08:43:24 +0100 schrieb Pieter Poorthuis:
> I'm using a Energic BT-001 headset (bluetooth 1.1, Motorale chipset)
> and had a terrible distortion as well. After having disabled
> automatic endianness fixup in the snd_bt_sco kernel module (line 32
> btsco.c:
> #undef AUTO_FIXUP_BYTESHIFT) it works flawlessly :).
Yeah, I found that part of the code suspicious too.
My current problem is that sending sound from the Netgear to the
headset works, but only some of the time (about 10% of it) and
non-reproducible too. When playing back a sound file sometimes I hear
something and most of the time I don't. Sound seems to come and go at
will. (Note: It's not a speaker problem. When there is no sound I still
hear the background static noise.)
I looked at the outgoing SCO stream with hcidump and that seems to be
fine. (E.g. I grabbed the raw data from the stream and played it back
on my Laptop's sound card and there the sound is continuously OK.)
I tried two different dongles (both work fine with the headset when
attached to my Laptop) but have yet to find a different headset to try.
The byteshift doesn't seem to have anything to do with it, despite
there being a minor correlation between sound switching on and off and
"Shift problem detected! Fixing to 1."/"Shift problem detected! Fixing
to 0." in the log (they _always_ come in pairs on the Netgear). I
experimentally changed the code to switch between byteshift on and off
every 15s and that didn't have any effect whatsoever.
(Note: Recording sound from the microphone seems to work always. But I
didn't test that very extensively.)
Next step would be for me to read more on the Headset profile to better
understand the hcidump output (and look for errors) and get a headset
emulator running on my laptop to check the SCO stream that is actually
received by the headset. When I have more time ...
--
Henryk Plötz
Grüße aus Berlin
~~~~~~~ Un-CDs, nein danke! http://www.heise.de/ct/cd-register/ ~~~~~~~
~ Help Microsoft fight software piracy: Give Linux to a friend today! ~
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-06 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 0:14 [Bluez-devel] SCO stuck on a Netgear WGT634U (mips) Henryk Plötz
2006-03-03 4:27 ` Brad Midgley
2006-03-04 1:41 ` Henryk Plötz
2006-03-04 7:47 ` Henryk Plötz
2006-03-06 7:43 ` Pieter Poorthuis
2006-03-06 8:01 ` Henryk Plötz [this message]
2006-03-06 19:10 ` Brad Midgley
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=20060306090140.e1e882d5.henryk@ploetzli.ch \
--to=henryk@ploetzli.ch \
--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;
as well as URLs for NNTP newsgroup(s).