There is no need to unpack the .tar update file yourself as we do it automatically (since ~4 years).
Posts by chewitt
-
-
-
If you are using 8.1.2 removing the "# samba.conf v4 (do not remove)" text will result in the Samba startup script thinking it's an older v3 config that is not compatible and thus we skip it at startup. Hence it has "do not remove" written. Do not change the [global] section, just append the root config to the end of the file copying the existing format.
-
Support for 3D features depends on the hardware decoding interface. Pi hardware is well supported. Everything else.. not as well. I'd expect Amlogic to be at the bottom of the list for great support and these days (with the 3D fad passing) I doubt that will improve.
-
All pi hardware devices are a BCM2835 device; newer devices have been given a higher model number but it's the same chip with a higher clock speed. On a normal Linux kernel they all show up in /proc/cpuinfo as the same chip and Kodi reflects this. We are doing nothing wrong and you are not missing out on anything. Very much a case of "Nothing to see here.. move along please"
-
^ as long as that exists there's really not much point wasting effort on creation of an LE add-on
-
-
Also make sure you're using a current version of PuTTY
-
Pre-alpha code is frequently full of bugs and stability issues. So, err.. no surprises here!
-
-
Lakaa is Lakka. I've never booted it so I cannot state whether it works exactly the same. In LE: create a swap partiion after installing and then create /storage/.config/swap.conf with the right content and it will be used "as a swap partition" .. no idea whether it also works as a hybernation partition; we don't support that function so you need to experiment. Content of swap.conf can be figured out looking at the URL that I posted.
-
Keep watching our GitHub repo. An inital PR with code for RK devices will be submitted soon. Once it appears you are welcome to self-build an image and experiment. If that isn't your thing (technically) you'll have to sit patiently and see where things go in the future (months not weeks).
-
You cannot control kernel time sequencing of mounts so symlinking things to /storage may (or may not) work and even if they happen to work now things may break randomly in the future. Just refrain from OCD and ignore /storage/movies etc. they are harmless!
-
The 8.0.2.1 release solely "fixes" the wireless driver to deal with a new internal board revision. Nothing was fixed for IR issues, and although there are IR changes in 8.2 releases the extender is simply a dumb cable that extends/moves the receiver.
-
Please do not cross post.
-
Delete the default 'sources' from Kodi configuration and just ignore the unused folders in /storage. It is not possible to prevent their re-creation on boot without making a custom image with changes, which is not worth the effort.
-
We are actively working on an implementation of The Update Framework; see The Update Framework (TUF) | Like the S in HTTPS, a plug-and-play library for securing a software updater
-
We have been working with Rockhip Linux developers for a while now and there is a roadmap towards future support for RK3328 devices. Based on the simple fact that this work is based upon recent mainline kernels and proper standards (not just the hacked-up junk kernels Amlogic has shipped in the past) RK images look quite promising.