Notices


Reply
Thread Tools
Posts: 32 | Thanked: 77 times | Joined on Dec 2011
#1
kbdd has been packaged for maemo in order to allow spp bluetooth keyboards as input.

From the documentation:
Code:
 kbdd can enable the following bluetooth keyboards:
        foldable  - Compaq/HP foldable keyboard
        stowaway  - Targus Stowaway keyboard
        stowawayxt - Stowaway XT
        snapntype - Snap'n'Type
        hpslim    - HP Slim keyboard
        smartbt   - Smart Bluetooth keyboard
        lirc      - LIRC consumer IR
        belkinir  - Belkin IR (not IrDA)
        flexis    - Flexis FX-100 keyboard
        g250      - Benq G250 gamepad
        pocketvik - GrandTec PocketVIK
        microfold - Micro Innovations Foldaway keyboard
        micropad  - Micro Innovations Datapad
        microkbd  - Compaq MicroKeyboard
        freedom   - Freedom keyboard (patched layout of bottom row)
        btfoldable - HP iPAQ Bluetooth Foldable Keyboard
        elektex   - Elektex Cloth Keyboard
        elektex_unmapped - Elektex Cloth Keyboard (Unmapped)
 
 To enable kbdd for your keyboard, two steps are neccessary
  - Pair the device such that it
    appears in the bluetooth device list.
  - Specify the keyboard driver using
    the kbdd config button.
 The bluetooth icon turns from white to blue if the keyboard
 is connected and a banner gets displayed.
 
 The kbdd daemon tries to connect to the keyboard every 30s,
 so the battery drain should not be too big. It connects
 to the uinput kernel module to create a virtual keyboard.
 The extkbd package can be used to automatically configure
 the keyboard layout.
 
 The original kbdd was spiced up with maemo patches to
 output a banner if the keyboard connected or disconnected.
 Since I only own a freedom keyboard, so far I only provide
 maemo patches for the freedom driver. However, the
 non-patched kbdd shoud run out of the box.
Help for a port to meego and a configuration GUI would be appreciated.
 
Posts: 32 | Thanked: 77 times | Joined on Dec 2011
#2
From another thread:

Originally Posted by lonk View Post
Ok here is a photo of the keyboard


And I'm going to start pressing keys from the first row top left to the right ( so ESC key, 1, 2, 3 ,4 .... BACKSPACE) then do the same with second row and so on


Here is the result for the first row from ESC to 5 (key 6 causes a crash and the terminal closes, it could be key 5 causing this )


Code:
Nokia-N900:~# kbdd -d -c /etc/bluetooth/kbdd/kbdd.conf
14 32
press 32
142 33
release 33
dð^[[^[[C22 57
press 57
 150 15
release 15
 ^[[^[[C30 12
press 12
-158 13
release 13
\^[[^[[C38 26
press 26
166 27
release 27
[^[[^[[C37 25
press 25
p165 26
release 26
þ^[[^[[C46 28
press 28
174 49
release 49
From the first keys i can see that the keyboard is not compatible to the freedom driver from kbdd and very probably also to all the other drivers. However the keypresses are detected and thus buiding a driver would not be a problem. The next package 0.6 will have the -n option to not output the keys to the kernel such that the terminal will not crash.

Code:
 sudo gainroot
 stop kbdd # to stop the running daemon
 rfcomm bind all #once to create the device files
 kbdd -d -n -c /etc/bluetooth/kbdd/kbdd.conf # to output the input keys without passing them to the kernel
 start kbdd # to start the daemon again
If you think it i worth than you could give it another try.
 
Posts: 638 | Thanked: 1,692 times | Joined on Aug 2009
#3
A "little" bug:

After the installation of kbdd the internal virtual keyboard does not work anymore.

Running:
apt-get purge kbdd

Solves the problem and makes standard virtual keyboard appear again.
 

The Following User Says Thank You to xes For This Useful Post:
Posts: 32 | Thanked: 77 times | Joined on Dec 2011
#4
I guess that is related to the fact that kbdd emulates that a keyboard is connected as long as it runs (not only if the keyboard really is connected).

On the tbd list.
 

The Following 2 Users Say Thank You to hypnotoad123 For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 01:18.