Quote from Ygdrassil

Why not create your own? It doesn't take long.

Here are the instructions

Here is a walk through

Tutorial worked great! Thanks!. I do have one more question. The keys all work great, however the remote requires multiple key presses sometimes when operating the remote. Is that related to an adjustment within the configuration and can I make an adjustment to fix the delay?

Hello All,

I picked up this remote due to its simple design and tried searching for the config without success. Would anyone happen to have the remote configuration for this remote? The description for this remote is as follows.

Original Replacement Remote Control - Android TV Box Controller for H96 MAX, MX10,MXQ, MXQ Pro,T95M, T95N. T95Q. T9. T95X mx9 H96 pro+ tx3mini tx3max x96mini X96 x96max (H)

Quote from JoeEdison

Hi kings322.
I had the same problem that I managed to solve thanks to this:

sd card - Resize file system on OpenELEC - Raspberry Pi Stack Exchange

However, there are small changes to be made.

You have to read the link first to understand and then do the following.

At home it looks like this:

Connect with PUTTY:

cd /

touch /var/lock/xbmc.disabled

killall -9 xbmc.bin

systemctl stop kodi.service

umount /storage

mount

parted /dev/rknand0

unit s

p

rm 2

mkpart primary 1081344s -1

quit parted

e2fsck -f /dev/rknand0p2

resize2fs /dev/rknand0p2

mount /dev/rknand0p2 /storage

df -h

rm /var/lock/xbmc.disabled

systemctl start kodi.service

Sometimes there are a few mistakes but you have to go all the way.

In any case with me it works perfectly.

I hope it will help you.

Display More

Thanks for the write up, but this did not work for me. I tried to follow the commands and some did not work.

Thanks again

Quote from quickfast

I've found that LibreELEC-RK322x.arm-9.80-devel-20200228170436-cd590c7-rk3228a-box.img works much better. It boots from the emmc just fine. I can't get the remote to work though. I can do systemctl stop kodi, systemctl stop eventlircd, then run ir-keytable -p NEC,RC-5,RC-6,JVC,SONY -t and I'm able to see the codes. They match exactly what's in the config I put in /storage/.config/rc_keymaps/ but when I start Kodi I am still unable to control it with the remote. Am I missing something?

Edit: after a lot of struggling I finally got it to work. For some reason the keymap had become 0kb and wasn't being loaded when I ran ir-keytable -a /storage/.config/rc_maps.cfg -s rc0. If you're trying to do this I recommend referring to How to configure IR remote control - Guides & How-tos - CoreELEC Forums

This is an excellent tool that allows me to fully backup my emmc for recovery and write images. Thanks for sharing. However, I do have a question on the installation of the image. When i look at the storage section of LE, I only see 328MB available. It does not capture all of the space in the emmc. Are you having the same problem with your setup?

Thanks in advance

Quote from UART

Взаимодействие с другими людьми

For USB/SD burn is:

LibreELEC USB-SD Creator

balenaEtcher

Rufus

Advise to try this method first.

Display More

Thank you.

I appreciate the help, but I meant installation to the internal emmc. I am able to create the sd with image but looking to install to internal emmc.

Thanks again

Quote from knaerzche

shippy

Thanks for the compliment - wasn't to easy, since no documentation is available about this soc ... SV6051 will work in both AP and station mode in LE. I'm currently adding a recipe for Armbian ... mainly because it will make porting to mainline way easier than doing it with LE ... you will have a full linux system available than ... should pop up there next few days/weeks. (BTW: You don't have to use a toothpick - devices will boot from sd card automatically - if there is one is inserted)

iluha24

You willl loose your android system an h96 mini if you want to install LE - you will have to erase the whole flash and you can't easily return to android. I DONT recommand this to inexperienced users. You will have to use linux since all windows tools don't allow writing to flash at start postion:

use rkdeveloptool - you will have to compile your own from GitHub - rockchip-linux/rkdeveloptool (maybe it can be compiled on windows too, I didn't test - I don't use windows at all) - or download my precompiled binary (x86_64) from here: rkbin/rkdeveloptool at libreelec-cleanup · knaerzche/rkbin · GitHub. Yor will also need a loader binary which can be downloaded here rkbin/rk322x_loader_v1.10.256.bin at libreelec-cleanup · knaerzche/rkbin · GitHub

0. Make sure you have the gunzipped version of LibreELEC-RK322x.arm-9.2-devel-20200114135155-0bca75f-rk3228a-h96mini.img.gz

1. Put the device in "loader mode" by pushing the button in the AV-outlet (example with an toothpick)

2. While pusing it attach the device with an USB-A-to-USB-A-Cable (use the first usb port from front) to yo computer (you should now see an USB device attached to your computer)

3. execute

Code

rkdeveloptool rd 3

to put your device in maskrom mode

4. Downloader loader to your device

Code

rkdeveloptool db rk322x_loader_v1.10.256.bin 

5. Erase the flash of your device by executing

Code

rkdeveloptool ef

This will erase you compete android system - no way back!

6. Execute:

Code

rkdeveloptool wl 0x0 LibreELEC-RK322x.arm-9.2-devel-20200114135155-0bca75f-rk3228a-h96mini.img

Wait until it's completely done with writing.

7. Execute

Code

rkdeveloptool rd

This will reset your device - and LE will come up

Again: I don't recommend this to anyone - I added this Image mainly because it can be used with other devices as HK1 lite.

This only way back is to short emmc (see freaktab for advices how to do that) - this will bring your device in maskrom mode - you can reflash android than. I already tried to make an usb-boot version - which seems to be next to impossible, because this device uses the old "rkboot" version of u-boot and an 3.10 kernel (and a fake android 9 version, which is in fact android 7)

@WindrunnerXT

If you want your device to be faster - try to use the device tree from v884k - the ddr timings are the same:

Insert the SD-Card in your computer open the LIBREELEC partion/device. Extract "SYSTEM" from LIBREELEC paration (using unsquashfs on linux or 7zip on windows) go to /usr/share/bootloader - you will there find rk3229-box-v884k.dtb - copy this file to "LIBREELEC". Edit extlinux/extlinux.conf and replace "rk3228b-box-v88mars-II.dtb" with that new filename.

Never heared of "S9012P" wifi - there is no driver available in RK kernel.

Display More

Hello,

Is there a windows tool where i can write the RK322x image to my MXQ Pro 4k? Does this only work in a Linux environment?

Hello,

I have a pc that has 1.5ghz processor and 2gb of ram and I am currently running LibreELEC from a usb drive. I have a display port to hdmi cable connected to my tv and get the audio stream through the cable, but I cuts in and out and echos. is this a common issue? any known fixes for this?

thanks in advance

Quote from ippon

I have a new TX3-Pro (S905X- Android 6) box. I run it with kszaq 7.0.2.009 version (thanks to kszaq, great job!). The only problem I had was that the remote control didn’t work at all. Also copying remote.conf from the Android /etc folder to libreelec /storage/.config didn’t help. I thought a while, that may be the device tree (dtb) was wrong for my box but this wasn’t. It was the remote.conf. It seems to me, that Android 6 uses a remote configuration different from the /system/etc/remote.conf.

After ‘googleing’ a while, I found a description from a openelec user. He build a romete.conf from scratch for a WeeTeck-Box. I tried and it works. I was able to generate a working remote.conf for my box and now may remote works perfectly. Another benefit is, I was able to do my preferred key mapping.

I’ve seen a lot of posts regarding a not working remote-control. Hopefully my post will help a little bit.

1) Peparation
Copy a remote.conf file to libreelec Configuration folder over SSH :
/storage/.config
or using Windows shares:
\\your_box_IP\Configuration

You can either use my file from the post or the file from your Android. If you use your file, take care that:

• all lines between key_begin and key_end are deleted or marked as comment (leading #)
• debug_enable = 1

Code

#******************************************************************************************
#
#    this file is configuration for each factory remote device
#
#    factory_code      each device has it's unique factory code.
#                      pattern: custom_code(16bit) + index_code(16bit)
#                      examble: 0xff000001 = 0xff00(custom_code) + 0001(index_code)
#
#    work_mode         0 :software mode  1 :hardware mode
#    repeat_enable     0 :disable repeat 1 :enable repeat
#
#    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    = 0x7f800001
work_mode       = 0
repeat_enable   = 1
repeat_delay    = 130
repeat_peroid   = 120
release_delay   = 20
debug_enable    = 1


# fn_key_scancode       = 0x52 #MOUSE
# left_key_scancode     = 0x25 #LEFT
# right_key_scancode    = 0x27 #RIGHT
# up_key_scancode       = 0x26 #UP
# down_key_scancode     = 0x28 #DOWN
# ok_key_scancode       = 0x0d #OK


mouse_begin
#        0 0x25 #LEFT
#        1 0x27 #RIGHT
#        2 0x26 #UP
#        3 0x28 #DOWN
mouse_end


key_begin
#   0x51 116 #Power
#   0x4d 164 #PLAYPAUSE (MUTE)


#    0x09 398 #RED
#    0x11 399 #GREEN
#    0x54 400 #YELLOW
#    0x4f 401 #BLUE


#    0x56 104 #PAGEUP (VOL-)
#    0xbd 168 #REWIND
#    0xbb 208 #FASTFORWARD
#    0x4e 109 #PAGEDOWN (VOL+)


#    0x25 105 #LEFT
#    0x27 106 #RIGHT
#    0x26 103 #UP
#    0x28 108 #DOWN
#    0x0d 28  #ENTER (OK)
   
#    0x53 102 #HOME
#    0x1b 1   #ESC (BACK)
#    0x49 46  #C (CONTEXTMENU)
##   0x52 nn  #MOUSE (dont use this line, key is mapped in fn_key_scancode)
    
#    0x30 11  #No.0
#    0x31 2   #No.1
#    0x32 3   #No.2
#    0x33 4   #No.3
#    0x34 5   #No.4
#    0x35 6   #No.5
#    0x36 7   #No.6
#    0x37 8   #No.7
#    0x38 9   #No.8
#    0x39 10  #No.9


#    0x44 14  #BACKSPACE
#    0x58 23  #INFO


#   0x4d 113 #MUTE
#   0x56 114 #VOLUMEDOWN
#   0x4e 115 #VOLUMEUP
#   0x09 364 #FAVORITES
#   0x11 102 #HOME
#   0x54 158 #BACK
#   0x4f 171 #CONFIG
key_end
repeat_key_begin
repeat_key_end

Display More

2) Set Factory Code
Open the /storage/.config/remote.conf in any editor. You can also use the windows share \\your_box_IP\Configuration.
Open a SSH session to your box (I use putty for this. User root, password libreelec).
Type ‘dmesg –c’ in the ssh terminal. Ignore the message, it’s only for clearing the cache.
Press any key in your remote control and directly dmesg -c in the ssh terminal. You will get something like this:

Code

wrong custom code is 0xXXYYZZZZ

Go to the editor with the remote.conf. You will find a line like this:

Code

factory_code = 0x12340001

Change the factory_code with this 0xZZZZ0001 (ZZZZ is the digits you have got as 'wrong custom code is' from the ssh above).
For example if you get in the dmesg wrong custom code is 0x14fg76ad then your factory_code should be 0x76ad0001.
Save the remote.conf and type 'remotecfg remote.conf' in the shell (or reboot your box). Factory code is set.

3) Key Map
Open the remote.conf in editor and the ssh in 2nd window again. Type Type ‘dmesg –c’ in the ssh terminal and ignore the message.
Press any key in your remote control and directly dmesg -c in the ssh terminal. You will now get something like this:

Code

remote: scancode is 0x0043,invalid key is 0x0000.

If you get this, the Factory code was set correctly.

Now you can start the do the keymapping. In my remote.conf file, you’ll find the lines between key_begin and key_end likes this:
# 0xca 116 ;POWER
# 0x07 105 ;KEY_LEFT
Start with the fist line. Press the POWER button on your remote. Type dmesg -c in the ssh terminal. You will now get something like this:

Code

remote: scancode is 0x0043,invalid key is 0x0000.

Change the 1st line in the remote.conf to
0x43 116 ;POWER
This means:
- removing the leading # (line is active)
- change 0xca to 0x43 (change old/wong remote code with the correct code.)
- keep 116 (this is the linux code for POWER button).You need to do this for all lines in the file. Don’t forget to save from time to time.

Do this for all lines in the file.
If you have no corresponding button on the remote, keep the line unchanged or delete it.
If you have keys on the remote with no corresponding line in the file, you can create a new line. For this, you need to now the right linux code. In the link below, you’ll find all avalible codes. Not all of them work in Kodi, so you need to play a bit with the codes.
linux/input-event-codes.h at master · torvalds/linux · GitHub

If you set the code for all buttons on your remote, save the remote.conf and and type 'remotecfg remote.conf' in the shell (or reboot your box). Key Maping is done.

4) Mouse
If you like to use the mouse function on your remote, you have to define one key on your remote as mouse key. To get the mouse working, you also need to set the values in the upper section of the remote.conf. This are the lines you need to change. The '0x25' is the value you need to change with the value you got bavk from the ‘dmesg –c’. You also need to remove the leading '#'.

Code

# fn_key_scancode       = 0x52 #MOUSE
# left_key_scancode     = 0x25 #LEFT
# right_key_scancode    = 0x27 #RIGHT
# up_key_scancode       = 0x26 #UP
# down_key_scancode     = 0x28 #DOWN
# ok_key_scancode       = 0x0d #OK


mouse_begin
#        0 0x25 #LEFT
#        1 0x27 #RIGHT
#        2 0x26 #UP
#        3 0x28 #DOWN
mouse_end

Display More

5) repeat key section
This is for keys on your remote where you like to have a repeat function if you press the key and keep it pressed. The only thing you need to do is to copy the relevant lines from the key section into the repeat_key section. I did it with the for lines for 'left', 'right', 'up', 'down'.

Display More

When I type in 'dmesg -c' in SSH I don't get the option to view the remote codes when I press key on my remote. I have attached what I get on SSH

I have a MXQ PRO 4K with libreelec installed on it. The remote that came with the unit works great but I need line of sight to use it. I'm trying to use the MINIX A2 Lite remote but some buttons don't work. Is there a tutorial on how to create a custom remote.conf so that I can use this remote?

Thank you

Hello,

I have my MXQ Pro 4k running krypton 17 and it works great except for one problem. I'm using the Minix Neo A2 remote and all of the buttons work except the power button. For some reason the power button is the volume up. Can I edit the remote.conf to fix the issue that I'm having? I have found a Wiki for the Minix Neo A2 remote here MINIX A2 - Official Kodi Wiki. I have also attached the remote.conf that I'm using. How can I edit the remote.conf to fix this issue?

Thanks

Quote from kings322

I have build 7.0.2.008 on my MXQ pro and it works great but I have a question. How do I change the default view on this build? I would like to have the Thumbnail view on everything. How would I go about doing this on this build?

Thanks

Bump. Is there any way to access the myvideonav.xml? I don't have permissions to edit these files

Hello,

I tried to install libreelec X86 installer on a Asus eeeBox and got a message that the installer only supports X86-X64 and the computer identifies as i686. I had windows 10 installed on the same machine. Is this a problem with the installer? Why would my computer identify itself as i686? The CPU is the intel Atom.

Thanks

I have build 7.0.2.008 on my MXQ pro and it works great but I have a question. How do I change the default view on this build? I would like to have the Thumbnail view on everything. How would I go about doing this on this build?

Thanks

Hello,

I installed LE build 009 to my MXQ Pro and it worked great. Then I used the usb burning tool to go back to stock so that I can use kodi with VPN, but that method was really slow when using kodi. I recently tried to boot from sd card and tried installing LE to internal again but I'm having an issue. After I install and try to boot up the screen is blank. I tried to boot to sd card after that and continue to get a black screen. To get kodi back I have to use the usb burning tool to flash stock image, then try to install kodi again. After that I continue to get black screen. Could that stock image be causing the problem that I'm having?

Hello,

Is there an addon that I can install to use Private Internet Access with libreelec?

That fixed my problem.

Thanks

Hello,

I have installed the 7.0.2.009 build on to my OTT MXQ pro 4k and some buttons on the remote are not working. I tried using WinSCP to delete and copy over the remote.conf to the /flash folder. Every time that I try I get an error. Is there another program that I can use to remove the remote.conf and replace it? What could be causing this error?

Thank you

I have tried all of the device trees that could possibly work with my a95x and the wifi doesn't work. Is this an issue with the S905X cpu and realtek wifi chipset? Has anyone had this problem with the S905 cpu and realtek wifi chipset? I had problems connecting to wifi on android. Could this be an issue with the A95X?