[kiv57]

Hi,

I have a dell keyboard with some classical media keys. Strangely, just 2 of them are recognized in xbmc, althought my ubuntu 8.10 deals with all of them "out of the box".

In the "/var/tmp/kiv-xbmc.log", I have, for the 2 working keys :
- Volume_Down (XF86AudioLowerVolume in X)

Code:

DEBUG: OnKey: 65450 pressed, action is 89

==> OK
- Stop (XF86AudioStop)

Code:

OnKey: 65454 pressed, action is 89

==> wrong action, i know, have to fix my keymap.xml.

For non-working keys :
- Volume_Up (XF86AudioRaiseVolume)

Code:

DEBUG: SDLKeyboard found something unknown (unicode <> printable ASCII): scancode: 123, sym: 0, unicode: 0, modifier: 4096

For other keys : only "scancode" changes : here are the scancodes :
- Mute (XF86AudioMute) : scancode: 121
- Previous_track (XF86AudioPrev) : scancode: 173
- Next_track (XF86AudioNext) : scancode: 171
- Play/Pause (XF86AudioPlay) : scancode: 172
- audio_program_launcher (XF86Tool) : 179

xmodmap -pke command says :

Code:

keycode 121 = XF86AudioMute NoSymbol XF86AudioMute NoSymbol XF86AudioMute
keycode 122 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume
keycode 123 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume
keycode 171 = XF86AudioNext NoSymbol XF86AudioNext NoSymbol XF86AudioNext
keycode 172 = XF86AudioPlay XF86AudioPause XF86AudioPlay XF86AudioPause XF86AudioPlay XF86AudioPause
keycode 173 = XF86AudioPrev NoSymbol XF86AudioPrev NoSymbol XF86AudioPrev
keycode 174 = XF86AudioStop XF86Eject XF86AudioStop XF86Eject XF86AudioStop XF86Eject
keycode 179 = XF86Tools NoSymbol XF86Tools NoSymbol XF86Tools

So the keycodes in xmodmap are matching the scancodes for non-working keys in xbmc log.

So what's the difference between working and non-working keys ?
Is there a way to fix it ?

I tried to fix it for several days (!) with evrouter, but I'm unable to make it seeing the entries in /dev/input/event*...

[kiv57]

Great news : all my media keys are now fully supported by xbmc 9.04, from keyboard and MX Air mouse.

Thanks to that release, xbmc becomes usable for me, and many other PC users I guess...

[CrashX]

See here for more keys that aren't mapped .. http://forum.xbmc.org/showthread.php?tid=50207 .. It gives an idea on how to fix it ..

[w1ll14m]

Thanx CrashX, it seems revision 23049 somehow resolved my problem.
Thanx fpr the reply!