From: Florian Echtler <echtler@fs.tum.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Re: Plantronics M2500 recording problem
Date: Thu, 2 Jun 2005 12:22:44 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0506021220030.10638@block> (raw)
In-Reply-To: <429E368C.6020407@xmission.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Are you saying the entire recording is bad if it starts out that way? it's not
> transient like interference?
I've had the same problem with my B-Speech Elect Headset. I've recently
swapped it with an old Plantronics M1000, which seems to work fine so far.
There were other issues, such as reconnection problems with keyboard and
mouse, when the B-Speech headset was in use. I suspect some kind of
incompatibility between the BT dongles and the headsets..
Yours, Florian
- --
Preserve wildlife - pickle a squirrel today!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCnt357CzyshGvatgRAqlNAKDGNo6ZaZ9RPCkxDAZP9z6f8IuvmQCfWo5+
5J+nrYkthYzEHCz2xtZFXTM=
=jR/S
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-06-02 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 22:18 [Bluez-users] Re: Re: Plantronics M2500 recording problem George Norton
2005-06-01 22:28 ` Brad Midgley
2005-06-02 10:22 ` Florian Echtler [this message]
2005-06-02 20:37 ` Brad Midgley
2005-06-03 11:41 ` Florian Echtler
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=Pine.LNX.4.63.0506021220030.10638@block \
--to=echtler@fs.tum.de \
--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