Posts by DaVu

    The optical out on your TV might be only meant for its internal DVB-S receiver (if it has one). In a little bit I doubt, that a conversion from HDMI to some optical out (Toslink or S/PDIF) will work in that way using external devices.It could probably send the 2 channels to your amp where you might get DolbyProLogic IIx or something like that. But that´s 2ch PCM then and not a conversion from a bitstream coming from HDMI to some optical out.


    ARC is something different which is also able to handle external devices connected via HDMI. But ARC also has to be supported by your AVR. I nearly have the same problem. My AVR also isn´t ARC-capable and if I ever get a 4kTV I have to make my thoughts how to deal with that.


    In my case I probably consider some HDMI spliiter (1 in 2 out). So I´m able to send the audio to the AVR and the video to the TV directly.

    No there aren't any differences.


    If Kodi crashes there should also be a crashlog. But I guess we have what we need from the kodi.old.log


    7:31:19.912 T:1939132432 INFO: AddOnLog: Joystick Support: Disabling joystick interface "linux"

    17:31:19.913 T:1939132432 DEBUG: SECTION:UnloadDll(/usr/lib/kodi/addons/peripheral.joystick/peripheral.joystick.so.1.4.6)

    17:31:19.914 T:1939132432 INFO: ADDON: Dll Destroyed - Joystick Support

    17:31:19.914 T:1939132432 NOTICE: unload skin

    17:31:19.914 T:1939132432 INFO: Unloading old skin ...

    17:31:19.926 T:1939132432 DEBUG: ------ Window Deinit (DialogButtonMenu.xml) ------

    17:31:19.927 T:1939132432 DEBUG: ------ Window Deinit (Home.xml) ------

    17:31:19.929 T:1939132432 DEBUG: FreeVisualisation() done

    17:31:19.950 T:1939132432 DEBUG: Previous line repeats 1 times.

    17:31:19.950 T:1939132432 DEBUG: ------ Window Deinit (DialogBusy.xml) ------

    17:31:19.994 T:1939132432 NOTICE: unload sections

    17:31:20.003 T:1939132432 DEBUG: LogindUPowerSyscall - delay lock sleep released

    17:31:20.007 T:1742676848 DEBUG: Thread Timer 1742676848 terminating

    17:31:20.011 T:1939132432 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x129ef10 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

    17:31:20.012 T:1939132432 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1304a58 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

    17:31:20.012 T:1939132432 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x129c4f0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

    17:31:20.012 T:1939132432 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x128f930 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

    17:31:20.012 T:1939132432 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x129c338 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

    17:31:20.026 T:1939132432 NOTICE: special://profile/ is mapped to: special://masterprofile/

    17:31:20.026 T:1939132432 DEBUG: object 0 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 1 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 2 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 3 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 4 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 5 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 6 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 7 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 8 --> 0 instances

    17:31:20.026 T:1939132432 DEBUG: object 9 --> 0 instances

    17:31:20.036 T:1939132432 NOTICE: application stopped...

    17:31:20.036 T:1818211184 DEBUG: Thread CRBPWorker 1818211184 terminating

    Let's wait for a dev to jump in


    If you want to put the effort in it, please share the crashlog (if there is any) as well.

    Well...I can't see much in that log. Is that the kodi.log after the reboot? If so, we also might need the kodi.old.log which might show the error then.


    Kodi logfiles are safed in that way:


    current session = /storage/.kodi/temp/kodi.log

    last session = /storage/.kodi/temp/kodi.old.log


    So if you Kodi reboots and you will grab the kodi.log, then that's from the currently running session. Please show us both logs.


    Thanks and sorry for the effort you have to do.

    Unfortunately this is not a debuglog.


    If you are facing that problem more often but you can´t tell when it will happen (so hard to reproduce), I would recommend to enable logging via the advancedsettings.xml:


    Code
    1. <advancedsettings>
    2. <loglevel>1</loglevel>
    3. </advancedsettings>

    That should enable debug logging but without that annoying overlay on the screen.

    If it´s only Wetek -> HDMI -> TV it might highly depend on the EDID which is delivered and what options are available.


    If the chain looks like explained above there´s also no benefit of using passthrough as your TV only has 2 speakers. So it´s 2 channels anyway.

    "169.254.194.171" that looks like a strange IP address an ofc there´s no route to the host if the accessing machine is in a completely different network.


    169.254.xxx.xxx IP adresses are most likely given if the DHCP server couldn´t submit an IP to the machine (DHCP IP range low, DHCP disabled or whatever).


    So I would recommend to check which IP (for example) your laptop or desktop has and probably change the IP of the LE device manually to something else if you are sure the connection (wired or wireless) to your network at home is fine. For windows machines the command to check the machines IP adress is ipconfig.


    For linux based systems it´s ifconfig or ip a.


    Let´s assume your machines have something like 192.168.1.29 you can´t ofc use the same IP on the LE machine. You have to use something different. I wold suggest some higher number at the end. Try: 192.168.1.180


    Manually editing the IP adresses is done at the LibreELEC settings: LibreELEC Settings [LibreELEC.wiki]

    Anyway...without the log we can´t tell anything. The IPs shown in the log are only your internal IPs and should all start with "192.168.xxx.yyy". So there´s generally no problem sharing them. The IP from my NAS is 192.168.1.175 and you can´t do anything with that info ;)


    The log would tell us exactly what´s happening. The only thing where it might be kind of hidden is, if you might have set-up a cronjob doing the automatic library scan via some "kodi-send"-command or a JSON request. Then there should be at least something from Kodis webserver be mentioned in the log. But I guess you would know if you have done that, because that has to be done manually via commandline.

    Most likely a problem with your electric installation. Call an electrician near by and see if he can fix it. Not a general Kodi problem. And solving eletrical problems via internet forums is a PITA and also pretty dangerous. I´ve seen ppl writing pretty much nonsense and bullshit.


    Call an eletrician is the best advice one can give.