Official LE13 Test Images for Amlogic (Kodi-22)

    IR remote details are defined in device-tree and (no surprise) the N2 dtb defines the Odroid remote not the Dreambox one. It can be overriden in a custom IR map file (there's a wiki article on that).

    The N2 dtb working proves there's no underlying kernel issue. The issue will be a difference between the actual hardware and how that hardware is currently described in device-tree. As the vendor kernel (which we have a device-tree file for) is rather different to the modern upstream kernel and I've never seen a Dreambox board we're reduced to guesswork and playing "spot the difference" with dtb files that work/don't-work. In this respect the N2 isn't so helpful as it isn't based on the W400 reference design and has a large number of differences.

    To narrow the field, please try other "meson-g12b" device-tree files and flag if any have working audio?

    I've also tested it now; there's no audio or Bluetooth on the Dreambox Two. However, I get Default and Bluetooth listed as audio devices, but no longer the Dreambox audio from the dtb.

    Hi chewitt,

    sorry, i've been very busy this week. Couldn't test the other dtb files to flag the device-trees with working audio.

    That will probably no longer be necessary, the sound works again with your new image from 30.04.2025 without _emanuel_s new dtb files.

    Bluetooth also works. But now the WiFi no longer works, the selection option is not displayed at all in the settings

    The log is: https://paste.libreelec.tv/rational-robin.log


    I also tested _emanuel_s new dtb-file with your "old" image from 22.04.2025. With this combination audio, bluetooth and WiFi work. The log: https://paste.libreelec.tv/enjoyed-mako.log

    Thank you both for your efforts :thumbup::thumbup::thumbup:


    I would also like to thank DeepL :angel:

    Vero 4K+ is an S905D (GXL) board with GBit Ethernet .. it's not going to be perfect (as per the current state of hardware decoding in the upstream kernel) but should be usable with un-exotic media. There's nothing special about the 4K+ hardware.

    Quote from Kris404

    Anyone tried these builds on the Vero 4k+?

    I'm new to LibreElec, but I've had success with the Vero 4k (non plus S905X) and was able to boot Armbian and both LibreElec builds linked in OP. I did have to change the u-boot config but with help from the guys at Armbian it eventually worked. See the full story here and instructions for Armbian here.

    After adapting u-boot, both Armbian and LibreElec boot fine from SD card. Rebooting still boots into OSMC somehow, maybe that depends on a different variable?

    It may be different for 4k+, but I don't have one to test. I have seen reports of successful Armbian boots somewhere on the OSMC Discourse.

    I managed to get UART access to the 4k, so if that's needed to debug anything please let me know.

    There is no need to chainload u-boot as Armbian does. Just use the AMGLX "box" image which includes s905_autoscript and boot.scr on the SD card and vendor u-boot will read one of them and reconfigure the boot environment to look for LE boot files first (and if not found, fall back to default boot into OSMC). It will be the same for Vero 4K and 4K+ boxes (and pretty much anything else with vendor u-boot on internal storage).

    That's good to know, thanks for the instructions! I remember vaguely that I've tried LibreElec without the u-boot trick before (just toothpicked it) and it didn't boot (always fell back to OSMC), but I probably did something wrong there.

    Thanks for all the work done on this, really appreciate it! It's cool to be able to breath new life into an older device that would otherwise gather dust or be decommissioned.

    Hi chewitt ,

    since you don't have a Dreambox, I just wanted to report that the new LE13 Nightly with linux kernel 6.15 (including commit 0f67578 - thanks for that) works on the Dreambox with audio and BT. 👍

    LE13 nightlies are bumped to Linux 6.15.1 and images in my test share are bumped to Linux 6.16-rc1. No functional changes are expected .. the media drivers are still abandoned.

    had tested libreelec lately for N2+ but there were quite some problem, but have since found CoreElec which nearly function flawlessly for the device (some modificatin needed for widevine to play disney+ or amazon vod, but that is probably outside coreEelec).

    is there a thread specifically on where to report bug for specific devices? thanks.

    Hi chewitt,

    it's a public holiday in germany today, so i had time to test your test image (6.16-rc1). It works on dreambox. :thumbup:

    Which branch the image corresponds to? I can't find the commit for 6.16-rc1 in master, amlogic or amlogic-upstream. :/