https://chewitt.libreelec.tv/testing/ has some experimental K19 and K20 images for C2. There are bugs, but H264/1080p works well enough and if you avoid fiddling with Kodi audio settings you shouldn't trip the main unresolved audio bug too often. The C2 image boots and runs Kodi 19 at least. I don't plan on maintaining the Matrix images as I've moved the codebase to (pre-Alpha) Nexus now. NB: You cannot update with these images as the boot process is completely different to older releases, so you must clean install.
Posts by chewitt
-
-
It's probably easiest to make a new SD cards and start over. The default 32MB /storage partition should be resized to 100% on first boot. For some unknown reason that didn't happen and unless you are familiar with Linux CLI commands and have another Linux VM around to mount the card and fix the partitions with, it's not something that's simple to resolve (cannot be done from the booted card). As a rule, the 2% of LE users who know how to solve that stuff just fix it instead of asking Qs in forums, so I assume you're iin the other 98%.
-
MeCool BB2 Pro S912
Use the box image and experiment with the MeCool KIII Pro dtb, it's probably identical specs.
-
The main challenge with u-boot on Meson8 boards is that half the stuff you think you know hasn't been implemented yet on the prehistoric version of u-boot that's being used .. it's an archeological exercise
LE's KERNEL file contains an initramfs so we don't use a separate initrd file, and we avoid the entire topic of coexistence with other distros by simply not supporting it. As a rule it's not a big requirement on ARM devices among our userbase so we avoid the heartache.
wrxtasy released images for C1 for a while and I can see active installs in our stats server, so there is prior-art in his GitHub repo. There is also ongoing effort from dtech to adapt his LE 9.2.x image.
There is also a slow-burning effort to run mainline kernels on Meson8 boards. The amlogic-mx branch in my LE repo builds images but we did not figure out the u-boot bootscripts needed yet, so we are interested in what you figure out. Keep sharing infos.
-
Current K20 images from my webshare have no hardware decode (which is why H264/HEVC and seeking etc. work great). All 1080p media will probably work fine on GXM and newer boxes due to better CPUs but GXBB/GXL struggle a bit unless the bitrates are low. I'm attempting to use the same ffmpeg sources as Raspberry Pi due to the huge time/effort that the Pi devs have put into ffmpeg/v4l2_m2m, but the current sources have become a bit too Pi flavoured and we didn't figure out how to add quirks for Amlogic yet. There is also no progress with "the noise" on GXBB/GXL/GXM boxes so beware of Kodi audio setting changes, as that's an easy way to trip them (if making changes, keep the TV or AVR volume super low, and if you trip it, toggling settings will fix it).
The purple line needs something in the HDMI/DRM code to be poked, a register is off somewhere on not being set. I've no idea how to do that so can't really investigate - I've flagged it to the upstream maintainers though.
NB: I have no real plans to maintain K19 images going forwards so 10.0.x files will probably be deleted in the next week. I'll fork the branch on my GitHub LE repo in case anyone needs to build from them.
-
1. The kernel expects to find SYSTEM in the same partition as the KERNEL (or kernel.img) file. I'm not aware of a way to pass SYSTEM as a param but since I can't think of any reason to put it anywhere other than the boot partition I'm not sure it would be needed.
2. "printenv" will show the u-boot environment via UART cable on a working board. If no UART you'll need to dive into the ancient Hardkernel sources. I wouldn't attempt to mess around with the default boot flow that's present in existing C1 images. It works, and the code behind it is crappy so by fiddling with it (from experience) you will only break something, and fixes bring new exiting bugs to play with.
3. I'm not really sure what the question is. Leave the boot flow alone.
-
-
You can play an audio file and start browsing the list, but it's not an automated thing. You would need to file a feature request in Kodi forums to see what response it gets from core devs. Sounds horrible to me
-
80Mo is 80MB or 80Kb? .. 80MB would be refused in our main images, but 80Kb would be no issue.
-
-
So the question is: Why is the route to the IPv6 default gateway not automatically added like it is the case for the IPv4 default gateway?
Two reasons, which are self-explanatory:
a) Nobody on LE staff has access to an IPv6 network so we are never testing it
b) None of the ConnMan maintainers have regular access to an IPv6 network, so they are testing infrequently and not seriously
User contributions to IPv6 debugging and fixes are very welcome
-
63 characters is the upper limit allowed for a passphrase in standards, although some routers allow 64 characters. ConnMan enforces the 63 limit. IMHO passwords that long are pointless. The exploits for WiFi networks are always about a protocol vulnerability or something in the iimplementation of a specific chip (at silicon level) or a software component in the wireless stack. Unless it's a WEP network (which is easy) no attacker is going to waste their time trying to brute-force the credential, so anything between 12-20 characters is enough.
Correct Horse Battery Staple | Generate Secure Memorable Passwords
-
There is an open pull-request to restore eSpeak (now eSpeak-NG) in https://github.com/LibreELEC/LibreELEC.tv/pull/5786
Can you explain the purpose for libttspico-utils? - I mean, clearly it does TTS, but how is it used and by what applications?. Apologies if these are dumb questions but current staff don't have much exposure to users with accessibility needs.
-
You get bonus credit if you submit the fix upstream to the add-on repo on GitHub
Here I think? https://github.com/melmorabity/plugin.video.francetv/
-
I suspect this has been fixed in the LE10 codebase. I'm frequently setting passwords via connmanctl and have never seen the behaviour of it prompting in the GUI when I try to configure something from the console.
-
The -wetek-play2.img.gz file is designed to boot the box using mainline u-boot (on SD, with emmc wiped). Use the "box" image and edit the dtb name (to the full name of the play2 dtb) in uEnv.ini if using factory boot firnware. NB: Renaming the KERNEL file guarantees the box will not be able to find it and boot.
-
1. Read RE: Cannot Install/Update Addons
2. You miss that anything found in that folder is experimental and never guaranteed to work or boot.
-
Wonder why libreelec doesn't have some utility to config this through interface..
because every monitor or TV panel is different so it would be fiddly as arse to script (perhaps more than doing it manually) and the number of nVidia users has been declining for years so the need to do it has also reduced.
