Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 1 of 2 12 LastLast
Results 1 to 15 of 22

Thread: GIGABLUE UHD TRIO 4K remote control IR codes

  1. #1

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts

    GIGABLUE UHD TRIO 4K remote control IR codes

    I have the GIGABLUE UHD TRIO 4K box and remote(pic attached) GIGABLUE-4K_TRIO.jpg

    I've noticed the Subtitle button on the remote does nothing (I know to get subtitles through Audio button instead).

    I started looking to see if this was fixable but saw that the IR inputs are not handled by ir-keytable or lirc or something I could troubleshoot/modify etc..
    I installed ir-keytable using opkg and the output of 'ir-keytable' was:

    Driver: ir_std
    Default keymap: rc-hi3798
    Input device: /dev/input/event0
    Supported kernel protocols: nec
    Enabled kernel protocols: nec
    Name: dreambox advanced remote control
    bus: 25, vendor/product: 0001:0002, version: 0x0100
    Repeat delay = 500 ms, repeat period = 125 ms


    When I ran /proc/stb/ir/rc# cat customcode , the output was 51ae

    looking around the box some more, i saw config.plugins.remotecontrolcode.systemcode = ConfigSelection(default="50af", choices=[("50af", _("Code 1")), ("51ae", _("Code 2"))]) which is ok.

    However, I can't find anywhere in OpenVix or OE-Alliance code that explicitly maps the dmesg output for 'playpause' (0x50af08f7) with the actual event or even the entry in debug log (18b ) or any other button.

    Link to spreadsheet with every button pressed and corresponding 'dmesg' entry and also 'debug log entry':
    https://docs.google.com/spreadsheets...P51EOV/pubhtml

    Does anyone have experience with the enigma2/openvix and remote control codes? Or any understanding of the flow from box getting IR signal to openvix processing signal?
    Or even whether it's possible to use ir-keytable or even lirc ?

  2. #2

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    I should also mention that changing the remote control system code to Code 2 resulted in same issues with buttons not being recognized.
    [50af being at the start of every dmesg entry for remote button push. (button for '4' is 0x50af9768) etc.]

  3. #3
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    22,516
    Thanks
    6,070
    Thanked 8,808 Times in 5,951 Posts
    If you look at boxbranding, remotes, there are other places where buttons are re-purposed globally. The gb ue 4k has a mod to "create" a help button.

    On PLI, ATV and also Vix, you can add modify function of keys using a translation.xml file. I can't remember the exact name, but debug log prints it.

  4. #4

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    Cool. It looks like the mapping @ https://github.com/oe-alliance/brand...cModel.py#L158 is incorrect.
    It has

    Code:
    			"gbtrio4k": "gb3",
    but the remote is gb4.

    It also seems as if those files are just UI related?

  5. #5
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    11,746
    Thanks
    1,886
    Thanked 4,147 Times in 2,749 Posts
    Does the screen show anything when the button is pressed (unhandled key icon) or no response at all?

  6. #6

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    For 2 buttons, the screen shows nothing(nor does the debug log) - dmesg does have code entry though:


    button dmesg ui debug logs
    context 0x50afa35c <NOT RECOGNISED-nothing on screen> no output
    subt 0x50afa15e <NOT RECOGNISED-nothing on screen> no output


    And for 3 buttons, it has the incorrect function performed


    button dmesg ui debug logs
    option 0x50af18e7 Subtitle KEY_SUBTITLE
    aspect 0x50af09f6 activatePiP KEY_SCREEN
    pip 0x50af5fa0 f2 KEY_F2

  7. #7
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    22,516
    Thanks
    6,070
    Thanked 8,808 Times in 5,951 Posts
    A sample commit is here, note the "remap" is what does it:
    https://github.com/oe-alliance/brand...dc7595cfa9e99f

    But you will be working on this folder:
    https://github.com/oe-alliance/brand...ng/remotes/gb3

  8. The Following User Says Thank You to abu baniaz For This Useful Post:

    Huevos (29-04-22)

  9. #8
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    11,746
    Thanks
    1,886
    Thanked 4,147 Times in 2,749 Posts
    @satteliter, Abu's post will help you with the 3 keys that are producing output in the debug log, but it can't help if the kernel drivers don't pass through a button press. In that case a fix from the manufacturer would be needed, or a patch for the kernel.

    Or alternatively, for the 3 working keys, you can create a user file: "/usr/share/enigma2/keytranslation.xml" and store it in your backup.
    More details here: https://github.com/OpenViX/enigma2/c...a86fd955cfc6da
    Last edited by Huevos; 29-04-22 at 07:59.

  10. #9
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    11,746
    Thanks
    1,886
    Thanked 4,147 Times in 2,749 Posts
    @satteliter, if you are up for testing we can try some experiments.

  11. #10

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    Yip, up for testing but I haven't got a build environment set up for oe/openvix. Not sure how easy this is?

    Is there any way to just set it to the correct remote type - gb4?

    gb4 is the trio4k remote but for some reason it's been mapped to gb3 remote - https://github.com/oe-alliance/brand...tes/gb4/rc.png


    Both UHD trio4k and UHD UE 4k have same remote(gb4) shown in listings:
    https://store.gigablue.de/4k-receive...d-trio-4k.html
    https://store.gigablue.de/4k-receive...uhd-ue-4k.html

  12. #11
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    7,406
    Thanks
    896
    Thanked 2,576 Times in 1,976 Posts
    Quote Originally Posted by satteliter View Post
    Yip, up for testing but I haven't got a build environment set up for oe/openvix. Not sure how easy this is?

    Is there any way to just set it to the correct remote type - gb4?

    gb4 is the trio4k remote but for some reason it's been mapped to gb3 remote - https://github.com/oe-alliance/brand...tes/gb4/rc.png


    Both UHD trio4k and UHD UE 4k have same remote(gb4) shown in listings:
    https://store.gigablue.de/4k-receive...d-trio-4k.html
    https://store.gigablue.de/4k-receive...uhd-ue-4k.html
    build environment - see bottom half of page. If you have ever built, then should be straight forward for you. This will also build OK with Ubuntu 21.04 and 22.04 (I have my main build on 22.04 at the moment and its rock solid)
    ref remotes .. gbquad4k & gbue4K have same remote (but not according to BoxBranding) and Yes remote is same for all (I have all 3 boxes) ..,. just don't know if difference between gb3 & gb4
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  13. #12

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    gb3 has 'f2' in place of gb4's 'pip

    https://github.com/oe-alliance/brand...tes/gb4/rc.png
    https://github.com/oe-alliance/brand...tes/gb3/rc.png

    other than that, cosmetically - they have all the same buttons in same places etc.

  14. #13

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    > build environment - see bottom half of page

    ?

  15. #14

    Title
    Member
    Join Date
    Feb 2021
    Posts
    34
    Thanks
    14
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by satteliter View Post
    > build environment - see bottom half of page

    ?
    just saw instructions on https://github.com/OpenViX/enigma2

    setting it up now.

  16. #15
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    7,406
    Thanks
    896
    Thanked 2,576 Times in 1,976 Posts
    Quote Originally Posted by satteliter View Post
    For 2 buttons, the screen shows nothing(nor does the debug log) - dmesg does have code entry though:


    button dmesg ui debug logs
    context 0x50afa35c <NOT RECOGNISED-nothing on screen> no output
    subt 0x50afa15e <NOT RECOGNISED-nothing on screen> no output


    And for 3 buttons, it has the incorrect function performed


    button dmesg ui debug logs
    option 0x50af18e7 Subtitle KEY_SUBTITLE
    aspect 0x50af09f6 activatePiP KEY_SCREEN
    pip 0x50af5fa0 f2 KEY_F2
    sub title does work if you have sub titles on the stream
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.