(2017-02-21, 11:32)contadino Wrote: @fritsch:
Ok, so i will have a look at the dirty regions management. Hope it helps a little.
Already enabled by default, you might gain a little by changing the dirty region algorithm, but don't think you will see a lot of different. Go look at the Kodi wiki for details on dirty region. One thing you will see is a setting for dirty region visualisation, this might point out if your skin is updating the screen when things are idle. One thing that can do this is scrolling text (which you should turn off in the skin if you can).
Quote:@wyrm:
Thanks for the info! Now it is clear, what causes the CPU-load. And that there is no hope to find another skin, which consumes less...
I like to think my skin is pretty light weight on system resources, but there is only so much that can achieve as we still have to display a set minimum amount of info on screen.
Quote:The only thing that i still don't understand:
When Kodi goes in sleep-mode (the screen gets darker), why does the system still collect infos 100 times per second? It could simply do nothing than waiting for an input.
But to change the actual behavior would cause a great coding effort i suggest?!
EDIT:
Maybe a "deep-sleep-mode" would be a good suggestion for a feature-request? 
You are incorrectly assuming how things work. As mentioned before by and large, Kodi runs a big game loop. For example
Game Loop
1 read user input
2 if movement
. move to appropriate item and read details from database if required
3 check if any displayable info has changed and update as required
4 starting at top of current screens skin file process tags and display output to frame buffer.
...
50 display frame buffer
51 return to 1
Event loop
1 If no event sleep
2. If event is top of frame
3 render screen
4. If event is timer event
5. execute timer action
6. If event is navigation event
7. update gui
...
Now what we currently have is more like the first example with a number of bits that are more like the second. Ideally what we want is the second example but to get there is going to take a very large rewrite of Kodi. So even if the screen goes blank, Kodi is still running thru the game loop so that the various things that need to happen, happen (this includes waiting for user input). As I said this is way way beyond my pay grade. Also I'm pretty sure we don't have anyone available with the knowledge, time and sheer bloody mindedness to currently make this happen. That and except for a very few people that realise just what a benefit this would be to Kodi there would be no apparent change to Kodi, so most users would not appreciate just what a heroic effort it was.
Wyrm
