View Single Post
Old 08-21-2012, 12:42 PM   #22
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,429
Karma: 10764602
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by ixtab View Post
It's very unlikely that doing "something wrong" (tm) with the diags kernel/partition would affect the battery when running in main. In fact, it's completely impossible IMO.

One could just as well wipe out the diags kernel and partition completely, or install Super Mario instead, or... well you see where I'm going - it just wouldn't affect the Kindle running in normal operation mode, because the normal mode doesn't touch anything "diags".
I agree that diags code should not affect main. I do not know which partitions he had messed up, but putting all the right ones back where they belong seems to have fixed it. My concern was a mismatched main partition and main kernel might cause power saving features to misbehave while in main.
geekmaster is offline   Reply With Quote