Quote:
Originally Posted by irreld
Yeah, That's REALLY a bad habit. Now I realized kindle is NOT as easy-going as any of my Android device.
After OTAed to 5.7.3 from 5.7.2.1 my battery only lasted two days with almost no use. So ps -e to find cvm using more cpu time than usual. vmstat said only 89% time cpu is idle. That's weird, and no index was seeming to be rebuilt. It seemed something prevented kindle to sleep. When I deleted my 120+ books, I even found several files won't delete from Windows.
|
That is (was) a PW-2 on 5.7.3 - similar to other reports here.
Also observed on my PW-3 on 5.6.1.1 - as high as 98% cpu time used while showing a screen saver.
After indexing 4 books (not 120).
See:
https://www.mobileread.com/forums/sho...0&postcount=33
Use the top command embedded in that post to see the framework threads (including the cvm threads).
1) The indexer was re-designed (well, at least re-implemented) with the 5.6.x series firmware and may still not be a 'stable' implementation (translation: lab126 may still be playing with it).
2) The old "search for garbage" test to see if the indexer is done no longer works (since the new indexer never really stops - it is just throttled now).
Quote:
Originally Posted by irreld
That's all my experience, and finally, a factory reset ruined everything. Ah.
BTW backdoorlockhack somehow failed to keep me in 5.7.2
|
Firmware since early in the 5.6 series (5.6.2...?) is known able to defeat the backdoor lock.
But this (revised old one) does work on 5.6.5 and is being tested on 5.7.x:
https://www.mobileread.com/forums/sho...&postcount=269
See post 4 of this thread if you haven't already seen it.
Note: Only the color Kindles run Android.
The grayscale devices run "Amazon Linux".