futeko.com FORUM

Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: mulderfox on November 26, 2019, 10:36:33 AM

Title: Q10 Pro :Kodi 18.x keeps crashing on either Official or Custom FW 2.1.4
Post by: mulderfox on November 26, 2019, 10:36:33 AM
https://www120.zippyshare.com/v/2DcWCUDl/file.html (https://www120.zippyshare.com/v/2DcWCUDl/file.html)

Hi!
This link contains my logcat.log file, which I created while retracing steps to recreate the recurring crash. I simply watch something for a while, then exit (or let it finish) and start navigating Kodi around - ending with a crash to the desktop.
I've sent this to pcristi, but I know he is quite busy, so I'm using the crowd's wisdom, in case anyone can analyze this and point me in the right direction to fix it.

Thanks!
Title: Re: Q10 Pro :Kodi 18.x keeps crashing on either Official or Custom FW 2.1.4
Post by: stl on November 26, 2019, 08:01:59 PM
The latest beta version isn't crashing on my Q10 Pro
Title: Re: Q10 Pro :Kodi 18.x keeps crashing on either Official or Custom FW 2.1.4
Post by: mulderfox on November 28, 2019, 05:10:53 AM
Quote from: stl on November 26, 2019, 08:01:59 PM
The latest beta version isn't crashing on my Q10 Pro
I'm using the latest version (18.5), but the same thing happened all the way since 18.0
Title: Re: Q10 Pro :Kodi 18.x keeps crashing on either Official or Custom FW 2.1.4
Post by: mulderfox on December 19, 2019, 02:24:10 AM
Just a quick update:
It seems the culprit is Kodi itself.
I've first tried to replace it with SPMC, but SPMC - development having been halted - is stuck at version 16.x and has some issue with its scrapers.
So, I've went to look for other Kodi forks, and found WBMC The version is the same as the latest kodi (18.5), but functionality for me is way better.
Skins work correctly, no crashes so far. copied over the playerfactory XML file from Kodi, so wrapper also works fine. The only thing was that the music scraping did not work properly, and I resolved it by deleting the mymusic db file, and let the system recreate the database.
Now all seems to work fine.

Just FYI for people who encounter similar issues.