Posts by wkchick

    afl1, installed your build on my Mini M8S II, and got the same result. Video started stuttering from 1:20 and halt at 1:47.

    I guess your build didn't incorporate features of the latest kzsaq build LibreELEC-S905.aarch64-7.0-devel-20161003204518-r23361-gb5788b7.img.gz. Playback of 4K H264 videos doesn't work.

    Anyway, thanks for your hard work and sharing.

    Great work, Kszaq. No more boot issues on my Mini M8S II using SD card and upated dtb.img. Playback of 4K H264 video contents went smoothly (tested with 120Mbps and 140Mbps Jelly fish and a BBC documentary). HD audio (140Mbps Jelly Fish is TrueHD) and CEC are also working.

    Thanks again.

    Sdcard LibreELEC with fixed S905X booting, no audio issue. For S905X don't delete dbt.img. Img is tested with Mini M8S and T95X and booting is successful everytime.

    Tested your build on my Mini M8S II by copying the file to 'update' folder using Samba share and reboot. No boot issue, but Audio output setting stuck at Bluetooth. Couldn't change it back to HDMI output (grayed, before update I was using HDMI for audio output). Problem gone after fresh SD image installation.

    CEC isn't working. System->Settings->Input devices->Peripherals field is also grayed. Will rolled back to kzsaq build LibreELEC-S905.aarch64-7.0-devel-20160915211230-r23341-gb83596f.img.gz to check whether CEC was working or not.

    Thanks for sharing.

    Edit: CEC works with kzsaq's build LibreELEC-S905.aarch64-7.0-devel-20160915211230-r23341-gb83596f.img.gz (at least with my Toshiba TV). Unlike afl1's latest build, there's no HD Audio output (e.g. no TrueHD, DTS-HD etc.).

    Which s905x box did you buy ? I'm waiting for a Mini M8S II and I'd like to try one of your libreelec version, as in my MX III Plus (s812) that works perfectly

    Don't worry, this kzsaq's build still works on Mini M8S II,

    No boot issue at all.

    Excuse me, what do you mean by 1/4 playback problem?

    I have a Mini M8S II (S905X, 2G RAM/8G Flash). I have tried 10 consecutive boots from the SD card with this build (LibreELEC-S905.aarch64-7.0-devel-20160910214144-r23325-g3be647e) and they have all been successful. Other builds I have tried (including the most recent from kszaq, LibreELEC-S905.aarch64-7.0-devel-20160910230431-r23333-gacc409d, and several I have made myself) fail to boot about 50% of the time with the error message "Could not mount /dev/mmcblk0p1". Thanks.

    I installed garyang's build 'LibreELEC-S905.aarch64-7.0-devel-20160910214144-r23325-g3be647e' on the same box last evening but it was too late to post any test result. I didn't find any folder missing, especially the 'Backup' folder. As a matter of fact, right after successful installation, I transferred Kodi backup (over 700MB) did some time before to 'Backup' folder through Samba share and restore. I reboot the box uncountable number of time and never failed once.

    The only drawback I found was, as kszaq pointed the previous post, no message displayed like what I had on my M18 box, just LibreELEC logo. I had to wait anxiously until the box reboot (like first installation and after Kodi restore).

    Thanks garyang for sharing his build and kszaq for his hard work, even without a S905X box in the meantime.

    Can you (S905X guys) test this build: LibreELEC-S905.aarch64-7.0-devel-20160909192321-r23330-g284fbb8.img.gz (diff included in folder)

    This is with console changed from tty0 to tty1. I am wondering if it can make an impact in any way. Thank you in advance for sharing your results.

    Experience on my Mini M8S II was even worse than before. Boot was only successful after 9 or 10 trials. Reboot failed again after successful installation. It took at least 2 to 3 trials everytime I reboot.

    On my M18 (S905) under Android (5.1), press the remote 'Power' button pop up a menu to choose between power off, suspend or reboot. However on the Mini M8S II (S905x) under Android (6.0), the remote 'Power' button will turn off the Android TV box, no pop up menu. Hope this information help.

    I neglected to mention earlier: 4k playback issues on an 1080p TV are still the same: big buck bunny 2160p30 switches to 1080p60, black screen, sintel 2160p24 switches to 1080p24, black screen.

    FWIW I don't get the logic behind using a 100Mbit PHY for a 4k box, it is *just* enough for jellyfish 90mbit. I realize on s905x you get it for free, but still...

    Just read this article: Tanix TX5 Pro TV Box Review – Part 2: Modding and Testing, under section 4K it said: 'The Amlogic S905X does not supports h.264 60 fps above 1080p'.

    I also don't get the logic of 4K h.264, which is supported by S905 but not by S905X while this format is now more and more popular in Asia. Not sure about what would happen with S912!

    Jellyfish 120Mbps 4K plays fine here in both H.264 and HEVC - but I have a S905 device. I'm afraid S905X as a costdown version might not be able to decode that high bitrates.

    I came to the same test result. Not only the Jellyfish, but also my 4K H264 video plays smoothly on M18 (S905) with build LibreELEC-S905.aarch64- I also noticed minor audio out of sync (audio ahead of video) on Mini M8S II but not on M18 while playing 1080p and 4K x265 contents. Seems like we have to wait for next S905X driver update.



    test5 works on my M8S II box, including WiFi (2.4GHz), Ethernet, CEC, Bluetooth (detect my Mi band when BT enabled), and needless to mention the USB. Playback of 1080p and 4K x265 10bit contents has no problem, except first few seconds of 4K x265 video was blanked. Playback of 4K x264 videos, however, doesn't work (stay at UI). The 4K x264 contents could be played under alex's OpenELEC on M18, not sure whether it was a hardware or software issue. All 4K contents were played on 1080p TV.

    What surprised me was memory usage of this build is very low. After playback of 1080p x265 10bit movie, memory usage on my M8S II is 15% (2GB RAM/8GB ROM) and after interrupting playback of 4K x265 content, memory usage is only 16%. I have never seen such a low memory usage figure before. The box is populated with over 8000 entries of video library and using Xonfluence skin (i.e. not the Confluence skin).

    Pity was I gave away all 1GB boxes I had and couldn't test this build on them. Memory usage is more important on those 1GB devices.

    Ah yes, I remember finding that forum through Google. But for some reason I cannot seem to get an account there, because the registration page doesn't like my answer to "5 minus 5", which I believe should be 0?

    If you knew what you need and how to flash the build to NAND or on SD card, this link Index of /image hosted all Alex builds. No need to sign up for download the files.

    Hopefully someone can help me. I need a remote.conf file for the Mini MX box. I have tried extracting it from both Alex's OpenELEC and android original firmware (OTA update file) without success. I would appreciate it if someone has this file and sends it to me, or show me how to extract it myself. The problem is that every time we update to a new version of LibreELEC we have to manually update this file. I wish we had OTA updates or .tar files to avoid losing our set-ups every time we update.
    Thank you very much.

    Not sure why you need the remote.conf file for your Mini MX box, cuz Mini MX is the default box for kzsaq's build. Anyway, you can download file named 'Beelink_MiniMX_factorycode-0xff000001.7z' from this link: Index of /LibreELEC/FILES/ . There you'll find remote.conf for Mini MX.

    As for updating, I experienced the same issue. However, before update, I make Kodi backup, copy the backup file to a PC, copy it back to the Mini MX box after updating, and then restore the backup. I have not tried copying the img.gz file to the update folder like what I did for RPi2. I used the SD card version and keep Android in NAND all the time. I am afraid updating with img.gz file in update folder might over write the Android in the box.

    Someone reported similar situation on another forum (M18 with Android in NAND and boot OE from SD card). How he fixed the problem was unplug the power of the TV (not only power off). He first boot to Android to check resolution setting, then boot OE again and problem gone!

    I have similar experience on Mini MX 1GB RAM, not only kszaq's LE build but also alex's OE build. Memory usage figures are about the same. I tested with 2160p x265 10bit videos (on my 1080p TV), playback won't even start if memory usage is over 50%. If I stopped playback at the middle and switch to another, playback couldn't even started as memory usage was almost 70%.

    Is there any background process running that keep the memory from releasing? Also if I populate my video library, I would never see memory usage below 35%.