Posts by chewitt

These days you can probably handle ext4 things under WSL, but NTFS dates from '90's era MS which was more aggressively against the idea of allowing use of anything other than the one true OS to rule them all..

Start with sharing a Kodi debug log with several plays that demonstrate the scenarios (with an explanation).

powerarmour read and implement a mode whitelist: https://wiki.libreelec.tv/configuration/4k-hdr .. then share a clean log.

The source Da Flex linked is outdated and won't compile for the Linux 6.6 kernels we use in LE12. This one is more up-to-date and should be fine: https://github.com/lwfinger/rtl8852bu. It's not something we will entertain adding to the main LE image, as we have a long-running policy of refusing to add more Realtek vendor drivers.

In Estuary:

Home > Add-ons > My Add-ons > navigate left so the view controls and filters are visible > Check for updates

I've watched some GoT episodes yesterday where I downloaded subs from OpenSubtitles and the line order was indeed bottom-up not top-down (so I can confirm a problem exists). However there were also episodes where subs were either already downloaded or perhaps embedded (not sure which, it was late) where the line ordering was displayed correctly, so it's not the case that all subs are bad and more testing is needed to narrow the problem. I'm travelilng for a few days now so can't easily check, but if you could do more testing to ping things down it would be helpful.

On restart binary add-ons like Tvheadend are binary incompatible and will be marked bad (until they update). If you have an issue with the repo .. force refresh it.

Original credit to Kwiboo who spotted the original problem and authored the patch.

Quote from meirick

But after restoring the backup, the same probleme appears.

Once you restore the LE11 (arm) backup on LE12 (aarch64) the restored binary add-ons aren't going to work as they are compiled for the wrong CPU architecture. This should eventually resolve itself when the LE11 add-ons self-update to compatible LE12 versions. In this scenario all you needed to do was update to LE12 and let add-ons udpate themselves, the clean install ahieved nothing.

I'll ask for a Kodi debug log, but I have a hunch that will reveal you're using some IPTV source with thousands of channels, which will mean it's a pirate source, and then we don't care about the problem. In the unlikely event I'm wrong .. provide the log.

Quote from 2469

is there a good guide on how to convert it?

There's probably something in Google if you look, but realistically there are only two options:

a) Move data off the disk, change the filesystem type, move the data back.

b) Shrink the NTFS partition, create an EXT4, start to shuttle the data from one to the other and progressively shrink one, expand the other, until all the data is moved, then delete the NTFS partition and expand EXT4 to 100%.

Both will be rather slow .. depending on how full the disk(s) are.

NB: No idea if there's an actual conversion routine. I wouldn't normally trust that kind of thing.

I suggested "video=HDMI-A-1:1280x720M@60" and not "video=HDMI-A-1:1360x768M@60" for a reason

In the past exFAT and NTFS required "userspace" drivers that suffered from slow read/write performance. These days both of those filesystem types have native kernel drivers so performance isn't an issue. However both have reliability issues and NTFS notably can have issues that can only be corrected using chkdsk.exe on Windows. As such, the preferred format for Linux drives in LE is still ext4.

The AMLGX "box" image might boot on the device, but there is no specific device-tree to use in the upstream kernel. I'd suggest starting with the U200 device (g12a) and seeing what works. WiFi and BT will depend on what chips are inside the stick, and the device-tree used (which needs to describe them). We do not support eMMC install.

LE does not support eMMC install on Android box/stick devices, only specific SBC boards.

LE executes /storage/.config/autostart.sh at the start of userspace boot long before the network is brought up. As a result the script logic will always return "Internet is not available. Exiting without download." making the script (as-is) pointless.

The low-skill approach to scheduling the script to run later in the boot sequence is to "(background)&" execution and use a sleep command (10s is normally enough). This will ensure the script works, but Kodi will have already started so there's no point trying to redirect messages to the console TTY for on-screen display alongside the LE boot splash which is quickly overwritten with the Kodi boot splash then home screen; although often that happens quickly so you only see the home screen.

The better approach is to schedule script execution with a systemd service as this supports dependencies; you can dependen on network-online.target to ensure the network is up and avoid the ping-Google check. If you further depend on kodi.target you can also use kodi-send to show a toaster notification in the Kodi GUI, e.g. "Image Downloading.." and then "Rebooting in 5 seconds" or such before you force reboot to update. Have a look at the example wireguard.service in /storage/.config/system.d/ for something similar to what you need. Beware that systemd does not inherit $PATH so you must use /full/path/to/binary in commands.

You don't add "files" to Kodi. You add a "source" which defines the base path and type of file (TV or Movies) to be scanned for, and then you scan the source; and the scan adds the files (that match online content libraries or local .nfo files).

All of that is explained in the Kodi wiki: https://kodi.wiki/view/Settings/Media/Library

Or you use the "Videos" non-library view which simply shows what's in the filesystem. You still need to add sources though.