All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Poorthuis <pieter@porthome.nl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO stuck on a Netgear WGT634U (mips)
Date: Mon, 06 Mar 2006 08:43:24 +0100	[thread overview]
Message-ID: <440BE81C.5040902@porthome.nl> (raw)
In-Reply-To: <20060304084732.1ee8b518.henryk@ploetzli.ch>


>
> Not completely solved yet, since the sound I hear in my headset is
> anything from inaudible to heavily distorted, but at least the SCO
> packets happily go in and out, so that should be solvable for me.
>
>   
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 :).

Btw, this headset costed me Euro 12.50, so is this the cheapest headset 
that works with btsco...?

Pieter


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-03-06  7:43 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 [this message]
2006-03-06  8:01         ` Henryk Plötz
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=440BE81C.5040902@porthome.nl \
    --to=pieter@porthome.nl \
    --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.