Posts by Da Flex

    Double post. Continue here:

    fezster
    January 15, 2024 at 12:58 PM

    Probably an (LS)PCON chip issue:

    smp
    January 15, 2024 at 2:36 AM

    PS: Guys, please do me favor, and stop those double posts:

    fezster
    January 16, 2024 at 11:37 AM

    I thought it was solved here:

    Butch74
    January 15, 2024 at 9:45 PM

    No double posts please. Closed.

    Argon cases are widely reported to cause hdmi issues, so first step would be to test without the case.

    I've mentioned that earlier:

    Hunduster
    January 10, 2024 at 10:07 PM

    Yes, Argon One cases are known for soldering problems on HDMI contacts, but then it wouldn't try to buffer before it crashes. A network issue is much more likely. If I remember correctly, log level 2 includes more network data.

    Hunduster Can you provide another log file for that error at log level 2? We still haven't found the real cause in the log.

    There is a warning about the <videodatabase> tag at advancedsettings.xml:

    Can you do a test run without <videodatabase> content?

    Thanks for removing all those NTP errors from the log.

    I think your NAS connection is OK, because you don't have the typical "waiting for buffer" warnings in the log.

    Most of the current errors are harmless, but I'm not sure about this error:

    The movie stopped at 19:54. Same behavior again.

    Yep, that error is visible in the log:

    Code
    Jan 12 19:54:31.760060 Kodi-WZ connmand[597]: ntp: adjust (slew): -0.012913 sec
    Jan 12 19:54:41.015071 Kodi-WZ kernel: rpivid feb10000.codec: rpivid_h265_stop
    Jan 12 19:55:08.864468 Kodi-WZ kernel: rpivid feb10000.codec: rpivid_h265_start: (3840x1616)
    Jan 12 19:55:08.891862 Kodi-WZ kernel: rpivid feb10000.codec: SPS changed
    Jan 12 19:55:08.892280 Kodi-WZ kernel: rpivid feb10000.codec: PPS changed
    Jan 12 20:00:00.289036 Kodi-WZ crond[390]: USER root pid 1340 cmd ntpd -n -p 172.22.29.1
    Jan 12 20:00:05.659047 Kodi-WZ crond[1174]: ntpd: reply from 172.22.29.1: peer is unsynced
    Jan 12 20:00:16.121645 Kodi-WZ crond[1249]: ntpd: reply from 172.22.29.1: peer is unsynced

    Looks like an NTP error. Read here:

    MultimediaGuy
    September 6, 2016 at 12:17 AM

    Because Bluetooth is involved, it's not possible without developer skills:

    chewitt
    March 16, 2019 at 4:11 AM

    You can try this custom build for simultaneous audio output:

    xhbl
    November 5, 2022 at 9:15 PM