public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin@scrye.com>
To: Bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluetooth headset not working
Date: Thu, 18 Oct 2007 11:45:17 -0600	[thread overview]
Message-ID: <20071018114517.4b6d1850@ghistelwchlohm.scrye.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]

Greetings. 

I recently had a chance to look at the new bluez-utils and the setup
for headsets. Very much nicer than any of the old methods. :) 

However, I can't seem to get my headset working with twinkle (or any
other phone app). 

I have setup my ~/.asoundrc. 
I can play audio to my headset via mplayer or aplay fine. 
When I try and set twinkle to use the ALSA bluetooth device it seems
like it opens the headset, and then it spits out: 

ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
available (92) 
ALSA lib pcm_bluetooth.c:417:(bluetooth_hsp_hw_params) Protocol not
available (92)

Then it goes to 100% cpu and unresponsive. 

ALSA bug? or bluez-utils? Anyone seen this before or have
a work around? 

twinkle-1.1-3.fc8.x86_64
alsa-lib-1.0.15-0.2.rc2.fc8.x86_64
bluez-utils-3.20-2.fc8.x86_64

I talked with the twinkle developers, and they say it's not an issue
with twinkle. See: 
http://tech.groups.yahoo.com/group/twinklephone/message/1879?l=1

Happy to provide info or debugging... CC me for faster response. 

kevin

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2007-10-18 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 17:45 Kevin Fenzi [this message]
2007-10-18 17:59 ` [Bluez-devel] bluetooth headset not working Jim Carter
2007-10-18 18:48   ` Kevin Fenzi
2007-10-19 16:03     ` Jim Carter
2007-10-19 16:42       ` Johan Hedberg
2007-10-19 19:23       ` Kevin Fenzi
  -- strict thread matches above, loose matches on Subject: below --
2007-10-20  2:10 KyoYin
2007-10-20 12:45 ` Johan Hedberg
2007-10-23  7:13 ` Johan Hedberg
2007-10-23  7:53   ` KyoYin
2007-10-23 10:02     ` Johan Hedberg

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=20071018114517.4b6d1850@ghistelwchlohm.scrye.com \
    --to=kevin@scrye.com \
    --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