[w1ll14m]

I have a problem with my dinovo mini on xbmc linux.
I'm currently running xbmc on rev 22040.
Newer revisions do compile and run well but they give me problems with the media keys on my dinovo mini.
Example:
Volume up = rewind.

is it a known problem with the recent changes ?

I've searched the forums, but couldn't find anything related, but still excuse me if this might be a double post.


regards,
William

[elupus]

didn't know about this one.. have one of those keyboards so will have alook. what linux system are you running?

[elupus]

Just checked on jaunty.. works just fine with a window manager running atleast

[w1ll14m]

i'm running gentoo linux.
It's just bare X11 and xbmc standalone.
i will try to get some debug information when the button is pressed.

Also, i use the usb (bluetooth) dongle that came with the package and the dinovo mini is set to pc mode.

Could it be hal or dbus related ?

--edit--
Added info

[elupus]

without window manager we rely on raw keyboard events. those are abit hit and miss to get right. but i think i know what's going on. looks to be yet another casualty of the recent directx merge

[w1ll14m]

ok, well here's some debug info:
==
15:16:48 T:3050395488 M:341291008 DEBUG: HAL: Device (/org/freedesktop/Hal/devices/usb_device_46d_c71f_000761E1A206_if0_logicaldev_input) Condition ButtonPressed | volume-up
15:16:48 T:2887424912 M:340918272 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
15:16:48 T:2887424912 M:340439040 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
15:16:48 T:2887424912 M:337895424 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
15:16:48 T:2887424912 M:337842176 WARNING: CDVDMessageQueue(audio)::Get - retrieved last data packet of queue
15:16:48 T:3050395488 M:337154048 DEBUG: SDLKeyboard: scancode: 162, sym: 0, unicode: 0, modifier: 0
15:16:48 T:3050395488 M:337154048 DEBUG: GetActionCode: Trying Hardy keycode for 0xffb3
15:16:48 T:3050395488 M:337047552 DEBUG: GetActionCode: Trying Hardy keycode for 0xffb3
15:16:48 T:3050395488 M:336887808 DEBUG: OnKey: 65459 pressed, action is 79
15:16:48 T:2887424912 M:336363520 DEBUG: CDVDPlayerAudio:: Discontinuty - was:3091464.629000, should be:18979666.666667, error:15888202.037667
15:16:49 T:3050395488 M:334532608 DEBUG: HAL: Device (/org/freedesktop/Hal/devices/usb_device_46d_c71f_000761E1A206_if0_logicaldev_input) Condition ButtonPressed | play-pause
15:16:50 T:3050395488 M:332185600 DEBUG: ------ Window Deinit (DialogSeekBar.xml) ------
==

Hal detects volume-up button
which in turn triggers action 79

Volume-down triggers ation 13 (stop now playing)

some debug when i press + (volume key on normal keyboard)
==
15:19:28 T:3050395488 M:327585792 DEBUG: OnKey: 65467 pressed, action is 88
15:19:28 T:3050395488 M:327585792 DEBUG: ------ Window Init (DialogVolumeBar.xml) ------
==

here it activates action 88 and volume goes up.
when i press - action 89 is triggered and volume goes down volume down

KeyID 65458 voldown scancode 174
KeyID 61522 volup scancode 176
KeyID 65453 volmute scancode 160
KeyID ?? record scancode 177
KeyID 65457 prev scancode 144
KeyID 65458 stop scancode 164
KeyID 65459 play scancode 162
KeyID 65456 next scancode 153

strangething: the key id of stop is the same as vol down?

Is there a place to look where those keys are bound to actions or scancodes?

--edit--
added more info

--edit--
added key id's

[thesoulhacker]

The media keys never worked for me on the mac mini, running the keyboard in bluetooth. Looking at the post above it seems like you guys had a fix implemented for it. Am i wrong making that assumption? was it just a linux fix?

I've been looking into getting this fixed for a while.

[elupus]

it should be fixed in svn for linux and the dinovo mini atleast. I've got no idea how that stuff works on the mac. It's still abit messy that code.

[w1ll14m]

it should be fixed in svn for linux and the dinovo mini atleast. I've got no idea how that stuff works on the mac. It's still abit messy that code.

yes indeed it seems after revision 23049 my problem is solved.
had some problems with libass so i reverted to r23049.

Thanks for the help and info!