X96 (S905X), power on by IR remote not working

Hi,
I have x96 (s905x) 1Gb, 1000Mb, WiFi.
How do I make box turn on by pressing the Power button from the remote control? Corelec Version 9.2.3 release.

By contact your vendor to get a proper bootloader. CoreELEC can’t do anything for this device as the bootloader source isn’t available.

Thank you for the answer, but there is another problem, periodically restarts or freezes kodi, and even the entire system (rarely). If kodi hangs, it’s just a black screen, and if it restarts, " system information shows" the running time * * * minutes, but the uptime command shows more running time.
P.S. This happens when the box is idle

OK! Thanks!
P.S. customer support, where is it?

@Portisch, gxl_p212 u-boot from CE-github works well on x96 board, but ddr_clk rate must be reduced to the CL11 area

How do I do this?

http://ix.io/2q2k
http://ix.io/2q2l

Thank you for the info!

But I stopped to support whole u-boot on generic devices. It just contain too much unknown factors and without matching hardware it’s impossible to guarantee the bootloader will work.

CE is only taking care of whole bootloader where the internal eMMC can be mechanical detached. This will be a “safety” if something bad happen to user device while flashing and the user is able to flash it again by himself on an external PC.

For the other devices if supported by SoC with soldered eMMC we offer BL301 injection. This will replace only the needed blob in the bootloader what is used by CoreELEC for the wake up features. The rest remain untouched. My experience for GXL shows me also it’s not 100% working there. Some devices may work normally, other may remain in a endless boot loop. That’s the main reason the BL301 injection is only available from G12A and up.

I understand, but what should I do in this case?
P.S. Android firmware is not working at all.

Learning how to code on u-boot?

Or hope someone provide you a “better working” bootloader ready to flash.
Also I am sorry, there was a “easy to use” Wiki on this u-boot repo what got deleted by a retired member.
There is no backup existing os the information is gone.

You know that your are on the wrong forum to request support?

System log output for: LibreELEC (official): 9.2.3
RPi Hardware Revision: 00c03112
========== /storage/.kodi/temp/kodi.log ==========
2020-06-24 11:17:12.713 T:3011987936  NOTICE: -----------------------------------------------------------------------
2020-06-24 11:17:12.713 T:3011987936  NOTICE: Starting Kodi (18.7 Git:leia_pi4_18.7.1-Leia). Platform: Linux ARM 32-bit
2020-06-24 11:17:12.713 T:3011987936  NOTICE: Using Release Kodi x32 build
2020-06-24 11:17:12.713 T:3011987936  NOTICE: Kodi compiled 2020-06-01 by GCC 8.3.0 for Linux ARM 32-bit version 4.19.122 (267130)
2020-06-24 11:17:12.713 T:3011987936  NOTICE: Running on LibreELEC (official): 9.2.3, kernel: Linux ARM 32-bit version 4.19.122

Maybe you try there: https://forum.libreelec.tv/

My competence in this matter is not sufficient …

I don’t understand, I have Corelec installed.

he means that you uploaded wrong logs from RPi

I don’t have an RPI. This is a mistake
http://ix.io/2q2W
http://ix.io/2q2X

You could try amremote (remote.conf file) instead of meson-ir if you use original box remote.



May be it could solve your issue, but I’m not 100% sure

I can’t use the original remote control due to the matching codes with other devices.
This problem started when I used the original remote.

Go over to Freaktab website and look for a custom Android rom.

Or go to XDA for an Android Rom here
Your box has been tested as working.

About | FAQ | Terms of Service | Privacy Policy | Legal Notice