View Single Post
Old 06-21-2015, 04:16 PM   #383
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by xor_ View Post
I noticed both KSM and koreader use suspend to RAM in their suspend scripts. What is the reason for not using suspend to disk?
KSM just used the same calls as nickel did at that time. Suspending to disk would heve been more time consuming. And in the case of KSM, where there is no point in saving its state for an extended period of time, simply powering off would be preferable to suspending to disk.

Quote:
Originally Posted by xor_ View Post
And when I send my device to sleep through the magnet cover mechanism, who handles that? Is that the suspend script in koreader / KSM, or something else?
In KSM, the suspend script is still existent, but it is never called. You would have to make some effort to call it manually.

As I see it, the power consumption during suspend (when you the script from KSM, and I guess it would be the same with koreader) is as it should be, namely close to none. The problem however is that something finishes the suspend state untimely. See this post and especially the log in the spoiler.

Last edited by tshering; 06-21-2015 at 04:32 PM.
tshering is offline   Reply With Quote