find /volume1 -type d -name @eaDir -exec rm -rf \"{}\" \;I've no idea why Kodi behaves like that, but the workaround would be to disable AFP services on the Synology box, as that's the reason @eadir files are created (to hold AFS metadata). It's unlikely AFP services are needed as all Apple kit from the last decade or more speaks SMB. Then do a recursive find/delete of the @eadir files with ^ the above command, reboot the RPi's and see what happens.
I haven't noticed this myself, but a) I'm not using the WP2 for much, b) I've erased emmc to boot the box using the upstream u-boot image on SD card (the wetek-play2.img.gz file in my test share) which may do power things differently.
^ we added a tools section to the latest versions, which will erase the mulit-partitioning that Windows is dumb about, making the whoie card writeable again. NB: I've only ever observed issues with the app when the card is done/failing.
Coming out of same mode puts it into a boot loop but keen to see how this can be fixed.
It's a self-inflicted problem that will be solved by uninstalling/removing the incompatible piracy shitware that caused the issue. If you want to use those add-ons you are not welcome in this forum (aka, you should read our forum rules again).
In the future the answer will be yes, and we should have about three months of previous images for download, but right now we're still in the process of making the changes to achieve that goal and there are none to speak of .. so no.
At the end of the day it is simple for people to make a USB and test to see what works for their use-cases, and a major task to aggregate and maintain results as we move frequently and continuously through combinations of newer kernels, drivers and firmware - which is why that idea dies on its arse each time someone raises it or well-meaningly starts a thread on the topic.
It seems to be a skin thing. I see the controls with Estuary.
Lately I have some problems with many addons, unfortunally they not working anymore (for example the promice, elementum, youtube).
We are delighted when piracy add-ons stop working. If you want them to use them, you are posting in the wrong forum.
USB boot may require a specific port to be used.
I can see time jumping around several times in the OS boot log so you might want to delay Kodi startup until the network is up and NTP sync occurs; this prevents issues with invalid certs due to OS time being before the start time of TLS certs.
However that repo has piracy content in addition to Bulgarian subtitles so I don't care about it working. The logs show the issue clearly.
LE has good core OS support for SM1 (S905X3) hardware but there are no drivers for the Amlogic WiFi chip thats inside and unresolved issues with 10-bit output and hardware decoding. You can run LE but only with software decode up to 1080p and Ethernet. There's no device-tree for that box but there are several other SM1 devices based on reference designs which will probably work.
This would be a feature request for Kodi not LE. You can make Kodi feature requests via the Kodi forum.
No, because Kodi does not support this.
LE10+ images no longer have optimised software HEVC decoding so performance is expected to be worse (no bug to report). It's not possible to reinvent the same level of optimisation using the newer video pipeline that we are using now. I'll also pass the comment that RPi02W is not supported hardware in LE10+ due to 512MB RAM being generally insufficient for a good Kodi experience now. It will work better on the LE9.2 codebase; although we have deliberately omitted support there because we don't want to encourage people to buy RPi hardware that is not supported in later releases.
I'll try that. I'm checking https://test.libreelec.tv/ and it seems there's only builds for RPi2 and RPi4? Mine's a RPi3.
Use the RPi2 image then.
Damn! Tried the toothpicked and it booted ,weired, all my other distribs boot directly, but let`s see
q200.dtb
LE uses different u-boot bootscript, so unless you (re)load it by forcing recovery boot you're trying to use legacy boot scripts which don't see our boot files. You'll need to do the same (for the reverse reason) if you revert back to older distros.
NB: I'm not aware of any issues with networking or repos. If you want any help with that topic you'll need to share boot logs and Kodi debug logs (not non-debug logs) so we can see what errors are reported.
For Sunvell T95V Pro tv box, image and device tree please.
Just experiment with some gxm box dtb files .. e.g. Q200.
FYI, this was submitted to the upstream kernel yesterday: https://patchwork.kernel.org/project/linux-…[email protected]/ .. so there will be a dtb in future nightlies. I also have the u-boot sources from Beelink so should be able to organise support for reimaging the box (installing to emmc) with upstream u-boot support too at some point.
