100 replies to this topic

[betacentauri]

You can also use evtest for testing. Should be on the feed. Maybe look into evtest source code or into e2 sources how they handle it.

[serdeliuk]

Hi @betacentauri, i tested evtest and works, it shows all keys, it seems that i have issues with SDL2 implementation, i will thy other SDL versions as well to check if it is a bug or i am missing a compile dependency 

[rantanplan]

mhh...

old kernel ...
there certainly can not hurt a cflags when compiling.
But that's just an idea out of the feeling.

 

CFLAGS += " -std=gnu11"

[serdeliuk]

I was busy those days and didn't had enough  time to investigate this, but now i am back in business, upgraded to OpenPLi 7.2 the dev env as well as the vusolo4k, however i was unable  to find a way to get all keys through SDL2, under directfb as well as from python with evdev module i am able to get all keys, so probably is something wrong with SDL2, their support forum seems to be useless as well.

[serdeliuk]

A nice surprise is that the SDL2.0.10 has been added to OpenPLi7.2 by default, thanks, also exists in binary repo but it is missing dev package

[WanWizard]

We filter -dev, -doc and -dbg packages from the feed to limit the size of the feeds.

[serdeliuk]

Hi @WanWizard i see, thanks, then you should remove -staticdev too "libsdl2-2.0-staticdev"

[WanWizard]

Thanks, guess we've missed those. I'll pass it on.

[serdeliuk]

I found the issue with the missing keys, the SDL2 does not have them implemented )))) i was able to add them to my SDL2 development tree and i have now all keys working, i will build a patch later today maybe you will add it to the recipe or to be downloadable at least for those who need it.

[WanWizard]

I will build a patch later today maybe you will add it to the recipe ...

 

Depends on what keys this is about...

[serdeliuk]

the patch will just add the missing keys, will not remove anything, following is a list of keys which does not work at all

 

AV - does not works with evtest either so will not be added

 

Event code 174 (KEY_EXIT)

Event code 377 (KEY_TV)

Event code 388 (KEY_TEXT)

Event code 370 (KEY_SUBTITLE)

Event code 412 (KEY_PREVIOUS)

Event code 407 (KEY_NEXT)

Event code 398 (KEY_RED)

Event code 399 (KEY_GREEN)

Event code 400 (KEY_YELLOW)

Event code 401 (KEY_BLUE)

Event code 352 (KEY_OK)

Event code 358 (KEY_INFO)

Event code 402 (KEY_CHANNELUP)

Event code 403 (KEY_CHANNELDOWN)

Event code 393 (KEY_VIDEO)

Event code 392 (KEY_AUDIO)

Event code 207 (KEY_PLAY)

Event code 377 (KEY_TV)

Event code 167 (KEY_RECORD)

Event code 385 (KEY_RADIO)

[WanWizard]

Ah, those keys...

[serdeliuk]

yeahhhh

[serdeliuk]

I have builded the patch and tested on my OpenPli 7.2 dev env and it works fine, build the SDL2 with all remote control keys as expected.

The attached patch will modify following files

 

include/SDL_keycode.h

include/SDL_scancode.h

src/events/SDL_keyboard.c

src/events/scancodes_linux.h

src/events/scancodes_xfree86.h

 

And will do following actions,

 

Rename following keys,

 

AudioPlay to PlayPause

AudioRewind to Rewind

AudioFastForward to FastForward

 

Add following missing keys,

 

Event code 167 (KEY_RECORD)

Event code 174 (KEY_EXIT)

Event code 207 (KEY_PLAY)

Event code 352 (KEY_OK)

Event code 358 (KEY_INFO)-EPG

Event code 370 (KEY_SUBTITLE)

Event code 377 (KEY_TV)

Event code 385 (KEY_RADIO)

Event code 388 (KEY_TEXT)

Event code 392 (KEY_AUDIO)

Event code 393 (KEY_VIDEO)

Event code 398 (KEY_RED)

Event code 399 (KEY_GREEN)

Event code 400 (KEY_YELLOW)

Event code 401 (KEY_BLUE)

Event code 402 (KEY_CHANNELUP)

Event code 403 (KEY_CHANNELDOWN)

Event code 407 (KEY_NEXT)

Event code 412 (KEY_PREVIOUS)

 

I think will be useful to be added to `meta-openpli/recipes-graphics/libsdl2/libsdl2` patches folder

 

 

Attached Files

•  solo4k-sdl2.0.10-add-missing-keys.zip   2.44KB   6 downloads

[WanWizard]

Added to the todo list.

[serdeliuk]

Thanks @WanWizard

[WanWizard]

Are these codes VU Solo 4K or VU remote specific?

[serdeliuk]

I don't think are specific for a remote or a box, i think it is safe to add the patch for all boxes as the patch add missing keys and rename some of declared ones to standard names.

If by chance some of new keys will differ on different remotes/boxes at least the user will have them generating events, with different names indeed but will work and will know where to search.

 

Just to test, my evtest say that my event0 has the following keys, if you have any stb by hand please check your output

 

Available devices:

/dev/input/event0: dreambox advanced remote control (native)

Select the device event number [0-0]: 0

Input driver version is 1.0.1

Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0

Input device name: "dreambox advanced remote control (native)"

Supported events:

  Event type 0 (EV_SYN)

  Event type 1 (EV_KEY)

    Event code 2 (KEY_1)

    Event code 3 (KEY_2)

    Event code 4 (KEY_3)

    Event code 5 (KEY_4)

    Event code 6 (KEY_5)

    Event code 7 (KEY_6)

    Event code 8 (KEY_7)

    Event code 9 (KEY_8)

    Event code 10 (KEY_9)

    Event code 11 (KEY_0)

    Event code 12 (KEY_MINUS)

    Event code 13 (KEY_EQUAL)

    Event code 14 (KEY_BACKSPACE)

    Event code 16 (KEY_Q)

    Event code 17 (KEY_W)

    Event code 18 (KEY_E)

    Event code 19 (KEY_R)

    Event code 20 (KEY_T)

    Event code 21 (KEY_Y)

    Event code 22 (KEY_U)

    Event code 23 (KEY_I)

    Event code 24 (KEY_O)

    Event code 25 (KEY_P)

    Event code 28 (KEY_ENTER)

    Event code 30 (KEY_A)

    Event code 31 (KEY_S)

    Event code 32 (KEY_D)

    Event code 33 (KEY_F)

    Event code 34 (KEY_G)

    Event code 35 (KEY_H)

    Event code 36 (KEY_J)

    Event code 37 (KEY_K)

    Event code 38 (KEY_L)

    Event code 39 (KEY_SEMICOLON)

    Event code 40 (KEY_APOSTROPHE)

    Event code 41 (KEY_GRAVE)

    Event code 42 (KEY_LEFTSHIFT)

    Event code 43 (KEY_BACKSLASH)

    Event code 44 (KEY_Z)

    Event code 45 (KEY_X)

    Event code 46 (KEY_C)

    Event code 47 (KEY_V)

    Event code 48 (KEY_

    Event code 49 (KEY_N)

    Event code 50 (KEY_M)

    Event code 51 (KEY_COMMA)

    Event code 52 (KEY_DOT)

    Event code 53 (KEY_SLASH)

    Event code 56 (KEY_LEFTALT)

    Event code 57 (KEY_SPACE)

    Event code 100 (KEY_RIGHTALT)

    Event code 102 (KEY_HOME)

    Event code 103 (KEY_UP)

    Event code 104 (KEY_PAGEUP)

    Event code 105 (KEY_LEFT)

    Event code 106 (KEY_RIGHT)

    Event code 107 (KEY_END)

    Event code 108 (KEY_DOWN)

    Event code 109 (KEY_PAGEDOWN)

    Event code 113 (KEY_MUTE)

    Event code 114 (KEY_VOLUMEDOWN)

    Event code 115 (KEY_VOLUMEUP)

    Event code 116 (KEY_POWER)

    Event code 128 (KEY_STOP)

    Event code 138 (KEY_HELP)

    Event code 139 (KEY_MENU)

    Event code 164 (KEY_PLAYPAUSE)

    Event code 167 (KEY_RECORD)

    Event code 168 (KEY_REWIND)

    Event code 174 (KEY_EXIT)

    Event code 176 (KEY_EDIT)

    Event code 207 (KEY_PLAY)

    Event code 208 (KEY_FASTFORWARD)

    Event code 272 (BTN_LEFT)

    Event code 273 (BTN_RIGHT)

    Event code 352 (KEY_OK)

    Event code 358 (KEY_INFO)

    Event code 370 (KEY_SUBTITLE)

    Event code 377 (KEY_TV)

    Event code 384 (KEY_TAPE)

    Event code 385 (KEY_RADIO)

    Event code 388 (KEY_TEXT)

    Event code 392 (KEY_AUDIO)

    Event code 393 (KEY_VIDEO)

    Event code 398 (KEY_RED)

    Event code 399 (KEY_GREEN)

    Event code 400 (KEY_YELLOW)

    Event code 401 (KEY_BLUE)

    Event code 402 (KEY_CHANNELUP)

    Event code 403 (KEY_CHANNELDOWN)

    Event code 407 (KEY_NEXT)

    Event code 412 (KEY_PREVIOUS)

[serdeliuk]

Just to mention, the above evtest output is from my Vu Solo4K

[serdeliuk]

Because the implementation of SDL keys, if a key is not declared even the key exists and generate events SDL will not display any event, because of that i started to dig into directfb first and was unable to find the issue, obvious why... so when started to look into SDL source i was mesmerized how badly/poorly is made, i wonder why they implemented only PC keyboard keys events(few mac keyboard keys too) when the main usage of the SDL is on embedded systems which does not have keyboards.....