From: John Gruenenfelder <johng@as.arizona.edu>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem with link keys
Date: Sat, 6 Aug 2005 02:07:23 -0700 [thread overview]
Message-ID: <20050806090723.GA13065@as.arizona.edu> (raw)
In-Reply-To: <1123304874.7296.3.camel@pegasus>
On Sat, Aug 06, 2005 at 07:07:53AM +0200, Marcel Holtmann wrote:
>> And it is working just fine. It only seems to misbehave when I power it off.
>> Are any other people on this list using a Plantronics M2500 headset and, if
>> so, are you experiencing anything similar?
>
>I see always a authentication failure in your log. This means you never
>succeeded with your command or you send the wrong log. However the usage
>of "hcitool cc ..." doesn't qualifies for a correct headset/handsfree
>profile setup and thus your headset may forget your link key. Use tools
>like hstest of btsco and try again.
>
>Regards
>
>Marcel
Ah yes, that was it exactly. It's now working very well, even after powering
on and off.
Now that it is working reliably, I just have two more minor questions about
btsco:
1) Is there any way to have btsco started when I turn on the headset? hcid
sees this event, but I did not see anything in the hcid.conf manpage for
launching processes.
2) btsco allows for creating a .btsco file with regex in it so that you can
make it do something on a button press. How do I learn what those regex
should be for my particular headset? Is it part of one of the packets
dumped by hcidump?
Thanks again for all the help!
--
--John Gruenenfelder Research Assistant, Steward Observatory, U of Arizona
johng@as.arizona.edu
Try Weasel Reader for PalmOS -- http://gutenpalm.sf.net
"This is the most fun I've had without being drenched in the blood
of my enemies!"
--Sam of Sam & Max
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-06 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 3:01 [Bluez-devel] Problem with link keys John Gruenenfelder
2005-08-06 4:10 ` Marcel Holtmann
2005-08-06 5:01 ` John Gruenenfelder
2005-08-06 5:07 ` Marcel Holtmann
2005-08-06 9:07 ` John Gruenenfelder [this message]
2005-08-10 14:14 ` Alexandros Vellis
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=20050806090723.GA13065@as.arizona.edu \
--to=johng@as.arizona.edu \
--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