View Single Post
Old 07-23-2014, 08:40 PM   #5
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by topcat07 View Post
have been turning device fully off

if i put it into sleep mode would i get this problem ?
It possibly would help. One of the reasons for seeing strange things like this is that the database on the device has become corrupt. In this case, the current reading position doesn't get stored correctly. As long as the device is running, everything seems OK. But, when you power off, the database isn't written to memory and when it turns on, old data is read. It sounds like the book is reopening to a spot near the last place you were reading. If that is the case, it suggests the database is OK, just that something is going wrong in calculating the position to open to.

So, some questions:

- Is this just one book, or all books?
- What format? epub, kepub, sideloaded kepup, PDF? For sideloaded kepubs, are they being sent from calibre via the KoboTouchExtended driver?
- Is the position always off by just a few pages? Does it get worse further along in the book? Does it reopen to the beginning of chapter correctly?
- If you use the table of contents or the navigation bar, does it go to the right place?
- What firmware version are you running?

There has been at least one firmware version that showed a problem like this. I think it was one of the 2.3.x versions. That had a problem that sounds like this one if the margin on the device was not set to the minimum. That has been fixed and I haven't heard of anything similar since.
davidfor is offline   Reply With Quote