2015-05-12, 23:13
Hello Community
i'am using Kodi with LiveTV for a long without problems. The only thing comes up after i moving the tv-backend (tvheadend but i testet it with other ones) on my main server. The server is running 24/7 -> so i bypass the whole "wakeup for some recordings" and only one device is running in the middle of the night.
But i'am now encounter the problem, that after a wakeup from a suspend (S3/S4 doesn't matter, as long as Kodi isn't restartet) Kodi tries to use the "old" connection, who is closed by the Backend (or my networkd-devices) because of the timeouts. Kodi react to this problems in "various" ways. Sometimes it's reconnect (ugly but ok), sometimes it crashes or it completely stalls. I quess it matters how the "network" react to the "usage" of a killed connection.
As a workaround i attached a script who stops Kodi before going to sleep and starts it after wakeup (btw Kodi start faster than my TV wake up...).
Can some else reproduce the problem ?
i'am using Kodi with LiveTV for a long without problems. The only thing comes up after i moving the tv-backend (tvheadend but i testet it with other ones) on my main server. The server is running 24/7 -> so i bypass the whole "wakeup for some recordings" and only one device is running in the middle of the night.
But i'am now encounter the problem, that after a wakeup from a suspend (S3/S4 doesn't matter, as long as Kodi isn't restartet) Kodi tries to use the "old" connection, who is closed by the Backend (or my networkd-devices) because of the timeouts. Kodi react to this problems in "various" ways. Sometimes it's reconnect (ugly but ok), sometimes it crashes or it completely stalls. I quess it matters how the "network" react to the "usage" of a killed connection.
As a workaround i attached a script who stops Kodi before going to sleep and starts it after wakeup (btw Kodi start faster than my TV wake up...).
Can some else reproduce the problem ?
