From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] report on new bluez headset
Date: Thu, 25 May 2006 09:33:04 -0600 [thread overview]
Message-ID: <4475CE30.7080109@xmission.com> (raw)
In-Reply-To: <4475C22B.9080908@free.fr>
Fabien
>> Yes, exactly. If I close the headset during a conversation then ekiga
>> completely freezes.
>
>
> For now this is not supported :-)
>
> In the long run it should be possible to tell ekiga that the headset has
> closed, however this would require some king of communication between
> headsetd and ekiga -- i'm not there yet :-(
this is only going to work if egika will listen for dbus events to that
effect. alsa provides nothing for signaling.
>> But the sound is not perfect. I hear some frying sound (un petit
>> gresillement), not very disturbing though but it is absent when I use
>> it with Ekiga.
>
> I noticed that. It's not perfect yet.
> I'm currently working on improving voice quality in general, but i looks
> it will end up with a kernel patch.
We've had quality problems that might be attributed to improperly pacing
the data sent through sco. I am not sure what the kernel provides--if
anything--in terms of timing.
What kind of kernel patch you are looking into?
>>>> - the device does not appear in the alsa mixer
alsa has two ways to look for devices. plugins do not show up using the
api everyone is used to unfortunately.
Brad
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-25 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 20:46 [Bluez-devel] New bluez headset implementation Fabien Chevalier
2006-05-18 23:46 ` Brad Midgley
2006-05-19 0:16 ` Denis KENZIOR
2006-05-19 3:16 ` Mayank Batra
2006-05-19 11:06 ` [Bluez-devel] New bluez headset implementation : the archive Fabien Chevalier
2006-05-20 15:39 ` [Bluez-devel] report on new bluez headset Giuseppe Castagna
2006-05-21 18:42 ` Fabien Chevalier
2006-05-21 20:03 ` Giuseppe Castagna
2006-05-25 14:41 ` Fabien Chevalier
2006-05-25 15:33 ` Brad Midgley [this message]
2006-05-25 16:30 ` Fabien Chevalier
2006-05-25 20:32 ` Brad Midgley
2006-05-26 11:29 ` Fabien Chevalier
2006-07-07 8:57 ` [Bluez-devel] New bluez headset implementation Mayank Batra
2006-07-12 4:49 ` Mayank Batra
2006-07-17 7:28 ` 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=4475CE30.7080109@xmission.com \
--to=bmidgley@xmission.com \
--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.