From: Florian Echtler <echtler@fs.tum.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Re: Plantronics M2500 recording problem
Date: Fri, 3 Jun 2005 13:41:45 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0506031302510.10178@block> (raw)
In-Reply-To: <429F6E0F.3080805@xmission.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I created a bug report for this one ([ 1213784 ] noisy sco recordings).
> It would be good to know what kernel version and bluez-libs versions you guys
> are having the problem with and if it's persisting between versions. Email me
> and I'll keep the bug report up to date.
I have Kernel 2.6.11-mh2 and Bluez 2.17. I'm quite sure the problem was
also there with 2.16, but as I mentioned, it's gone with the other
headset.
Yours, Florian
- --
Preserve wildlife - pickle a squirrel today!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCoEH77CzyshGvatgRAgvZAJ9dFG6CQMFrgGQqFpguHEzLxmsQowCg3YvG
vzgtb3f+vey5Nm9k551gFUc=
=FdFB
-----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
prev parent reply other threads:[~2005-06-03 11:41 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
2005-06-02 20:37 ` Brad Midgley
2005-06-03 11:41 ` Florian Echtler [this message]
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.0506031302510.10178@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