Posts by raindrop

Quote from dtech

Okay, so there's some misunderstanding between us here. If your factory "working" configuration with code 0xfe010001 works, then why didn't the box work after a fresh installation, without any external configuration file? Because the remote control configuration linked from GitHub is part of my Generic_S912 image by default, and if there is no external remote.conf, it will be loaded automatically. (You can find this file on your own box here: /etc/amremote/remote.conf.)

I always ran earlier builds of kszaq or wrxtasy LE 8.2.5 on these old boxes, and had a habit of adding a remote.conf  file before trying a remote. I had no idea that your builds have remote files built-in.

After reading your last message, I deleted my 'modded' conf file from the SD card and rebooted the LibreElec, and what you know: factory remote worked (including ok button) without needing an external remote.conf file.

I guess I was being too smart to add a remote.conf file before trying a remote without an external remote file .

Well, I added following line in my remote.conf file for my factory remote (factory_code = 0xfe010001).

 0x13 28  ; Enter

.... and now OK button is working . I have not tested the remote.conf files that you have linked from your github page but I believe those files would have worked too.

Thank you for all your help.

Quote from dtech

But, if your remote.conf contains any comments or explanations, you can send it and I can help you make a working one based on them.

Hmm, the remote.conf file on my Nexbx A1 clone has no key-code 28. Maybe that's why OK button does not work. This remote also worked with H96 Pro+. File is attached below and it has comments in the file but I am not sure how accurate are the comments.

Quote from dtech

raindrop Did you try the remote control config file I sent?

Yes, I did see your last message & tried remote.conf  file that you have posted but then I hit a snag and needed to test it a bit more before I could post a coherent reply.

- After I learned that I can use armremote with your legacy LE builds, I had to dig up my old SD card with LE 8.x which had the original remote.conf file for my S912 box. I moved over the remote.conf file from old SD card to newer one with your legacy build LE 9.2.8.16 . After I booted the device, I used the factory remote for that device. Remote worked ok except the the LE did not recognized the key-press of 'OK' button.

- I had an old Nexbox A95x box with factory remote so I downloaded your A95x remote file and moved it to my LE 9.2.8.16 SD card. That remote.conf file worked the same way. The A95X factory remote did work with your A95X remote file except the OK button was not recognized.

- Then I tried another A95X remote.conf file from my own archive and it also had the same issue, the OK button presses were not recognized.

- Then I spend an hour searching on internet I discovered that LE recognizes two separate IR codes for 'OK' button and 'ENTER' button. So I turned on the air-mouse feature on the remote and then 'OK' button was recognized, because I guess LE recognized that key-press as 'ENTER' button in air-mouse mode. This trick to enable air-mouse mode to enable 'OK' key press worked for all three remote.conf files including the on you posted.

I looked in to different remote.conf files and discovered the key-code 97 (as in 0x06 97 ) represents the OK key-press but I do not know the code for 'ENTER' key. If someone know the key code form ENTER key then I can swap the 0x06 value of 97 key-code with the 'ENTER' key value and see if remote would work.

Or if there is another way to remap the key, I can try that as well.

Thanks.

I have an S905X box (Nexbox A95X clone) lying around so I decided to test it with latest LE firmware. I used "LibreELEC-AMLGX.aarch64-12.0.2-box.img.gz" on an SD card with 'gxl_905x_p212_.dtb'. Here is what I found:

-When I tried to specify HDMI audio pass-through options, the DTS-HD MA was not greyed out. However when I played a Blu-ray rip with DTS-HD MA or Dolby-TruHD, I got only silence. So non of high-resolution audio format worked with GXL-212 board. I guess LE 11.x would be same. I did not test pass-through of Dolby-TruHD on S912 box.

-I tried to play a Blu-ray rip (1080p with HD audio) with DRM PRIME decoder' option turned on, I sometime got flashes and blobs of color and HEVC seek froze the playback.

-I tried to play a Blu-ray rip (1080p with HD audio) with DRM PRIME decoder' option turned off. It worked with 5.1 audio but you are right HEVC seek broke the play back.

- I did not even bother with any 4k video on S905 box.

Question: What are the most functional and stable chipsets to be used for LE 11.x & LW 12.x ? I mean between Rockchip, Allwinner & Broadcom, which one supports video hardware acceleration + Hi-res audio pass-trough + 4k HDR playback?

Thanks.

I have an S912 box (Nexbox A1 clone) lying around so I decided to test it with latest LE firmware. I used "LibreELEC-AMLGX.aarch64-12.0.2-box.img.gz" on an SD card with 'meson-gxm-nexbox-a1.dtb'. Here is what I found:

-When I tried to specify HDMI audio pass-through options, the DTS-HD MA was greyed out so it could not be turned on. When I played a Blu-ray rip with DTS-HD MA, then only core DTS 5.1 audio played. So I guess DTS-HD MA is no-go with LE 11.x & 12.x on Amlogic S912 & S922x boards.

- When I turned on 'DRM PRIME decoder' option and tried to play a 4K file, Kodi crashed immediately on this S912 box.

-I tried to play a Blu-ray rip (1080p with HD audio) with DRM PRIME decoder' option turned on, but video playback froze after 20-30 minutes.

-I tried to play a Blu-ray rip (1080p with HD audio) with DRM PRIME decoder' option turned off. 1080p did play but the box overheated and froze in about 15 minutes.

- I switched back to other SC card containing "LE 8.2.5 (wrxtasy-kszaq)" and DTS-HD MA and Dolby TrueHD both worked. Also 4K video worked with hardware acceleration. No crashes noted.

Now does anyone know if 'DRM PRIME decoder' and DTS-HD MA pass-through work on an S905X3 chipsets for LE 11.c or 12.x ?

Hello all,

I am running latest 'LibreELEC 9.2.8.16' file on a Nexbox A1 clone device (S912/gxm_q200_2g). Everything including LAN & bluetooth is working ok after this fresh clean install but I am having trouble configuring IR remote with this device. I am not sure this is right thread for IR remote questions so plz move this question to appropriate section:

I read the LibreELEC wiki on IR remotes, but my issue is not addressed there. I have taken following steps so far:

I logged-in via SSH and issued following commands with results:

LibreELEC:~ # ir-keytable
/sys/class/rc/: No such file or directory
No devices found

Another attempt to check current keytable went like this:

ibreELEC:~ # ir-keytable -r
/sys/class/rc/: No such file or directory
No devices found   

An attempt to test ir-keytable went like this:

LibreELEC:~ # LibreELEC:~ # ir-keytable -c -w /usr/lib/udev/rc_keymaps/odroid
-sh: LibreELEC:~: not found

Another try to load preconfigured odroid keytable file which came with the system:

LibreELEC:~ # LibreELEC:~ # ir-keytable -c -w /usr/lib/udev/rc_keymaps/odroid
-sh: LibreELEC:~: not found

I do have keymaps file that I downloaded from internet. I placed the file in /storage/.config/rc_keymaps/ location and edited the /storage/.config/rc_maps.cfg file. However when I issued ir-keytable -a /storage/.config/rc_maps.cfg command, I got following error:

 /sys/class/rc/: No such file or directory

From other posts I learnt to look for 'lircd.conf' file in '/storage/.config/' directory. However I do not see an 'lircd.conf' file in that locaiton.

So from reading wiki, it appears that lircd protocol is not running and no IR receiver driver is loaded. Is there a fix for this situation?

I am writing this to say big Thank You to dtech and everybody else who is involved in maintaining these legacy builds.

I just flashed "LibreELEC 9.2.8.16" posted on the first page to my 6 years old no-name S912 box (Nexbox A1 clone). It worked flawlessly even without needing to change dtb file. Kodi recognized both WiFi and bluetooth built into this unit.

Its amazing to use a 2025 LE build on a 6+ years old hardware which can use hardware acceleration where my Odroid N2+ cannot.

edit: Ethernet did not work with provided dtb so I switched it with gxm_q200_2g.dtb and now Ethernet works as well.

Quote from chewitt

NB: You will probably want to turn hardware decoding off on the N2 (same as all G12A/B and SM1 devices). H264 works well but HEVC isn't so good and anything 10-bit wedges the board.This does limit the board to 1080p, but it works well. If you want 4K support you will need to run a vendor kernel image like CE.

After about 4 hours of tinkering, I could not get my Odroid N2 to work with hardware decoding and then I found your post explaining the situation.

I am also having issues with LE passing-through DTS-HD MA via HDMI as all I can get is a static noise from my AVR. However when I change the audio stream to 5.1 format, my AVR can play it just fine. Is this is another limitation of Odroid N2 where it cannot pass-through HD audio?

Thanks.

Quote from Shonk

I have some bootloaders in my mega dump

https://mega.nz/folder/8qhRRaYJ#2ZA3VLjvLT6wg0IwsTF27g

in H96 Pro+ Firmware Fixed Uboot Power On Libreelec/Uboot Files

im not sure if i have them all as it was a fair few years ago

Thank you.

It seems that I am bit late to this thread. I had my H96 Pro+ in storage due to remote power off issue. I just discovered this thread but it seems I am too late as all the links to the uboot files for this device are not working any more.

Can anyone share 'u-boot_q201_v5_v6_blue_pcb.tar.gz' file as I cannot download it from the links provided in previous pages.

Many thanks.

Portisch   bumerc

Alright I installed the 'Network tools' add-on however I had to enable 'Unknown Sources' option under the Add-on menu.

Hello,

I have same question about the usability of official IR remote for Rock64 devices. Now we have official LibreELEC 9.1 builds availble here: LibreElec 9.1 for Rock64 board and LibreELEC 9.1 for Rockbox Basic . Does these builds have support for official Rock64 IR remote?

If these builds do not have support for official Rock64 IR Remote, then are there any work around (Remote map files) available?

Thanks

Hello,

I am trying to run iperf3 on my installation of Libreelec on my two Amlogic Krypton boxes. But I am not sure from where to obtain the iperf package and how to install it. Can someone please point me into right direction?

The specific questions that I have is which iperf package I need for Krypton Libreelec and which directory to put the package in? Are there any other steps involved to 'install' the package. I tried to find 'Network Tools' package which is supposed to have iperf included but I could only find the source code on github.

Any help wold be appreciated.

Hello All.

First of all hats off to all the developers who are putting their time and hard work in to this project.

I have installed a "LibreELEC 8.2.4.2-S905Test" file on a AmLogic 905X box few days ago to test it. I have an older AVR unit which can only decodes Dolby Digital and DTS 5-1 bit-streams. I am planning to rip my Blu-Rays into DTS-HD + Core ,so I decided to test the pass through functionality of the Kody 17.6 which came with LibreELEC 8.2.4. I selected 2 speaker set-up and enabled Passthrough with Dolby Digital and DTS capable receivers selected. 'Sync to display has been' disabled. I can passthourgh Dolby Digital without any issue but I tried 3 different video files with dts audio but I could not passthrough DTS stream.

I have exactly same issue with Kody v17.6 on Android 7.1 on same 905X box.

I have an older Linux box (XIOS-DS) from 2012 and I played back same files on it. I have noticed it can passthough DTS (as welll as DTS Core from a DTS-HD stream) without issue with same AVR and TV set-up.

I am have uploaded screenshots of my Kodi set-up and log files. since I do not have permissions to attach files yet: https://drive.google.com/drive/folders/1l4pagt3yjadoz4bu8d-_navdeq4ryq8u?usp=sharing

Any help would be appreciated on what can I not passthough DTS audio?