View Single Post
Old 05-02-2017, 12:37 AM   #68
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by nooboo View Post
I've done a factory reset at least 3 or 4 times already. The problem goes away for a day or two, then comes back.

I don't know much about caches, but which of the following would likely clear the cache?

1 - resetting Kindle - yes?
2- restarting Kindle - yes?

3 - changing font or font-size - maybe ???
4 - closing book & opening a new book - maybe ???

5 - going back to Home page - no?
6 - putting Kindle to sleep then waking up again - no?

Any other thoughts?
1 = yes
2 = yes
3 = yes (rebuilds new font cache, then renders current page, in-validates other cached pages)
4 = only if it causes a '3'
5 = no (because if you go back to book, you go to the last page opened)
6 = no (because there is no 'reset' or 'restart' involved, only suspend (freeze everything) and resume (unfreeze every thing).

Since the reader is closed source, the above is only what can be reasonably expected.
But that does not mean the programmer who wrote it was doing what is reasonably expected.

Last edited by knc1; 05-02-2017 at 12:47 AM.
knc1 is offline   Reply With Quote