Quote:
Originally Posted by jgoguen
I suspect the high CPU process will be the Adobe ePub renderer or the ACCESS KePub renderer.
|
My initial tests confirm this, but the point is less to find out what is causing it as when it is triggered. At least, presuming it's not a run-away auxiliary process.
Quote:
|
Also, how are you defining "high CPU"?
|
... a very important question. For the purposes of this issue, it would be anything consuming cpu continuously (i.e., >50%) when the device should be idle. But unfortunately busybox ps doesn't seem to give a cpu%, so I'll settle for anything that has used >10 seconds or is changing continuously.
Eliminating things with cpu used of 0:00 gives a pretty short list, but I've experimentally been using this as a filter:
Code:
ps | awk '$3!~/^0:0/'
Quote:
Originally Posted by geek1011
grep -Er . /sys/class/power_supply/*/uevent
|
Added that to my script.
Quote:
|
It would probably also be a good idea to record the CPU usage too.
|
You mean from ps like I did above? or did you have something else in /proc in mind?
(...record book and position...)
Quote:
Originally Posted by geek1011
That would be more something for NickelDBus
|
...
Quote:
|
it wouldn't be hard to also make it return the book's URI.
|
That would be a welcome addition to the script.
I just looked at NickelDBus yesterday, lots of interesting stuff there.
I'm sure extracting current book and position might be useful for other things too.