Quote:
Originally Posted by hobnail
imagine that a specific location in some book causes the reader software to freeze. At least then you could reboot and try again, only to have it freeze. But as it is now at least you have a way out by rebooting.
|
That "resume" file must be:
- Created when you power down
- KOReader actually should create it by intercepting the power down
- Deleted after a resume
Now, if KOReader is frozen, no interception, no creation.
Another approach would be to ask the user if they want to resume when such file exists. This whole resume "feature" can be guarded by a non-default option.
I have to say, I've never ended up in a frozen loop with my other device though.