File locations discussed on the Kodi wiki map to:
/storage/.kodi/userdata/server.key
/storage/.kodi/userdata/server.pem
I've no idea if anything else is needed.. but we haven't done anything to disable the feature.
File locations discussed on the Kodi wiki map to:
/storage/.kodi/userdata/server.key
/storage/.kodi/userdata/server.pem
I've no idea if anything else is needed.. but we haven't done anything to disable the feature.
Currently VIM1 only. VIM2 support will come with the switch to modern kernels (soon, but not this week).
As I said before, I have no knowledge on how the Windows stuff works.
Looks like the device-tree was merged for Linux 5.1 (see [v5,1/5] arm64: dts: rockchip: Add DT for NanoPC-T4 - Patchwork) so it should be picked up in the mainline rebase work at some point. If someone submits a valid Linux 4.4 device-tree to @kwiboo's rockchip kernel repo it can probably find it's way into the ongoing alpha releases for RK hardware. Otherwise I have nothing to add .. I'm not that involved in the RK work.
NFS is marginally more efficient but not natively supported on Windows. I've used SMB for years without issues .. if it has problems the issue is configuration or inadequate bandwidth.
a) Poking /sys will work if you figure out the right command (not very helpful advice I know)
b) Multi-channel audio is in the to-do list, but not the highest priority at the moment
c) Not at the moment .. the V4L2/GBM code will need to evolve support for VNC
d) Most likely the TVH add-on currently in the repo doesn't match the minimum version for the Kodi nightly; once 9.0.1 is out this should get resolved
1. No
2. It's possible but normally impossible to pin down to a specific thing. SMB2/3 will give faster throughput (an incentive to update)
3. Our testing showed a positive improvement. All testing is subjective to environments.. YMMV.
4. Honestly no idea how Windows handles version negotiation. Kodi on Windows uses the native SMB capabilities of the OS whereas on other OS (Linux/Android/macOS etc.) we use smbclient (part of Samba).
We cannot use Python3 because Kodi has a hard dependency on Python2. Team Kodi will switch to Python3 for v19 to ensure the change happens before the end of Python2 support in 2020.
Run "journalctl -b 0 --no-pager | paste" to share the systemd journal .. the Kodi log won't show anything about the OS or the time period before Kodi starts which is where any delays/issues are.
Not supported, and no plans to support. Sorry..
LibreELEC Downloads – LibreELEC <= has .img files that can be restored to SD card, the .tar (update) file cannot be used for installs. If you want to install via noobs; just boot via noobs lite and LE should be one of the available install options.
You can use a bind mount (in autostart.sh) to make it appear in /usr/bin/rsync
^ currently on the 16th revision of the patch series, so probably a few revisions to go yet ![]()
Definitely not going to return.
Go read about "WannaCry" ..