View Single Post
Old 05-15-2016, 06:33 AM   #158
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
The next update of KSM 08 will contain an option to log suspend data. As somebody might like to try it already now, I upload a preliminary version of it. The suspend data will be logged, if preventfreeze.sh is running. In the final version, there will be the option to run preventfreeze.sh without or with logging suspend data.

In order to read the log:
(KSM home) "tools" > "explore" > "explore kbmenu.msh" > "log" > "suspend log.txt"

Note: You can enable/disable preventfreeze by setting "[general]preventfreeze" to true or false with the help of "configure." (The default setting is "true.")

Here is a sample log:
Spoiler:
###
2016:05:15_11:32
suspend started: Sun May 15 11:30:47 CEST 2016; duration: 0d:0h:1m:13s
battery before suspend: 100
battery after suspend: 100
start_nickel.sh
nickel
sickel-launcher
###
2016:05:15_11:35
suspend started: Sun May 15 11:34:08 CEST 2016; duration: 0d:0h:0m:55s
battery before suspend: 100
battery after suspend: 100
reader.lua
###
2016:05:15_11:40
suspend started: Sun May 15 11:35:30 CEST 2016; duration: 0d:0h:4m:33s
battery before suspend: 100
battery after suspend: 100
launcher
###
2016:05:15_11:44
suspend started: Sun May 15 11:41:48 CEST 2016; duration: 0d:0h:2m:14s
battery before suspend: 100
battery after suspend: 100

Below the line "battery after suspend: ...", can appear a list of select running processes that could give you a hint which application triggered suspending. In the sample log, the first suspend was triggered by nickel, the second by KOReader, the third by PBChess, the fourth (no processes listed) by KSM. Very short periods of suspension will not be recorded at all.

Note that the time recording is not very precise. But since you are probably interested in longer periods of suspension (hours or days), this should not be a problem.
Attached Files
File Type: zip KSM08_log_suspend_data.zip (895 Bytes, 256 views)

Last edited by tshering; 05-15-2016 at 06:39 AM.
tshering is offline   Reply With Quote