From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Some bluez-gnome 1.2 bugs
Date: Mon, 08 Sep 2008 20:06:59 +0200 [thread overview]
Message-ID: <1220897219.11655.2.camel@californication> (raw)
In-Reply-To: <48C562D4.9020005@free.fr>
Hi Fabien,
> >> I just started to play recently with bluez 4.x.
> >>
> >> I found at least two very annoying bugs in the bluez-gnome-1.2 wizard:
> >> - On my debian testing system, the wizard does not allow me to enter
> >> the pin code. The pin code just gets displayed a fraction of second an
> >> then disappears. As a consequence the default 123456 pin code gets used
> >> and pairing fails.
> >
> > I am working on improving the PIN handling way, but at the same time I
> > have to make sure that it works with Simple Pairing and in the most
> > simple way. It is not that easy.
>
> I just retried with the latest 1.3 release. This time i am able to pair
> my headset. :-)
it is not perfect yet. Just a quick hack to pick 0000 as PIN code for
headset devices.
> > Also for some devices the PIN code needs to be random instead of 123456.
> >
> >> - If i try to go back to the first wizard page where my bluetooth
> >> device is displayed, it is already selected. I have no way to go to the
> >> next page : the next button stays grey whatever i do. (screenshot attached).
> >
> > Hold shift while selecting to unselect and then select again. I know
> > that this is broken.
>
> Looks you fixed that too :-).
It was actually pretty simple to fix.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-09-08 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 7:51 [Bluez-devel] Some bluez-gnome 1.2 bugs Fabien Chevalier
2008-09-05 16:58 ` Marcel Holtmann
2008-09-08 17:37 ` Fabien Chevalier
2008-09-08 18:06 ` Marcel Holtmann [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=1220897219.11655.2.camel@californication \
--to=marcel@holtmann.org \
--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