Official LE11 Test Images for Amlogic (Kodi-20)

  • An S905 can almost handle 1080p HEVC in software so MPEG2 at 720p/1080i should be do-able. It would still be nicer to have proper hardware decoding.. but that needs someone to take an interest in the vdec code. MPEG2 isn't a complex driver, and it's likely broken due to a few small changes due to general V4L2 evolution since it was first written, but we're approaching three years since someone last seriously looked at the code and it appears nobody (who can code) cares enough to look.

    Shouldn't an S905 handle HEVC completely in HW, I've finally finished setting up my Odroid C2 with the profiles and libraries and now when I went to test playback some stuff played perfectly with seeking and everything, some didn't play at all and some were stuttery. As far as I know my Odroid should handle HEVC at 4K/30 HW, at least that's what it says on the manual, so why am I getting these issues?

  • Shouldn't an S905 handle HEVC completely in HW, I've finally finished setting up my Odroid C2 with the profiles and libraries and now when I went to test playback some stuff played perfectly with seeking and everything, some didn't play at all and some were stuttery. As far as I know my Odroid should handle HEVC at 4K/30 HW, at least that's what it says on the manual, so why am I getting these issues?

    The point being made was that MPEG2 media can be (or could be, if we disabled the broken MPEG2 hardware decoder) be decoded in SW.

    S905 does indeed have hardware HEVC decoding capabilities, but with some bugs (seeking is one of them) that remain unresolved pending the attentions of someone with coding skills taking an interest in fixing them (so not me). The H264 hardware decoder is generally in a much better state, and everything else (apart from MPEG1/2) .. e.g. MPEG4 is software decoded.

    The vendor kernel still runs best on Amlogic hardware, but that's outside the scope of this thread or upstream kernel images.

  • S905 does indeed have hardware HEVC decoding capabilities, but with some bugs (seeking is one of them) that remain unresolved pending the attentions of someone with coding skills taking an interest in fixing them (so not me). The H264 hardware decoder is generally in a much better state, and everything else (apart from MPEG1/2) .. e.g. MPEG4 is software decoded.

    So for the time being HEVC playback going to be bad :')

    I tried SW but i ran with the issue of audio sync, the video plays, not the best playback but good enough and the audio is out of sync. Still some files refused to play and would crash the system. I guess I should keep transcoding from the server until HEVC decoding capabilities are implemented. I don't have the coding skills but I can try to do something, if you have any idea where I can start that will be great.

    Thank you again for your support, it really is a great project.

  • @chewitt: You recently gave me a test image that unfortunately didn't boot. It had a linux 6.1 kernel.

    Did you fix that with the nand on some boxes?

    If so, could you build the box img for me?

    Would be interesting if wifi works there.

    It works with my dtb in le-nightly (6.0.9) but not in armbian-current (6.0.14) or in armbian-etch (6.1).

    (brcmfmac debug log attached)

    >>> found the patch armbian bug, now wifi works on 6.0/6.1.1

  • @chewitt: woks nice without:

    amlogic-0022-FROMLIST-v6-dt-bindings-power-Add-G12A-NNA-power-dom.patch.aus

    amlogic-0023-FROMLIST-v6-soc-amlogic-meson-pwrc-Add-NNA-power-dom.patch.aus

    amlogic-0024-FROMLIST-v6-arm64-dts-Add-DT-node-for-the-VIPNano-QI.patch.aus

    amlogic-0025-FROMLIST-v6-drm-etnaviv-Add-nn_core_count-to-chip-fe.patch.aus

    amlogic-0026-FROMLIST-v6-drm-etnaviv-Warn-when-probing-on-NPUs.patch.aus

    amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch.aus

    amlogic-0052-WIP-arm64-dts-meson-add-support-for-the-NPU-on-Radxa.patch.aus

    Wifi only works setting

    LibreELEC.tv/amlogic-0088-WIP-arm64-dts-meson-add-initial-device-trees-for-Dre.patch at bb98dc6f00cc16e33796ac0dc4fc672281a7093f · chewitt/LibreELEC.tv
    Just enough OS for KODI. Contribute to chewitt/LibreELEC.tv development by creating an account on GitHub.
    github.com

    to

    Code
    <&gpio GPIOA_11 GPIO_ACTIVE_LOW>;

    The log in the attachment

  • @chewitt: now it works nice

    one patch hung, but build boots.

    Code
    APPLY PATCH (device)      projects/Amlogic/devices/AMLGX/patches/linux/amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch
    patching file arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
    Hunk #2 succeeded at 2493 (offset 1 line).
    patching file arch/arm64/boot/dts/amlogic/meson-g12b.dtsi
    patching file arch/arm64/boot/dts/amlogic/meson-sm1.dtsi

    The log in the attachment

  • I had tested it like this before:

    but it only caused interference with the IR remote control. (gpio-keys-polled) After a few button presses, the exit menu suddenly starts to flicker on off on off... Kodi can then no longer be operated and must be terminated via terminal. I hadn't caught either the LED or the Power HW button at the time. With your patch I have the same flakes. The HW power button and the LED don't work either. Dreamtwo has an RGB LED. I think Dreamone is only blue. If I set the gpio-keys-polled to GPIO_ACTIVE_LOW, the menu stops flickering, but it still appears with almost every X keystroke, but you get out with exit.

    What are the adc keys for? how can i test it?

  • Not sure if this relates to the OS or Kodi (then a query for kodi.tv). Issues with playback, seeking and subtitles. AlexELEC with Kodi 18.5 for mostly HD H264 off an SD. Playing a first file is always or mostly fine. Any next file may play or always plays shifted, so I need to stop and start.

    1) Reason enough to try a new build?

    2) I have read in http://wiki.libreelec.tv/hardware/amlogic.

    Still, a few questions. It appears I need builds marked as 'box'. Is my only source http://test.libreelec.tv/11.0/Amlogic/box?

    Should I consider test builds in other locations?

    Builds for 10 are not for Amlogic (http://test.libreelec.tv/10.0/Generic), so unsuitable?

  • It appears I need builds marked as 'box'. Is my only source http://test.libreelec.tv/11.0/Amlogic/box?

    Builds for 10 are not for Amlogic (http://test.libreelec.tv/10.0/Generic), so unsuitable?

    Experimental LE11 test images are here: https://test.libreelec.tv/11.0/Amlogic or https://chewitt.libreelec.tv/testing/ nothing else will run on Amlogic hardware. If there is no specific device-tree for your box you will need to experiement (lots of devices are similar.. we have no idea what specs/hardware your box has). Note that the boot process is different to legacy images. There are no LE10 images (or nothing worth using). There is zero support for piracy images like AE in this forum.