Posts by JonSnow

Quote from anthontex

Yesterday I've watched the football match in 4K hevc main10 without problem on a 1080p monitor for me it's ok (mini mx)

Edit: speaking of 2160p@50 hevc main10 channels remember there is also an hardware issue with most amlogic s905 (except of wetek hub for now that ships revision C). So some of these channels will freeze and won't be played.
An example is Hotbird 4K1 that randomly after minutes stops or Canal+ on Astra.

Wonder if the newer MiniMXIII has the same processor, I don't have a 4k TV yet and not planning on getting one just yet but still curious to know since the old mini mx was released just a few months prior.

Quote from xbliss

Anyone try this on the Cheapo 25-30$ boxes like the MXP?

It should work but I advise spend the extra $$ and get the MiniMXIII or at least a device with 2GB RAM to counter the issue few post above.

Quote from kostaman

Below is the quote from kszaq when i was testing the Dev builds prior to Public Release.
He is aware.

"The memory usage is caused by how Amlogic's video decoder allocates memory for playback in S905 devices: it uses Continuous Memory Allocator to reserve huge amounts of memory and it becomes temporarily unavailable to Kodi."

Hope this helps you.

Thanks, good to know he is aware of the issue. So i suspect this is the same with LE on the Odroid C2 and Wetek Hub?

Quote from wkchick

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

I updated my post with logs maybe you can do the same. This will probably help kszaq much more then us just posting issues without logs.

kszaq i will start a new thread if you would like as to not clutter this thread.

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 but not as quickly which is better. On my raspberry pi2 running osmc ram is always below 25% 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.

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, eventually would like to replace the rpi2 for the mxq pro.

My mxq has 1gb ram 743MB usable, 590MB (21%) free on boot, which is the same on the rpi2. 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 starts filling up. 52% ram used is when i stopped and grabed a copy of the logs, 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, but this should be good enough to show what i'm talking about.

Note: altered some parts to remove ip addresses and replaced with xxx

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

I have the same mxq remote as pictured in mark-aus-51 post (with numeric keypad). i have attached the remote.conf from android which i also confimed again the remote and all buttons are 100% functional in android.

In LE the back button (right side above the arrow keys but below the blue vol+ key) does not do anything in the UI but during video playback it only shows and hides the last kodi directory.

The volume +/- go left or right in UI or during video playback vol down seeks back, vol up does nothing.

Working buttons:
Backspace/Del button which is on the right side of the 0 (zero) key = works perfectly as the back key.
Home (house) button = working and goes Home.
Menu Button which is below the home button = works as the context key aka 'C' key on the keyboard.
Mute (left side of the 0 key) = working

Broken buttons (i dont use but may help others):
Green App button = Launches the Pictures library no matter if in settings, home or video it always opens Pictures. Maybe remap to launch video addons or Programs?
Red Setup button = Does not do anything in kodi or video playback. Remap to settings?

remote.conf i used with my custom OE is found here remote.conf

Edit:

Just tried the remote.conf from alex github linked above again with 002 and now everything is working 100% including vol+/-, back button. Everything is 100% working, so maybe use that as reference during install instead. The red setup and green app buttons do not do anything with alex remote.conf but i dont use those anyways.

The issues i have with this build:

1) wiping data/cache via recovery = no more LE and drops you to the LE shell instead, which explains my above post.
2) remote is not 100% functional however all buttons worked 100% with android prior to flashing. Now only OK, arrow keys, home buttons work and Back and volume +/- do not do anything once on LE. Copying the remote.conf from my working OE build (based on alex sources) or the remote.conf from alexs github for the mxq = nothing works dead remote. Anyway to fix the back button?
3) power off and reboot work when using the Kodi soft buttons, after selecting 'power off system' the box powers off and turns back on when the power button is pressed on the remote. However if you press the power button on the remote while the box is already on it looks like it powers off but no longer powers back on with the remote. I suspect the device goes into suspend and gets stuck in limbo which was the same issue with all OE builds i tried. I'm hoping suspend can be disabled completely and once you press the power button on the remote it just powers off the box instead. Suspend seems useless and breaks things so hoping this can be addressed in a future build.

I will test hd audio 3d etc in the coming days.

Cant get this to boot on my mxq pro 4k v1 blue board. This board has an issue with the toothpick button (not soldered), i can get into recovery via adb or ssh and had my own custom OE from alexs sources.

When installed from SD or flashing from recovery i always get the below not sure how else to install aml_autoscript from the zip

Error in mount_flash: mount_part: Unknown filesystem

Edit:

I flashed back to Android put aml_autoscript and libreelec....update.zip on SD card (without factory_update_param.aml), launched Backup&Upgrade app in android selected the libreelec.zip and proceeded with the upgrade. Box rebooted and started flashing and once complete it booted LE successfully.