Linux bluetooth development
 help / color / mirror / Atom feed
From: Ed Tsang <netdesign_98@yahoo.com>
To: Bluettooth Linux <linux-bluetooth@vger.kernel.org>
Subject: Fail to store link key for Blackberry
Date: Tue, 11 May 2010 13:48:55 -0700 (PDT)	[thread overview]
Message-ID: <682855.82528.qm@web52605.mail.re2.yahoo.com> (raw)

Hi,  
I was having trouble pairing with Blackberry (bluez-4.60). It was paired, but the next connection require pair again.
 hcidump: "Link Key Request Negative Reply"
  check  /var/lib/bluetooth/xxx/linkkeys   not there.
  Delete the device from BB side, went through pairing again
   hcidump: > Link key Notification .. type 6 (Changed Combination key)
   but  ../linkkeys still not there.
  Trace down to dbus-hci.c   hcid_dbus_link_key_notify()
/*  Only store the link key if one of the following is true:   
     2. this is a changed combination key and there was a previously
     stored one */
...
   if (key_type < 0x03 || (key_type == 0x06 && old_key_type != 0xff) ||
...
if I change it to the following, then the ../linkkeys is stored and paring with the Blackberry only need to do once   
   if (key_type < 0x03 || (key_type == 0x06) ||

Look to me " hcidump: Link key Notification .. type 6 (Changed Combination key) " the "6" is coming from Blackberry. 
I tried deleted the device from the Blackberry, delete the device and remove the battery from the Blackberry....
 hcidump > link key notification still type 6.

/*     * 2. this is a changed combination key and there was a previously
     *    stored one */ 
in general make sense until we encounter device like this or for whatever reason, we lost the local link
key for the device, then we might be stuck in "pairing everytime connect".

Any comment?

Ed



                 reply	other threads:[~2010-05-11 20:48 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=682855.82528.qm@web52605.mail.re2.yahoo.com \
    --to=netdesign_98@yahoo.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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