this should get mostly working keys for tilt2 users:

http://www.happyassassin.net/extras/tilt2/rootfs.img

instructions: 1 - grab that and replace the rootfs.img in the root of your SD card with it.
2 - edit the file STARTUP.TXT in the root of your SD card. on the long line with 'cmdline' in it, add this to the parameters:

physkeyboard=tilt2

it should wind up looking something like this:

set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock-7x00.a11=500 msmvkeyb_toggle=off physkeyboard=tilt2 pmem.extra=1 gsensor_axis=-1,-2,3 force_cdma=1"

that's it! now just boot android and you should have mostly working keys that do what they say on the labels. The dpad may be slightly broken and I haven't mapped functions for the OK and Home buttons, or the blue functions for most of the bottom row keys, but all the important symbols should work right. Thanks a lot to reefermattness for testing this for me - he verified it works well for him.

Tomorrow Markinus' kernel fixes for some Rhodium keyboard quirks - that are in the kernel in reefermattness' cab, but not in the upstream htc-msm-android kernel builds - should go upstream. Then I can get a single keymap done which should hopefully have all functions working whatever kernel you use. hopefully! Right now if you use this on the htc-msm-android build a few more things will be broken, like the dpad, though it's still pretty much usable.

I'll try and do a Touch Pro 2 layout map tomorrow if people send me the info. Here's the skinny.

You need to get a real terminal app: pTerminal isn't good enough. Android Terminal Emulator seems good. Grab that, and run it. It'll show a Linux-style command prompt.

Run the command 'getevent'. It should complain a bit about not being able to open some devices, and then it'll just...sit there, until you press a key or the touchscreen. When you do that, you'll see a bunch of hexadecimal numbers printed to the screen.

The *middle* number of the *second* line of each 'block' of output (play around pressing a few keys to get a feel for the output; a good way to see what one block looks like is to touch the touchscreen, which will generate a long block labelled 'event1', then press a key - keypresses are 'event2', so you can see where the keypress block starts from where 'event1' turns into 'event2') should be a four-digit one which is different for each key you press. What I need to know is, for every key on the keyboard, what that number is. Most importantly the ones that don't do what they're supposed to. I've got a reference picture of the Touch Pro 2 keyboard:

http://mynokiablog.files.wordpress.c...keyboard-2.jpg

if yours looks different from that, tell me how (or preferably take/find a picture). And tell me exactly what variant of the TP2 yours is. Thanks!