From: martin f krafft <madduck@madduck.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pairing with headset
Date: Wed, 22 Sep 2004 09:50:30 +0200 [thread overview]
Message-ID: <20040922075030.GC8233@cirrus.madduck.net> (raw)
In-Reply-To: <200409220107.46086.pavouk@pavouk.org>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
also sprach Pavel Ruzicka <pavouk@pavouk.org> [2004.09.22.0107 +0200]:
> You must hold headset button for about 7 seconds, when blue LED on
> Jabra goes permanently ON. Now is headset in pairing mode, and you
> will see it in hcitool scan. Jabra BT250 is visible only in
> pairing mode. Probably due to security reasons.
Oh, okay; now I got it working.
> This headset can be paired only with one device.
That's really annoying.
> Do you have some other experience?
No, but I will let you know.
> Other problem is, that I don't know if there are some working bluez sound
> driver. I doesn't test it.
It is being worked on.
http://sourceforge.net/projects/bluetooth-alsa
http://www.gargan.org/linux/snd-bt-sco/
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
spamtraps: madduck.bogus@madduck.net
"twenty-four hour room-service must be one of the
premiere achievements of modern civilization."
-- special agent dale cooper
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-09-22 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 19:06 [Bluez-users] pairing with headset martin f krafft
2004-09-21 20:23 ` [Bluez-users] suse9.1personal and bluetooth modprobe Massimiliano Cuccia
2004-09-21 20:23 ` [Bluez-users] pairing with headset Brad Midgley
2004-09-21 23:07 ` Pavel Ruzicka
2004-09-22 7:50 ` martin f krafft [this message]
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=20040922075030.GC8233@cirrus.madduck.net \
--to=madduck@madduck.net \
--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