public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: David Elze <wegwerf@datenschrott.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] headset via bluetooth-headset not fully working
Date: Sun, 04 Nov 2007 17:14:25 +0100	[thread overview]
Message-ID: <1194192865.2823.20.camel@aero64.datenschrott.de> (raw)

Hey, 

I'm running Debian unstable and want to do some VoIP stuff with my
HBH-PV700 (Sony Ericsson) headset over a standard bluetooth dongle
(usb).

Pretty everything works as it should: 
1. I can pair the headset correctly (hcitool, gnome bluetooth 
   manager and friends) [1]
2. I can start the headsetd via 'headsetd -n' to get its output
3. When I run 
   'aplay -Dplug:headset /usr/share/sounds/alsa/Front_Center.wav'
   the headsets does a beep, I can hear some silent noise (nothing
   like the expected sound, only background noise that is slightly
   louder than the headset normally is if there is no aplay involved)
   but not the expected sound and headsetd says [2] whereas my 
   .asoundrc looks like [3]

So everything seems to be fine: the connection does work, if I send some
sound to the headset-alsa-device it recognizes that, beeps and starts to
'sound' different then before but I just hear no sound. I increased all
audio levels via alsamixer, I put the usb-stick into another usb-port
(because I read something about problems with certain usb-hubs and
sco-like stuff) and did some strace'ing and aplay -verbose but there
were absolutely no error messages.

Maybe you guys have an idea or at least some rtfm-hint because I don't
know what to do anymore. The headset itself is working correctly, I
tested it twice with my normal cellphone.

Thanks for any hint :-)

Greetings, David

[1] 
BD Address:  xx:yy... (removed for obvious reasons)
Device Name: HBH-PV700
LMP Version: 1.1 (0x1) LMP Subversion: 0x9240
Manufacturer: Philips Semiconductors (37)
Features: 0xbc 0x28 0x01 0x00 0x00 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch> 
<sniff mode> <SCO link> <HV3 packets> <CVSD> 

[2] 
headsetd[3109]: Configuration phase ended: target bdaddr is xx:yy:...,
timeout is 6000 ms
headsetd[3109]: Changing state: Idle-->Paging
headsetd[3109]: Changing state: Paging-->Connecting
headsetd[3109]: Changing state: Connecting-->Ready
headsetd[3109]: Changing state: Ready-->Opening
headsetd[3109]: SCO channel opened handle=0x002b mtu=64
headsetd[3109]: Changing state: Opening-->Streaming
headsetd[3109]: Appli closed socket
headsetd[3109]: Changing state: Streaming-->Zombie
headsetd[3109]: Nobody uses SCO channel anymore, closing it.
headsetd[3109]: Changing state: Zombie-->Connected

[3]
pcm.headset {
        @args [BDADDR TIMEOUT]
        @args.BDADDR {
                type string
                default "xx:yy:..."
        }
        @args.TIMEOUT {
                type integer
                default 6000
        }
        type        sco
        bdaddr      $BDADDR
        timeout     $TIMEOUT
}
ctl.headset {
        type sco
}



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-11-04 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 16:14 David Elze [this message]
2007-11-04 17:12 ` [Bluez-users] headset via bluetooth-headset not fully working maho+bluez
2007-11-04 17:46   ` David Elze

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=1194192865.2823.20.camel@aero64.datenschrott.de \
    --to=wegwerf@datenschrott.de \
    --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