PVR manager is starting up at 0% forever

[IcePlanet]

After installing enigma2 plugin and trying to run TV in the upper right corner there is

PVR manager is starting up 0%

and rotating circle forever.
In the log I see message that channels have been loaded.

What I tried:

1. Uninstall and install Kodi again, but the plugin is back also remembering all configuration.
2. When I try to uninstall the plugin itself from Kodi UI it freezes and after killed by android the plugin is back with all configuration
3. I deleted the cache from within Kodi settings (no change)

Phone used is Samsung S10 running on Android 10
Network is reachable, confirmed by opening webif
Attached are logs from uninstall attempt and from the pvr manager is starting with 0% foreve

Log from PVR manager is starting up 0%:
kodi_loading.log

Log from uninstall attempt:
kodi_uninstall_enigma2.log

I'm not using it very often, but I'm sure some time ago (unfortunately I'm not sure how long the time is) it was working flawlessly.

[phunkyfish]

It looks like it's still reading the EPG data. Can you use a paste site and provide a full debug log? So a debug log from a restart until it's started up. You can use a GitHub gist of the file is large.

[IcePlanet]

@phunkyfish I'm not sure what are you missing in the logs. They are (as uploaded in my first message) complete. I have now downloaded them and checked sha. This is how I got them from kodi.
In kodi I setup the debug log as following:

• Enable debug logging YES
• Enable component-specific logging NO
• Enable event logging YES
• Enable notification event logging YES

Out of curiosity I started now my notebook with Kodi, it was for sure working there, but I was long time not using it, and it has the same symptoms.

I also checked the last cca 3-5 links from the log and all are accessible and giving result.

[phunkyfish]

Sorry, my mistake!

[phunkyfish]

Can you try starting Kodi, leave it for 10 minutes and then post the debug log?

[IcePlanet]

This is problematic (I have already tried multiple times) because when I leave the TV screen on it freezes hard and windows kills it, I can leave it max cca 30s to 1min then I must move to another screen in kodi.
On android the behavior is the same, if I have the TV screen open for long it seems on, but it's dead and I'm not even able to open the 3 buttons down, the only option that works is reboot of device via power button.

For each freeze I got this screen twice (if it helps).

[phunkyfish]

That is very strange. Are you able to try a kodi 19 nightly?

[IcePlanet]

Yes, no problem tried: KodiSetup-20200322-6b1585df-master-x64.exe the result is still the same + new issue, kodi can not be switched off with the enigma2 plugin (seems like it is really trying to do something in background), it hangs and windows shoots it down.

BUT I have downloaded kodi-17.0-Krypton.exe (yes I know it is old but I remembered that it was working previously so wanna try), which is bringing the vu+/enigma plugin within install file and it works on first attempt flawlessly (configured IP and port that was all). TV was on in cca 10 seconds with all channels.

Is it possible to trace the changes in meantime or it is too many changes? Or is there any other way to trace the change causing this strange behavior?

[phunkyfish]

It’s because it never finishes starting up. Have you tried clearing the PVR database?

[phunkyfish]

Or deleting all setting and starting up from scratch?

[IcePlanet]

On Windows tried to delete everything found (The nightly and 17.0 have been both installed the same way: uninstall previous one, in total commander delete everything what 'looks like kodi' and then install), everything works until the enigma 2 is activated (situation is the same in 18 and 19).

On android as I have written previously there I'm not aware how to do clean install as the enigma2 client has survived everything tried until now.

Cleaning PVR database via 2 approaches found:

1. Delete TV.db and epg.db (not sure about this 2nd file name)
2. In Kodi go to setup, pvr & live, General, Clear data

None of the 2 deletions above worked in nightly or in actual stable 18.

[IcePlanet]

Maybe how the problem can be identified is to compare plugin from 17 (named vu+/enigma2) with new one from 18.
When the 17 needs 10seconds and 18 freezes after minute (the same computer, network, box) then I believe it is worth to look at time in detail what takes how much time. I'm happy to do it, however do not know where/how to start, can someone help and guide me?

In the meantime the solution with downgrading on android did not work as the plugin can not be loaded (unknown error message), can someone please tell me where to delete and what to get rid of the new plugin?

[phunkyfish]

Have you been able to you delete the addon settings?

I’m sorry. I only started working with the addon from v18 so nothing nothing about it prior to that.

[phunkyfish]

Is kodi actually crashing or is it just freezing?

[phunkyfish]

If you have remote access configured I could try and debug it remotely. PM me on the forum it this is possible.

[IcePlanet]

@phunkyfish thanks for the interest and willingness. We can try to setup some debug session, but now I'm at work :-) so maybe later in the evening.

To your questions:

• Android add-on: No I was not able to delete, it stays there (including configuration) and resists any attempt to delete (after uninstall the kodi folder data/org.xbmc.kodi/ is gone so I do not understand where it can survive)
• Kodi on android is freezing whole android and only power button reacts (restart or power off device)
• Kodi on PC is "stopped working" so the circle is rotating, mouse moving, but nothing else and after cca 1 min the windows will kill it

What I have made is test with kodi 17 and VU+ /enigma2 plugin on windows:

1. When I press Kodi in start menu I started stop watch
2. At 04.38 I pressed TV in kodi interface
3. At 7.23 I selected channel
4. At 13.86 the channel was playing (audio + video)

When kodi 17 is able to get playing channel in 14 seconds I would like to hope that 18 will be able to achieve comparable result (if not faster). Maybe there can be something identified in log to understand where is the difference. Attached is complete log from this attempt on KODI 17. (all tests on windows have been done from the same machine, on the same network and to the same sat receiver):
kodi.log