Our repo is intended for binary addons that are distro or hardware specific. I see no binary code in your add-on sources so unless there's some reason I'm not aware of the better place to submit it would be the Kodi addon repo where it can benefit all Kodi users vs. the smaller subset that run LibreELEC.
Posts by chewitt
-
-
LE is intended for dedicated HTPC installs so we do not support (and the installer will not allow) installations to a spare partition shared with other OS, it will only allow install to a complete drive. It's possible to manually work around that, and there are dual-boot threads in these forums if you go look for them. NB: As a general rule an RPi3B+ is a much better HTPC than any old laptop you might have.
-
If they are Bluetooth Low-Energy devices the current LE kernel doesn't support BLE and this PR (which was never merged) is required:
-
That's my point. The NUC is only a bit more expensive and does this, and also H.265 without any issue up to 4K. Even the Celeron.
I'm answering the original question asked. You're telling someone they need to spend $150+ on a new device to get Netflix with HDR support (which hasn't been asked for). Your point is irrelevant.
-
4.) You're welcome to install Skins, but if you install piracy "builds" you will receive no further support in this forum (read forum rules).
-
Go look at the commits on GitHub.
-
It's possible to play Netflix on an RPi3 (3B+ is better) but not more than 720p resolution as video is software decoded. It's best to mildly overclock the RPi to improve the CPU performance, and install a heatsink to help with cooling.
-
Grab the logs from the logfiles SMB share and upload them so we can see what errors (if any) are being thrown.
-
Nothing useful in that output, other than a hint that it was an addon. So, full debug log of Kodi startup to see how far it gets please.
-
The problem with cross-platform backup/restore is that Win/Mac/Linux/Android share ~90% of their configuration, but ~10% is platform specific and may cause Kodi to choke on things during startup. Kodi doesn't claim to support it; neither do we. The additional issue with Win > Linux is Windows\paths\are\like\this and Linux/paths/are/like/that, so all media in DB files has an invalid path. It's not technically impossible to correct things, but it's not particularly simple either (and we don't provide guides for things we don't support).
The LE backup function will capture any Docker containers installed via our addon repo. It won't capture anything stored elsewhere on /storage as the backup script only archives /storage/.kodi, /storage/.config and /storage/.cache. To backup/restore with our files, use our backup/restore function (in the settings addon). We don't test restore of our backup files with other Kodi addons so YMMV. At the end of the day LE backups are just a tar file, so doing things manually just requires you to run tar commands.
-
You can add a second USB device but Kodi will only be able to output audio from one of the two devices.
-
Microsoft wants everyone to use authenticated access to shares. There are at least 2000+ different combinations of Windows, Windows config options, and Samba versions in the wild so it's impossible for anyone to give a direct/straight answer to the "why did my stuff stop working?" question. The sooner everyone gets onboard with the new plan and starts using username/password access, the sooner everyone can get back to watching movies instead of trying to diagnose why their insecure guest or anon access (mostly) no longer works.
-
It's a Kodi problem, and it needs to be solved by Kodi developers not LE developers.
-
Clean install.
Connect the DVI monitor
SSH in and run:
cat /storage/.kodi/userdata/guisettings.xml | paste
cat /storage/.kodi/temp/kodi.log | paste
Shutdown
Connect the HDMI panel
Boot up
SSH in and run:
cat /storage/.kodi/userdata/guisettings.xml | paste
cat /storage/.kodi/temp/kodi.log | paste
Share the four URL's generated by the | paste command.
-
For upgrade RK3399 64Bit -> 32bit you need to create /storage/.update/.nocompat first to override the compatibility check at update.
You need to create the 'canupdate.sh' script that is used to validate the update in case of wrong arch, then this is not required.
-
No, because there are no Mali T820 blobs in the sources released so even if the sources are complete and bootable (which is doubtful given the woeful combined reputations of SinoVOIP and Realtek) we can't create an OpenGLES environment for Kodi to run in. It may be possible to run a software OpenGL environment via Xorg, but CPU performance on ARM boards normally isn't great and we will remove support for Xorg in LE 10.0 so even if it runs it's not a technical direction we would invest time into. It's also unlikely there would be support for GBM and V4L2 hardware decoding as those depend on kernel frameworks that don't exist in Linux 4.9 (only in recent kernels). The final nail in the coffin: LE would not invest resources in any platform where the SoC vendor makes no effort to upstream to the Linux kernel (while releasing hardware that uses it, which constitutes a GPL violation). If they can't be arsed to support Linux properly, we can't be arsed to support their hardware.
-
You can downgrade via the 'update' function in the settings addon, but Kodi will not automatically downgrade addons and config so you might see issues (some times you don't, sometimes you do). It's best to downgrade and then restore from backup (which you took, right?) so that everything is back to Krypton levels.
-
I have no intention of publishing development/test images anytime soon because I have no time to support anything at the moment. Once LE 9.0 has shipped I'll start to push changes into the amlogic branch of our main repo and some nightly builds can be organised.
