I guess driver for wifi+bt module is this one: GitHub - paolosabatino/ssv6x5x: ssv6x5x driver adapted to for rockchip rk322x Since no mainline driver -> no support in LE.
I don't know about keymap from the top of my head, but you can surely find some guide on net.
What kind of Wifi+BT chip does it have? Can you check chip markings or alternatively provide dmesg output from Android?
Regarding IR - I find it hard to believe that IR wouldn't work. Most probably it just uses remote with different keymap. You can run ir-keytable -t -p NEC,RC6 and press few keys on your remote. If key presses are decoded, you just need to change keymap.
I updated updates to 10 beta4 and added A64. No testing was performed but it should work as well as previous updates.
There is no beta 3 with passthrough support. Either you used beta 3 and somehow enabled passthrough, which is not supported or you used passtrough test image (beta 2).
Build server is temperamental at times, so just check again after a few days.
Oh seems with the last patches (maybe Rockchip: linux: add patch to fix RGB to YUV422 conversion in dw-hdmi · LibreELEC/LibreELEC.tv@8cce2e2 · GitHub) fixes the black screen on some emulators (especially Stella2014).
That patch is specific to RK, so it must be something else.
Why is it beta? Nightly builds for H3 seems VERY stable. I have Pi0, Pi3 and i can compare.
Because status is determined for all platforms together. Believe me, there are bugs even on H3, just not screaming ones.
I have the same issue with a Samsung TV, but this only started somewhere between version 8 & 9 of Kodi. There has also been a major libcec update in that timeframe. Some bisecting to find the cause might be possible. Do you have any idea what would be the most probably cause for the regression, Kodi or libcec (or something else)?
There is no LE8 for Allwinner, at least not from official git tree. Depends on which SoC you're talking. If it is A64 then regression most probably comes after switching to HW CEC driver. I don't have a clue for others.
How can i install it?
All addons needs to be build by yourself. There is no addon repo for old images.
There is an issue with Widevine library on all ARM platforms and it's possible that it won't be solved soon.
Does Disney+ use Widevine? If so, note that this is SW decoded and then there is currently issue with it: Latest Widevine 4.10.2252.0 fails to load · Issue #678 · xbmc/inputstream.adaptive · GitHub
I connected it to a 1080p monitor and it showed up and I was able to configure it. When I connected it back to my 4k LG TV the TV doesn't detect a display signal but I can see the device on my wireless network. So it was probably booting originally but my TV just wasn't seeing the signal, and it still doesn't.
I too have issues with any H6 board and my LG TV in 4k@60 mode. Any mode with 297 MHz pixel clock or lower (4k@30 and lower) should work fine. However, my 4k@60 monitor works fine. I have yet to find a fix for that. Currently the only workaround is to lower resolution on some other display first, which is then remembered on Kodi.
Yeah, I can give you diagnosis - HW doesn't support 10-bit H264 (nor any other 10-bit content), so this must be SW decoded and converted to 8-bit. If you disable DRMPRIME decoding in playback settings, you'll get just that. Graceful fallback obviously isn't implemented, it's one of the rough edges. But SW decoding of 10-bit content is more demanding, so you usually won't get good experience anyway.
It's solved by applying windowing/gbm: Add display clock by popcornmix · Pull Request #19601 · xbmc/xbmc · GitHub you suggested some time ago and enabling "Sync video to display" in settings. Hope these commits will make it to LE soon.
I believe this is Kodi 20 feature and not planned to be backported to LE10. However, if enough noise is made about it, we might reconsider 
I found another possible improvement. If you switch to ondemand governor, you can try following settings:
LibreELEC.tv/cpufreq at master · LibreELEC/LibreELEC.tv · GitHub
offbeat note that overlays currently work only on RPi and Allwinner, maybe Amlogic (not 100% sure). Based on PWM addresses, tony013 uses Rockchip (RK3399), which doesn't support overlays yet.
Which codec? Or better yet, can you provide small sample? Note that not all codecs supported in HW work. Currently supported are MPEG2, VP8, H264 and HEVC.
I removed test image. It was highly experimental and later I decided to drop support for A20 altogether, which meant that I stopped experimenting with A10 too. Few reasons:
- I don't have any A10 HW
- A10/A20 image quality was poor (far more issues than H3 or newer)
- HW lacks support for expected features (I think A10 chokes on full HD videos)
- A10 and A20 SoCs are pretty different to H3 and newer, which would double the work
you mean that our Orange Pi plus 2E does not have mainline driver for Wifi and won't be supported?
Exactly. It was decision made by team. Out of tree wifi drivers are not fun to update and they break often when kernel is updated. We could have at least 15 drivers at this point, if we would go this route. Anyway, in my experience, wifi module on the board is not that great. You could make your own image with added driver or just use USB wifi dongle.
you didn't tell which board you're using.
Afaik the dtb is created during kernel build - and I searched packages/linux for scripts that I could overload ...
didn't find some.
If you want to go this way, you have to make kernel patch and add it to "patches" folder.
So I tried to create an overlay file, added it to extlinux.conf - but then, LE does not boot any more.
This should work for Allwinner boards, if you use latest image. But I suspect you're using different platform.
