Posts by chewitt

Currently not working but being actively investigated. No timeline on when something public might be ready.

milhouse will pick that commit into his builds for some testing and as long as no issues are observed we'll add it into an update while reminding the Pi Foundation folks that the issue is still outstanding. The patch will probably miss LE 9.0.1 (which is due imminently) but land in LE 9.0.2. Keep using the modified test image for now; it's better to have a system that works with a few more unresolved Kodi bug than something with fewer bugs that doesn't work.

Not possible until HDR support gets added to the Linux kernel. It is being actively worked on (by Intel engineers).

Yes pls.

Ahh.. would be good to test then. Can you spin an image for the user?

Raspberry Pi 3 built-in WiFi SSH NTP Problem · Issue #1519 · raspberrypi/linux · GitHub

links to Sets the BCDC priority to constant 0 · raspberrypi/linux@983cf7a · GitHub which from the age of commits i'd expect to be included with our kernel, but it's not something I can test (am travelling at the moment).

I've pinged some of the pi folks, but traffic to that GH ticket might be a good idea too

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

If it's a BT device? it can be un-paired in LE settings.

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).

05:13:36.005 T:1567286128   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAME:PASSWORD@SYNOLOGY/root/Videos/Movies/The%20Fly%20(1986)'
unix_err:'16' error : 'Invalid argument'

^ are you connecting with a valid username/password?

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..