From: "Jasper Mackenzie" <jasper@treshna.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Help getting Plugz going
Date: Mon, 02 Apr 2007 23:12:48 +1200 [thread overview]
Message-ID: <op.tp5lfmu1mz9ilx@rayleigh> (raw)
Gidday.
I am trying to get a JABRA BT135 working on my mums laptop with limited
success.
Currently the older btsco way is 1/2 working, with mic working, poor
quality, but working.
The 'speaker' bit ... reciving audio is not working, as in theres no
sound just a faint hiss, that starts and stops when the audio starts and
stops, with beeps from the headest at appropriate times to indicate that
it was recieving audio.
btsco was run and compiled as per the Download and build instructions.
Due to the poor recording quality and the lack of playback, i figured that
plugz would be the way to go.
I googled as much as i could for a more comprehensive howto on install ing
and running Plugz, but only returned howtos for the btsco method,
Hence I am asking for help as to how to setup Plugz for an almost idiot.
What I tried:
almost built from source, until i saw that debian has a bluetooth-alsa
package (Debian Unstable)
copied .asoundrc to the home and root directories, ran headsetd -n
then tried to connect to the headset via various methods. Sorry dont have
the box on hand, so i cant say what exact command i used to try and
connect to the headset, but none of them produced any output from
headsetd, and none produced any audio in te headset.
I wasnt sure whether or not I was to put the mac address of the headset in
the asoundrc file or not, and if so where. it looked like these things
were inherited from environmental variables.
so major concerns: what to do with asoundrc, how to run headsetd, and
connect to headset.
The bluetooth adaptor is a D-Link cf card in a pcmcia converter, it is the
HCI type (CSR) .. sorry all from crappy memory)
TIA
Jasper
-------------------------------------------------------------------------
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
next reply other threads:[~2007-04-02 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 11:12 Jasper Mackenzie [this message]
2007-04-02 14:05 ` [Bluez-devel] Help getting Plugz going Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2007-04-02 19:30 Jasper Mackenzie
2007-04-02 20:50 ` Brad Midgley
2007-04-02 22:21 Jasper Mackenzie
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=op.tp5lfmu1mz9ilx@rayleigh \
--to=jasper@treshna.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.