Start kodi -> exit kodi -> complete freeze no react to anything, killed Log:.Start kodi -> TV -> PVR manager is starting up 0%, wheel is rotating, mouse moving but that's all Log: kodi19_20200322-6b1585df_PVR_0.log.Start kodi -> Download enigma2 -> open settings -> Connection -> Change IP to 192.168.43.81 -> OK -> Dialog box of enigma2 client that it needs to restart -> Clicking OK -> Complete kodi freeze, no mouse movement all dead -> Killed via via task manager Log: kodi19_20200322-6b1585df_install.log.Start kodi -> activate debug log -> exit kodi (all OK no log).I know it is very vague suspicion, but it is only idea. In the evening I would try to look in the source code, but my suspicion now is reading loop that is not terminating as should, fetching the data multiple times without cleaning 'some' variable prior to next loop. It got the data and they are of the same size (4335). Length: 4335Īnd here is the file I got if I put it in chrome (file is XML, only renamed to txt as gui did not like xml): Why it is fetched twice, isn't there "wrong" loop?.Why it is not there? It is the same URL and it has already once returned the data.22:42:52.408 T:25358 WARNING: CPeripheralBusAndroid: failed to update input device with ID 7 because it couldn't be foundĪt line ~5800 I would expect same text as at line 2364. 22:42:52.408 T:25358 WARNING: CPeripheralBusAndroid: failed to update input device with ID 4 because it couldn't be found 22:42:50.208 T:25569 DEBUG: Thread Timer start, auto delete: false 22:42:49.750 T:25447 INFO: AddOnLog: Enigma2 Client: pvr.vuplus - GetHttp Open webAPI with URL: '' Length: 4335īelow are the lines 5795 to 5804 from kodi_loading.log (v18): 22:42:19.038 T:25447 INFO: AddOnLog: Enigma2 Client: pvr.vuplus - GetHttp Got result. 22:42:19.037 T:25460 INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?) 22:42:19.037 T:25460 DEBUG: Thread FileCache start, auto delete: false 22:42:19.015 T:25447 INFO: AddOnLog: Enigma2 Client: pvr.vuplus - GetHttp Open webAPI with URL: '' (all tests on windows have been done from the same machine, on the same network and to the same sat receiver): Attached is complete log from this attempt on KODI 17. Maybe there can be something identified in log to understand where is the difference. 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). At 13.86 the channel was playing (audio + video).At 04.38 I pressed TV in kodi interface.When I press Kodi in start menu I started stop watch.What I have made is test with kodi 17 and VU+ /enigma2 plugin on windows: 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.Kodi on android is freezing whole android and only power button reacts (restart or power off device).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// is gone so I do not understand where it can survive).We can try to setup some debug session, but now I'm at work :-) so maybe later in the evening.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |