public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Carter <jimc@math.ucla.edu>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluez-gnome wizard deficiencies make it mostly useless
Date: Wed, 12 Nov 2008 10:39:07 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0811121011130.25291@simba.math.ucla.edu> (raw)
In-Reply-To: <491AB358.9000209@SSpaeth.de>

On Wed, 12 Nov 2008, Sebastian Spaeth wrote:

> I see 2 solutions and I would like input in what bluez-gnome devs think:
> 1) Try to pair with random PIN if that fails try "0000", "1234", "1111".
> This would at least cover about 90% of all devices and only special case
> the rest.
> 
> 2) Prepopulate a Random PIN in a field but allow the user to override
> that PIN. After all he should know best what PIN to use.

3)  A little more complicated: if the device class suggests no keyboard,
try the hardwired codes listed above, and in the 10% of cases where that 
fails (or if the device class suggests that there is a keyboard), then pop 
the dialog box for solution #2.  Particularly crappy devices may have a 
problem if pairing fails, so it could be helpful to have an override to 
bypass the hardwired codes even for device classes where they would 
normally be tried.

James F. Carter          Voice 310 825 2897    FAX 310 206 6673
UCLA-Mathnet;  6115 MSA; 520 Portola Plaza; Los Angeles, CA, USA  90095-1555
Email: jimc@math.ucla.edu    http://www.math.ucla.edu/~jimc (q.v. for PGP key)

       reply	other threads:[~2008-11-12 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <491AB358.9000209@SSpaeth.de>
2008-11-12 18:39 ` Jim Carter [this message]
2008-11-12 19:29 ` bluez-gnome wizard deficiencies make it mostly useless Bastien Nocera
2008-11-12 19:59   ` Jim Carter
2008-11-13  9:40   ` Sebastian Spaeth
2008-11-12  9:17 Sebastian Spaeth

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=Pine.LNX.4.64.0811121011130.25291@simba.math.ucla.edu \
    --to=jimc@math.ucla.edu \
    --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