All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rattling noise with bluefritz 2.0
Date: Thu, 28 Feb 2008 17:43:01 -0500	[thread overview]
Message-ID: <1204238581.4816.10.camel@pc.ilinx> (raw)
In-Reply-To: <200802281729.42989.Jens-E.Hansen@gis.de>


[-- Attachment #1.1: Type: text/plain, Size: 2353 bytes --]

On Thu, 2008-02-28 at 17:29 +0100, Jens-Erik Hansen wrote:
> 
> To get a bluetooth headset work with Twinkle/Ekiga/Skype I enhanced
> my .asoundrc at first.
> In several documents I read that you can use a pcm of type bluetooth

Yeah, that's what I did, but even with the patch you reference below for
pwlib, ekiga still barfs trying to open the audio device.  More on that
below, but for now, following your procedure...

> but that
> never worked for me so I have to use type sco (see pcm.headset).

I tried your configuration but ekiga complains, on trying to open the
audio devices:

ALSA lib pcm.c:2105:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_sco.so
ALSA lib pcm.c:2105:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_sco.so
ALSA lib pcm.c:2105:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_sco.so

So obviously you have something providing that "sco" pcm module.

> To get ekiga working with this alsa devices please follow
> http://forums.droplinegnome.org/viewtopic.php?t=5538&sid=ca7c1f8a8b259c2bf3a9fc6a42ba573c
> If you use a debian sid distribution

Ubuntu Gutsy in fact.

When I use instead:

pcm.headset {
   type bluetooth
   device 00:1A:45:1B:19:89
   profile "auto" #optional, supported profiles are: auto, hifi and voice
}

I can use arecord ... | aplay and I hear myself just fine, but ekiga
pukes out:

ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL headset
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL headset

and I do eventually get a connection and can hear on the headset but the
UI ends up hanging -- doesn't paint.

On a second invocation I get connected to a phone I have dialed but the
connection dies quite quickly and ekiga says:

(ekiga:24243): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1715: handler `2996' of instance `0x8466978' is not blocked
ALSA lib pcm_bluetooth.c:1179:(bluetooth_cfg) Error 22 while configuring device
ALSA lib pcm_bluetooth.c:1179:(bluetooth_cfg) Error 22 while configuring device
ALSA lib pcm_bluetooth.c:1179:(bluetooth_cfg) Error 22 while configuring device

and I get the warning dialogs about not being able to play or record
from the soundcard.

b.


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-02-28 22:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 19:10 [Bluez-users] rattling noise with bluefritz 2.0 Jens-Erik Hansen
2008-02-26  7:05 ` Leszek Koltunski
2008-02-26 18:27   ` Christian Schuglitsch
2008-02-28  4:02     ` Brian J. Murrell
2008-02-28 16:29   ` Jens-Erik Hansen
2008-02-28 22:43     ` Brian J. Murrell [this message]
2008-02-29 17:09       ` Jens-Erik Hansen
2008-03-01  1:19         ` Brian J. Murrell

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=1204238581.4816.10.camel@pc.ilinx \
    --to=brian@interlinx.bc.ca \
    --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 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.