Posts by chewitt

Generic S812 devices are not officially supported but there are community builds available. RockChip devices are not currently supported, hence no builds available. If you are generally "a bit of a noob" with these boxes it's probably best to stick with Android.

Set a small and badly named "wait for network" boot delay in the LE settings add-on. It sounds [sic] like Kodi is starting before the audio drivers have finished loading in the kernel, and if not loaded Kodi won't auto-detect the audio hardware.

It means the version of inputstream.rtmp in the Kodinerds repo was compiled against an older (now out of date and incompatible) Kodi API version.

Install the officially supported (and compatible) one from the LE repo - or post in Kodinerds forums.

Scope: No, probably because we have no support for PPTP/L2TP and no plans to add them.

If you have issues with 2TB+ drives the problem will be SATA chipset firmware not the Linux drivers. It's quite common to find older drive caddy's from the era before 2TB drives that have bad firmware. Anything recent should be fine.

LibreELEC is only for Kodi. RasPlex is for OpenPHT. RasPlex borrows the core OS from LibreELEC and the developers of both project collaborate on things of mutual interest, but ultimately RasPlex is a separate distro. If you want to run OpenPHT you're best off asking for help in the RasPlex forums.

I did create a build for ATV based on LE 7.0.2 and my github branch has 99% of the changes, but in my opinion the end result wasn't great and it's not something I am prepared to publicly support (too many other things to sweat time on) so I made a decision to not release it. AFAIK Sam is still releasing OSMC for AppleTV so maybe look at that option.

Use an SFTP client and transfer artwork files to a local folder you create on the box, e.g. /storage/artwork

Internet connection means "path between you and the service you're accessing" not the link speed between your router and the ISP, which is nearly always going to be good and above suspicion. The problem is somewhere in that path, and again, cache tweaking solves local (not remote) network problems. If it takes 5-30 seconds to get a stable flow of bits from the remote server, that's how long it takes.

No debug log demonstrating issues = no problem to investigate.

You can post logs and dig into things all you like but this is a driver issue that needs to be fixed by nvidia. Let me know when you get a support ticket, because then (and only then) I can enquire with their support team.

You have pirate add-ons/repo's installed. No support is provided to users of that crap.

Nope, and I would discourage anything from being created because users get very OCD about "performance" numbers and raw metrics on CPU etc. are misleading on the overall performance and experience of a device.

Faster I/O on the card will always help the overall LE/Kodi experience, but the "slow" I/O on the card is still many times faster than your ISP connection so buffering issues are about ISP/latencies not hardware. The read-ahead setting in the buffer can be increased, but cache tweaking only ever solves local network performance issues, i.e. bursty wifi and drop-outs, not "my internet connection isn't fast enough" type issues. As a broad rule unless your internal network is crap (in which case the solution is fixing your network) cache tweaks should not be needed.

There is nothing we can do to make it appear. Our end is good, and we have no idea which mirror you're talking to.

I've seen a couple of reports (on other builds, it's nothing Slice specific) where people aren't seeing 8.0.0 in the lists of available manual updates. This can only be an issue with mirror servers as the JSON file queried by the settings add-on is 100% correct on our servers.

There have been similar reports from internal testing but it's not been something we've been able to pin down.

100% not supported, thankfully..