From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Brad Midgley <bmidgley@xmission.com>
Subject: [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -)
Date: Thu, 09 Nov 2006 21:42:30 +0100 [thread overview]
Message-ID: <455392B6.5060209@free.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
Brad, Marcel & all
I started working on improving Linux SCO headsets support something like
9 months ago.
Unfortunately, some tough months at work took me out of my spare time
hobby for a few month. :-(
In the meantime Brad took care of the baby and has put it in btsco CVS.
I found the time to take the baby back, so i started to rework on it a
few weeks ago. I fixed a few bugs in the daemon and in the plugins, and
redesigned the SCO flow control patch after Marcel's review of my code.
And finally the result is there: i managed to get perfect sound quality. :-)
By perfect i mean no scratches, and what is really really important for
telephony applications: minimal delay.
So it was time for me to eat my own dog food : i switched to use it as
my primary business phone two days ago. :-)
(Ok, i still have a plan old phone on reach when things don't go as
smoothly as expected ;-)).
This is not perfect yet but is definitely getting closer to something
that is useable on a day to day basis. (I still have some unreliable
behaviours in the control path)
On the bad side of things, it's still a pain to
install, as you still need to patch both the kernel and ekiga to have
things actually work as expected.
By this e-mail, i'm looking for successes/failure reports with different
headsets, and with others VoIP softwares.
Enjoy !!
PS: Brad, i will send you an e-mail to see how i can merge this with
what is in CVS, to stop my "out of band" deliveries :-)
[-- Attachment #2: bluez-headset-20061109.tar.bz2 --]
[-- Type: application/x-bzip, Size: 237792 bytes --]
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-11-09 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 20:42 Fabien Chevalier [this message]
2006-11-20 22:33 ` [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Jose Vasconcellos
2006-11-20 23:06 ` Brad Midgley
2006-11-21 7:35 ` Marcel Holtmann
2006-11-21 15:03 ` [Bluez-devel] SCO flow control (Was: New bluetooth-headset release 20061109) Jose Vasconcellos
2006-11-21 15:26 ` Marcel Holtmann
2006-11-21 17:26 ` Jose Vasconcellos
2006-11-21 17:53 ` Marcel Holtmann
2006-11-21 18:52 ` [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Jose Vasconcellos
2006-11-21 20:05 ` Fabien Chevalier
2006-11-21 20:39 ` Jose Vasconcellos
2006-11-22 11:12 ` Fabien Chevalier
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=455392B6.5060209@free.fr \
--to=fabchevalier@free.fr \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bmidgley@xmission.com \
/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.