Posts by DaVu

    Have you done specific changes to the whitelist option? Probably disable the 25fps option for the specific resolution?

    If the stream does something strange we can´t do much. And just for the note. There are a bunch of illegal streams you are using. Seeing the HBO streams which normally need to be paid. Receiving them for free is nothing I would call legal.

    So please don´t expect too much of support while using IPTV simple in a very grey area

    you could try to rename the guisettings.xml and see if that fixes something.

    ssh in and try mv /storage/.kodi/userdata/guisettings.xml /storage/.kodi/userdata/guisettings-old.xml

    Then reboot.

    If that doesn´t help, I fear that we need to reset the Kodi installation completely by doing:

    mv /storage/.kodi /storage/kodi-backup

    then reboot

    With that change you will end up with a vanilla Kodi but all previous settings, changes, addons and such are stored in the "kodi-backup" folder. So they are not gone completely. You should be able to move specific TVH files to their new locations in order to not setup TVH from scratch completely. Probably CvH is able to tell you which files need to be copied to which location.

    lusum

    Please check with existing Kodi addons if the coding style is correct. The PRs I send you are only those things I saw at a first look.

    If you PR your add-on to the Kodi repo and if something needs to be fixed, I'm sure the reviewers will tell you what you need to change.

    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
    <advancedsettings>
      <loglevel>1</loglevel>
    </advancedsettings>

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