remote.conf repository

  • Hello,


    It is possible to make a remote.conf repository?


    It will great to have a folder to all remote configuration.


    I am looking for Mini M8S II device. Anyone could share it?


    Regards.

  • Great idea I'll do the same.

    MXQ M10 S805 - LibreELEC 8.1.9
    NEXBOX A5 S905X - LibreELEC 8.1.9
    BEELINK MXIII II S905X - LibreELEC 8.1.10

    Edited once, last by kodiuser1 ().

  • That great!


    I think that it will be stored in the kszap repo, with device trees.


    It will be great to have a photo of the remote, maybe there are same remotes for different devices.


    Kind regards.

  • Here is a Beelink remote.conf works with LibreELEC-S905.arm-7.0.3.012c.img.gz


    Thanks @ Poida for the remote.conf file


    BEELINK.zip?dl=1
    [hr]
    Here's a MXQ remote.conf works with LibreELEC-S805.HD18Q.arm-7.0.2.7


    MXQ.zip?dl=1

    MXQ M10 S805 - LibreELEC 8.1.9
    NEXBOX A5 S905X - LibreELEC 8.1.9
    BEELINK MXIII II S905X - LibreELEC 8.1.10

    Edited once, last by kodiuser1 ().

  • Tronsmart S95/S95x remote.conf
    Thanks to hscotty55 for this one.




    Also. Quick question about this remote. I want to change the top right Mouse button to be a global Stop button since mouse functions on these remotes are useless.
    Anyone know how. Ive looked at the conf file and cant figure it out.
    Thanks.

  • Charbs


    It's pretty simple

    Edited once, last by routir ().


  • Charbs


    It's pretty simple


    Thanks so much. I will give this a try.
    Is the mouse key on all remote.conf always the fn_key_scancode ?
    Also how would I have found out that global stop was 116? Is this listed somewhere?
    And just curious what the # does when adding it to the front of the lines you suggested.


  • Is the mouse key on all remote.conf always the fn_key_scancode ?
    Also how would I have found out that global stop was 116? Is this listed somewhere?
    And just curious what the # does when adding it to the front of the lines you suggested.


    fn_key_scancode is usually a programmable button, it might handle some other function.
    When the mouse button is pressed you can move the pointer UP/DOWN/LEFT/RIGHT by pressing the circle around OK button. And by adding # you just block unwanted lines.
    116 - a standard linux command as listed there


    You may also have a look at creating remote config from scratch

  • fn_key_scancode is usually a programmable button, it might handle some other function.
    When the mouse button is pressed you can move the pointer UP/DOWN/LEFT/RIGHT by pressing the circle around OK button. And by adding # you just block unwanted lines.
    116 - a standard linux command as listed there


    You may also have a look at creating remote config from scratch


    In that link you posted for the command list it seems like I should be using 128 not 116


    #define KEY_POWER 116 /* SC System Power Down */


    #define KEY_STOP 128 /* AC Stop */

  • In that link you posted for the command list it seems like I should be using 128 not 116


    #define KEY_POWER 116 /* SC System Power Down */


    #define KEY_STOP 128 /* AC Stop */


    My mistake! Use 166 command.

  • New problem. Although the mouse button does in fact stop playback, it now disables the OK button and the blue highlight around the item disappears when i try to select something right after I hit the mouse/stop button. I have to press the mouse button again to use the OK button. So strange.


  • New problem.


    Have you changed both lines with 166?
    key_begin
    key_end


    Also try to delete or block with # these ones:
    ok_key_scancode = 0x55
    pageup_key_scancode = 0x04
    pagedown_key_scancode = 0x1b

    Edited once, last by routir ().