Posts by chewitt

Hi, feature requests for Kodi should be made via the Kodi forums.

There are some known caveats with the Amlogic mainline codebase right now, but the core OS is in good shape on the C2 and this morning I added support for the Odroid C4 to my work-in-progress branch. LE will continue to champion upstream Linux kernel development and the future of Linux and Amlogic (and Allwinner, Rockchip, Raspberry Pi, etc.) support within Kodi; for our own personal fun and amusement, to benefit the wider open source community, and never for profit. If you're familiar with the author Douglas Adams, everything to do with CE is ring-fenced with an "SEP field".

Run "journalctl | paste" about 1 min after boot and share the URL please. This will show more info about services starting and sequence.

Telegraf is a metrics/monitoring tool for IoT platforms. It has nothing to do with social media - I think you're conofusing with Telegram.

It's a known and unresolved bug, and all development on LE 9.0.2 is completed. Best to use LE 8.2.5.

Kodi master was bumped the other night and most add-ons in the repo need to be rebuilt and version bumped before they will work. That process is being done right now .. so sometime in the next 24h the repo should be up-to-date again.

Use /storage/.config/system.d/ .. as /storage is the only persistent area of the filesystem, everything else is created on boot.

It's been tested with a proper HDMI analyser and other bench equipment - at 4K resolutions the clocks are unstable and it will not lock onto HDMI 2.0 frequencies correctly so you have a bunch of display problems that will not be solveable in software. People can always revert the change to experiment, but S805X was never meant to be a 4K part so I'm not surprised it's out of spec.

Mali = GPU, used for rendering GLES content on screen (e.g. Kodi). It has nothing to do with hardware video decoding.

LE Settings > Connections > Browse the list, you should see networks listed twice, once with wlan0 and again with wlan1. Select the wlan1 connection and 'connect' the connection.

I'll talk to the maintainers about making the change, as it was originally raised for a reason.

btw, see drm/meson: add mode selection limits against specific SoC revisions - Patchwork for the first attempt at keeping S805X devices to 1080p. It looks like the patch will take some revisions get merged, but it will come.

LE is focussed on being an awesome media playback OS for Kodi and we have no ambition to become a general purpose distro that people can use for webcam chats with their family and similar - Covid or no Covid. As a result there is an intentional lack of webcam drivers in the OS, and no plan to change that an add bloat that overall nobody uses (aka the death of a thousand cuts). It's open source though, so if you want to experiement on your own, that's fine with us. You already figured out the easiest way to add a driver. If you wanted to bundle them as an add-on, have a look at how the DVB driver add-ons are handled - lots of prior art in the build-system.

Quote from buzzmarshall

So that kinda had me wondering what direction was better to look into "stateful or the newer stateless" and didn't want to go in a direction that was opposite to where everyone here is working towards.

Hardware IP is either stateless or stateful .. it's not a choice. Amlogic is stateful.

Kodi v19 is still in a pre-Alpha state, and that suits us just fine since there's still a ton of plumbing that we'd like to do for GBM/V4L2 support on ARM devices. So there will be an LE10, but not anytime soon, and we're not in a rush. The K19 add-on Python3 migration situation will also ensure lots of people will remain on K18 for a while yet anyway.

I've no idea which image Hummingboard might require, but LE10 pre-Alpha images for iMX6 are here: Index of / .. best to test on a clean SD card as iMX6 things are a little experimental and unmaintained.

The original Amlogic vdec work last year was done before a firm API was agreed and documented for stateful decoders, and the current stateful V4L2 code path in ffmpeg is based on that work. Since then the API was confirmed, and most of the vdec code has been reworked for it (HEVC is the main remaining one - it's also the most complex so has been deliberately left until last). Now ffmpeg needs to have the matching userspace work to align a few things around the confirmed specs. There are a bunch of things that need tweaking, but main thing that doesn't work right now is flushing/draining so we see hangs with seeking and when you reach the end of file (end of playback). Raspberry Pi needs the same/similar changes; RPi0-4 use the same stateful path for H264 and some other decoders in the original RPi IP, while H265 which is new IP added for RPi4 is stateless and uses the same code path Allwinner/Rockchip use (which is already in good shape). There are a couple of people who can do the work, but it's taking an eternity for other items to be cleared from their to-do list (mostly HDR related) so that fixing this is the top item.

frankviana 8726MX devices like the WeTek Play(1) aka WeTek OpenELEC box are Meson 6, not Meson 8. There is little mainline kernel support for that hardware generation and nobody I know of is working on mainline kernel support. I do not expect this to change.

Bubba2017 the above videos were filmed using an Odroid C1 (S805) and it will be a while before we make any attempt at public images for Meson 8. You can also expect issues with "M8 boxes" because there were probably 30+ different Chinese manufacturers simultaneously producing identical labelled boxes with slightly different hardware inside. Most of the hardware differences aren't a problem, but not all, so they will always be a bit of a lottery to support. I would expect any future official support/images for S802/S805/S812 to focus on a limited set of devices with public sources where we can go check what their legacy kernel has implemented.

Someone fat-fingered a filename. It has been corrected.