From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] I got plugz to compile but now there is no sound on the headset after connecting
Date: Thu, 18 Jan 2007 18:49:03 +0100 [thread overview]
Message-ID: <45AFB30F.6040809@free.fr> (raw)
In-Reply-To: <45AE1BFE.5301.0014.0@novell.com>
Olin Atkinson wrote:
> Wait, I lied. The command line is giving the following output:
>
>
> DEBUG(pid=7544): _snd_pcm_sco_open: Starting pcm_sco_headset plugin.
> DEBUG(pid=7544): _snd_pcm_sco_open: Open mode is for Playback.
> ALSA lib pcm_sco.c:533:(_snd_pcm_sco_open) Unknown field max_periods
> aplay: main:550: audio open error: Invalid argument
> oatkinson@oatkinson1:/windows/D/projects/gspcav1-20060925> aplay -v
> Aborted by signal Interrupt...
>
Hi Olin, the provided asound.conf was bogus, this is now fixed in CVS.
Cheers,
Fabien
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-18 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 19:55 [Bluez-devel] I got plugz to compile but now there is no sound on the headset after connecting Olin Atkinson
2007-01-18 17:49 ` Fabien Chevalier [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-17 19:26 Olin Atkinson
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=45AFB30F.6040809@free.fr \
--to=fabchevalier@free.fr \
--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.