View Single Post
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#295
Greetings:
I'm trying to attach a Solidtek ASK3462 keyboard to my N900.


I installed extkbd, extmou, and rebooted and re-paired....
Keyboard and its touchpad were up and running!!!

Went to Setting > Personalization > External Keyboard; and set it to
Generic 105-key (intl) PC
USA
Intl
and SAVE.

...no change! It still acts just like the internal keyboard.
Alphabetic keys, Function keys, Cursor keys all work.
Numeric keys, shift key, symbols do not work.

Symbols and numbers and be accessed with a long press.

And as a test only, I even tried setting the keyboard to Dvorak.
(i.e. a change that I would definitely notice, if it worked)

No change.

I then spent the past 8+ hours reading about xkb and re-reading your posts.

I'm beat.... help...
---------------------
  • Am I doing anything obviously wrong?
  • What should happen after changing the keyboard definition?
    The manufacturer has moved many of the symbols keys, so I don't expect them to work.
    But the number keys are right where they should be; so shouldn't they should work?
    How about SHIFT and CAPS-LOCK?
---------------
Some background info:
  • N900 PR1.2
  • List of BT connections:
    Nokia-N900-42-11:~# hildon-im-xkbtool --list
    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: "BTKB-1736"
  • /usr/share/hal/fdi/policy/20thirdparty/99-x11-external-keyboard.fdi:
    <?xml version="1.0" encoding="UTF-8"?>
    <deviceinfo version="0.2">
    <device>
    <match key="info.capabilities" contains="input.keyboard">
    <match key="info.product" contains="BTKB-1736">
    <merge key="input.x11_options.XkbModel" type="string">pc105</merge>
    <merge key="input.x11_options.XkbLayout" type="string">us(intl),gb(intl)</merge>
    <merge key="input.x11_options.XkbOptions" type="string">grp:win_switch,caps:shiftlock</merge>
    </match>
    </match>
    </device>
    </deviceinfo>
 

The Following User Says Thank You to kbyork For This Useful Post: