View Single Post
Old 01-08-2016, 08:24 AM   #207
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 roger64 View Post
Of course, the Koreader way is better: you check when you wish to update, you are told there is -or not - an update available (stable or develop channel) and you go for if you wish.

Thanks for your reply.
Hmm...
Reads like you answered your own question better than I did.

This BackDoor Lock works with (or against) the Amazon automatic updater.
KOReader does not use the Amazon automatic updater, it provides its own update controls.

= = = =

In fact, given a moment or two to think about it - IIRC:
I think that KOReader's start-up on a Kindle device stops the Framework daemon.
And it is the Framework daemon that handles the forced updates.

Last edited by knc1; 01-08-2016 at 08:27 AM.
knc1 is offline   Reply With Quote