Posts by chewitt

Are you using the Generic Legacy image? The default (GBM) Generic image no longer contains nVidia drivers due to their lack of support for modern Linux graphics standards.

Unless you have a fast Intel CPU device; leave it at the default (1080) setting.

Mi Box S Gen 2 uses an S905X4 chip and the mi stick 4K is either S905Y4 or S805X2; in all cases there is negligible usptream kernel support for those chipsets so no current plans for LE support. If the bootloaders are unlocked you can probably get CE to run on them, but that's a topic for the CE forum not here.

IMHO wait until the RPi5 bits arrive then pull the drive out and connect to the new(er) RPi5 based NAS device. As much as I like the Slice box it's slow and dated and having the drive connected locally to the new stuff will just be easier.

Please report this to the add-on support thread in the Kodi forums; then someone might make changes to correct the issue upstream.

I'd suggest updating to a current LE12 nightly (which are quite stable to use) as a first move. Then if the issue is still present, share a sample (90-120 seconsds) from a media file that allows the issue to be recreated. Then pi devs can have a look.

There aren't many Android users in this forum (for obvious reasons). Better to ask in the Kodi forum or an Android forum.

Even if it is 'only' 25% difference, it's the difference between 1080p anything playing (S905X3) or being stuttery and un-watchable (S905).

WireGuard.Address = 192.168.4.2/24

What happens with /24 instead of /32 ?

Quote from Tartarus

but unfortunately on S905 720p also stutters, although there is no big difference in raw computing performance.

There is a sizeable raw compute performance difference between S905 ([email protected]) and S905X3 ([email protected]+) hardware.

Quote from Free Man

Oh, one other question - will it support h265 playback?

Yes, HEVC/H265 is hardware decoded to 4K60 and HDR with 10-bit depth.

You can do "dmesg | paste" and "cat /storage/.kodi/temp/kodi.log | paste" to generate two URLs; one for each log. If either of them is large the combined logs + extras that "pastekodi" generates might be too large for the ix.io paste service.

Quote from Free Man

Would you recommend a 4 or 8GB Rpi5 for running LE?

I wouldn't look at the 8GB model unless planning to run containers and such in the background. For normal LE use a 2GB board would be fine so the lower spec 4GB board is more than enough.

Quote from jack121

Would LE install onto a zidoo z9x pro

100% no, it has a Realtek RTD1619BPD SoC chip with zero upstream kernel support.

This is a box for the pirate BeOutQ satellite service in the Middle-East (targetted at Saudi Arabia). According to a UEFA report on the box that I found in Google it has a Montage M88RS6060 tuner and this chipset has drivers in the upstream kernel (CONFIG_MEDIA_TUNER_M88RS6000T) which are not currently enabled in the AMLGX image; but the user behind the video has presumably self-built an LE image after enabling the needed things.

LE10/LE11/L12 all support DVB hardware (internal or external) *IF* the hardware has upstream drivers. Your WP2 box has old drivers written for 3.10 kernel that were ported to 3.14 .. and nothing newer. I made an attempt to clean-up the tuner/demod/diseq drivers (enough to compile them on a recent/current kernel, see https://github.com/chewitt/linux/commits/dvb-sucks) but these drivers are not modular following modern kernel standards and more code-glue is needed to make anything work; and AFAIK the signal from the tuner and demod needs to be processed by an Amlogic demux driver which doesn't exist. I have no real clue how the DVB stuff works and I don't write code .. someone that does needs to take that work forwards.

TL/DR; nothing new .. nothing that will advance the non-support for the tuners in your WP2 box.

To my ears that sounds like even greater justification

Thanks for confirming. The change will go into LE12 with https://github.com/LibreELEC/LibreELEC.tv/pull/8201

I'm reading your description and my first thought is .. this user needs to get a NAS box and migrate the mess of USB drives and cables and wall-warts into a single device that just sits in the network serving media. Not the cheap option, but it'll be a pile more reliable for any client box/board to work with and you'll quickly forget all about USB woes and focus on movie watching.

NB: No idea about numbers of drive limits or power limits; not my area of expertise.