fix audio and bluetooth for dreambox one/two:
copy dtbs to first partition amlogic/
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.
LibreELEC-AMLGX.aarch64-13.0-devel-20250115231833-f7f63d7-dreamone.img.gz
LibreELEC-AMLGX.aarch64-13.0-nightly-20250124-0e145cf-dreambox-one.img.gz
It could be, in any case the old Dreamboxes were protected by an extra chip or SIM. And the developers talked about the tpm. In any case it's not worth the effort to hack it.
Regarding CoreElec: Yes, I've given up on that completely because the source is no longer compatible with the Dreambox. The Dreambox uses an ancient manufacturer kernel (4.9) and the associated bootloader, which prevents a lot of things, e.g. new CoreElec with video (in my old one, even DVB-S2 works).
The huge difference between an Amlogic Dreambox and a conventional Amlogic Android box is that the Dreambox has a security chip (tpm) built in. This means that if I swap the bootloader for one not built by the manufacturer, the box is broken. This is also the reason why there is no separate Dreambox image in the Nightly. The board-specific images here all have a bootloader for the kernel 6.X flashed at the beginning of the SD. So you can only use the box image of the Nightly for the Dreambox, which is intended for manual configuration. LibreElec uses a brand new kernel 6.X. the Dreambox's conventional boot loader can no longer handle such a kernel and the box simply freezes.
To boot a kernel 6.X on the Dreambox anyway, you can only do this:
1.) Dreambox boot loader decrypts and opens the box
2.) finds the autoexec.img script and executes it.
3.) The script overwrites the boot loader with a new bootloader that is for kernel 6.X and is located on the first partition.
4.) the new bootloader starts the kernel and LE
5.) LE switches off and wants to shutdown the kernel. But the Dreambox now reboots into the manufacturer image because the bootloader for kernel 6.X cannot operate the security chip. So a script has to help out again so that the box does not boot again and shuts down when it boots in the manufacturer's bootloader again.
I know, it's all complicated. I've been doing this for years now. To make it short, the images in Ihad are built 1 to 1 like those in Nightly, I even grabbed the last ones directly from the download feed. You just have to flash them.
I hope I don't get into trouble because of the link (everything I did there is published).
packed images are ready here for all 3 bootloader variants:
a) for original bootloader, *.img.gz
b) GPT multiboot loader (manufacturer Multiboot) *gpt-multiboot.img.gz
c) gboot multiboot *multiboot.img.gz
Believe me, I would prefer it without this stupid tpm chip. The new Dreambox doesn't have one anymore. Because they only sell boxes anyway and no longer have any developers who can even build something like that. The new one is like any conventional Android box.
What irony, developers protect their work with a tpm chip, but have no work anymore...
It is absolutely necessary to provide the LibreElec image with a chain boot loader. Otherwise the manufacturer's boot loader of the Dreamboxes cannot boot the image. A script for repacking is available here on github, or the pre-packed images are available from me on ihad.
I do only repack the normal *box.img after building, add extra scripts (autoexec.img, ..) and a chain u-boot.ext to FAT partition and rename it to DREAMBOOT.
All changes are only necessary for the original tpm protected dreambox bootloader in order to boot or shutdown the 6.X kernel.
There are no src changes/patches, all is original LE git.
I've got only a packing script nothing more.
it can all be done from Nightly builds or *.tar from Nigthly can be used for update.
hi, I've got problems connecting with BLE Remote.
It work's nice in rasbian bookworm on RPI5 and also in Vendor os on Amlogic device.
But not in LE 13.
Has anyone an idea how to fix?
LibreELEC:~/.kodi/addons/script.module.bluepy3/lib/bluepy3 #
LibreELEC:~/.kodi/addons/script.module.bluepy3/lib/bluepy3 #
LibreELEC:~/.kodi/addons/script.module.bluepy3/lib/bluepy3 #
LibreELEC:~/.kodi/addons/script.module.bluepy3/lib/bluepy3 # hcitool lescan
LE Scan ...
00:09:34:B2:CA:2B DM Remote
00:09:34:B2:CA:2B DM Remote Advanced
00:09:34:B2:CA:2B DM Remote
00:09:34:B2:CA:2B DM Remote Advanced
^CLibreELEC:~/.kodi/addons/script.module.bluepy3/lib/bluepy3 # bluetoothctl
[bluetooth]# scan le
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# hci0 type 6 discovering on
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 43:54:A2:00:1F:AC Discovering: yes
[bluetooth]# [NEW] Device 00:09:34:B2:CA:2B DM Remote Advanced
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffb4 (-76)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffb1 (-79)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffaa (-86)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffac (-84)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffb4 (-76)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffaf (-81)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B ManufacturerData.Key: 0x06c4 (1732)
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B ManufacturerData.Value:
[bluetooth]# 00 00 00 00 00 00 ......
[CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffb0 (-80)
[CHG] Device 00:09:34:B2:CA:2B RSSI: 0xffffffae (-82)
[bluetooth]# scan off
[bluetooth]# hci0 type 6 discovering off
[bluetooth]# Discovery stopped
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B RSSI is nil
[bluet00:09:34:B2:CA:2B9:34:B2:CA:2B
[bluetooth]# [CHG] Device 00:09:34:B2:CA:2B Trusted: yes
[bluetooth]# Changing 00:09:34:B2:CA:2B trust succeeded
[blue00:09:34:B2:CA:2B9:34:B2:CA:2B
Attempting to pair with 00:09:34:B2:CA:2B
[bluetooth]# hci0 00:09:34:B2:CA:2B type LE Public connected eir_len 30
[CHG] Device 00:09:34:B2:CA:2B Connected: yes
[DM Remote Advanced]# hci0 00:09:34:B2:CA:2B type LE Public disconnected with reason 1
[DM Remote Advanced]# Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device 00:09:34:B2:CA:2B Connected: no
[bluetooth]# see also:
LE13 build from official works fine.
I've tested it on dreambox two.
current build works well on dreambox 
docker build --pull -t libreelec tools/docker/jammyworks 
First I've tested "y", but also no install.
I've got a problem to build it:
I've just tried to get the wifi to work. I adapted the patch from you so that it works on both dreamboxes. I built it into an original LE.
I know this drive, but got one big problem:
chewitt: can you add the dreambox patches again?
test-build from your amlogic branch 6.2.9:
[ 9.458149] brcmfmac: F1 signature read @0x18000000=0x17224356
[ 9.459823] Bluetooth: Core ver 2.22
[ 9.459938] NET: Registered PF_BLUETOOTH protocol family
[ 9.459944] Bluetooth: HCI device and connection manager initialized
[ 9.460100] Bluetooth: HCI socket layer initialized
[ 9.460110] Bluetooth: L2CAP socket layer initialized
[ 9.460205] Bluetooth: SCO socket layer initialized
[ 9.462673] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[ 9.489571] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...I reduced the speed to: "sd-uhs-sdr50;" like in the mainline-android and wifi works:
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
* Copyright (c) 2019 Christian Hewitt <[email protected]>
*/
/dts-v1/;
#include "meson-g12b-dreambox.dtsi"
/ {
compatible = "dream,dreambox-two", "amlogic,g12b";
model = "Dreambox Two";
};
&sd_emmc_a {
sd-uhs-sdr50;
};