Posts by Skinjob

    Well, I should be on the latest version of Kodi for the S805 chip; 8.0.1a. But before this version, I had installed the 8.0g and 8.0b versions; and they had the same result: which is while the Beelink/Tronsmart remote does work with these editions of LE, half the buttons don't. However, under Android on the MXQ box, all buttons on this remote does work. So I copied the Android remote.conf file, and I am posting it here (see below). I am hoping I can just add codes from this file to the LE default config file. But I don't know which codes in the remote.conf file correspond to which keys on the remote.


    In fact, I don't even know where LE is storing its default remote configuration. I do not see a remote.conf file in the .configfiles directory, or any of its subdirectories. Moreover, it seems that whenever I try to install my own remote.conf file in the .configfiles directory, no matter what remote.conf file it is, both remotes stop working in LE! So I have to figure out what's happening there, before I can even think about changing the default remote configuration.


    Picture of your remote please.


    My remote is the Beelink S82/Tronsmart S95. It looks similar to this.


    Dont insert link to sellers.


    I don't see where I did that?



    DEFAULT REMOTE.CONF CONFIG FILE FROM ANDROID (WHICH PROPERLY OPERATES BOTH BEELINK & VISSON REMOTES):


    (n.b. This remote.conf file is found in the system/etc folder of the Android system on the OTT MXQ S805 Kodi box. It is meant to control the Visson S82 remote. But with the USB dongle for the Beelink remote installed, the box works perfectly controlling all of the buttons on this secondary remote, alongside the default remote).


    #*********************************************************************************************************
    #this file is configuration for each factory remote device
    # work_mode 0 :software mode 1 :hardware mode
    # repeat_enable 0 :disable repeat 1 :enable repeat
    #
    # factory_code each device has it's unique factory code.
    # pattern:custom_code(16bit)+index_code(16bit)
    # examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
    #
    # release_delay unit:ms.release will report from kernel to user layer after this period of time
    # from press or repeat triggered.
    #
    # debug_enable 0 :debug disable 1 :debug disable
    #
    # SW MODE:
    # bit_count how many bits in each frame
    # tw_leader_act time window for leader active
    # tw_bit0 time window for bit0 time.
    # tw_bit1 time window for bit1 time
    # tw_repeat_leader time window for repeat leader
    # REG
    # reg_base_gen set value for PREG_IR_DEC_BASE_GEN
    # reg_control set value for PREG_IR_DEC_CONTROL
    # reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
    # reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
    # reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
    # reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
    #*************************************************************************************************************
    #amlogic NEC remote
    factory_code = 0xfe010001
    work_mode = 0
    repeat_enable = 1
    repeat_delay = 40
    repeat_peroid = 39
    release_delay = 121
    debug_enable = 1


    fn_key_scancode = 0x00
    left_key_scancode = 0x51
    right_key_scancode = 0x50
    up_key_scancode = 0x16
    down_key_scancode = 0x1a
    ok_key_scancode = 0x13
    pageup_key_scancode = 0x55
    pagedown_key_scancode = 0x54


    mouse_begin
    0 0x51
    1 0x50
    2 0x16
    3 0x1a
    mouse_end


    key_begin
    0x01 11
    0x4e 2
    0x0d 3
    0x0c 4
    0x4a 5
    0x09 6
    0x08 7
    0x46 8
    0x05 9
    0x04 10
    0x13 97
    0x19 15
    0x42 14
    0x16 103
    0x1a 108
    0x51 105
    0x50 106
    0x11 102
    0x18 104
    0x10 109
    0x4c 125
    0x5a 119
    0x59 122
    0x52 128
    0x58 123
    0x54 120
    0x55 121
    0x40 116
    0x41 113
    0x45 130
    0x49 134
    0x0a 133
    0x48 138
    0x4d 70
    0x0e 136
    0x0f 138
    0x43 132
    0x03 127
    0x06 139
    0x44 140
    0x00 63
    0x02 395
    key_end
    repeat_key_begin
    0x01 11
    0x4e 2
    0x0d 3
    0x0c 4
    0x4a 5
    0x09 6
    0x08 7
    0x46 8
    0x05 9
    0x04 10
    0x13 97
    0x19 15
    0x42 14
    0x16 103
    0x1a 108
    0x51 105
    0x50 106
    0x11 102
    0x18 104
    0x10 109
    0x4c 125
    0x5a 119
    0x59 122
    0x52 128
    0x58 123
    0x54 120
    0x55 121
    0x40 116
    0x41 113
    0x45 130
    0x49 134
    0x0a 133
    0x48 138
    0x4d 70
    0x0e 136
    0x0f 138
    0x43 132
    0x03 127
    0x06 139
    0x44 140
    0x00 63
    0x02 395
    repeat_key_end
    [/quote]

    What chip is in this box of yours ?? Confusing in your post MXQ S805.
    What LE Version are you using ??
    Are you running LE Via SD Card boot with Android still internally.??



    I mention the chip, its an Amlogic S805. So I'm using the latest build of LE for this chip, v.8.0.1a, via SD card boot with Android internally. The box brand is MXQ (OTT).

    I am not able to get some of the keys to work on my Beelink S82 (aka Tronsmart S95) remote (using an MXQ S805 box). They are: Power, Home, Volume, Mouse, Menu. When I try reading codes for these buttons with the "dmesg -c" command in terminal, nothing happens. None of those keys gets returned. Not even the keys on the Beelink remote that do work under LE. Only the keys the MXQ's stock Visson remote get return codes in terminal. Is there a trick to this I am missing?

    UPDATE: Thanks for the responses, guys. In short time, I've already solved the problem (finally!). I had a hunch the problem stemmed from Paragon EFTS Linux partition reader-writer for Windows. So what I did was use an LE backup (.tar) fiile that I had on my (Mac) that was copied from the old install, and then copied that over to the box via SSH. So the files don't go through Paragon or Windows. This time the backup worked. However, my Beelink remote no longer works, but I'm putting that in another thread!


    (BTW, I originally tried cloning the old SD card to the newer, larger SD card.... several times. That never worked!).

    For 2 days I've been banging my head against the wall, trying to in Libreelec (v8.0.1a on an S805 box) what should be a simple task: transfer my Kodi config files to a new install (I simply want to put my LE install on a faster SD card!). Doing the obvious, saving a backup in LE settings and then restoring the backup on the new SD card is impossible for me. I add the backup to the new SD card's backup directory. But after I restore, my install is corrupted, and after I wait for LE to fix the corruption, the backup is gone and everything is reset to zero. After reformatting and reinstalling LE on the new card, I tried just overwriting the default "addons" and "userdata" directories, with the folders in my old directories. Same result: upon reboot, LE is corrupted and tries to fix itself, then deletes everything I added and returns to stock settings.


    So how I am I doing the transfers? Well, of course I can't simply access the .kodi files straight off the SD card. as neither my Mac nor Windows computers will see those ext4 files. Since I can't get the Mac to properly read&write to the LE SD card no matter what software I try, I installed Paragon's "EFTS" software, which allows you to read & write ext2-3-4 partitions under Windows. Maybe its not writing those files correctly, but I don't know where the problem lies. I'm at a loss to figure out how to move my addons & configs from the old SD card to the new. Surely this is possible with LE??

    So I specifically go out of my way to say I am only interested in recommendations for a 905 box, and I do not want to hear about the WeTek or circuit board devices (like the Odroid). I already know what I DO NOT WANT, and I specified what I DO NOT WANT to avoid wasting time, since I don't plan to spend a week researching a tv box. And what do I get as responses? One only naming a WETEK and the other only naming a CIRCUIT BOARD DEVICE.


    So it looks like even if I go out of my way to avoid getting such stupid useless UNHELPFUL responses, I'm still going to get them no matter what, as people here insist on only naming those 2 type of devices. (I hope you've at least gotten your commissions on that crap you're peddling). And apparently, I also have to justify WHY that I want the type of device I am asking about, because its not obvious enough to one of you geniuses why people would go to the trouble to install LE on nand. Well nuts to that. I want to buy a box soon not next year, so I'll get my information elsewhere, end of story. (insert whammy finger emoticon here :@ )

    Ok, so I'm loving LE on my MXQ S805 (on SD). I want to get a newer box, with more memory (ie. 2gb), maybe 4k support (though I have a 1080 tv, not a 4k tv). So I'm looking at midrange S905X boxes, around $70 (my budget). I've spent hours searching this question, but I still can't find clear information saying which boxes will definitely allow LE (Krypton) to be installed to NAND memory. (So this leaves out the WeTek Hub or circuit board devices; ie. RPi). Assistance please!