From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset)
Date: Fri, 05 Sep 2008 19:00:42 +0200 [thread overview]
Message-ID: <1220634042.6714.89.camel@californication> (raw)
In-Reply-To: <20080905162654.GA17843@lapse.rw.madduck.net>
Hi Martin,
> > don't use headsetd. Use the audio stuff that comes with bluez-utils.
>
> So I am trying, and I got a little further, installing the right
> lines into .asoundrc as per
> http://wiki.bluez.org/wiki/HOWTO/AudioDevices. I have gotten beyond
> issues of
>
> bt_audio_service_open: connect() failed: Connection refused (111)
> aplay: main:564: audio open error: Connection refused
>
> but it still doesn't want to work. If I execute
>
> arecord -D bt500v -f S16_LE | aplay -D bt500v -f S16_LE
>
> then the headset makes a noise, the bluetooth LED flashes and
> arecord prints
>
> Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
>
> But then after about 30 or 40 seconds, it all fails:
>
> ALSA lib pcm_bluetooth.c:464:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION failed : Input/output error(5)
> arecord: set_params:979: Unable to install hw params:
> ACCESS: RW_INTERLEAVED
> FORMAT: S16_LE
> SUBFORMAT: STD
> SAMPLE_BITS: 16
> FRAME_BITS: 16
> CHANNELS: 1
> RATE: 8000
> PERIOD_TIME: 125000
> PERIOD_SIZE: 1000
> PERIOD_BYTES: 2000
> PERIODS: 4
> BUFFER_TIME: 500000
> BUFFER_SIZE: 4000
> BUFFER_BYTES: 8000
> TICK_TIME: [0 0]
> aplay: playback:2019: read error
>
> I have bluez-audio installed, but /etc/bluetooth/audio.conf is
> default. No PulseAudio or anything other than plain ALSA here...
>
> Any clues?
actually I have none. It simply works for me. And I have tested it a
lot. There are some rare conditions where the btusb driver is off on the
16-bit boundaries, but I am looking at a fix for it. However this will
not disturb the audio service. You just don't here anything.
Regards
Marcel
-------------------------------------------------------------------------
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=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-05 17:00 UTC|newest]
Thread overview: 14+ 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 21:03 [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset) 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=1220634042.6714.89.camel@californication \
--to=marcel@holtmann.org \
--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