94 replies to this topic

[WanWizard]

 

2.4GHz RF Wireless Tastatur

 

So it is not an IR remote.

[Abu Baniaz]

Not sure if this helps...

 

root@gbue4k:~# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      gigablue remote control
Select the device event number [0-0]: 0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "gigablue remote control"
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 62 (KEY_F4)
    Event code 102 (KEY_HOME)
    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 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 226 (KEY_MEDIA)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
    Event code 275 (BTN_SIDE)
    Event code 276 (BTN_EXTRA)
    Event code 277 (BTN_FORWARD)
    Event code 278 (BTN_BACK)
    Event code 352 (KEY_OK)
    Event code 357 (KEY_OPTION)
    Event code 358 (KEY_INFO)
    Event code 361 (KEY_ARCHIVE)
    Event code 362 (KEY_PROGRAM)
    Event code 364 (KEY_FAVORITES)
    Event code 365 (KEY_EPG)
    Event code 370 (KEY_SUBTITLE)
    Event code 375 (KEY_SCREEN)
    Event code 377 (KEY_TV)
    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 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 412 (KEY_PREVIOUS)
    Event code 438 (KEY_CONTEXT_MENU)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)
    Event code 8 (REL_WHEEL)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    400
    Repeat code 1 (REP_PERIOD)
      Value    125
Properties:
Testing ... (interrupt to exit)
***********************************************
  This device is grabbed by another process.
  No events are available to evtest while the
  other grab is active.
  In most cases, this is caused by an X driver,
  try VT-switching and re-run evtest again.
  Run the following command to see processes with
  an open fd on this device
 "fuser -v /dev/input/event0"
***********************************************

[serdeliuk]

Thanks, interesting, your kernel event driver does not have KEY_A or any other key as keyboards, but have EV_REL and EV_REP as a game controller, your remote control does not have axis control and gamepad, right?

[serdeliuk]

Thanks, interesting, your kernel event driver does not have KEY_A or any other key as keyboards, but have EV_REL and EV_REP as a game controller, your remote control does not have axis control and gamepad, right?

Also have buttons as a gamepad

    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
    Event code 275 (BTN_SIDE)
    Event code 276 (BTN_EXTRA)

    Event code 277 (BTN_FORWARD)

    Event code 278 (BTN_BACK)

Edited by serdeliuk, 15 May 2020 - 08:24.

[serdeliuk]

However, even it has, does not work, due the same workaround.

Edited by serdeliuk, 15 May 2020 - 08:27.

[Abu Baniaz]

My remote is here

https://github.com/o...otes/gb3/rc.png

[serdeliuk]

The actual remote does not seems to have gamepad, but who knows, maybe gigablue had a such remote or intended to, what model of gigablue is this one?

Edited by serdeliuk, 15 May 2020 - 13:53.

[WanWizard]

In most cases, the code used is based on SDK demo code, and the remote is whatever was available on Alibaba that has the correct price. I doubt there is anything intentional going on here...

[serdeliuk]

Possible, but the similarity exists, only one event driver, a lot of extra events on the same single device, lockout due the workaround of all those events...

Edited by serdeliuk, 15 May 2020 - 14:05.

[WanWizard]

We know that, I'm still waiting for a suggestion for a fix so the workaround is no longer needed.

[serdeliuk]

I am working on the solution and i am almost at 50% to solve the issue i hope to have time to do it until this weekend end, or till next's week weekend.

Edited by serdeliuk, 15 May 2020 - 14:10.

[WanWizard]

 

Looking forward to it, the less workarounds, the better !

[serdeliuk]

  agree

[serdeliuk]

I am working on the solution and i am almost at 50% to solve the issue i hope to have time to do it until this weekend end, or till next's week weekend.

 

Ah, it is already Friday.... 

[Abu Baniaz]

what model of gigablue is this one?

GB UE 4K

Sent from my Moto G (5S) using Forum Fiend v1.3.3.