I don't keep track of them all .. but they're all in this section of the forums.
Posts by chewitt
-
-
Online docs talk about global limits but I believe you can set them in individual service files too, and /storage/.config/system.d/ allows you to override any of the embedded .service files with your own (stop/disable the embedded service, then enable/start the custom one). LE doesn't allow you to install things to the core OS (everything is inside a read-only squashfs image) so any extra things you added via docker (or things wrapped as Kodi binary add-ons) must be using the persistent /storage area which is writeable so you can make direct changes.
-
8GB is the normal minimum we quote for any Kodi install (hence the previous CM1/CM3 with 4GB are limiting) but 16GB is probably a better size to have headroom unless you want to experiment with retro gaming or docker in which case the 32GB card might be attractive (and only $5 more).
As the Slice has a solid metal case a heatsink that achieves contact can conduct more heat away, but there's never been an official heatsink that does this - only homebrew designs that users created for themselves, and the extremely exact dimensions required probably need adjusting for the newer chip design. So the easier option is to get the normal stick-on RPi heatsinks and use those. The result is not as efficient, but it's still an improvement on having no heatsink(s) at all, and you can get them from any Pi reseller for $1.50.
-
There's no generic S805 image but there's a couple of community releases in these forums which you can experiment with .. it'll be a trial and error process to find something that works.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
An educated guess is .. you didn't set whitelist entries so everything is running at 60Hz instead of 25/50 or 29.97/59.94.
In Kodi video settings.
-
I'm not sure it's the reason, but all the Netflix developers are German

Add-on suggestions are best made via the respective add-on support thread in the Kodi forums.
-
We'll add that to the list of things CE don't understand then. It's a lengthy list.
-
Long story short .. there's nothing in the logs. For the sake of experimenting please configure things then stop Kodi with "systemctl stop kodi" and then reboot. Is the calibration preserved? .. this should isolate whether it's the multi-year recurring issue of the OS hard-terminating Kodi (because it's taken far too long to shut-down) which can corrupt guisettings.xml and results in a new file on restart. Also useful to know .. do other settings get lost too?
-
LE supports update from .tar file and .img.gz so it's not a problem.
-
As a rule LE (the OS) and Kodi are a simple update. The challenge has always been user-install add-ons. The more junk that's installed the greater the likelihood of something having issues. Make a backup and move it off-box and you can always recover things.
-
We don't support auto-restore from backup on first boot (and have no plans to add it) but in LE 9.0 the first selection on the first-run wizard is a language chooser .. which might help.
-
Current efforts are not in vain, and while I can't go into details, I don't have concerns about S905X2/D2 support.
-
I'm not sure whether ARM's open-source group have been given the internal approval to submit code to Panfrost yet, but the request has been made and they're keen to start. Meanwhile a couple of ARM engineers are engaged with the Panfrost devs, testing code, and generally finding other ways to be useful. We (LE) are partly responsible for some of the those connections being made

-
Kodi uses libaacs to read BR media and libaacs will not function unless there's a KEYDB.cfg file present with appropriate content for the disc that you are trying to play. I have no personal knowledge on makemkv so I can't comment on how you'd make that work.
-
The alternative is a huge number of spam bot posts per-day which is repetitive and demoralising work for the forum staff who already give up a large amount of their personal time to help the project. We value making their forum lives easier above a little wordplay inconvenience for users. Sorry but it's not going to change.
-
Lima submitted its kernel driver today. It's not the first submission but this time around it has a fairly distinguished list of "Signed-off-by" signatures on-board so I'm hopeful it goes into the 5.1 merge list and there's a date that I can drop one of the larger patch-sets. Panfrost also merged initial mesa stub support which will make mesa packaging easier from 19.1 onwards. All over the codebase we're starting to see lots of the jigsaw pieces slot into place although community development is often a frustratingly slow process. I'm confident that in the future we'll be able to release a single Amlogic image that supports GXBB + GXL + GXM devices, though that's a long-term goal (not in in this half of the year at least).
-