public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Bläsing" <matthias.blaesing@rwth-aachen.de>
To: linux-bluetooth@vger.kernel.org
Subject: Bluetooth audio and nokia HDW-3 do not work
Date: Mon, 21 Jul 2008 11:29:47 +0200	[thread overview]
Message-ID: <1216632588.24708.9.camel@enterprise.glx> (raw)

[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]

Hello,

I had a bluetooth headset (Nokia HDW-3)  running once (it was in the
times of btsco (I think the whole package was calles bluetooth-alsa). As
I understand bluetooth audio should be its successor. Ok - I tried it
and got nothing. I have the 0.36 Version of bluez installed (compiled
from the debian package).

This is the .asoundrc:

pcm.bluetooth {
   type bluetooth
   device 00:03:89:51:8F:12
   profile "voice"
}

ctl.bluetooth {
   type bluetooth
   device 00:03:89:51:8F:12
   profile "voice"
}

When I connect the headset and try to play sound from mplayer:

mplayer -ao alsa:device=bluetooth <audio file>

I get these entries in syslog:

Jul 21 10:01:29 enterprise hcid[20068]: link_key_request (sba=00:03:7A:AA:A9:34, dba=00:03:89:51:8F:12)
Jul 21 10:01:30 enterprise hcid[20068]: link_key_notify (sba=00:03:7A:AA:A9:34, dba=00:03:89:51:8F:12)
Jul 21 10:01:38 enterprise hcid[20068]: Audio API: received BT_GETCAPABILITIES_REQ
Jul 21 10:01:38 enterprise hcid[20068]: Audio API: sending BT_GETCAPABILITIES_RSP
Jul 21 10:01:38 enterprise hcid[20068]: Audio API: received BT_SETCONFIGURATION_REQ
Jul 21 10:01:38 enterprise hcid[20068]: config sco - device = 00:03:89:51:8F:12 access_mode = 2

Mplayer is frozen and when I try to stop mplayer (Control-C) it reports,
that it was interrupted in ao2_init (the name implies, that it didn't
send anything).

Trying to set the volume by using amixer leeds to a flood of the syslog
with these messages:

Jul 21 09:53:08 enterprise hcid[20068]: Audio API: sending BT_CONTROL_RSP
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: received BT_CONTROL_REQ
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: sending BT_CONTROL_RSP
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: received BT_CONTROL_REQ
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: sending BT_CONTROL_RSP
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: received BT_CONTROL_REQ
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: sending BT_CONTROL_RSP
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: received BT_CONTROL_REQ
Jul 21 09:53:08 enterprise hcid[20068]: Audio API: sending BT_CONTROL_RSP

I really don't know where to look further - any help is appretiated 

Thanks in advance

Matthias

-- 
So long and thanks for all the fish!

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

                 reply	other threads:[~2008-07-21  9:29 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=1216632588.24708.9.camel@enterprise.glx \
    --to=matthias.blaesing@rwth-aachen.de \
    --cc=linux-bluetooth@vger.kernel.org \
    /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