Posts by chewitt

LE will always prefer to route over Ethernet if Ethernet + WiFi are available but I don't think that's relevant. if your phone connected to the WiFi network cannot access the GUI of an app which is on the LE/HTPC device with a valid IP in the WiFi network; the issue is with the app on the LE/HTPC device not "listening" for traffic on that interface. Apps are "bound" to IP/port combinations (and IP's belong to interfaces). I'd guess the app is bound solely to the Ethernet IP/port and thus does not listen for traffic on the second (valid) WiFi IP/interface on the host system. That's an app issue, not an LE issue.

"netstat -a" will show you all the open ports and assocaited interfaces. Start there.

Ansible is normally used to describe software packages as part of continuous integration workflows. It's not used (or needed) in LE.

Developers use a variety of text editors to update code/config files and "git" provides version management/control of the changes. Same for Kodi and most open-source software these days.

Quote from Shoog

As far as I am aware this feature is no longer provided in any official versions of LE and there is no interest in bringing it back because of the number of people who end up bricking their boxes using it.

^ as the man said. It will reappear in the future, but not in its current forum, and probably with a restricted set of hardware targets

balbes150 has some mainline kernel test images that run on VIM2 boards using panfrost instead of the missing mali blob. Things run "okay" but panfrost has some OOM stability issues that probably won't be resolved until we switch over to a proper kernel driver. I think we're a couple of months away from something stable enough for regular use. I'd stick in the stoneage for a little while longer until there's a clear option

What happens if you remove the incomplete "options=" line?

vpeter can you do an RPi image for these folks to test with this commit: TEMP: bump connman to HEAD to test ntp fix · chewitt/LibreELEC.tv@10982bd · GitHub

There are some connman changes in the last week which tweak the retry behaviour (it also impacts behaviour with WireGuard) and those changes may also resolve the issue. If it does fix I will get the connman folks to make a release so we can bump master/9.0.

Compile [LibreELEC.wiki]

^ this wiki guide tells you how to self-compile an LE image. It does not tell you how to create the extra code packages and compile those into the image. You have to figure out that part on your own because a step-by-step guide for your exact use-case does not exist.

You either need to self-build an LE image with a new "can-utils" package that compiles the source code and places the resulting binaries into the squashfs SYSTEM image file. Or you could package it as a Kodi add-on that can be installed from an add-on repo (but still needs the source code to be pre-compiled). I'm less sure about the "hardbyte-python" content. It may be enough to simply copy the files to /storage. As a general rule "maker" projects will be easier with Raspbian as LE distro packaging requires everything to be pre-built and embedded; there is (deliberately) no apt-get or ability to compile and install things to the (read-only and no compile tools) squashfs files.

I'm aware of only two legitimate IPTV services; both providing access to the local content of a specific country and a limited range of channels from that country. Every other IPTV service we've looked at (hundreds of services, all paid-for services) are pirate services. It is commercially possible to license the number of channels that most IPTV services contain (1500+) but to cover the real-world licensing costs this would require a user-fee of $90+/month not the typical $5/month that pirate operators charge.

I'd guess you originally installed OpenELEC which used a smaller boot partition size. The LE 7 > 8 update kept within the OE size limits so manual update via the GUI worked. The 8 > 9 update is larger and won't fit the OE partition size so the update will abort with a message saying the partition size is too small. The easiest way to solve that is following a simple "backup > reinstall > restore" sequence. From the description you've skipped the backup and simply reinstalled LE which overwrote the existing install (the USB is an installer, not an updater). While annoying, the positive is you won't be restoring back all the extra cruft that you inherited from the original OE install (loads of language add-ons that aren't needed etc.) and the accidental spring clean should have things running smoother than before.

It's possible to have multiple NIC's active in LE, e.g. Ethernet and WiFi at the same time and connman (the connection manager) has a preference for the default route (internet access) to be handled over Ethernet if both interfaces are active - traffic will route via the better connection. You should be able to simply access the GUI of installed add-on apps via either active interface as long as the apps are configured to listen on all local interfaces, i.e. do not have their comms bound to a single interface. If that's not the case you'll have to make a feature request to whoever created the apps; it wasn't LE team because we have always refused to provide those "dual-use" tools associated with piracy.

Please explain the network configuration in more detail. Which device is connected to which, and what is the function of the LE/HTPC box?

ping lrusak

30 seconds reading the content added/removed section of your IPTV provider's forum shows them (not surprisingly) to be a pirate IPTV service.

The current Slice image is just our standard Raspberry Pi image with an extra overlay loaded via config.txt for ethernet, sound and the LEDs, plus the Kodi service add-on.

Deinterlace is configurable under Open-GL (on x86 hardware) but not when using Open-GLES (on ARM chips). They are distinct and quite different ways to render video on-screen.

If things take 50 seconds to boot there's an issue somewhere. Sharing the systemd journal log after boot should show where the delay is; unless the issue is in u-boot before the kernel/system (which generate the boot log) run.

Please understand that RK development is "work in progress" and far from complete. Playback glitches should be expected.

You can mount the Gluster node via CIFS/SMB or NFS .. there is no support for their native client libs in LE or Kodi. You can either remote mount to a local folder using the systemd SMB/NFS .mount templates in /storage/.config/system.d or use the Kodi client capabilities as normal. IMHO unless you need to use/learn GlusterFS for some other purpose it's probably an unnecessary complication.