Notices


Reply
Thread Tools
Posts: 19 | Thanked: 4 times | Joined on Nov 2010
#281
Originally Posted by freemangordon View Post
Sorry for being slow but it was Saturday evening . Did you succeed to install extkbd?

Cheers.
I was personally surprised by the depth in which this application is tackling the problem... Great Job.
Feature Request for GUI of program:
Assigned keyboard short cuts to allow total control of Maemo 5 using keyboard only (maybe a mouse emulator using arrows when a visual element of a menu is displayed)
Thanks
 
Posts: 9 | Thanked: 0 times | Joined on May 2011
#282
Hi guys i want to replace one layout with another how to do that? The layouts are placed in /usr/share/X11/xkb/symbols/ , right so how to "refresh" the layouts list?
 
Posts: 166 | Thanked: 74 times | Joined on May 2010
#283
Originally Posted by nCode View Post
Hi guys i want to replace one layout with another how to do that? The layouts are placed in /usr/share/X11/xkb/symbols/ , right so how to "refresh" the layouts list?
Check out the base file within the rules directory--from there, you can mix and match all the settings (including which layout is mapped to various model/language/variant combinations).
 
Posts: 166 | Thanked: 74 times | Joined on May 2010
#284
So using evtest and xinput, I've been able to verify that all the keys are making it to my n900 and confirmed that the default keycode mappings should be valid. However, for some reason, the mappings aren't working. Only the following keys are working:
- all letters
- space
- tab
- backsapce
- enter
- comma
- period
- shift (though not at the same time as i press another key)
- esc
- directional keys
- f keys

Numbers, most special characters, and most special keys (such as capslock, ctrl, alt, etc) aren't working though events are sent in. Any idea what could be wrong? I've tried different mappings, but I can't get any of these other keys to work. Has anyone else experienced similar issues and/or know how to get numeric keys and special keys working?
 
Posts: 166 | Thanked: 74 times | Joined on May 2010
#285
Here's what lshal is reporting:

Code:
  input.device = '/dev/input/event4'  (string)
  input.product = 'Motorola Bluetooth Wireless Keyboard'  (string)
  input.x11_driver = 'evdev'  (string)
  input.x11_options.XkbLayout = 'us,us'  (string)
  input.x11_options.XkbModel = 'pc105'  (string)
  input.x11_options.XkbOptions = ',caps:shiftlock'  (string)
  input.x11_options.XkbRules = 'evdev'  (string)
  input.x11_options.XkbVariant = ''  (string)
  input.xkb.layout = 'us'  (string)
  input.xkb.model = 'nokiarx51'  (string)
  input.xkb.options = {''} (string list)
  input.xkb.rules = 'base'  (string)
  input.xkb.variant = ''  (string)
  linux.device_file = '/dev/input/event4'  (string)
Is the nokiarx51 model supposed to appear there? My bluetooth keyboard seems to be using that mapping...
 

The Following User Says Thank You to jschan For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#286
Originally Posted by jschan View Post
Here's what lshal is reporting:

Code:
  input.device = '/dev/input/event4'  (string)
  input.product = 'Motorola Bluetooth Wireless Keyboard'  (string)
  input.x11_driver = 'evdev'  (string)
  input.x11_options.XkbLayout = 'us,us'  (string)
  input.x11_options.XkbModel = 'pc105'  (string)
  input.x11_options.XkbOptions = ',caps:shiftlock'  (string)
  input.x11_options.XkbRules = 'evdev'  (string)
  input.x11_options.XkbVariant = ''  (string)
  input.xkb.layout = 'us'  (string)
  input.xkb.model = 'nokiarx51'  (string)
  input.xkb.options = {''} (string list)
  input.xkb.rules = 'base'  (string)
  input.xkb.variant = ''  (string)
  linux.device_file = '/dev/input/event4'  (string)
Is the nokiarx51 model supposed to appear there? My bluetooth keyboard seems to be using that mapping...
May I have your /usr/share/hal/fdi/policy/20thirdparty/99-x11-external-keyboard.fdi attached here.
 
Posts: 166 | Thanked: 74 times | Joined on May 2010
#287
sure, thanks in advanced for looking into it!
Attached Files
File Type: txt 99-x11-external-keyboard.fdi.txt (573 Bytes, 98 views)
 
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#288
Originally Posted by jschan View Post
sure, thanks in advanced for looking into it!
And could you do lshal > hal.txt and attach hal.txt here
 
Posts: 166 | Thanked: 74 times | Joined on May 2010
#289
absolutely--i shortened it a bit. please let me know if i left out key info you are looking for.
Attached Files
File Type: txt lshal.txt (6.6 KB, 134 views)
 

The Following User Says Thank You to jschan For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#290
Everything looks ok and TBH it is different from your previous posting:

input.x11_options.XkbOptions = ',caps:shiftlock' (string)

vs

input.x11_options.XkbOptions = 'grp:alt_shift_toggle,caps:shiftlock' (string)

But it should work in both cases.

The only thing I could think of is that your keyboard reports itself having too much capabilites:

info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys', 'input.mouse', 'button'} (string list)

I would recommend to search for 'input.keyboard', 'input.keypad', 'input.keys', 'input.mouse' in .fdi files in /usr/share/hal/fdi/policy/

Later on when I have time I will check my Apple Wireless and will compare lshal result with yours
 

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

Tags
bluetooth, keyboard


 
Forum Jump


All times are GMT. The time now is 17:39.