touch /storage/.update/.nocompat
wget https://releases.libreelec.tv/LibreELEC-RPi2.arm-9.2.8.tar -O /storage/.update/
reboot^ I think you should be able to just SSH into the console to download the correct image file and cross-grade to the RPi2 image. You need to disable the compat check with the touch command else it will flag you are using a different image and abort the update.
I've no idea. I've never bothered with skin editing to set defaults because the effort involved will be greater than just setting the view type the first time I navigate into some new part of the Kodi GUI.
Each section of the Library (Movies, TV Shows, Collections, etc.) has its own view type so users are sometimes confused by why changing the default view is not a single global change and they need to set it again in other sections (each section) but once you have changed a section view and leave that section of the GUI it should remain changed. You will not be able to edit the skin xml files directly as they are located in a read-only filesystem.
The knowledge hasn't been lost, but the patches to make it work are large and invasive and much of the code needs to be rewritten from scratch as GBM/V4L2 works completely differently. The work is not impossible to do, but one goal of the GBM/V4L2 work is to upstream everything so that all distros have good media performance on Pi hardware (with a focus on RPi4) not just LE/OSMC who were mad enough to entertain a 50,000 line patchset in the past. The nature of the changes needed for optimised HEVC means they will be hard cum impossible to upstream, and while the percentage of LE users that might want the patches is high, most other distros with an actual patching policy refused the existing patches, so the total percentage of Pi users (all distros) that want the patches is low - and hence the Pi Foundations motivation for reinventing this capability is pretty low. Forcing updates is not their motivation at all, but a few users updating to RPi4 to gain more features including hardware HEVC decode doesn't hurt either.
No idea. I build in an 18.04 VM and haven't seen any issues for a long time (other than self-inflicted).
I have all devices that need performance connected via Ethernet but for dev work I'm often fiddling with something in a location that doesn't have an Ethernet cable nearby and the device doesn't have working WiFi support. I solve that with an old Apple A1rport express in bridge mode .. the last one I picked up from eBay was $12, and all I do is plug in a short-ish Ethernet cable to the device and ta-da it's on the LAN.
The upstream kernel is full of "prior art" https://github.com/torvalds/linux…t/dts/allwinner and would be my starting point. I don't see any existing H313 device-trees though, so I suspect your quest needs more fundamental "board bring-up" in the kernel than a device-tree file.
I've moved the thread to the Allwinner section so others comment.
Our userbase has a large number of people using DVB features with RPi2/3 hardware so we are waiting (and actively working on) hardware deinterlace support. Once that's in a public-testable state we will probably release an LE10.0.x "beta" for RPi2/3 users and encourage people to shake out the issues. There will still be a moderate percentage of pitch-fork waving villagers complaining about the loss of optimised HEVC support too; but since that's unlikely to be reimplemented we'll just have to weather that storm.
Correct, same answer as before for the same reasons.
No, old images have been deleted from the server. Each release is tagged in sources if you need/want to self-build them.
Please read (or Google translate) https://wiki.libreelec.tv/hardware/intel…ric#nvidia-gpus .. AMD would be preferred.
HDR is not supported in LE10 Generic images using X11 rendering. There are some LE10 "GBM" builds being released in the forums, and LE10.2/11 nightlies have similar changes. Kodi 20 is the target to have HDR features implemented or at least usable on the majority of hardware and the majority of needed features (full support will take a while, HDR is rather complex).
Nope. The tethering feature in ConnMan was designed for (and is the same as) the hotspot feature on a mobile phone. So you can choose SSID/passphrase and whether the tether is active (on/off) but nothing else. NB: I am often working with development devices that only have Ethernet support in a location where the only sensible connectivity is WiFi .. an Ethernet bridge solves the issue. The last one I picked up from eBay was an Apple A1rport express for $12 + postage.
RPi3 boots and runs fine with the exception of no hardware deinterlace, no 3D support, an dno optimised software HEVC support. If you use it for H264 and a more limited range of media it's very stable.
If you enabled ethernet tethering the Pi provides DHCP to devices via Ethernet. However the tether hides devices behind NAT so they will not be visible to other devices on the network. This is not configurable, connman provides a deliberately simple hotspot, so if you really want the devices on the Network you need to use a device that works as a bridge (not a router).
Just wget the image file, unzip, and use dd to write the USB .. or use any other SD card writer app you prefer.
Codec: H264 - MPEG-4 AVC(part 10) (avc1) Video resolution: 3840x2160 Frame rate: 25
RPi4 supports H264 up-to 1080p so this is expected. If you re-encode the media to HEVC (which is supported at 4K) it will play fine.
