Seeking problems are a known issue that will not be fixed in current release. If you're lucky it might be fixed in 9.0.
Posts by chewitt
-
-
THE LIBREELEC INSTALLER DOES NOT INSTALL TO PARTITIONS, IT WILL ERASE THE ENTIRE SELECTED DRIVE
If you don't believe me, feel free to erase your own setup while testing before giving out advice.
-
I haven't been able to get LE 8.2 releases to mount a TimeCapsule from Kodi as Apple has their own shitty SMB implementation that doesn't appear to play nice, but I was able to make things work using kernel level mounts. Google for recent TimeCapsule threads in this forum and you'll find the instructions.
-
Commits · kodi-pvr/pvr.stalker · GitHub
The only commits since the "df111a0" githash that we use for Krypton are translations and a gcc compiler fix that we don't need. So whatever the EPG issue is, it won't be fixed with the 'newer' version. Even if we look at the master branch there's only some stuff to handle Kodi API bumps and nothing interesting.
-
If you are using an official LE 7.x/8.x release iptables is enabled but has no rules so the firewall is not the issue.
-
No. Android .apk files are NOT supported.
-
USB 3.0 means nothing really exists among cheap ARM devices. Drop that requirement and lots of Amlogic (and soon some Rockchip) devices are possible. It's not really required.
-
Try a USB 2.0 port?
-
Please test with a current Leia build and if the issue remains, report to Kodi developers via their forums. At this part in the release cycle for Krypton, even if the bug is found in Krypton, the fix will go into Leia.
-
^ to save repeating myself.
-
Update to 8.2.1 and if not resolved, report as a bug to Kodi developers via Kodi forums.
-
How are you connected to the Internet? Ethernet or another WIFI device?
-
Kodi upscales content to the base resolution configured. This was 1080p. It is now 2160p. More upscale processing = higher CPU temps.
In the past Kodi only had to scale SD and 720p to 1080p which was a small jump in resolution and rendering processing power, and it only changes refresh rate, not resolution, except on some Android devices. Handling 4k (and 8k in the future) requires a code level rethink. Increasingly people have low power devices that can hardware decode 4k media but due to slow ARM CPU's and internal memory bandwidth constraints they cannot handle 4k GUI and overlays. Kodi does a better job of scaling SD/720p to 1080p and it's easy, whereas AVR's and TV's typically do a better job of scaling 1080p to 2160p than Kodi. Kodi attempts to run at the max refresh rate supported so 29.97Hz runs at 59.94Hz etc. but new 120Hz capable screens double 60Hz which requires more processing than available. Kodi needs to evolve the concept of resolution switching in addition to refresh rates, but we nearly always need to manually intervene and impose limits rather than auto-detect capabilities. It's a complex topic with a web of interdependent variables. Kodi developers are currently in the process of figuring out how to technically deliver a solution for this without too much code spaghetti and a reasonable 'configuration' user experience. Oh, and at the same time we're rewriting the Linux graphics stack to support HDR, and other colourspace/metadata things that add complexity to the 4k process.
TL;DR .. today Kodi works as expected. In the future Kodi aims to be more flexible to get the best output from individual devices.
-
Test a Leia development build (if possible) to check it's not already been resolved. If not, report to Kodi developers via their forums.
-
On what LE version?
-
I'm not using any illegal/streaming addon. I'm using Sabnzbd, which is usenet client, plus Sonarr/Radarr/Hydra - all from thoradia repo.
Stealing copyrighted media from usenet is still stealing copyrighted media. The tolerated presence of that repo on this forum needs to be revised.
-
Pastebin a Kodi debug log pls.
-
It's a problem for all devices bar the handful that have been widevine L1 certified and have device-specific certs embedded in their firmware. WP2 and Hub are certified devices, but we would need to implement OP-TEE secure boot on Linux. We are aware of work being done for a European telco IPTV project that uses Amlogic S905D devices that we would like to learn from, and may revisit things in the future once a mainline kernel codebase is available. It's not going to be an LE9 feature.
