That depends on your definition of perfectly. Our official view is that it's a hack to be discouraged. It is not perfect.
Posts by chewitt
-
-
most add-ons store metadata in /storage/.kodi/userdata/addon_data/ so look there
-
-
Everything is possible but there is no interest in adding this or other drive crypto things to official releases; largely because if we add one we'll be asked to add others and that bloats our codebase with complex niche features that very few people will ever use. It's the type of things that should be handled via an add-on in our add-on repo that the community maintains.
-
Unless your network is dysfunctional SMB is perfectly fine for sharing.
-
Add "tty" or "debugging" to kernel boot params in extlinux.conf (in the first partition on the boot disk) and a console will be available on CTRL+ALT+F3. The first just gives the console. The second also puts various subsystems into extra (and persistent) logging mode; as well as having the console.
-
-
There's a paste function in LE 8.0 settings add-on that sends logs to sprunge.us and shows the URL on-screen, but that doesn't address the OP's requirement of sending to a syslog server.
-
You can install the rsyslog add-on from the LE add-on repo.
-
Your log shows piracy add-ons installed so support stops here. You'll probably find removing them solves the problem - we see regular issues with pirate crapware accessing the DB at startup to self-enable, install more crap, and deliberately break 'competing' add-ons.
-
RPi3 defaults to a safe "global" wireless regulatory domain, but this only sees channels 1-11 and may not be fully compatible with the radio properties of some access points that are using a local-country regdomain. The above
sets the regdomain for Germany (DE) and other locations generally follow the normal ISO country codes; GB, RU, CN, US, etc.
-
Have a look at MusicBrainz 'Pickard' .. it's much (much) more than a tag editor, but if you want to cure a whole bunch of other tagging related things that you're probably unaware of in your library and ensure your media scrapes correctly it's the best option.
-
It's something we already do in Generic/x86_64 with Chromium. The main use-case we've seen is access to services like Netflix or Amazon which also need flash or widevine support. It's probably not too hard to create/package netsurf as an add-on, but would it support those services?
-
In Kodi Jarvis favourites is a buried item with a star shortcut on the Kodi home screen. In Krypton favourites has been promoted to a top-level item on the home screen (if you have it exposed in skin settings) so there is no need for the star shortcut. In other skins the decision to show anything is up to the skin author.
-
add "dtoverlay=pi3-disable-wifi" to /flash/config.txt and reboot
-
Time to add SHA256 checksums in our build system. Who will start on that (I have free time)?I think it's time we did this. Let's chat.
-
Did you migrate/restore anything (i.e. config) from the WP1 install? .. I'm using a WP2 with the stock remote as my current 'daily driver' and there's no repeat issues in the default image.
-
At this stage it's too early to say what the future holds for 32-bit Amlogic devices. Kodi needs to clean-up Linux support similar to how the Krypton move to "mediacodec" simplified Android support. In the long term Kodi wants a V4L2 based Linux video architecture, and that almost certainly requires Linux platforms like Amlogic (and Raspberry Pi) to be running a current/mainline Linux kernel with V4L2 video drivers. Older 32-bit S802/805/S812 devices are stuck on an ancient 3.10 kernel that falls wildly short of that requirement. If code clean-up progresses quickly it is quite possible that a 64-bit Amlogic device will be required for Kodi v18 support on Linux.