x50: Shutdown image is not displayed on auto-shutdown

[GoogleCodeExporter]

Auto-shutdown (activated if device is in standby for x hours) does go through 
Fskin.window.doQuit, and standbyImage.draw is called (and finished) correctly. 
However, the screen isn't updated, and keeps showing the standby image.

Original issue reported on code.google.com by quisvir on 5 Dec 2011 at 11:06

[GoogleCodeExporter]

Additionally (not the same issue really), the fallback to system standby 
function doesn't work properly. If shutdown image is set to cover, and there is 
no current book, system option should be displayed (i.e. one of the selected 
wallpapers). However, this only works if the system standby function has been 
executed before in the same session (for instance, because standby image is set 
to cover, and that used the fallback to system).

Original comment by quisvir on 6 Dec 2011 at 9:42

[GoogleCodeExporter]

Second issue fixed in revision fc559cfcce. My attempts to fix the first issue 
have been unsuccessful so far...

Original comment by quisvir on 6 Dec 2011 at 11:22

[GoogleCodeExporter]

Have you tried to call Core.ui.updateScreen for timer-triggerd shutdown?

Original comment by Mark.N...@gentlemansclub.de on 7 Dec 2011 at 7:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

No effect :/

Original comment by quisvir on 7 Dec 2011 at 12:25

[GoogleCodeExporter]

So lets recapitulate:
When the shutdown is timer-triggerd the device is already suspended. 
(after kbook.model.suspend)
With unaltered firmware the screen is cleard by some IOCTL call at 
OS/shell-script level, after shutdown of the framework.

So it seems framework-functions (or hardware?-unlikely) to draw/refresh the 
display isn't accessible while suspended.

Maybe a strange thought: what about "waking" the framwork (kbook.model.resume) 
before shutting it down? 
But this can also result in some strange side-effects.
Check where is it called?
    StandbyImage.draw called in hooked Fskin.window.doQuit(), before the actual call to the system-function.
And Fskin.window.doQuit() is also called by manual shutdown. And at this moment 
the framework is active.

So, don't know where this leads...

Original comment by Mark.N...@gentlemansclub.de on 7 Dec 2011 at 2:57

[GoogleCodeExporter]

That's a good idea! I'll do some experimenting tonight. I'm thinking, do a full 
resume (hopefully in the background), then give the _regular_ shutdown command. 
If it works, there shouldn't be any side-effects. Thanks again Mark!

Original comment by quisvir on 7 Dec 2011 at 6:12

[GoogleCodeExporter]

It worked! I couldn't get it to wake up with 'manual' commands, so I've 
resorted to bubbling the power switch. Will push the new code in a bit.

Original comment by quisvir on 7 Dec 2011 at 9:25

[GoogleCodeExporter]

Fixed in Revision 1be7524b7a.

Original comment by quisvir on 7 Dec 2011 at 9:31

• Changed state: Fixed