(2017-06-20 23:10)pemartins Wrote: I have no idea how to do such a thing nor if it can be done, browsed around a bit but found nothing useful. But there's really no point, if it is "nonsense" then it is what it is.
If that's not the problem/solution then theoretically you still have a solution, if things worked great in Kodi 16.1 and now work badly in 17.x and newer, at least theoretically all you gotta do is undo the changes made and it all should work great again.
There as been A LOT of changes between kodi 16.1 and kodi 17.x
Removing all of them would only lead to goes back to kodi 16.1 (what you could already do by simply staying with kodi 16.1 obviously)
Now here is the thing: what you think should be the cause of the issue should not be it because your avancedsettings value were exactly the same than the ones kodi uses by default
But maybe default value is not applied correctly in kodi
Or, like da-anda said, applying it with advancedsettings may cause the CPU frequency to raise. In this case it would be a wild comparison between 10% usage at x GHz and 69% at y GHz
The only way to know would be to force the CPU to run at the same frequency no matter what