Thread: Debug logs on KA1?
View Single Post
Old 10-20-2017, 11:58 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
From what I have seen, the problems that cause the device to restart don't tend produce a trace log. The crash and restart happen in such a way that the log can't be written.

What's the problem you are seeing? It should fall into one of two types. Either an immediate restart, or a hang followed by a restart after some time. I can't think of he last time I saw the first for a book. The last one I do remember was for some Pocket articles. This was fixed in 4.6.9960.

The other type is triggered by sickel. It is a process monitor and will restart the device if it sees that a process is no longer responding. The last one of these I can think of was is a problem with kepubs with a lot of chapters. This seems to have been fixed with 4.6.9960 as I haven't been able to reproduce it recently.
davidfor is offline   Reply With Quote