Reply
Thread Tools
Posts: 7 | Thanked: 0 times | Joined on Feb 2010
#221
Hi
Coming here as the happy owner of the N900 I really want to be able to use a BT keyboard with the device. Unfortunately I have no skill in programming what so ever and therefore I have a hard time understanding the above explenations.
Is there anyone that could provide for me (I think there are others as well) a very basic step by step instruction on how to make a BT keyboard work with the N900?
Kind regards
 
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#222
Originally Posted by borgmountain View Post
Hi
Coming here as the happy owner of the N900 I really want to be able to use a BT keyboard with the device. Unfortunately I have no skill in programming what so ever and therefore I have a hard time understanding the above explenations.
Is there anyone that could provide for me (I think there are others as well) a very basic step by step instruction on how to make a BT keyboard work with the N900?
Kind regards
You can't get a lot easier than JoHny's instructions here
http://talk.maemo.org/showpost.php?p...&postcount=174
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
Posts: 85 | Thanked: 29 times | Joined on Jan 2008
#223
Hi,

I was intrigued by the post from jakoleh, who obviously had no trouble to configure his non-us keyboard, by issuing the same command as his:

Code:
setxkbmap -v 10 -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model nokiasu8w -layout fi
No error on the command line.

Then I issued the same command for a french layout.

Code:
setxkbmap -v 10 -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model nokiasu8w -layout fr
And this gave the following error:

Code:
Error loading new keyboard description
Note: Changing from "nokiasu8" to "pc105" model result on my N900 in the above error as well, regardless of the layout.

Ulysses
 
Posts: 94 | Thanked: 10 times | Joined on Jan 2010
#224
I had a look and I don't think that there's a fr layout defined in /usr/share/X11/xkb-chinook/symbols/nokia_vndr/su-8w...
 
Posts: 94 | Thanked: 10 times | Joined on Jan 2010
#225
Further on my problem getting Ctrl to work on my dinovo mini, here's a xev output:

KeyPress event, serial 40, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109249971, (598,205), root598,261),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:

XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109250161, (598,205), root598,261),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

A successful key (TAB as an example) looks like this


KeyPress event, serial 26, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109423817, (598,205), root598,261),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XmbLookupString gives 1 bytes: (09) " "

XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3e00001,
root 0x44, subw 0x0, time 109424025, (598,205), root598,261),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XFilterEvent returns: False


Does anyone know anything about XLookupString and why it is failing for Ctrl?

Anyway I can observe happens when I press the Ctrl on the N900s keyboard? (xev does not seem to log keypresses on the device itself!)

Thanks

Last edited by meep; 2010-02-15 at 00:19.
 
Posts: 7 | Thanked: 0 times | Joined on Feb 2010
#226
Alright installed rootsh
How do I do the next step. What and where do I write:

First, you need to enable bluetooth HID support, edit /etc/bluetooth/main.conf and remove "hid" from "DisablePlugins=" line. Then send these commands:
stop bluetoothd
start bluetoothd

Kind regards
 
Posts: 85 | Thanked: 29 times | Joined on Jan 2008
#227
meep, fr and fi are both defined in the same place: /usr/share/X11/xkb-chinook/symbols/

I have no idea why it works for the fi and de layout but not for the fr nor be.
 
Posts: 94 | Thanked: 10 times | Joined on Jan 2010
#228
Originally Posted by Ulysses View Post
meep, fr and fi are both defined in the same place: /usr/share/X11/xkb-chinook/symbols/

I have no idea why it works for the fi and de layout but not for the fr nor be.
True but fr does not look like it's defined within this file which will be referenced when using the su-8w layout:

/usr/share/X11/xkb-chinook/symbols/nokia_vndr/su-8w.

I don't think the folders under symbols for countries are actually being referenced when setting keyboard maps as they're not referenced for use by anything else so far as I can see (could be wrong)

Cheers
 
Posts: 7 | Thanked: 0 times | Joined on Feb 2010
#229
I seem to get stuck at step five where I get the following error message:

Error org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with signature "" on interface "org.bluez.Input" doesn't exist

What do I do wrong.
Can anyone please enlighten me

Kind regards

------------------
Originally Posted by JoHnY View Post
Some commands need to be run as root, if you haven't already done it, install package "rootsh" and then you can gain root privileges by entering "sudo gainroot" in the X terminal.

First, you need to enable bluetooth HID support, edit /etc/bluetooth/main.conf and remove "hid" from "DisablePlugins=" line. Then send these commands:
stop bluetoothd
start bluetoothd

Now:

1. Enable bluetooth through GUI (if it's not on) and pair the keyboard with the device through GUI (although I'm not sure if pairing through GUI is necessary to get the keyboard working, but it does not hurt and you need to do it just once)
2. Issue the following command:
Code:
dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.DefaultAdapter
You'll get a response like: object path "/org/bluez/11984/hci0"
4. Enter this command: hcitool scan (be sure that your bluetooth keyboard did not fall into sleep mode in the meantime and that it's still sending out information about its presence - usually indicated by blinking blue light)
After some time, you should be able to see the MAC address of your keyboard (if you don't have 10 other people having the same bluetooth keyboard in a close distance to you, you should be able to identify yours by the name)
5. Send this command:
Code:
dbus-send --system --print-reply --dest=org.bluez  /org/bluez/11984/hci0/dev_00_07_61_75_xx_xx org.bluez.Input.Connect
BUT you need to replace /org/bluez/11984/hci0 by whatever response you got in step 2 (actually the number should be only thing that will be different) and replace 00_07_61_75_xx_xx by the mac address of your keyboard from step 4 (replacing all colons by underscores)

Now you should be able to use the keyboard, but only functional characters will be letters a-z, space, backspace and Enter (not even numbers)
To get the keyboard to be fully working, continue with these steps:

1. Download xkb-chinook.tar file from this post: http://talk.maemo.org/showpost.php?p=441444&postcount=3 and untar it to the /usr/share/X11 directory (Copy it to the /usr/share/X11 directory, then go to that directory and type "tar xf xkb-chinook.tar". You will probably have to be root to do this and you can delete xkb-chinook.tar file after you untar it to save space.)
2. Then, as root, do:
Code:
cd /usr/share/X11
cp -i xkb-chinook/symbols/pc xkb/symbols/.
cp -i xkb-chinook/symbols/us xkb/symbols/.
cp -i xkb-chinook/geometry/pc xkb/geometry/.
3. Type this command: hildon-im-xkbtool --list
This will list all connected HID devices, it will look like this:
Code:
ID 0, Name: "Virtual core pointer"
ID 1, Name: "Virtual core keyboard"
ID 2, Name: "TSC2005 touchscreen"
ID 3, Name: "omap_twl4030keypad"
ID 4, Name: "Freedom Pro Keyboard"
The "omap_twl4030keypad" is the N900's hardware keyboard and after that line, you should see your keyboard connected (Freedom Pro Keyboard in my case above). Write down the ID of your keyboard.
4. Do: setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us
Replace "-device 4" with your device ID of your keyboard from step 3, if it's different, but most likely you will get 4 as well.
5. Press any key on the N900 keyboard (not on the bluetooth one). I don't know why this is needed, but it is :-)
6. Your keyboard is now fully functional.

When you turn your keyboard off and on again, it will now pair automatically and the only thing you need to do is to issue the setxkbmap command from step 4 above, to get all keys working.

Hope this helps.

JoHnY
 
Posts: 85 | Thanked: 29 times | Joined on Jan 2008
#230
Is anything changed after the latest firmware update (3.2010.02-8.002) as to what concerns us in this thread, pairing/connecting/remapping bluetooth keyboards?

Thanks in advance.
 
Reply

Thread Tools

 
Forum Jump


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