Posts by _emanuel_

  • [LE 13, Amlogic, RPI5] can not connect to BLE Device

    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?

    see also:

    [kernel 6.9.5, bluez 5.70] Failed to connect to peripheral · Issue #35 · Mausy5043/bluepy3
    Hello, maybe someone can help me or know more about the topic I've build bluepy3 modules in LibreElec toolcain. First I've used bluez-5.72 src, for building…
    github.com

  • Official LE12 Test Images for Amlogic (Kodi-21)

    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:

    android_kernel_gigaset_mt6768/drivers/gpu/drm/panel/panel-boe24-jd9853-vdo.c at 1382e85603836dbc1deebbe4d5da78500afd143c · nift4/android_kernel_gigaset_mt6768
    Contribute to nift4/android_kernel_gigaset_mt6768 development by creating an account on GitHub.
    github.com

  • Official LE11 Test Images for Amlogic (Kodi-20)

    test-build from your amlogic branch 6.2.9:

    branch_amlogic.log

    I reduced the speed to: "sd-uhs-sdr50;" like in the mainline-android and wifi works:

  • Official LE11 Test Images for Amlogic (Kodi-20)

    I finally managed to get LibreElec to work on the dreamtv mini UltraHd (s905x2, u211, 2GB, 100Mbit LAN).

    Unfortunately I still have to work with the u-boot.ext (from a u200) + a s905_autoscript.

    I fail to boot with u-boot flashed on raw sd card, until now.

    I tried it as described with the fip and bin built for a u211.

    So far I haven't had any luck.

    But I've already built a device tree that makes everything work (eth, wlan, bt, rc-remote, usb-2.0, usb-3.0).

    The only thing that doesn't work is HW DRM decoding. The player gets stuck and you only hear audio.

    But the box can also handle SW decoding well.

    All boxes like videostrong/mecool KM3, KM9... (s905x2, 100Mbit LAN ) should run with the device tree.

  • Official LE11 Test Images for Amlogic (Kodi-20)

    log caught while box frozen:

  • Official LE11 Test Images for Amlogic (Kodi-20)

    That's all disabled by default in vendor dts. I thing they do only use the dt's value for their own closed src drivers.

    linux-meson64/dreamone.dts at master · emanuel4you/linux-meson64
    linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.
    github.com
    linux-meson64/dreamone.dts at master · emanuel4you/linux-meson64
    linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.
    github.com
    linux-meson64/dreamone.dts at master · emanuel4you/linux-meson64
    linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.
    github.com

    gpio-keys-polled: ir keystoke issues on exit menus (armbian too)

    leds: tested a lot without success, need to talk to vendor

    adc_keys: I need to test this ones

    by the way: my test driver hits two modulators and LNB on the i2c. :D

  • Official LE11 Test Images for Amlogic (Kodi-20)

    @chewitt: did you forget to remove the patch 'amlogic-0091-FIXUP-add-adc-gpio-keys-and-led-s-to-dreambox.patch' before merging nigthly? This only causes trouble, because the exit dialog opens with almost every keystroke on the infrared remote control.

    Sometimes the box still hangs when switched off (even entering: # systemctl --force --force poweroff). I got a last error message in the terminal: Can't close watchdog. So this one hangs.