Posts by ChimeyJimmey

Precise answer is - 720p (~)flawless.

1080p - stuttering like hell.

I have moved several KODi folders (e.g. userdata) from 8Gb class 4 TF card to internal,

and IMHO - fanarts are loading faster.

It would be great if someone could share a successful U-Boot re-flash experience and know-how for H96Pro+...

For me - it's not acceptable.

The question is not if, but when, it will malfunction. Like everything else.

S905/S905X with mods are maxing up to 50°C, S912 gets higher (~60°C), but all depends on the "design", especially with the cheap "karate" boxes...

I would suggest definitely to consider implementing some improvements of the current "stock" heat dissipating "solution(s)".

Otherwise - it will run as good as it gets, crash/burn and... You're off to the next 30-40+ $ one...

That's quite an interesting statement, based entirely on "assumption(s)", and wrongful...

Because,

as SoC definition suggests:

See where Mali-450 is residing?

Two chips, next to the CPU, are memory modules.

The third - NAND/eMMC.

As per "performance" governor,

you have to add this line in "/storage/.config/autostart.sh":

echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

to make it a persistent setting each boot/reboot.

After first testing the behavior of the box (performance and thermal state), of course.

And which on this picture is the GPU?

All the pros (and cons), which this early "alpha" stage of Kodi 18.x "Leia" / LE 9.x will bring you, with respect to the S912 specifics (no GPU drivers available).

Quote from rajawaqas

... I install two heat sink Soc chip and one heatsink on gpu( raspberry pi 3 heat sink)...

Would you, please, be able to elaborate on GPU chip, on which you've expicitly installed a dedicated heatsink?

I'm very curious to see that.

Nothing special in my setup,

except:

1. Hardware decoding for everything, always, apart from Amazon/Netflix.
2. CPU governor is set to "performance". My boxes are "cooling modded", neatly inside the chassis.
3. No synchronization of frames to display rate and etc.

These:

• LibreELEC-S905.arm-adamg-1.0.8.img.gz
  
  
• LibreELEC-S905.arm-adamg-1.0.8.tar

S905/S905X, which I have, do not exhibit any issues, when passing through Atmos 7.1 and DTS:X audio...

I haven't noticed any frame drops with text subtitles, 4K content runs smoothly (depending on the source type),

and inputstream depending addons (Amazon/Netflix) also run fine (top quality 720p).

So, the statement, that S905/S905X boxes are recommended for LE as "all-in-one" capable, against S912,

remains valid still.

At least - this is my conclusion, based on personal experience, so far...

Quote from Brachiator

I installed LE on my internal last week and now I'm back on my SD card because the speed difference was negligible and loosing Android was not worth it.

You can have them both, you know...

Either by relocating certain folders (e.g. .kodi/userdata) to NAND/eMMc (/dev/data),

or like this:

[HOWTO] Boot from SD card, use internal memory for data

I know, libhybris hack, right?

Just wanted to check whether it might be a HW or setup issue...

Anyone achieved flawless playback of Amazon/Netflix streams, even @720p, on S912 with LE+Leia... ?

So far - I could not...

S905/S905X cope with it, S912 - tragedy...

Quote from sergiosmail

Using an external USB/network dongle works flawlessly, but using the on board ethernet doesn't work (same for wireless)

Any help will be welcome

Either the NIC is faulty,

or, most likely, there is no proper firmware for it, yet.

Provide us with the output of these commands, for start:

dmesg | paste
ifconfig -a
iwconfig
ethtool eth0
udevadm info /sys/bus/sdio/devices/sdio*

What about using USB-LAN adapter, even just for testing purposes?

Thanks for the information about this tool!

Will try to install raw image of SLES 12 SP2 on a VM drive to test its capabilities...

What kind of attention are you talking about?

Normally,

widevine libraries should be in /storage/.kodi/cdm folder. At least - that's where the inputstream is looking for 'em by default.

1.0.6 upgrade is not deleting this folder and its content,

and I haven't noticed any of the previous update releases to touch it either.

Just create cdm folder once and put the appropriate libwidevinecdm.so in it,

and you should be safe.