Jump to content


Photo

solo4k sdl


  • Please log in to reply
100 replies to this topic

Re: solo4k sdl #61 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 14 January 2020 - 19:13

The first box I have handy reports:

Input driver version is 1.0.1
Input device ID: bus 0x19 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 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 119 (KEY_PAUSE)
    Event code 128 (KEY_STOP)
    Event code 139 (KEY_MENU)
    Event code 156 (KEY_BOOKMARKS)
    Event code 158 (KEY_BACK)
    Event code 167 (KEY_RECORD)
    Event code 168 (KEY_REWIND)
    Event code 174 (KEY_EXIT)
    Event code 207 (KEY_PLAY)
    Event code 208 (KEY_FASTFORWARD)
    Event code 226 (KEY_MEDIA)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 352 (KEY_OK)
    Event code 358 (KEY_INFO)
    Event code 362 (KEY_PROGRAM)
    Event code 365 (KEY_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 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 405 (KEY_LAST)
    Event code 407 (KEY_NEXT)
    Event code 412 (KEY_PREVIOUS)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)

 


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #62 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 14 January 2020 - 19:20

Great, so my keys not overlap your, some of VU keys exists on your box too with the same name, so i think is safe to add the patch for all boxes 


init 2 && init 3


Re: solo4k sdl #63 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 14 January 2020 - 19:21

if you have more boxes and you are willing to share the evtest output i can add all new keys to the patch, as it seems that your output have some extra keys, on which box what tested?


Edited by serdeliuk, 14 January 2020 - 19:22.

init 2 && init 3


Re: solo4k sdl #64 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 14 January 2020 - 21:23

The only other non-VU+ boxes I have running at the moment:
 

Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x14e4 product 0x0 version 0xc
Input device name: "dreambox 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 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    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 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 111 (KEY_DELETE)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 119 (KEY_PAUSE)
    Event code 128 (KEY_STOP)
    Event code 136 (KEY_FIND)
    Event code 138 (KEY_HELP)
    Event code 139 (KEY_MENU)
    Event code 142 (KEY_SLEEP)
    Event code 144 (KEY_FILE)
    Event code 148 (KEY_PROG1)
    Event code 150 (KEY_WWW)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 158 (KEY_BACK)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 167 (KEY_RECORD)
    Event code 168 (KEY_REWIND)
    Event code 172 (KEY_HOMEPAGE)
    Event code 174 (KEY_EXIT)
    Event code 207 (KEY_PLAY)
    Event code 208 (KEY_FASTFORWARD)
    Event code 215 (KEY_EMAIL)
    Event code 217 (KEY_SEARCH)
    Event code 226 (KEY_MEDIA)
    Event code 227 (KEY_SWITCHVIDEOMODE)
    Event code 352 (KEY_OK)
    Event code 357 (KEY_OPTION)
    Event code 358 (KEY_INFO)
    Event code 359 (KEY_TIME)
    Event code 361 (KEY_ARCHIVE)
    Event code 362 (KEY_PROGRAM)
    Event code 364 (KEY_FAVORITES)
    Event code 365 (KEY_EPG)
    Event code 366 (KEY_PVR)
    Event code 370 (KEY_SUBTITLE)
    Event code 373 (KEY_MODE)
    Event code 375 (KEY_SCREEN)
    Event code 377 (KEY_TV)
    Event code 381 (KEY_SAT)
    Event code 385 (KEY_RADIO)
    Event code 388 (KEY_TEXT)
    Event code 390 (KEY_AUX)
    Event code 392 (KEY_AUDIO)
    Event code 393 (KEY_VIDEO)
    Event code 394 (KEY_DIRECTORY)
    Event code 395 (KEY_LIST)
    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 408 (KEY_RESTART)
    Event code 412 (KEY_PREVIOUS)
    Event code 438 (KEY_CONTEXT_MENU)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    700
    Repeat code 1 (REP_PERIOD)
      Value    100

and

Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x1
Input device name: "dreambox 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 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
    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 208 (KEY_FASTFORWARD)
    Event code 352 (KEY_OK)
    Event code 358 (KEY_INFO)
    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)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    400
    Repeat code 1 (REP_PERIOD)
      Value    160

Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #65 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 14 January 2020 - 21:47

Thanks, i will add all new keys and provide the new patch


init 2 && init 3


Re: solo4k sdl #66 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 14 January 2020 - 21:51

Just committed the old one, and ran a test build. Builds fine.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #67 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 14 January 2020 - 22:15

Yeeeee, many thanks @WanWizard


init 2 && init 3


Re: solo4k sdl #68 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 14 January 2020 - 22:55

Sorting the new events i saw that my RC epg button generate KEY_INFO while on your events seems to exists as well KEY_EPG, i added my key as EPG in the initial patch, i will add the rest of keys and rename my epg key back to info.

I think the thread title should be renamed to "openpli sdl2 missing keys" or "sdl2 missing keys"


Edited by serdeliuk, 14 January 2020 - 22:57.

init 2 && init 3


Re: solo4k sdl #69 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 15 January 2020 - 00:33

Some remotes have both an EPG and an INFO button, some only one of the two. My VU+ remote for example only has EPG.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #70 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 15 January 2020 - 10:18

I see, now, i cannot recall if my AV button from my remote control worked or not from t he beginning, but now it seems broken, does not generate any event and does not lit the LED unde the TV-POWER button as any other keys does. Your RC has an AV button, it works?


init 2 && init 3


Re: solo4k sdl #71 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 15 January 2020 - 15:26

The AV key can't be used afaik, it doesn't generate an event. It is used (on a VU+ remote) to toggle the remote between TV and STB.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #72 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 15 January 2020 - 16:46

Aha, good to know


init 2 && init 3


Re: solo4k sdl #73 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 15 January 2020 - 18:14

I have created a new patch with all keys which should replace the previous patch, included following new keys,

 

 

Event code 0 (REL_X)
Event code 144 (KEY_FILE)
Event code 215 (KEY_EMAIL)
Event code 226 (KEY_MEDIA)
Event code 357 (KEY_OPTION)
Event code 359 (KEY_TIME)
Event code 361 (KEY_ARCHIVE)
Event code 362 (KEY_PROGRAM)
Event code 364 (KEY_FAVORITES)
Event code 365 (KEY_EPG)
Event code 366 (KEY_PVR)
Event code 373 (KEY_MODE)
Event code 375 (KEY_SCREEN)
Event code 381 (KEY_SAT)
Event code 390 (KEY_AUX)
Event code 394 (KEY_DIRECTORY)
Event code 395 (KEY_LIST)
Event code 405 (KEY_LAST)
Event code 408 (KEY_RESTART)
Event code 438 (KEY_CONTEXT_MENU)

 

Attached Files


init 2 && init 3


Re: solo4k sdl #74 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 15 January 2020 - 18:32

Am I correct that this is a replacement of the previous one, not a cumulative patch?


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #75 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 15 January 2020 - 19:13

Indeed, the previous one should be replaced by this one, with new name as well, to reflect not just solo4k boxes, but all.


init 2 && init 3


Re: solo4k sdl #76 WanWizard

  • Forum Moderator
    PLi® Core member
  • 53,317 posts

+1,052
Excellent

Posted 15 January 2020 - 19:18

Ok. Merged.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: solo4k sdl #77 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 15 January 2020 - 19:21

Many thanks


init 2 && init 3


Re: solo4k sdl #78 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 4 May 2020 - 16:08

See here
https://github.com/O...ea56d75e376fec4
The lock releases the device and other application can access it.

 

I am almost done with my ZX80 Sinclair Spectrum emulator which run under SDL2 but my enigma2 plugin have some issues.

If i start the plugin from extensionsmenu or pluginmeun the app starts as expected but the previous menu it is not closed because i lock the fb with `fbClass.getInstance().lock()`  in order to be able to show the emulator on screen and because the emualtor has 4:3 format it ends with two stripes of previous image on sides.

 

It is there any other way to do this?

 

If i do not call fbClass.getInstance().lock() the screen it is cleared properly but the emu screen does not appear, if i call fbClass.getInstance().lock() the emu screen appear over previous screen and when i exit the emu the screen it is cleared...


Edited by serdeliuk, 4 May 2020 - 16:09.

init 2 && init 3


Re: solo4k sdl #79 betacentauri

  • PLi® Core member
  • 6,190 posts

+273
Excellent

Posted 4 May 2020 - 16:20

Can't you clear whole screen when you open the emulator?

 

Or add a screen to the plugin which shows a black, white,... background.


Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: solo4k sdl #80 serdeliuk

  • Senior Member
  • 298 posts

+13
Neutral

Posted 4 May 2020 - 16:28

The plugin already open a black screen, properly if i do not lock the fb, if i lock the fb draw the black window after i exit the emulator.... i can try to draw a blackscreen from the emulator itself but i wanted to avoid this as i am sure that i am doing something wrong, i saw other plugins with similar issues they open first a menu and then this remain behind the scene unseen, but this is not a solution as well :)

 

If i issue a key command over the web let say http://192.168.1.13/...trol?command=60 the screen is updated and the emulator appear, but only the frame in the buffer


init 2 && init 3





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users