- in other words: can I decide from two given hashes which is the elder and which the newer one ?
Based solely on hashes, no. You would need to check git repo which is newer. Hash is just some hex number, calculated from data. In fact, from security perspective, you should not be able to infer any useful information from hashes alone.
EDIT: To be clear, hashes are taken from git commits, we don't have any control over them.
There is not such thing as generic boot image. While file system and kernel are same for all H3 based boards, bootloader (U-Boot) is customized for each board separately and this fails in your case.
No. Most likely DRAM driver driver doesn't work. If you have serial to usb cable, you can try to find correct connector on board and connect it. That way you can see how far boot comes. If it's really DRAM driver, chances are basically non-existing to do anything. Unless, of course, if you know software reverse engineering techniques, but in such case you probably wouldn't ask these questions.
Disclaimer: We don't support random TV boxes based on Allwinner chips. That being said, it might work with existing image. So which image did you use? And by "installing" you really mean installing with install2emmc script or do you mean booting from SD card? You also didn't provide enough detailed photos - most interesting things are markings on various chips but we can't read them.
Nope. While basic Linux support is slowly materializing, two major blockers are still at the same spot - HDMI audio (no useful driver) and bug in display driver (big code change may be required to fix it).
oddebian thanks, but unfortunately everything checks up. I sporadically managed to reproduce the issue on my own builds, which is improvement. However, even with all minor differences ported from BSP driver, issue was still there. I'm not sure it's the driver issue anymore.
oddebian I have exactly the same board, with same markings on the board. So it must be something on SW side. I did few more tests with official LE 10.0.2 release and I managed to get corrupted deinterlacing only once. However, it stayed corrupted also over reboots until I plugged off power supply for few seconds and plugged it back on. After that, I couldn't reproduce it anymore. So it must be some issue which persists over boot. Maybe some clock setting. Can you provide output of cat /sys/kernel/debug/clk/clk_summary, executed during bad deinterlacing?
EDIT: I managed to reproduce it once on latest, self-build image. However, reboot restored deinterlacing.
As i had Orange Pi3 in mind which has a H6 CPU, for which you mentioned above it does HW.
Yes, of course. My brains don't work for some reason.
Pi3 doesn't decode HEVC in HW, it just have extremely optimized SW decoding, but only in LE9.2 and lower, not LE10. I'm not sure what is 10-bit HEVC performance.
oddebian Currently I can't think of any data that would help in narrowing down issue. Sadly only way to fix it, is to reliably reproduce it on my development system, but I don't have any success with that.
Oh i thought thats just the name of the decoder(DRM Prime) , and not realated to Amazon. Today i learned :).
Ah, sorry, brainfart on my side. DRM prime is really a decoding method, you're right 
Anyway, I'm pretty sure you tried to watch 10-bit HEVC and H5 doesn't have appropriate core neither to HW decode nor HW render it. H6 does, so it will be very low CPU utilization.
You can use mediainfo addon, which shows basic information about video file.
DRM Prime
I guess Amazon Prime? Note that if Widevine (or basically any other) DRM plugin is used, video is always decoded on CPU. Cortex A53 cores are just not designed for that task. Because of that, being able to play only 720p HEVC sounds about right. Another part of your problem is that 10-bit HEVC stream was selected. This is not supported by HW in any form, even rendering it via "direct to plane" method selected by default. Kodi doesn't yet know to fallback to GPU rendering in such cases. If you select GPU rendering in settings, video will be there, but due many inefficiencies in decoding and rendering process, it will most likely be slideshow.
What do I need to do to get the wifi working?
Your own image with wifi driver. It was explained many times "why" in main topic of Allwinner subforum.
I used the Raspberry Pi Imager. The imager kept giving me an error saying it couldn't create the config.txt file, so I moved on from that, figuring I could just edit the settings in Kodi. Not a problem I need solved, just mentioning it in case that matters.
config.txt is RPi specific thing and is not applicable to any other platform.
When I turn on bluetooth and then go to the bluetooth tab it says no bluetooth adapter, and after a reboot (with it still enabled) it says bluetooth disabled.
What do you mean by "turn on"? Board doesn't have integrated bluetooth. Did you use USB bluetooth adapter?
Everytime i get a blank screen when i try this kernel parameter:
initrd=/edid.cpio drm_kms_helper.edid_firmware=edid/edid.bin video=card0-HDMI-A-1:3840x1080D
edid/edid.bin doesn't exist, so yeah, kernel gets confused. Note, loading custom edid is not really supported as of now in some LE images (including AW), because kernel tries to load file before filesystems are even mounted.
Can you try with nightly image?
No, just put tar file in /storage/.update folder and reboot
oddebian I can't reproduce this issue on images built by me, even 10.0.2. So I can't really do much. Except upload 10.0.2 update, which you can use and issue may be gone: http://jernej.libreelec.tv/test/le10/Libr…735-7140f60.tar
but is it possible, that xrandr isnt a command anymore?
xrandr has never been supported on LE ARM images, at least to my knowledge. xrandr implies X11, which is not used here and it's on its way out even for Generic. Here Kodi directly interacts with DRM drivers, without any window manager in between (GBM mode).
