Posts by jim_p

    I can not remember if hdmi cec was working when it had the android os. Here is the output of dmseg and fw_setenv

    # fw_setenv
    ## Error: variable name missing

    You are also right about lsusb showing the wireless card

    # lsusb
    Bus 001 Device 003: ID 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network Adapter

    Because the mxq's wireless reception is kinda bad where my hdmi cec capable tv is located, I did not connect the tvbox to it in order to get all the above without lagging. I have it next to my pc, running with no "monitor", so I could connect easily.


    Maybe the word misconfiguration is not the right one. But how shall I describe what you mention in the second sentence, which is what really happens? That is why I think the forementioned script is a good workaround, because it sets this parameter on the fly.

    Also, is there something can I disable under settings > player > videos > postprocessing that will help the situation? Like disable vaapi altogether? :/


    Has this patch been added to le's code as of today? I just upgraded to today's nightly-20210425-999da98 and the problem is stil there.

    Hello again.

    This is the continuation of this issue on kodi's github.

    Minimum opengl version for kodi 19 under linux · Issue #19521 · xbmc/xbmc · GitHub

    As lrusak suggested there, I open this thread to continue the discussion here. Also, I have found a few more minor issues while running the nightly builds the last ~10 days.

    Hardware specs.

    An old intel celeron t3000 and its intergrated gpu, plus 2gb of ram

    # lscpu | grep Model
    Model name:          Celeron(R) Dual-Core CPU       T3000  @ 1.80GHz
    # lspci -k 
    00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
    Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
    Kernel driver in use: i915

    Libreelec version: The latest nightly as of today April 24th 2021, i.e. nightly-20210423-5701db2.

    Log: Any available log is mentioned in the issue's report in github.

    Steps: Also mentioned in the issue report.

    So, the suggested solution does work, but I think it would be nicer to have a script that "auto" selects the proper driver for libva based on the gpu driver that is used, e.g. something like this one

    External Content
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Also, could that variable be set to i915, because that is the driver the kernel uses for that gpu? I assume not, but I wanted to ask anyway.

    Moreover, I also assume that setting that variable in there overrides any other. I tested it on my niece's 10th gen nuc and it lacked hardware acceleration even on h264!

    One more minor issue on the above system is that it reports -1Mhz as the cpu speed under system info > hardware.

    I don't care about 10bit h265. In fact, the only time I have tried h265 playback on a device which I own (the 2 mxq boxes) was just a few days ago. H264 was all I could play until then.

    How can I check that I do not have the same issue with the unsoldered pin? I can open the box, but where is it located?

    As for the one with s905, today I will try your build with the device tree you suggested. How can I check if I have realtek wifi on it? There is no lspci and lshw -C network reports that rtl8189es is used for it, so I am 99.9% sure it is realtek.

    I am talking about the one for s805, because that is what the plain mxq has, which I got from here.

    Index of /S805/

    If you want to read my... trials and tribulations with mxq 4k pro, please read my thread here.

    Hello. I installed your build on an mxq with s805 a few days ago. I did not have time to test it, because I also had to "revive" an mx4 pro 4k, but I was amazed with how trouble free its installation was. Flash to sd, boot the device from sd with the "toothpick method", installtointernal, done!

    Today I decided to test what it can play, so I downloaded a couple of h264 and h265 samples from It can play both h264 and 265, but it really struggles on 10bit h265.

    I noticed that it does not get input via hdmi cec. When I press the remote control of my tv, its led blinks so it does get the input. Cec adapter (under settings > system > input > peripherals) is enabled and so are most of its options in there.

    Any ideas why?

    Let's bring the discussion back to le and let's say I want to install the le version that is mentioned here.

    you accept the very "work in progress" state of modern kernel support in LE images.

    Where can I find an recent/nightly/unstable image of le 10 for s905 (or even s805)? Will I need a specific device tree to make it work? Because lakka uses something generic and I assume that is the reason that none of its network interfaces works...

    How often does it get updated and from where? Will I have to manually download the image file inside the .update folder to update it every time?

    I do not mind daily or very frequent updates. Besides, I use a rolling release distro on my pc for the last 13+ years and I am used to it. What worries me is the whole procedure of "put the right thing on the right place or the hw won't work as it should (if not at all)".

    Right now, I use le (latest stable versions) on an old x64 laptop and on an rpi3b+. I also used it on my rpi zero from late 2016/early 2017 until the first releases of 9.x that came with kodi 18.1/2 in early/mid 2019. Then kodi itself became too slow for the zero, so I switched to lakka and added a couple of games.

    Speaking of the zero, I think that menu navigation and the general responsiveness of both ce (on s905) and le (on s805) feel a little less sluggish than the zero. The rpi3b+ literally flies compared to them. All of them were tested on the same tv, with the same remote control (the tv's remote) and via cec.

    Da Flex
    Understood. However, coreelec may be the only way to get a fairly recent and functional version of kodi, because the le one that also works comes with kodi 17 and this version will be unsupported by addons soon because it can't run python3. At least kodi 18 can...

    Allow me to disagree. The difference between this


    and this for instance


    is that the first one is for devices with 1gb of RAM and the second one for devices with 2gb of ram. I assume that those devices have the same bootloader, cpu etc but differ in ram.
    Actually, after checking almost all the device trees, I think they are named with this pattern

    (some amlogic related code)_(bootloader version)_(amount of ram)_(wired network speed)_(extra info when needed)

    As for the remote control support, I read yesterday that it is actually broken for this device in any *elec. It is 7.30am now that I am writing all this and I can't find the page in my browser's history, but I will post again when I find it.

    I did a few more tests and here are the results.

    Ce 9.2.7 with no device tree because I forgot to paste the copied file.

    It boots fine and both wireless and wired network worked. I installed it to the rom and it fails to boot, going straight to black screen.

    Ce 9.2.7 with the forementioned device tree for realtek wifi.

    It boots fine but I only tested the wireless connection and it seems stable. Shall I make the big step and install it to its rom?

    Lakka boots fine from the sd, but no wired or wireless connection can be done. In fact, all I see under scanned wifi networks is some garbled text and none of the 2 wireless networks that are available near me.

    The system info page is probably pulled by /proc/cpuinfo and similar "files". Dmesg, on the other hand, does not anything useful as you check check here. There is no info about the cpu or the bootloader in there.

    When you say "a usb connection can help", do you mean to connect the box via usb (type a to type a)? I do not have such a cable, but I will try and find one. Also, can I use a usb stick and do everything I already do with the sd card? Obviously, the box has to be able to boot from that usb...

    As for the device trees, I think I tried the one that comes as close as possible to the hardware I have. That means there is no point in trying the ones that come for devices with 2gb of ram or trying the ones that come for a very specific device (i.e. wetek hub and mecool ks2). Thus, the only device tree that remains is the one named


    I doubt it will work, but I will give it a try and report back. What is the worst thing that can happen if I use the wrong device tree?

    p.s. In case I have not mentioned it already, I have noticed that its remote control does not work on anything except the stock rom. This is a small issue for me, because I know any *elec can work via hdmi cec. But MY tv (= the one that I want to connect the tvbox to) does not have hdmi cec. Thus, using an distro like lakka, which works properly only with a game controller, is possibly a more viable option.

    As I have said above, I know that there is an existing ce build (9.2.7, kodi 18.9) for s905. I have tried it already, it does boot, it does install to the internal rom, but it has connectivity issues. I don't know if those issues are related to wrong (?) device tree I have used. All I know is that there is no wired connectivity and the wireless one drops and does not reconnect. Unless this major problem is fixed, coreelec is a no go for me.

    Moreover, since the info I get under settings > system info > hardware is way too generic as seen here, is there a way to get something more specific, especially for the cpu and the bootloader?

    Imgur: The magic of the Internet

    First of all, it is not the s905x, it is plain s905.

    I am not really interested in reinstalling something that is actually an android rom. I would prefer something like libreelec or lakka and use it for a single purpose. The main idea for le on it was to gift it to an old person that would use it for youtube and some iptv.

    However, if reinstalling the original rom will solve any of my forementioned issues, I am willing to try.

    Hello everyone! This is my first thread here, so please excuse any mistakes.

    As of last Friday, I am the new owner of 2 old tv boxes: an mxq (amlogic s805) and an mxq pro 4k (amlogic s905, 1gb ram, p200 bootloader). I decided to install libreelec so as to make them useful again.

    Installing it on the one with s805 was an easy task. I found 9.2.6 in this thread, flashed it on my sd card, started the box with the "toothpick method", it booted just fine and I simply connected via ssh and ran installtointernal. It took me 15-20 minutes at most.

    Before that, I also tried the build from this thread and it worked fine too, but I decided to find something newer since kodi 17 is no longer supported.

    However, installing anything on the other one, the one with s905, has been a big pita so far! First and foremost, the device itself does not have a reset button, so making it boot to recovery was a tedious task by itself. I had to install a terminal emulator on its android based os and use reboot update.

    Then, I started with coreelec 19 from the sd card and all I managed was to put the device into a bootloop because of the wrong device tree. The device was on bootloop even with the card removed! After that, I came accross this build. I only ran it once from the sd, but it was enough to get me out of the bootloop. I did not want to install it because it is on kodi 17 too.

    Index of /s905/

    So I went back to coreelec to try 9.2.7 this time. Why? Because I noticed my device has p200 bootloader and 9.2.7 had a device tree for that (gxbb_p200_1G_1Gbit). It booted just fine, so I got excited and I ran installtointernal instantly... and I regretted it a few minutes later! After it was installed to its rom I discovered that the wired interface was not working at all and the wireless one was dropping and did not reconnect! I still wonder how I managed to make installtointernal work while connected wirelessly. My tv and my router are in different rooms and all I can use is wireless when I connect any box on the tv.

    All this led me back to the forementioned build from kszaq with kodi 17. I ran it from the sd card and both wired and wireless worked fine, so I decided to install it to its rom. But now, when I start the box without the sd card, it shows nothing on the tv. Not even the amlogic logo with the tiger. It is just black. When I start it with the sd card, so it boots FROM it, I see libreelec booting as usual and reaching kodi 17.

    What am I doing wrong?

    If it helps, I also tried lakka's build for s905. It boots, but it does not detect any wireless networks... And I have no idea how to install this on the internal memory so as to help more.

    Please share any ideas and thank you in advance :)