public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Cc: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
Subject: Re: [Bluez-users] Keyboard Device Pairing (gmane: message 13 of 20)
Date: Mon, 25 Sep 2006 23:47:06 +0200	[thread overview]
Message-ID: <1159220826.20997.21.camel@localhost> (raw)
In-Reply-To: <beb7688e0609220628p6239199ai9c5479725e09b894@mail.gmail.com>

Hi Chris,

> > > [root@localhost]# hidd --connect 00:0D:3C:40:68:7C
> > > <window popped up asking for a passkey>
> > > Can't get device information: Too many levels of symbolic links
> > > [root@localhost]# hidd --connect 00:0D:3C:40:68:7C
> > > Can't get device information: Function not implemented
> >
> > Random guess, but that to me looks like "errno" is getting undefined
> > values and is printing whatever random number of error it happens to find.
> 
> I continued to play around with it, and tried using kbluetoothd to
> connect. When I was again prompted for a passkey, I keyed it in on
> both my PC and on the keyboard, and it suddenly started working. I'm
> not confident I could get this working again if I had to. Is there a
> tutorial somewhere on pairing bluetooth devices? I didn't find
> anything on bluez.org.

there is no really tutorial. And in case or pairing problems it helps to
run "hcidump -X -V" to see what is going on. However with the D-Bus API
you have a CreateBonding command that will take care of everything and
at some point we will have a connection wizard. If I have enough free
time to write all this GUI stuff. I am not really a GUI programmer.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-09-25 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22  0:57 [Bluez-users] Keyboard Device Pairing Chris Spencer
2006-09-22  1:15 ` Chris Spencer
2006-09-22  8:10   ` Paul LeoNerd Evans
2006-09-22 13:28     ` [Bluez-users] Keyboard Device Pairing (gmane: message 13 of 20) Chris S
2006-09-25 21:47       ` 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=1159220826.20997.21.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=leonerd@leonerd.org.uk \
    /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