Posts by chewitt

/usr/share/kodi/addons/service.libreelec.settings/resources/lib/modules/updates.pyc

Your next two challenges being:

a) This file is inside the read-only SYSTEM file that's decompressed to create a virtual filesystem on boot.

b) This is (pre)compiled Python code, so it's a binary not an editable text file.

The issue stems from https://github.com/dtechsrv/Libre…05/options#L162 and similar config for all the other Amlogic legacy build devices dtech is supporting. It needs to be changed to HTTPS in the buildsystem and then the image(s) recompiled and released to include that change. I'm not sure it's worth the effort just to remove some log noise though.

Shielding probably isn't the issue, but mechanical issues seem to be common once people add connectors and extenders. At the end of the day ..

Quote from forrester

Why shouldn't it be possible for Libreelec to do the same for the proxy settings?

It's not impossible. It's just unlikely to be implemented because, a) few people use/require local proxies and you're probably the 2nd or 3rd person that I can recall wanting to use them in the last decade, b) it would require Kodi patching and we try to minimise that, c) there's a simple workaround (as you have now implemented).

Errors in log files do not always mean something bad. LE/Kodi does not support HDCP so the DRM display pipeline does not support SecurePath, so that fails and widevine will not be able to show 4K content. However, widevine will then fall-back to a non-secure path with limitations (1080p max) and show something (which it does). TL/DR: Ignore the misdirection.

Quote from spigui

regarding hardware acceleration, with the original Tv Box´´´´ s Android 4.4.2 it works perfectly with the app Airscreen, it plays perfectly at 1080p x265 from UMS on a PC through WIFI 2.4. Maybe this information helps to find a solution.

The upstream codec drivers (in the staging area of the kernel) are incomplete and do not support Meson8 hardware. Knowing it works on a prehistoric vendor kernel from 2010/11 doesn't help with that.

Quote from spigui

it would be interesting if the Chromecast could be ported to the TV Box. I have the first one from 2013 and it still works perfectly with all the streaming apps. Is it possible to do that?

Google provides sources for all the open-source software they use in their Chromecast devices. However, and very intentionally, they provide sources without git history so you cannot easily see what they changed, and they don't provide sources for any of their own-code bits (which remain closed-source). There are also Amlogic kernel sources for older boxes and you can grab the latest AndroidTV or AOSP sources (which are public) so could in-theory create a newer Android release, but mating them into something that boots, runs, and is reliable, will required deep technical skills and several thousand man-hours of effort. Good luck

The correct solution is setting the TV to 'auto-scan' instead of overscanning, but if that doesn't work Kodi has a manual calibration function. Note that manual calibration needs to be repeated for each resolution/refresh combination that you whitelisted (or each combo where the TV shows the problem) by setting the desktop resolution to that combo and then calibrating. Again, the better option is using auto-scan.

It's working here on an iPhone 14 (17.6.1) using Librespot and normal Airplay streaming. I'm technically using an LE13 image and an RPi5, but the Kodi version is from before the bump to Kodi piers (i.e., the same Kodi version as LE12 images), the Liprespot add-ons are essentially identical, and RPi4 vs RPi5 makes no functional difference. NB: Airplay streaming generally works better, there's less lag on playback, but I assume that's not an option if using an Android phone.

Nothing in the logs (as expected). Since Intel drivers are involved (and them having such a wonderful reputation) take a backup and bump to the latest LE13 nightly which is now running Linux 6.10 (so newer Intel drivers). I'm grabbing at straws a little, but there's logic to the request.

Quote from wyup

How does the Android running Chromecast 4k do compare to LE on RPI4B for video hardware acceleration or graphical UI?

Does Android use OpenGL or Vulkan for this?

The Chromecast has an Amlogic S905Y3 chip with Mali G31 GPU inside and supports OpenGLES. It's a faster chip than the Broadcom SoC in the RPi4, and the OS runs from internal eMMC storage, but Android has a much greater general OS overhead so I usually find the Kodi GUI runs "about the same" on most Android devices with my (large) media collection as it does on an RPi4B's inferior but less loaded hardware.

Hardware Video Acceleration is something different. RPi4B supports only H264 (to 1080p) and HEVC (to 4K) whereas the Chromecast supports a much wider range of codecs. That said, most of the extra codecs Chromecast supports are legacy ones and the RPi4B can software decode the legacy media using them. The main real-world difference will be VP9 media support.

Note that RPi5 significantly outperforms RPi4.

Share a full debug log file .. it will contain more info on your setup.

The bug I am referring to in that thread is this one https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10199

I've no idea what the issue you're seeing is, but I'd ask that you try updating to a current Generic (non-Legacy) LE12 nightly to see if any of the changes pending for 12.0.1 make a difference?

Quote from kurai

Only major pain in the butt I really encountered was Windows' habit of assuming it's the only OS on the disk

Yup, Windows does that. What to do

The GPLv2 Linux kenel is considered to be pure code from a license perspective, so loading an external vendor module that often has no license or some proprietary license "taints" the kernel's purity. In short, the messages are harmless.

No RPi board has hardware support for VP9 media and RPi3 doesn't have the CPU grunt for software decoding. You need to use H264 content (which can be decoded) or use different hardware. RPi4 can handle 1080p and RPi5 has the oomph to handle most 4K30 VP9 media (but not 4K60).

Updating to LE12 won't solve anything.

video=HDMI-A-1:1280x720M@60

Older "HD Ready" TVs often support 1080i resolutions not 1080p so you might need to force 720p output by adding that ^ to the boot params in cmdline.txt (on the same line). Also try different cables on different TV ports.

Quote from forrester

why isn't Libreelec/connman using the Proxy-config from Kodi for these checks?

Proxying in Linux is always application specific so Kodi proxy configuration is for Kodi and is not shared to other applications. You can also set a proxy in ConnMan (per connection) but I have a hunch the initial requests for ipv4/ipv6.connman.org are intentionally not routed to a configured proxy as those checks are performed before the network is declared up (and thus the connection that proxy config is associated with is not yet established).

I think nightlies need me to finish working on a Linux 6.10 kernel bump and send a pull-request, but that might take a while as work and life have a higher priority at the moment. Hopefully before the end of August, insh'allah.