All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Phil Endecott" <spam_from_bluez_users@chezphil.org>
To: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Apple wireless keyboard
Date: Thu, 24 Apr 2008 16:49:32 +0100	[thread overview]
Message-ID: <1209052172510@dmwebmail.dmwebmail.chezphil.org> (raw)
In-Reply-To: <2D804CC1-0304-47A8-B67F-00814B3BE516@gmail.com>

Hi Johan,

Johan Hedberg wrote:
>> - Installing a kernel with the bluetooth modules.
>> - Installing bluez-utils.
>> - Starting hidd and hcid (enabling them in /etc/default/bluetooth on
>> this Debian box)
>
> This might have been the first step that went wrong. hidd has been  
> superseded by the input service already some time ago.

I'm using the Debian package of bluez-utils version 3.30-3, following 
their instructions in /usr/share/doc/bluez-utils/README.Debian.gz.  
I've already submitted some suggested changes to this document, so if 
there are some more things that they need to update, let me know and 
I'll file a report.

> You can check  
> whether it's enabled e.g. with the bluetooth-properties app that comes  
> with bluez-gnome (assuming you use Gnome).

I'm not using Gnome.

> You will need to tell the  
> input service about your keyboard using the CreateDevice D-Bus method  
> call (maybe bluetooth-properties even supports doing this through its  
> GUI). Some python examples can nevertheless be found in the BlueZ  
> wiki: http://wiki.bluez.org/wiki/HOWTO/InputDevices

>> - Running hcitool scan to get the keyboard address (which I've now
>> written on the back)
>> - Running hidd --connect <addr> and typing 1234RET on the keyboard
>
> Both of these are fine but instead of using hidd you'd use the Connect  
> method that the input service provides (I think there's an example of  
> that too in the wiki).

Hmm.  So rather than running "hcitool scan" and "hidd --conect <addr>", 
I have to write a few lines of python (a language I've never used) to 
communicate over dbus (a protocol that I've never used) to this "input 
service" thing?  If that's the case, then I can't say this looks like 
an improvement in usability.

>> So
>> after I reboot the keyboard should be able to connect without user
>> interaction.  But so far I have failed to make this happen.
>
> Probably because you don't have a HID server to accept the incoming  
> connection request.

hidd --master --server is started by the Debian init.d script.

See my other messages for my further thoughts about why this is not 
working; I think it's a lower-level problem.


Regards, Phil.





-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-04-24 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 14:58 [Bluez-users] Apple wireless keyboard Phil Endecott
2008-04-22 15:13 ` Odysseus Flappington
2008-04-23 19:04   ` Phil Endecott
2008-04-23 19:50     ` Odysseus Flappington
2008-04-24 15:32       ` Phil Endecott
2008-04-23 17:25 ` Johan Hedberg
2008-04-24 15:49   ` Phil Endecott [this message]
2008-04-24 17:29     ` Johan Hedberg
  -- strict thread matches above, loose matches on Subject: below --
2006-07-12  4:07 [Bluez-users] Apple Wireless Keyboard William Voorhees
2006-07-12 23:27 ` Marcel Holtmann
2004-06-11 18:44 [Bluez-users] apple wireless keyboard Simone Crippa
2004-06-14 12:31 ` Collin R. Mulliner
2004-06-14 23:29   ` Marcel Holtmann
2004-06-14 16:16 ` Marcel Holtmann

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=1209052172510@dmwebmail.dmwebmail.chezphil.org \
    --to=spam_from_bluez_users@chezphil.org \
    --cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.