We will solve the problem by removing (or not adding) support for all the install-to-internal stuff in official releases. It adds lots of complexity for marginal gain and results in too many support posts. Some community developers will persist with the idea, but eventually they will probably burn out from all the effort and will realise we made the correct choice.
Posts by chewitt
-
-
Different Amlogic devices do different things based on hardware, the whims of source media, and the collection of patches and hacks applied by different community build creators. However, until Kodi actually has designed-in support for HDR there is basically no point in trying to answer the question.
-
It is possible to create a udev rule that runs "mount -o remount,ro /path/to/mount-point" but this will prevent data from being written. It will not stop something in the OS from reading the drive. NB: There is nothing in LE that copies add-ons automatically from an SD card or USB drive. Your description makes no sense.
-
There is no "regardless of the log" when banned repos etc. are present. Support stops until clean logs are provided. It is not debatable.
-
'/full/path/to/binary' not just 'binary'
-
ISTR there were H.264 decoding artefact issues in early S905 chips (when using a specific codec) because at the time the WeTek S905 devices were a little unique in using a later chip version that didn't have the problem .. but it's so long ago I forget what the technical details were. It was a specific profile or something. So, it may be possible.
-
Please (re)test with a current Leia milhouse release. Lots of 4k support related things were changed since 8.2 and even if we could pinpoint the issue in an 8.2 release the fix would be going into 9.0 anyway.
-
Oh, that doesn't sound too promising... I was not aware that amlogic is that unsupportive... Thanks for explaining.
Amlogic aren't at the front of the charge towards V4L2 but they aren't last in the race either and I wouldn't call them unsupportive. There is ongoing effort from them, but as is often the case, their "open source" development is done behind closed doors and even when you have direct contact with Engineering staff (as we do) it can be difficult to track where things are and things often just appear without announcement.
-
There will be a boot time improvement (to your always on device) using the internal storage, but the claimed benefit of faster I/O performance when browsing libraries etc. is negated when you use an SD card for storage because that's where Kodi stores it's DBs and thumbnail images and all the read/write activity happens. If you're not going to see the main benefit you might as well avoid all the complexity of trying to make a split setup and have an easy life. So, just run LE from the SD card.
-
The install.sh script references in the shop URL that you shared suggest it requires "out of tree" driver modules to be installed, and the only mention of "Aoide" that I can find in the Raspberry Pi kernel is Add Aoide DAC II Driver by howardqiao · Pull Request #1559 · raspberrypi/linux · GitHub which was not merged due to code licensing issues. It can probably be made to work with a custom image, but we don't provide custom images
-
Login to the Pi (server) and learn how to use the 'sed' command to bulk rename files. Job done.
-
The / root partition is just a virtual filesystem comprised of the contents of the kernel.img and SYSTEM files; which you already have (or they are in /flash, or in the install folder within the build.blah components of build-system) so there's no need to go around dumping stuff.
-
The (final) answer is no, because this would require a USB port to remain in a powered state while the box is off, and manufacturers of cheap Amlogic boxes do not invest in the power circuitry that's required to make that happen.
-
I'm not sure why people expect pre-Alpha state software to be error free.
-
Create a new SD card, insert the card and power on. Now press the power button on the remote during boot and it will alternate between booting from the SD card and the internal eMMC (it's not NAND, despite the on-screen message). The boot device selection persists until you change it.
To migrate data; make a backup and move it off box, then restore it to the SD card after initial setup has been completed.
-
Is there any guide which lists what is the minimum featureset from the Linux kernel that is needed for LibreElec to work?
The answer would be device and kernel specific (as is the nature of kernels) so the best source of documentation is our GitHub repo. We are not as minimal as we started out, but we're still a lightweight distro.
-
Some of the devs have N1 boards now, so support of some kind will be worked into the general RK recipe.
-
We prefer not to get wallpapered with forum spam, which is why the word is in a filter list. Just use HID, we know what it stands for and it requires less typing.
