Next step is to use a current milhouse (Leia) release. If the issue is still present, then we start looking for where the bug is.
Posts by chewitt
-
-
-
It might be possible to support that SoC, but it's not mentioned in current Amlogic documentation and we have enough issues supporting the stuff that is, so I don't see if leaping onto our agenda.
-
You can block writing *to* the USB drive (using the command I posted before) but once the USB device has been mounted you cannot block reading or copying *from* the USB drive. LE has a single user, root, who can access anything.
-
This USB dongle has a Mediatek MT7610U chipset. There are only vendor provided drivers available (nothing in the mainline kernel) and their quality is best described as crap (and I'm being extremely polite about the code). Until Mediatek get their sh1t together and upstream a proper driver to the Linux kernel, or someone in the open source community does the work for them, we will not support it.
-
One ugly hack is to get things configured as you want, then shutdown Kodi from the console and copy /storage/.kodi/userdata/guisettings.xml to a location like /storage/.config and then use the /storage/.config/autostart.sh script (which doesn't exist unless you create it) to copy them back to /storage/.kodi/userdata on each startup. This forces known-good settings to be used instead of the probably corrupted settings that weren't saved correctly on shutdown.
-
add the pi3-disable-bt overlay to config.txt
-
Follow linux-lima and mesa-lima github commits and issues/PR comments not the very out of date website.
-
Enable/disable under the services menu. RPi3 has crap BT though, so it's best left disabled so you can use an external USB dongle.
-
I was under the impression that the whole point of alpha releases is to get some testing so at least the number of errors can be kept at a minimum.
Your statement is correct. However, there are no official v18 alpha releases available yet.
-
There are no plans to add Java to our images.
-
The default fonts should handle Spanish diacriticals. Check the subtitles show correctly in another player app like VLC. If they don't, the recordings didn't save the subs correctly. If they do .. no idea.
-
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.
-
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.