All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Help getting Plugz going
Date: Mon, 02 Apr 2007 14:50:48 -0600	[thread overview]
Message-ID: <46116CA8.20008@xmission.com> (raw)
In-Reply-To: <op.tp58g0h8mz9ilx@rayleigh>

Jasper

> The I did see this, but it left me with a few questions that I couldnt  
> resolve:
>   "If you base your .asoundrc on the example alsa-plugins/asound.conf from  
> cvs,
>    you can edit it and add your SCO headset address. Then change the alsa d
>    evice in xmms to headset and run /usr/bin/headsetd.
>    You should be able to use the headset at this point"
> 
> I dont have the .asoundrc from cvs, just the example provided with the  
> bluetooth-alsa source,
>   and looking at the file i wasn't sure where to add the headset adress,
> also
> I started /usr/bin/headsetd but what then?

fwiw, I made some improvements and put a line in the asound.conf that 
should help you see where to put the address.

> Do i need to connect the headset with hcitool cc <addr>, i did this with  
> no success
> Is the idea that headsetd, like with hidd, connects automatically when it  
> sees the headset?
>   Sorry Ime not sure how to connect once headsetd is running.

headsetd will connect on demand when you use the audio device.

after your address is in .asoundrc, you can launch an alsa client and 
set the alsa device to "headset" and try to use it. see the build page. 
most clients don't let you easily choose this device.

> Are there any diagnostics that i can run to get an idea where the process  
> is failing?

hcidump -X -V will have a lot of output, but in the dump you'll find the 
occasional gem to figure out what is happening. I run it, try to do the 
operation that is failing, then stop the dump and examine its output.

brad

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-04-02 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 19:30 [Bluez-devel] Help getting Plugz going Jasper Mackenzie
2007-04-02 20:50 ` Brad Midgley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-02 22:21 Jasper Mackenzie
2007-04-02 11:12 Jasper Mackenzie
2007-04-02 14:05 ` Brad Midgley

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=46116CA8.20008@xmission.com \
    --to=bmidgley@xmission.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 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.