Posts by ChimeyJimmey

GDPR-2

I am not confident the issue roots in your latest build,

as I am experiencing the same Kodi crashes also in Win and Linux (all Alpha releases from December 21st on), which is remedied by re-installing and pre-configuring all my addons from scratch.

So far - I was not able to pin-point it to a particular component, as (crash) logs on all platforms are not providing any clues, none whatsoever.

Therefore,

for now I'm blaming mostly my sophisticated implementation.

But I'm eager to test your next build.

Upgraded to 8.90.1 - everything crap.

Reverted back to 8.90.0, disabling autoupdate on the boxes until further notice...

Heh, dream on.

Nope.

Good one!

That's the best way to remember something forever - empirically discover it yourself.

Right.

Now,

let's compare the price of Intel NUCs and "those trash Android media players"...

That's the one.

I assumed that was the reason.

I see that autoupdate script is not active in this build.

And:

Quote

# cat /sys/class/thermal/thermal_zone0/temp

cat: read error: Invalid argument

Temp readings are invalid...

Cooling modd it.

Turn on the AML HW decoding capabilities (MPEG, AVC, HEVC and etc),

then accept the software based decoding/decrypting concept of streaming services like Amazon/NetFlix, whose quality will be (forever) limited to 720p at best on S9xx based LE boxes.

No relation between these keys and LE, AFAIK...

What about this?

Do you have /c/backup on your time capsule?

Do you have /storage/mnt on your LE box?

Are you sure that NFS service is properly set on your time capsule?

I also do not use 100Mbit copper, except on management interfaces, limited to it.

Each (infrastructure) solution has its specifics.

That's why we're looking for resolutions (workarounds, at least) and this is one of them.

Each has to decide if it suits the needs, but at least it's been made publicly available to try it.

Quote from Tim_Taylor

I don´t see a big difference in practice using Gbit network

I´ve checked it out - videos aren´t playing better after local NFS mount.

Maybe it works in some cases using fast ethernet only

Well,

my humble experience with S905/S905X/S912 boxes has showed that when playing content from NFS mounted via Kodi - the box freezes on 10-15 minute. Regardless of cache settings. No such issue in comparison with SMB3, same cache settings, same source server.

When OS (LE) is mounting NFS to a local folder - no such issues observed. See this thread.

Also,

I could not distinguish a big difference in performace/throughput between NFS3 and SMB3...

Quote from tennis

what and where should I copy?

Thank you

You have to make a local folder,

add the following into .config/autostart.sh, for example:

mkdir -p /storage/MEDIA
sleep 10 (or sleep 15, or more, empirically discovered value)
mount -t nfs <IP_of_the_source_server>:</NFS_export_folder> /storage/MEDIA

Of course,

you can mount NFS shared folders to existing, pre-built ones, like /storage/videos, /storage/music and etc.

My two cents on this topic:

NFS via Kodi - crap!

Mount NFS export folder into a local for LE one, then present it to Kodi.

This skin appears to be 450Mb+ ?!

Abandon it on these devices, use SiLVO mod, for example.

Expected outcome.

Unless someone fixes the u-boot for H96Pro+,

that's how it's gonna be.

I don't see why not...

Just make the proper sym links...