I threw in a new log.
Apparently you also added a big ass GIF in your signature...
Does it really have to be that obnoxious in size?
This is a support forum, not an fanart agency.
I threw in a new log.
Apparently you also added a big ass GIF in your signature...
Does it really have to be that obnoxious in size?
This is a support forum, not an fanart agency.
Apparently you haven't bothered to read the forum rules when registering to this forum.
FYI: we have a zero tolerance when it comes to using illegal video streams.
Your kodi.log file is infested with various repositories and addons that are banned by Team Kodi, and thus also by LibreELEC.
Either you submit a clean kodi.log file without any of these addons, or you can find your support outside the LibrELEC forum.
And what about the video types?
Raspberry Pi and Rockchip RK3328 devices are completely different animals, so will need a Rockchip RK3328 build of LibreELEC.
AMD support hasn't always been optimal (thanks to the lack of proper AMD video drivers).
Does your Core i5 have an internal GPU onboard? It's likely much better supported than the old AMD 5450.
Also, h264 videos should not be a problem. However, h265/HEVC videos will have to use the CPU for decoding, which can be a problem on older machines, resulting in a jerky video display or even slide shows.
Installing drivers separately in LibreELEC is not an option. All things need to be compiled along with the rest of the source code into a new build.
The Raspberry Pi upto the newest 3B+ variant does not do either 10bit or HDR hardware-wise. 10bit video is recoded into 8bit video on-the-fly.
HDR support in Kodi 18 is still a work-in-progress altogether.
HDR is the biggest problem/challenge for Intel-based GPU's running Kodi. Intel UHD graphics has the best papers there, AMD Ryzen/VEGA video drivers are still at an experimental stage, and Nvidia doesn't even have 10bit support under Linux. Don't be surprised when Nvidia support for Kodi/LibreELEC is fully dropped in the (very) near future.
For all other AMLogic or other hardware, have a look here at START HERE - Pick the Right Kodi Box (updated May 2018)
autostart.sh should always start, perhaps that's a better alternative.
First double-check the full path of a couple double movies, and see if there is any difference. Even a space can make up a different path.
Setting the content multiple times shouldn't create multiple entries, but I guess anything is possible.
It *should* be possible. Have a look here: XBMC JSON-RPC Reboot Freeze
Kodi 18 Alpha and HDR are still very much a work-in-progress, but yes... The "latest" build is indeed the correct one.
First of all, this is an English only forum, so please always add the English translation to your posts.
Also, using capital letters only in your text is considered yelling or screaming, according to Internet etiquette, so please don't do that.
That is not a debug log. A real debug log file is a FULL kodi.log file with debugging enabled, and not edited, redacted or shortened in any way.
Sorry, but the Clean Library function has no instruction set whatsoever to delete physical files, with or without a user's consent. It only deals with the video and/or music databases.
Start with providing a proper debug kodi.log file.
The RPi 3B+ has the wifi/bt module from the RPi Zero W, which is apparently "better" than its predecessors as far as hardware goes. Still, the RPi's antenna is simply small comparted to external antennas. In terms of software/drivers there is not much you can do, working with LibreELEC.
Windows laptops & Android have different hardware and different drivers. The one thing you could do is do a speed test with all hardware involved, and see what is the outcome.
Wifi surely can have its advantages, but the outright winner with network speeds is always the device with the cabled ethernet connection.
Normally all drives get their own device number in Linux, just lilke the drive letters in Windows. Hower, LibreELEC may get confused when drives with identical names for partitions are used. Or missing partition labels at all. The same may apply to identical path names.
Can you connect all possible drives, log into your LibreELEC box, via SSH, and get us the output URLs of :
Hopefully that will clarify things for us a bit.
It's pretty simple: just like upgrading, you paste the (downgrade) file into the .upgrade folder, and reboot the machine.
"/storage/.update/" can be found via logging in via SSH, and do a "cd /storage/.update" command.
Folders and files preceding with a dot (.) in Linux are hidden.
The upgrade folder should also be visible when connecting your File Browser via Samba with the Slice device.
You can also boot from USB on a RPi 3(B+) there days, so switching a USB stick with an operating system shouldn't be much of a problem. Quickly replacing a micro SD card has its downsides, especially when the RPi has a casing around it, and it is mounted against a wall like I have done.
LE 8.2.5 is EOL, try the latest Milhouse builds for Kodi Leia to see how BT works with them.
Sorry, but there is no crystal ball here available to know whatever piece of hardware you have, to even begin to know if you want is possible.