From: "Crni Gorac" <cgorac@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Plantronics 350 headset
Date: Sat, 23 Feb 2008 16:25:19 +0100 [thread overview]
Message-ID: <c02b565a0802230725v771c8dd9r4178847a36d07491@mail.gmail.com> (raw)
Trying to make Plantronics 350 headset to work with BlueZ, on a
Slackware 12 installation updated to today released BlueZ 3.26
Slackware packages. I've put PIN number to corresponding file in
/etc/bluetooth/passkey directory, also create corresponding
/etc/asound.conf file. Afterwards, I've changed my
/etc/bluetooth/hcid.conf, so that same PIN code is put there, under
"options "section, and also changed my /etc/bluetooth/rfcomm.conf file
to list my headset there. Afterwards, I've employed rfcomm to bind
my headset, and then "hcitool cc" to connect to my headset. However,
while connection is listed when I issue "hcitool con" immediately
afterwards, headset seems to be disconnected after couple seconds -
another "hcitool con" shows no connections. So, my questions are:
- Anyone having experience with making Plantronics 350 works on Linux?
- Is there any place where steps needed to employ Bluetooth headset
under Linux are described? Obviously,
http://wiki.bluez.org/wiki/HOWTO/AudioDevices is less than complete
description, and trying to get some clue from the rest of BlueZ
documentation is really frustrating (well, at least to myself)...
Thanks.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2008-02-23 15:25 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=c02b565a0802230725v771c8dd9r4178847a36d07491@mail.gmail.com \
--to=cgorac@gmail.com \
--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