If you'd like to submit the kernel defconfig change to our master branch it's no drama to add it to future Generic releases.
Posts by chewitt
-
-
The original SliceOS update function is based on noobs and points to files that probably don't exist anymore (as 5Ninjas are no longer around). I would clean install the current LE image (re-flash the eMMC storage) .. Kodi v15 (SliceOS) to Kodi v18.5 is a large jump.
-
-
You can just create the same rules on both clients as rsync (with the right comman) does action "sync" not a simple push of content from A > B.
-
The connman tethered AP feature "is what it is" unless someone submits code to connman to add features and we (LE staff) have no plans to start writing connman features. It's probably not impossible to add packages for host_apd and more fucntions, but we have no desire to be a router OS so there are no plans to do that either - but we're open source so you're welcome to experiment on your own. The practical solution to "I want a cheap wireless router" is to get a cheap (hardware) router. Or you can switch distro to something with package management that allows configurability. LE is by deliberate design a locked-down and fixed medicentre purpose (not router or general purpose) distro.
-
We have no plans to create add-ons for pCloud but you can probably find a Docker container that includes the client.
-
You can use rsync (in the network tools add-on) with SSH key authentication (to avoid passwords) to sync the thumbnail cache from client 1 (master) to client 2 (client).
-
Assuming this is Pi hardware you edit cmdline.txt which is on the FAT32 partition.
-
Google have done something which restricts API usage and breaks the add-on. These thing happen once in a while. There's probably more info in the add-on support thread in the Kodi forums.
-
LE bakes all compiled code into the SYSTEM image file which is read-only and there's no package management so it's not possible to change anything. The only way to change would be self-compiling with an older version. The better apprpoach would be reporting the niggly issues to the add-on devs via their support thread in the Kodi forums so the issues get fixed.
-
It needs CONFIG_AQTION=m enabling in the kernel defconfig. Ping milhouse
-
You can append ?mirrorlist to the URL of whatever file you're trying to download.
-
S812 has quite a bit more grunt than S905 but .. not much use without the HDMI driver. Fingers crossed..
-
Thankfully I'm not the only person working on mainline support
-
GT King and King Pro should both work as the hardware is almost identical .. although ealier versions of their Android firmware have u-boot versions that can be fussy with SD card or USB booting. The washed out screen colours are caused by the vendor u-boot setting HDMI properties that the latest kernel releases don't fully understand. The correct but slow fix is extending the DRM driver. The faster but more brutal fix is to replace vendor u-boot with mainline u-boot (which doesn't support the HDMI properties that aren't supported in the kernel .. thus sidesteps the issue). I have Beelink's u-boot sources if we need to go in that direction, but Oleg is also experimenting with another approach which might be more subtle
-
LE runs the current/latest connman release. I'd guess the reason IPv6 support upstream is much the same as ours .. until developers are forced to use IPv6 connections it remains largely uncharted territory. If you ping "wagi" in the #connman IRC channel on freenode he'll be happy to take constructive feedback on what's missing. He's familiar with LE .. we've collaborated on a number of things in recent years.
-
Correct. Kodi v19 release has been reshaped into an interim release to force/kick-start the Python3 transition and bigger-ticket items like HDR and GBM/V4L2 support will shift to Kodi v20 .. hopefully on something close to the original v19 schedule (not that Kodi ever does formal scheduling).
-
Amlogic's "Meson 8" platform (S802/805/812) shares a lot of IP with the GXBB (first generation S905) hardware so support in the mainline kernel is in reasonable shape (bootable and usable) apart from a lack of an HDMI driver which is fundamental for mediacentre use. One of the kernel maintainers Martin Blumenstingl continues to poke away at the Meson 8 codebase and (coincidentally) in the last week he got CVBS output working. As long as he continues his efforts I'm confident there will eventually be a Eureka! moment with HDMI that allows us to consider adding back support (and even if we don't do something official - for community images to exist) but until that happens LE 9.0 is the end of the line for those devices. Meson 6 (8726MX) support in the mainline kernel is almost non-existent and those devices are considered obsolete.