Posts by wkchick

Quote from afl1

I can confirm running HW support for VP9, playing 4k 60fps.
This is my test build with VP9: LibreELEC-S905.aarch64-7.0-devel-20161006124814-r23325-g3be647e.img.gz

First test:
VP9 is stopping playback at deterministic places
e.g.: The Curvature of Earth 4K 60FPS.webm stops at 1:47.

It looks like some bug in vp9_update_frame_header procedure.

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.

Quote from afl1

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.).

Quote from uomoint

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,
LibreELEC-S905.aarch64-7.0-devel-20160915211230-r23341-gb83596f.img.gz

No boot issue at all.

Quote from kszaq

Second test build: I reverted some kernel config changes I made that may have influenced ability to boot on S905X. Please have a look:
2016-09-25-devel-2

Thanks for your prompt response and hard work. But sorry, still doesn't work on my Mini M8S II, LibreELEC logo didn't even shown.

I used a fresh SD card installation.

Quote from ecko404

Box 1: Beelink Mini MX TV, Amlogic S905, 1GB+8GB.
Box 2: NEXBOX A95X Amlogic S905, 1GB+8GB.
TV: Vizio M49-C1 4K
HDMI cable: HDMI 2.0
Running Libreelec on both box on a class 10 SD card.

7.0.2.006:
Both Mini MX and A95X, 4K playback is working great. No 1/4 problems. All test files I try works.

7.0.2.007:
On A95X 4K playback is working great. No 1/4 problems. All test files I try works.
On Mini MX, some 4K playback is ok, other are not. Test files I have are working great. Seems like only HEVC x265 10bit files are doing the 1/4 playback problem.

I reverted to 7.0.2.006 on the Mini MX for now. Big thank you for all your work kszaq!

Display More

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

Quote from macman88

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.

Quote from kszaq

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

This is 7.0.2.007 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.

Quote from koenkooi

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!

Quote from koenkooi

3 consecutive boots from uSD: can't mount mmcblk0p1
2 consecutive boots from USB: can't mount LABEL=boot
[hr]

Same here on my Mini M8S II.

Quote from kszaq

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-7.0.2.006.img.gz. 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.

Thanks.

Quote from kszaq

wkchick Please post a link to a short sample that exhibits the issue so that I can test myself.

kszaq,
I tried but could not find proper video editing tools to cut a few hundred MB from my file. Anyway I download test video from Jellyfish Bitrate Test Files and test. I picked jellyfish-120-mbps-4k-uhd-h264. It works on M18 with alex's OpenELEC or lwiddif's LibreELEC build but not on Mini M8S II.

Thanks so much for your work.

debug log of 4K x264 video playback problem mentioned earlier: audio only, stay in UI for around 30 seconds then screen blank.
log-2016-08-27-02.58.52.zip - Google Drive

Problem started from 23:02:12.

Thanks.

kszaq

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 6.95.3.2 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.

Quote from MrMagic

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.

Quote from Majorero

Hi,
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.

Quote from kostaman

Something wrong in detecting your TV resolution on start up.
Your box is showing 1280 x 720 native resolution as it fails to detect your TV resolution on start up.
Try turning on the TV first and then the box.
Go into Android and turn off Auto Detection in resolution settings. I dont know if this is relevant.

Lastly in LE go to Settings/System/SystemSettings/Input Devices Peripherals/CEC Adapter
Devices to power on during startup select NONE
If that is how the TV is being turned on.

Sorry but that is all i can suggest.
I have a MiniMX but dont have this issue.

Display More

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!

Quote from JonSnow

One of my main issues with OE was ram management, after using a few addons (youtube etc), browing the library and playing a few videos, ram would quickly fill up to about 65%, once playback was stopped it would not release any ram until you rebooted the box. This would result in slow performance and then freezing once ram got to about 85% used which required a hard reboot.

This is 10x better on LE but ram slowly continues to increase on LE as it did with OE, and it is not being released. On my raspberry pi2 running osmc ram is always below 30% when idle regardless of what addon was used or what video was played. This seems like an OE/LE issue vs a box or build issue to me since on osmc i can go weeks or months without rebooting or freezing with pretty much the same configuration.

Let me know which logs you need and i can get them for you, i keep the rpi2 on 24/7 and would like to do the same with these s905 boxes and not have to worry about rebooting or freezing.

My mxq has 1gb ram 743MB usable, 590MB (21%) free on boot.

Regarding the power off issue from the remote, its actually not going into suspend/standbuy. Its just turing off the hdmi output to the tv, if you wait about 20 seconds the hdmi signal is restored.

Edit: Attached is the log of a fresh install on an SD card with a random bunch of kodi video addons, the box boots up with about 20% ram used and after playing, skipping, browsing different addons you can see ram slowly filling up. I took these logs at about 52% ram used, it will not freeze until it gets to about 85% which will happen in a few days if the box is left on 24/7.

Display More

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%.