All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Brannlund <johan_brn@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Headset not working with audio service
Date: Tue, 11 Dec 2007 02:06:55 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.12.11.02.06.55@yahoo.com> (raw)

Hi. I can't get my motorola H300 headset to work with the bluez audio 
service - on older kernels, it did work with headsetd, once I'd applied 
the SCO flow control patch (the bluetooth controller on my laptop is one 
of those troublesome broadcom devices).

Here's what I did and what happened:

$ arecord -D headset -f S16_LE test.wav
Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, 
Mono
ALSA lib pcm_bluetooth.c:370:(bluetooth_hsp_hw_params) Protocol not 
available (92)
Aborted by signal Interrupt...

Even though arecord complains about an error, I get a file test.wav that 
correctly recorded what I said and I can play it through my regular 
speakers. But when I try to play it back through the headset I get

$ aplay -D headset -f S16_LE test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
ALSA lib pcm_bluetooth.c:370:(bluetooth_hsp_hw_params) Protocol not 
available (92)
aplay: pcm_write:1265: write error: Invalid argument


and aplay exits almost immediately, without playing any sound. When I run 
the above aplay command, bluetoothd-service-audio outputs



audio[7384]: Accepted new client connection on unix socket (fd=8)
audio[7384]: Package PKT_TYPE_CFG_REQ:0
audio[7384]: State changed /org/bluez/audio/device0: 
HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
audio[7384]: /org/bluez/audio/device0: Connecting to 00:XX:XX:XX:XX:XX 
channel 2
audio[7384]: State changed /org/bluez/audio/device0: 
HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_CONNECTED
audio[7384]: /org/bluez/audio/device0: Connected to 00:XX:XX:XX:XX:XX
audio[7384]: State changed /org/bluez/audio/device0: 
HEADSET_STATE_CONNECTED -> HEADSET_STATE_PLAY_IN_PROGRESS
audio[7384]: SCO socket opened for headset /org/bluez/audio/device0
audio[7384]: SCO fd=10
audio[7384]: fd=10, fd_opt=1, pkt_len=48, sample_size=2, rate=8000
audio[7384]: 30 bytes sent
audio[7384]: 1 bytes sent
audio[7384]: State changed /org/bluez/audio/device0: 
HEADSET_STATE_PLAY_IN_PROGRESS -> HEADSET_STATE_PLAYING
audio[7384]: Unix client disconnected (fd=8)
audio[7384]: State changed /org/bluez/audio/device0: 
HEADSET_STATE_PLAYING -> HEADSET_STATE_DISCONNECTED


Any ideas? This is with bluez 3.22 and the very latest 2.6.24-based 
Ubuntu kernel. 2.6.24-rc3 gives the same result...

- Johan


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

                 reply	other threads:[~2007-12-11  2:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pan.2007.12.11.02.06.55@yahoo.com \
    --to=johan_brn@yahoo.com \
    --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.