Posts by jernej
-
-
32-bit AW SoCs should be good: LibreELEC.tv/linux.arm.conf at master · LibreELEC/LibreELEC.tv · GitHub
64-bit AW SoCs miss one option: LibreELEC.tv/linux.aarch64.conf at master · LibreELEC/LibreELEC.tv · GitHub
Which board do you have?
-
Is there a chance for official NanoPi K1 Plus support?
Only boards which are or will be officially supported by Linux kernel can be supported. Somebody must submit DT upstream and once it's confirmed, we can talk again.
Note: We don't accept additional out-of-tree wifi drivers anymore. It's also stated in first post of this topic. In short, unless someone manages to include rtl8189ES driver in Linux, it won't be supported.
-
Or has handling of interlaced content been somewhat abandoned with the new framework (I hope not - it's still used for a large chunk of ATSC and DVB TV, plus DVD and Blu-ray)
No, Allwinner and Rockchip implements it. Main requirement is v4l2 deinterlacing driver. LE uses out-of-tree ffmpeg v4l2 deinterlace filter implementation, written mostly by me. Kodi then uses standard ffmpeg infrastructure - first it decodes frame in DRMPRIME format and if content needs deinterlacing, it pushes frame through deinterlace filter. If not, it's displayed directly. It's still considered tech demo, since there are known corner cases, which don't work (mostly frame dropping).
-
None. H313 and H616 (basically same thing) are not supported (yet).
-
Note, we don't add new wifi drivers if they are not in kernel. So while you can make your own image with added driver, driver itself won't be accepted in official LE.
-
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.
-
Post
Nightly images for A64, H3, H5, H6 and R40 boards
WARNING: Since of the release of LibreELEC 10 stable, nightly images are NOT recommended for every day use, especially if you need addons!
Images and updates:
Nightly images and update files are available here. Please note that update files are board specific now.
H3 based boards:
- BananaPi M2+
- Beelink X2
- Libretech ALL-H3-CC (Tritium) (H3 SoC)
- NanoPi M1
- OrangePi 2
- OrangePi PC
- OrangePi PC Plus
- OrangePi Plus/Plus 2 (same image for both boards)
- OrangePi Plus 2E
A64 based boards:
- OrangePi Win
-…jernejMay 18, 2019 at 5:09 PM -
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.