Posts by chewitt

Kodi Settings > System > Logging

Quote from sunlollyking

So i've created the directory .nocompat

It's a file not a directory. The full path for 'touch' is /storage/.update/.nocompat

Another method is to untar the update file and move KERNEL, KERNEL.md5, SYSTEM, SYSTEM.md5 to /storage/.update and reboot.

I'm (still) failing to understand what you are trying to achieve. Synchronous playback on multiple devices?

Full clean build? .. or you pulled changes and just did a respin?

You cannot edit the original skin files as those exist inside the read-only SYSTEM file, but you can copy (clone) the skin directory to a writeable location like /storage/.kodi/addons/skin.myskin and then edit the addon.xml file for the skin to rename it so there's no name clash between the embedded skin and your cloned one. Stop and restart Kodi (or reboot) and then enable and select the skin to be the active one. Use kodi-remote from the SSH console or kodi-send commands to reload the skin as you make/test changes.

USB 2.0 ports provide different speeds and current draw limits to USB 3.0 ports. Power and bandwidth on a specific port (and the upstream hub) are also shared between other devices connected to the same hub). I'd guess you had the device in a 2.0 port and have now moved it to a 3.0 port .. or something like that.

Kodi is crashing. You'll need to enable debug logging and then share the resulting Kodi crash log for anyone to comment.

There are hundreds of HOWTO articles on installing grub2 out there. I don't have one to-hand so you will need to go find and read one. The main point to understand is bootloaders are installed to a root disk device like /dev/sda, not partitions like /dev/sda1, or folders inside the filesystem contained within a partition. The only files that need to be copied are KERNEL/SYSTEM. The bootloader will want a config file though, which should reside in the same partition. The grub2 config file will have some kind of 'APPEND' line for boot params and you can crib that content from the syslinux.cfg file.

Our distro packaging makes customising the skin complicated because Estuary is inside a squashfs file (SYSTEM) which is expanded into a virtual and read-only filesystem on each boot. You can clone the skin to /storage and then make changes to the clone, or you create a custom LE image that compiles the changes into the image.

LE is minimalist so we don't have git and change management tools in the filesystem. You could add them via a Docker container if you wanted to, with a clone of the Kodi repo to e.g. /storage/xbmc.repo acting as the source of the skin and symlinks between the root folder of the Estuary skin files and /storage/.kodi/addons/skin.MyEstuary making the skin appear locally. It has the advantage of being somewhat self-contained on the device. It requires quite a bit of setup/fiddling though (and there are no guides for it) and you need to reinvent the wheel when moving to another device. If the changes are not extensive; perhaps skip "doing it right" and just clone the skin files locally and apply changes; and rinse/repeat occasionally if needed.

The ultimate "doing it properly" is creating a custom image with the changes baked in. I have virtual machines and resources for that, and I'm using this workflow:

Fork https://github.com/xbmc/xbmc/ to your own GitHub account. Now clone your repo locally, git remote add an 'upstream' source for the Kodi repo, and git checkout -b a local topic branch to contain commits for your skin changes. You can now make changes and git commit them to the branch, and generate diff patches using git format-patch. Over time and if required, you can git fetch upstream Kodi changes from their repo and git rebase your local branch against them, and regenerate the patches.

Fork https://github.com/LibreELEC/LibreELEC.tv/ to your own GitHub account. now clone your repo locally, add an upstream remote for the LE repo, and checkout a local topic branch for your LE image changes. Add the diff patch(es) generated in the Kodi repo to packages/mediacentre/kodi-theme-Estuary/patches/ then commit them to the branch. You can now build a custom image that applies the diff patches to the skin. You can periodically fetch changes from our upstream repo and rebase your branch against them. and then rebuild the image.

No idea what works best for you .. it's about time/effort/resources/skills available

If the file glitches consistently in both LE and Kodi on Windows that might hint at a VAAPI hardware decoding issue. MPV is also a big fancy wrapper around libavcoded, but is probably using a different underlying version and/or is software decoding the file resulting in a different code path and capabilities. You can experiment in LE by disabling VAAPI hardware decoding. You can also experiment with an LE13 nightly which has newer kernel (drivers) and FFMpeg versions to see if newer is better (not always).

The extlinux.conf file is in a VFAT partition readable (and thus editable to change the dtb name) on any modern OS, even Windows.

Quote from bulk

Do you recommend another board that works better with LibreELEC than RPi5?

Nope. I have 40+ ARM SoC boards and RPi5 is the best (consistent and reliable) experience of them all. I don't ever use WiFi with any device though, and if forced to use WiFi i'd be using a USB device with a proper external antenna, or a WiFi bridge; not the onboard module which I've always found to be a bit rubbish for streaming use.

The error message is generated between kernel + iwd + ConnMan so isn't something we control and the key is something obscure and internal to 802.11 radio standards. If you're already using a WPA2/3 mixed mode network poor signal strength is probably the underlying cause.

There is no database or config file in Kodi that stores ROM/Emulator/Controller data but if you are using IAGL? it stores that kind of information under /storage/.kodi/userdata/addon_data/plugin.program.iagl/dat_files .. there's usually an XML file per target platform (being emulated).

Have you tried installing other emulators so there's a choice to use? (no idea if that might prompt something... just a guess).

LE13 has general rendering improvements over LE12 and older releases as @sarbes has spent time on optimisations.

Note: the patch I linked will do nothing for you on an x86_64 device as it's for the OpenGLES rendering path (used with ARM SoC devices) and Generic does not use GLES rendering. There's probably a similar point in the OpenGL code path where you can add something similar though.

The website/webserver is up and working fine, so if there's a problem, it's local to your environment or connection.

Quote from ghtester

Mostly due to unfixed issues with subtitles that I have reported a long time ago

One of the decisions made when doing a takeover of the project 18-months ago was ignoring the historic issues list and starting out with a clean slate. The historic issue list has ~1500 open tickets with no priority, most poorly reported, and most poorly investigated, and mostly no idea whether the reporting users are even around and still using Tvheadend. Why burden the 'new' team with a huge pile of old crap? .. it's a better use of very-finite human resources to focus on what's still current and cared about.

Anyone with a still-valid issue is encouraged to report it via https://github.com/tvheadend/tvheadend/issues - Follow the template and provide logs from tests with a current/recent release. Old issue reports are visible here: https://old.tvheadend.org/projects/tvheadend if there is any merit/value in linking some old data/info in the new report.

emelsky If you are able to boot some other OS, e.g. Ubuntu Live USB, the issue is the BIOS not liking our syslinux bootloader. If that's the case you can boot into Ubuntu and perform a manual install. In short; create a new GPT partition scheme with two EXT4 partitions (BOOT = 512MB or 1GB and STORAGE = remaining space). Copy the KERNEL and SYSTEM files to the boot partition then install and configireu the working bootloader, e.g. if the Live USB uses grub2, install that, along with a boot entry to auto-boot LE (crib the content from the syslinux.cfg file). It's probably a good idea to ensure you're using the latest BIOS/firmware for the T620.