From: SA <sa@claborn.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How to setup a headset as an audio device? Getting "Device busy" errors
Date: Mon, 4 Feb 2008 17:52:04 -0600 [thread overview]
Message-ID: <200802041752.04450.sa@claborn.net> (raw)
In-Reply-To: <479D1EFB.9020005@gmail.com>
On Sunday 27 January 2008 18:16:59 Eugene wrote:
> Hello,
> try to
> aplay -v -D bluetooth './your-sound.wav'
> and send its output. Else, did you started bluetooth audio service?
> To check, use:
> ps ax | grep bluetoothd-service-audio
BTW I started off using KDE and the bluetooth applet to pair the device. It is
now listed in the "Paired/Trusted Devices" screen. It it also listed in
the "Configured Input Devices" section of "Input Devices".
I'm a little suspicious of the KDE applets, does anyone know what tools to use
on the commandline to make sure that the connection/pairing is good? It shows
up with hcitool scan:
citrine:~ # hcitool scan
Scanning ...
00:0D:3C:6F:0E:89 Jawbone
#
Output of trying to play:
:~> aplay -v -D bluetooth /work/tmp/Audio-tmp/11\ -\ How\ Can\ I\ Keep\ From\
Singing-.wav
ALSA lib pcm_bluetooth.c:1189:(bluetooth_init) Connection fail
aplay: main:546: audio open error: Connection refused
I don't see anything useful in /var/log/messages
I tried deleting the pairing, re-pairing and immediately doing the "aplay"
test and still I get the same error.
As far as the bluetooth audio service, I'm not sure. As I mentioend, I'm on
SuSE 10.3. It only has /etc/init.d/bluetooth which I think is supposed to
handle all types of bluetooth connections - like a wrapper or something.
ps ax |grep blue
27467 ? Ss 0:00 /usr/sbin/hcid -s -f /etc/bluetooth/hcid.conf
27472 ? S 0:00 /usr/lib/bluetooth/bluetoothd-service-input
# cat /etc/bluetooth/audio.service
[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service
My bluetooth adapter is the good old USB D-Link DBT 120 that works on
everything (Mac, Linux etc).
hcitool con shows:
# hcitool con
Connections:
hcitool rssi 00:0D:3C:6F:0E:89
Not connected.
I'm not sure what that means. I wonder if it means it's not really connected?
JW
--
----------------------
System Administrator - Cedar Creek Software http://www.cedarcreeksoftware.com
http://jwadmin.blogspot.com/
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-04 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 4:56 [Bluez-users] How to setup a headset as an audio device? Getting "Device busy" errors SA
2008-01-28 0:16 ` Eugene
2008-02-04 23:52 ` SA [this message]
2008-02-05 2:04 ` Leszek Koltunski
2008-02-05 18:29 ` SA
2008-02-05 18:33 ` SA
2008-02-05 18:41 ` Brad Midgley
2008-02-05 21:42 ` SA
2008-02-05 21:46 ` SA
2008-02-05 22:11 ` SA
2008-02-06 8:43 ` Guillaume Bedot
2008-02-06 1:47 ` jayjwa
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=200802041752.04450.sa@claborn.net \
--to=sa@claborn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox