I have a problem whereby after resuming from hibernation the system doesn't start responding until after there is input from the user such as mouse movement or a key press. To say it is frustrating is a bit of an understatement.
Originally I thought it was a bug with the front end I use Centrafuse so I created a thread.
After a bit more investigation it seems as though there are other threads with exactly the same problem in other front end sections
RESUME after hibernate frodoplayer paused until user input
So I thought that I would create a more generic thread in this section so that it gets a bit more exposure and hopefully someone can help come up with a resolution.
Can anyone think why the system would just hang after resume and then just spring to life perfectly as soon as a small mouse movement is made?
It seems that possibly whatever those players are using to know that you have resumed from hibernation isnt triggering until you move the mouse/provide some kind of input to the operating system. This afternoon I'll play around with some WS_SHELL hooks and see if it's possibly one of them. It'd be interesting to find out of there are any similarities in how the effected different frontends detect going in, and coming out of hibernation.
What is frustrating is that if I use a different mp3 player it resumes from hibernation fine and continues playing. But when using Centrafuse it doesn't. Like malcom2073 said, it's like all the frontends are using a similar method for their resume process that isn't quite working.