From: martin f krafft <madduck@madduck.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device
Date: Wed, 27 Aug 2008 22:03:14 +0100 [thread overview]
Message-ID: <20080827210314.GA15253@lapse.rw.madduck.net> (raw)
In-Reply-To: <34CE4798-1CBA-4F76-BA4D-A5E814D84C0E@holtmann.org>
[-- Attachment #1.1: Type: text/plain, Size: 1644 bytes --]
also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.27.0618 +0100]:
> you don't have to. The bluez-utils-3.36 comes with an audio plugin
> that does all this for you. You just have to add 4 magic lines
> into .asoundrc. See wiki.bluez.org for these for it.
So I added
pcm.bluetooth {
type bluetooth
device 00:1A:45:14:EE:D7
}
to .asoundrc and if I try to play something with aplay, I am told that
Playing WAVE '/usr/share/twinkle/ringback.wav' : Unsigned 8 bit,
Rate 8287 Hz, Mono aplay: set_params:918: Sample format non
available
Trying to use the device with twinkle, the programme starts up
taking ages trying to connect (http://bugs.debian.org/475962) and
eventually just says that it cannot access the speaker/microphone.
When twinkle tries to talk to the headset, the bluetooth LED starts
to blink, the headset makes the
noise it makes when a connection is established, and after a while,
twinkle tells me
snd_pcm_hw_params failed: Invalid argument
and then
snd_pcm_hw_params failed: Input/output error
The bluetooth LED continues blinking and the headset will not make
the disconnection sound until I turn bluetooth off. Once I turn it
back on, the headset disconnects, and the cycle repeats.
I am using 2.6.27-rc4 and bluez-utils 3.36-1.
Any ideas what may be wrong?
--
martin | http://madduck.net/ | http://two.sentenc.es/
"it isn't pollution that's harming the environment.
it's the impurities in our air and water that are doing it."
- dan quayle
spamtraps: madduck.bogus@madduck.net
[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-08-27 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 7:36 [Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device martin f krafft
2008-08-22 8:33 ` Marcel Holtmann
2008-08-26 16:35 ` [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) " martin f krafft
2008-08-26 17:19 ` Marcel Holtmann
2008-08-26 20:34 ` martin f krafft
2008-08-27 5:18 ` Marcel Holtmann
2008-08-27 21:03 ` martin f krafft [this message]
2008-09-05 16:26 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset) martin f krafft
2008-09-05 17:00 ` Marcel Holtmann
2008-09-08 20:33 ` martin f krafft
2008-09-23 13:00 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset martin f krafft
2008-09-23 13:37 ` Stuart Pook
2008-09-29 21:41 ` SCO headset, bluez-4.9 & linux 2.6.27-rc7 -> Unable to install hw params Stuart Pook
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=20080827210314.GA15253@lapse.rw.madduck.net \
--to=madduck@madduck.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox