[8.0.2e] LibreELEC 8.0 for S905/S905X

Quote from phoenix73

I did installtointernal for LE 7.0, is it ok to do it a second time ?

Sure, it will destroy your LE7
If you don't want to clean install, you can copy the patch and the dtd to the update folder of LE7.
I did everything from scratch

I took a look in install script. It search for remote.conf in various locations

if [ ! -f "/tmp/remote.conf" ] ; then
      echo -n "Backing up remote.conf..."
      mount -o ro /dev/system /tmp/system
      if [ -f /tmp/system/remote.conf ]; then
        cp /tmp/system/remote.conf /tmp/remote.conf
      elif [ -f /tmp/system/etc/remote.conf ]; then
        cp -PR /tmp/system/etc/remote.conf /tmp/remote.conf
      fi
      umount /tmp/system
      echo "done."
    fi

But I didn't have any of those. Do you have one for MXIII ?

It can work, but I didnt want to keep my prev configs, a clean install is recommend.
"I did everything from scratch": putting everything to work costs me 10min effort (thanks to trakt.tv app)-(and also learned the new menus).
Good luck

Quote from treeno

I am not sure if these apply to Bluetooth keyboards, but have you tried going to Settings > LibreELEC and changing the settings under Keyboard in the System tab?

You were right !

It is now fixed, with setting AZERTY into LibreELEC system's keyboard !
Thanks

Quote from Paithan

It can work, but I didnt want to keep my prev configs, a clean install is recommend.
"I did everything from scratch": putting everything to work costs me 10min effort (thanks to trakt.tv app)-(and also learned the new menus).
Good luck

+1, better do clean install.

Just did it, installtointernal and rebootfromnand, so far, so good

Quote from phoenix73

I took a look in install script. It search for remote.conf in various locations

But I didn't have any of those. Do you have one for MXIII ?

I'm presuming you mean Beelink minimx iii...?

#*********************************************************************************************************
#Beelink mxiii 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    = 0xff000001


work_mode          = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay    = 20
debug_enable     = 1


key_begin        
    0x48 102    #HOME
    0x01 158    #BACK
    0x03 103    #UP
    0x02 108    #DOWN
    0x0e 105    #LEFT
    0x1a 106    #RIGHT
    0x07 97    #OK
    0x13 139    #MENU
    0x58 114    #VOL-
    0x0b 115    #VOL+
    0x5c 264    #FN
#   0x14 704    #POWER
key_end


repeat_key_begin    
    0x48 102    #HOME
    0x01 158    #BACK
    0x03 103    #UP
    0x02 108    #DOWN
    0x0e 105    #LEFT
    0x1a 106    #RIGHT
    0x07 97    #OK
    0x13 139    #MENU
    0x58 114    #VOL-
    0x0b 115    #VOL+
    0x5c 264    #FN
#   0x14 704    #POWER
repeat_key_end

Quote from trogggy

I'm presuming you mean Beelink minimx iii...?

Code

#*********************************************************************************************************
#Beelink mxiii 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    = 0xff000001


work_mode          = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay    = 20
debug_enable     = 1


key_begin        
    0x48 102    #HOME
    0x01 158    #BACK
    0x03 103    #UP
    0x02 108    #DOWN
    0x0e 105    #LEFT
    0x1a 106    #RIGHT
    0x07 97    #OK
    0x13 139    #MENU
    0x58 114    #VOL-
    0x0b 115    #VOL+
    0x5c 264    #FN
#   0x14 704    #POWER
key_end


repeat_key_begin    
    0x48 102    #HOME
    0x01 158    #BACK
    0x03 103    #UP
    0x02 108    #DOWN
    0x0e 105    #LEFT
    0x1a 106    #RIGHT
    0x07 97    #OK
    0x13 139    #MENU
    0x58 114    #VOL-
    0x0b 115    #VOL+
    0x5c 264    #FN
#   0x14 704    #POWER
repeat_key_end

Display More

On my MXIII with LE 7.0, in /flash/remote.con, I've :

#*******************************************************************************                                                                                                                      **************************
#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    = 0xff000001


work_mode               = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay   = 20
debug_enable    = 1


key_begin
    0x48 172
    0x01 1
    0x03 103
    0x02 108
    0x0e 105
    0x1a 106
    0x07 28
    0x13 139
    0x58 114
    0x0b 115
    0x5c 63
    0x14 116
key_end


repeat_key_begin
    0x48 172
    0x01 1
    0x03 103
    0x02 108
    0x0e 105
    0x1a 106
    0x07 28
    0x13 139
    0x58 114
    0x0b 115
    0x5c 63
    0x14 116
repeat_key_end

Default remote.conf for LE ?

Quote from willyfan

Hi All, I have some problem with a MXQ pro 4K box.
I installed the last version on SD with restart & upgrade method because the box don't have a reset button. All is ok, libreelec is installed.
But I tried many device trees and wifi don't work. Tried gxbb_p200_1G_mxq_pro_4k.dtb, gxbb_p201.dtb, gxbb_p200_1G_100M.dtb.
No way.
Wired is working.
USBs are all working.
Beside, another problem is that the box don't go on with remote, I need to disconnect and connect power.
Someone can help me?

Display More

No people with MXQ pro?

The problem is that "MXQ pro 4k" is not a specific box, but more of a generic label that is used by multiple manufacturers and sellers. The box I own (see my signature) works fine with the generic gxbb_p200_1G_100M device tree, but yours is most likely newer and uses a completely different board and wlan chipset. Did you try one of the "realtek" device trees?

You can open the box and take a picture of the PCB. Then we might be able to help you further.

Not being able to switch a powered off box with the remote is an issue many boxes have. Current understanding is that in order for this to work, the manufacturer needs to make sure that the u-boot bootloader correctly recognizes the remote signal. This takes extra work, so with the cheap boxes, it often is neglected. My MXQ Pro 4k simply switches the hdmi output in its android firmware when I push the button.

I'm running this latest beta on Wetek Play 2. The audio passthrough patch is working great for me (I have a separate PC as backend for TVHeadend server), even better than on 7.0 where I got constant buffering problems on some (French) DVB-T HD channels with E-AC3 Surround sound. These channels play fine in 7.95.beta6 with passthrough.

Passthrough on Live TV has been one of the most important features for me so for it to have been missing from Kodi 17 was very disappointing.

Thanks to kszaq and afl1!

Quote from mmpp

Did you try one of the "realtek" device trees?

You can open the box and take a picture of the PCB. Then we might be able to help you further.

Not being able to switch a powered off box with the remote is an issue many boxes have. Current understanding is that in order for this to work, the manufacturer needs to make sure that the u-boot bootloader correctly recognizes the remote signal. This takes extra work, so with the cheap boxes, it often is neglected. My MXQ Pro 4k simply switches the hdmi output in its android firmware when I push the button.

Tried realtek trees, same results.
I will take a picture in the night. There is some operation in android in order to have more info about chipset? The box start ok in android...

Hello, first of all i must say thanks for the great work, i've installed on sd on my new amlogic 905x box and it came to new life (android experience was crappy)
Everything works great except one minor flaw with hdmi-cec which fails to turn on the device when i switch to the box input or when i turn on the tv.
Everything else cec-wise works great, the box turn off with the tv, the tv remote control the box etc... but i wish to put the box remote in a drawer so anybody has found a solution to have the box turn on automatically? thanks very much
Francesco

Already playing with 8.0.0.a with a fresh install on SDcard
S905 P200-2G-100mbits device tree (minim8s)
Nothing wrong for now, wish I could choose French as a Language, but this is a beta so no big deal

Will maybe try an update, hoping I won't have the boot bug I had last 2 times.

Quote from willyfan

No people with MXQ pro?

Which version MXQ pro box you have ? s905 or s905x, because i have S905x and everything is working with device tree gxl_p212, my remote is working and i can power on box with remote.

On my wetek hub, the ir remote stopped working after I upgraded beta6 to 8.0.0a. Manually doing a

remotecfg /flash/remote.conf

fixed it.

60fps video playback seems to be fixed in 8.0.0a. Thanks for all your hard work kszaq