Kodi backups are always hardware dependent, but Pi 2B, 3B and 3B+ are hardware compatible (using the same OS image) so whatever the issue is, that's not the problem. The important thing to remember is that restoring data between devices is simply about stopping Kodi (systemctl stop kodi) then moving a small number of key files back to the right places, then starting Kodi again (systemctl start kodi). The tar file can be unpacked and you can move files back manually if required.
Posts by chewitt
-
-
-
The onboard wifi on a 3B should support AP mode, although normal wireless performance isn't the best so AP wireless performance is probably similar and you might need an external USB dongle. The challenge there is that not all drivers support AP mode and there's really no way to tell without trying them. If you can find a USB wifi dongle that uses the ath9k driver; it's one of the best/better drivers.
Raspbian will be much the same. It's all about about hardware and drivers and both distro's are broadly equal on those.
-
LE uses connman which does send the hostname in the DHCP request. However, if the positively ancient Samba support in current ASUS routers is representative of their router codebase it's more likely that the router (even if it's a shiny new model) has some ancient DHCP server binary that only supports older windows-only methods of name registration.
NB: The hostname should be changed via the LE settings app. This writes the file to oe_settings.xml which is read and propagated to the .cache and other locations on startup. You should not modify the file directly.
-
Code
kodi-send --host=127.0.0.1 -a "UpdateLibrary(video)"read this for more commands: List of built-in functions - Official Kodi Wiki
-
LibreELEC has never released official images for Allwinner hardware so we have never published addons for those devices to our repo. The H3 image you've installed probably originates from an Italian community builder who adapted the older OE images by jernej to our codebase. It's his responsibility to provide addons for his images.
NB: In the near future there will be official releases and those will come with official addons. Fun times ahead
-
No Linux kernel has full 4k HDR support. The current 3.14 kernel predates HDR and has been hacked by Amlogic and various community groups to have some resemblance of HDR support, but the test cases it was coded for are limited and bits are missing. Folks over at CE lack the kernel development skills to architect and solve those problems which is why they've flip-flopped between kszaq, osmc and our older kernel in the hope they find something that works. We (LE) are not wasting our time on that quest because we know none of them work properly, and the 3.14 kernel is not really worth the effort. The situation on mainline kernels is also incomplete as HDR and other HDMI 2.0 elements are still being coded. The good (long-term) thing is that those feature are being actively worked upon, and unlike ye olde 3.14 kernel, the code is written properly.
-
Start with a current Milhouse development build as this has a much newer Linux kernel and the mmc driver initialisation problem (-110 is just a generic error code, it's not so helpful) may have been resolved in more recent kernels.
-
There is a VNC server addon for LE allowing you to connect from PC to HTPC, but nothing exists that allows connecting from HTPC to PC.
-
What hardware do you have?
-
is there any reason why these quirks are not already upstream and included in kernel sources? - e.g. patches being submitted and rejected by kernel maintainers?
-
There are niche but known issues in the Pi firmware used in 8.2.5 but current milhouse releases will have newer firmware that resolves some of them. Update and retest, then if issues are still present, post in the milhouse support thread in the Kodi forum to ensure the issues are flagged to Pi foundation staff for further diagnosis.
-
The bootlin branches are now some way behind current LE and current Kodi so additional work is needed over the next few weeks to adapt some of the changes so there's a common approach over other SoC types. Then we can get things merged into Kodi and look into some of the other distro packaging challenges. Allwinner "support" is still some way off, but it's been really positive to see things progress and our long-term vision for a unified zero-copy video pipeline taking shape.
-
No ETA. The amount of remaining work to switch GXBB/GXL hardware up to mainline with an HDMI 1.4 featureset is small, but also dependent upon a limited number of developers who have a huge paid-job workload, so pro-bono work progress is frustratingly slow. There is still no clear mainline path for GXL devices for various currently insurmountable technical reasons (drivers, etc.)
-
In the last couple of weeks the SFTP feature was removed from the main Kodi codebase. It can now be (re)installed as a binary add-on (vfs.sftp) but LE hasn't added it to our build-system so it's not in our repo. That will probably happen at some point, but I wouldn't promise when.
-
I already did.
-
I haven't been able to get my Digi+ working in Openelec after following your instructions, any ideas or tips?
If you install OpenELEC (a long-dead project) your problem is not our problem. If you install the BerryBoot "LibreELEC" image you are not running proper LibreELEC and your problem is not our problem. Install LibreELEC natively (so the running kernel is our kernel) and we'll provide support.
-
The scrolling text is probably kernel log output so the device is trying to boot something, but that's not a supported device so whatever image you found will have an incorrect device tree, which leads to random problems. Device tree files are device and kernel specific.
