SMB access has nothing to do with skins. It has everything to do with the Kodi SMB client defaulting to SMB2 which will not be compatible with shares that only use SMB1 (e.g. a USB disk plugged into a router that runs an ancient version of samba) .. but this is very easily fixed by setting the Kodi SMB client to min/max SMB1 in the Kodi settings GUI and then rebooting.
Posts by chewitt
-
-
Kodi supports 2160p without any issues. It doesn't support HDR. They are related (HDR is only used on 2160p media) but different things. HDR support is "work in progress" and may (or may not) be in K19 as the schedule for K19 was changed to bring forwards the introduction of Python3 changes to the Kodi ecosystem.
-
Acestream engine plugin worked perfectly with leia based system, like nightly build from 12.10.
Users of piracy plugins and tools are not welcome in this forum.
-
You'll need to recompile the LE image with the changes applied as a git patch to the original sources, or you use another distro that supports your hardware which has more conventional OS packaging that allows files in /usr/share to be edited.
-
No change.
-
We removed all support for the Amlogic vendor kernel used in older releases so an LE 9.2 release is not possible. Meanwhile; here's Linux 5.5-rc3 kernel and Kodi v19 (pre-alpha) running on a WeTek Hub http://ix.io/25bl and WP2 http://ix.io/25gh. Recent changes to the hardware decode driver require some rework to ffmpeg and Kodi before I can push an update to LE master branch and make nightly builds usable again. I'm also exploring what's needed for mainline u-boot to run on those devices.
-
You might need to allocate more GPU memory in config.txt?
-
You need to clone the skin files to /storage/.kodi/addons/<skin> and change the skin name (to avoid namespace clashes) and then make changes to the (now writeable) skin files. Then stop/restart Kodi and select your modified skin name.
-
If/when Kodi supports multi-threaded SW decoding .. LE will support multi-threaded SW decoding. Nag upstream.
-
Your non-debug Kodi log doesn't show much, but since the media is 2160p ~ if it's an HDR file Kodi does not currently support HDR so the colours will appear muted and washed out. Solution is to see if the original disc has a non-HDR version on the disk and re-rip.
-
I've asked the connman devs for a version bump. Once that's released and tested in Milhouse nightlies I'll resubmit a PR. Now the kernel driver has gone upstream (for Linux 5.6) the packaging is a little easier.
-
I made the decision to stop patching audio card names in the kernel so we hoard fewer patches. This means the AMLGX and AMLG12 card names will be replaced with more random names (whatever is in the device-tree file). Anyway.. I'm still in the middle of fiddling with audio things in the Linux 5.5 kernel so some things work, some don't work. I'll have a look at VIM3 in the next couple of days..
-
"curl icanhazip.com" usually works .. "curl ipinfo.io" also works for me
-
If you can tell us what the firmware name is? .. we can investigate why/where it went missing.
-
"systemctl status kodi.service" ???
-
sinisab89 I binned your last two posts because:
a) If you want to keep discussing CE please use their forum.
b) Users of piracy add-ons like Elementum will not recieve support in this forum.
-
^ edit "PreferredTechnologies = ethernet,wifi,cellular" to be "PreferredTechnologies = wifi,ethernet,cellular" and save/reboot. This ensures connman will allow a persistent default route over WiFi, else when you connect Ethernet connman prefers it and overwrites default routes. You can also use the console "connmanctl" utility over SSH to set the Ethernet interface properties (static address, etc.) but I suspect the GUi will behave once you've changed the technology preference.
-
"If it works, don't fix it"