Posts by thebakker


    I'm trying to add my dualshock 4 to libreelec, but it keeps geving errors. I tried it with the build-in bluetooth of the mini pc, and also with a ble dongle

    Here are my logs:

    It seems it creates an exception

                                                       Exception type  : DBusError
                                                       Exception value : org.bluez.Error.Failed -- No discovery started
                                                       System info     : uname_result(system='Linux', node='LibreELEC', release='5.10.47', version='#1 SMP Thu Jul 15 01:45:06 CEST 2021', machine='x86_64', processor='')
                                                       Python version  : 3.8.9 (default, Jul 15 2021, 01:46:40)  [GCC 10.2.0]
                                                       Kodi version    : 19.1 (19.1.0) Git:6402a50950ff6463042f8891ec4029c782730391
                                                       sys.argv        : ['']
    2021-08-14 07:27:28.069 T:991      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
    2021-08-14 07:27:28.131 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=0" may be unconnected (no ELD data)
    2021-08-14 07:27:28.132 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=1" may be unconnected (no ELD data)
    2021-08-14 07:27:28.132 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=2" may be unconnected (no ELD data)
    2021-08-14 07:27:28.133 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=3" may be unconnected (no ELD data)
    2021-08-14 07:27:28.133 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=4" may be unconnected (no ELD data)

    There are no audio devices detected. What are you using?

    HDMI#2 seem to be connected. xrandr --verbose|paste may show more details.

    For the failing pastekodi use pastekodi -c >mylog and put the file manually to a paste site.

    I'm using this: NiPoGi Mini PC, Intel Celeron J3455 8GB RAM/128GB ROM Mini Computer met Windows 10 Pro, Micro PC ondersteuning Dual HDMI 4K, Wake On LAN, Tiny Desktop PC voor business, vergadering, kantoor, school en HTPC: Computers & accessoires

    It is a mini pc with 2 HDMI outputs. I have the stuttering on both ports.

    This is the output from xrandr:

    Currently I have the mini pc connected to my regular display (it has no sound) (samsung S24D340) to configure everything. When everything works, I want to connect it to my TV

    EDIT: so, I have some more test. When I connect the mini pc to my display without sound, and then the video is very choppy, and sometimes just freezes.

    mglae response, made me test it at my tv. When I connect it to the tv everything works. So I guess that there is a bug(?) when there is no audio device.

    Sadly both links are not working for me, but I'm having some internet connection problems myself lately, so who knows.

    But there is also hastebin (with 60 days retension) ;)

    It was too big for pastebin. This is my hastebin link:


    In case that doesn't work: this is a google drive link:

    External Content
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Yeah, sorry, I completely forgot about nightly.

    I have 9.97.1 generic.x86_x64 installed

    I tried a local file, it starts quicker. But it stutters even more than through plex

    I noticed LE only uses 1 core (core 1: 100%, the rest is only 10%)

    Here are my logs: (the pastekodi command didn't return anything, so I uploaded the logs to my nas)

    Synology Drive…rS9i0gs9fKICI-5reATmqg1Qg

    I see these errors in my logs:


    I had an Intel j3455 box laying around. And decided to use that one instead of my rpi4 for libreelec. But the performance is terrible.

    I use kodi Plex Connect to watch my movies from my server.

    My rpi starts a movie in 20s. But the j3455 does more than a minute to start. It also stutters on my j3455. The movie is just a h264 1080p movie

    I just did a clean install of the latest kodi and latest kodi plex connect.

    The passmark score of the j3455 is more than double of the rpi4. Is there something I'm missing? Do I need to do more configuration for x86?

    Thanks in advance

    Yeah, but someone on github commented this:


    I'm closing the ticket because this is not a bug, it's the expected behaviour now RPi devices in LE10 no longer use legacy vendor drivers (behaviour is now consistent with other LE devices since ~2012).

    Follow the section on Intel GPUs and repeat for your RPi4. If you need further support please start a thread in the forums.

    So I'm looking at that now.

    I fixed it, see edit

    Edit: it is fixed:

    I followed this and follwed the intel steps, but the extlinux.conf or syslinux.cfg didn't exist, so instead I added

    drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:[email protected]

    To /flash/cmdline.txt

    Orifinal problem:

    I made a git bug report, but I wanted to know if someone else has the same problem?

    Describe the bug

    When I boot my raspberry pi an afterwards start my tv, I don't get video out. Even when I unplug and plug in the hdmi after they both are started.

    But when I first start my tv, and then boot my rpi it works fine

    To Reproduce

    Steps to reproduce the behavior:

    1. Install 9.95.5
    2. start RPi4
    3. Start soundbar (HEOS) and tv


    • LE Version: 9.95.5
    • Hardware Platform: RPI4

    Log file

    Log from when the problem exists:

    Log from when I first start the tv:

    Additional context

    It worked fine when using LE 9.2.X

    I have my rpi4 connected to my soundbar, and the soundbar to the tv

    check the output of

    systemctl status kodi-autostart.service

    You might need to wait until you have a network connection and docker is started

    Thanks, I got the error

    Mar 14 09:25:36 LibreELEC sh[724]: the input device is not a TTY

    This was an error from my docker command, I fixed it by removing the "-it" argument

    Is there also a log from the shutdown script?

    Quote from ghtester I know, maybe I am wrong but I still believe in this case these commands should not be queued. is run at the very start of usespace boot, so the network is not started, kodi (which runs docker via an add-on) is not started. So running the docker command at that point will *allways* fail, and (backgrounding)& is the correct approach.

    The case statement ^ above was incorrect, not sure if it was copy/paste typo or what but I edited it to be correct.

    As lrusak says, look at systemd logs

    But the shutdown doesn't. I think I have the problem you describe: docker gets closed and after that the shutdown script gets called.

    Any idea where I can see the shutdown log?

    EDIT I found a workaround:

    I couldn' get it working, so I made a node-red flow on my server that creates a HTTP api, and converts the http data to MQTT

    And put a wget in my startup and shutdown script:

    wget -T 2


    I followed the guide for creating autostart and shutdown commands (This guide). But my commands dont run

    I I have the following code:

     sleep 50
     docker run -it --rm eclipse-mosquitto mosquitto_pub -h -t plexBox/state -m "ON"

    And in the

    I have docker installed through libreelec. And when I run these commands manually, they work.

    Anyone a suggestion?