Kobo Glo HD does not maintain reading position

[fbrII]

Anybody else having this problem, anybody found a solution?

Often after reading and then turning my reader off, when i next open it, it will be on the wrong page normally at the point I started the previous session but sometimes even further back then that. This also happens requently when changing from one device to another, like an e-reader to my tablet or vice-versa

Also, hitting the sync button will not bring me to the position where I left off last either. Any thoughts or suggestions?

[davidfor]

Firstly, the Kobo ereaders only sync reading positions for kepubs purchased from Kobo. These books and status will sync to any other Kobo device or app logged into the same account.

Losing the reading position for books usually means the internal database on the device is corrupt. The database stores details of the books and is updated with the reading position as you read. If it is corrupt, then the changes do not get written to the database. When you restart the device, the corrupt database is read and it contains old reading positions.

If this is the case, the solution is to sign out of the Kobo account on the device and back in. This will create a new database and load the book details again. You will lose the reading status and position for all sideloaded books, but they should be updated correctly as you read again.

[Ripplinger]

How far off from your last position are you when you reopen the book? I've read of a few instances where someone with a cover with a flap on it would accidentally turn pages a bit while closing the cover (the flap would brush against the screen barely but enough to flip pages).

I've never once had that happen on my Glo HD, even on the rare occasions that I turn it off. I just about always put it to sleep and not turn it off though. Have you tried just letting it sleep instead of doing full shut downs or is there a reason you prefer shutting down? It's a minimal battery drain when in sleep mode, and waiting for any reader to start back up again always drives me nuts . Sleep means you begin reading instantly when you open the cover.

[fbrII]

How far off from your last position are you when you reopen the book?

Very rarely is it a matter of a few pages. Most often it is where i started the previous reading session rather than where I finished. But I have had it open up like at the second or third chapter when I maybe near the end of a book. It is almost if not always at a previous reading position (one where I had quit) but often not at the most recent position. I switch between different e-readers so one may sit for a week or two so that's how I got into the habit of shutting down.

I will go back and to just letting it sleep and see if i get different results.

Thanks

[fbrII]

If this is the case, the solution is to sign out of the Kobo account on the device and back in. This will create a new database and load the book details again. You will lose the reading status and position for all sideloaded books, but they should be updated correctly as you read again.

If sleeping rather than shutting down doesn't resolve the problem - i will give this a try.

And thanks for the input

[davidfor]

Originally Posted by fbrII

If sleeping rather than shutting down doesn't resolve the problem - i will give this a try.

If I was a betting man, I would put money on the database being corrupt. Using sleep will probably solve the immediate problem. But, if the database is corrupt, you will eventually run into more problems. Sooner or later you will need to fix it. If you want to, you can check the database using an SQLite management tool, or, if you are a calibre user, my Kobo Utilities plugin.

[fbrII]

If you want to, you can check the database using an SQLite management tool, or, if you are a calibre user, my Kobo Utilities plugin.

Gave it a try - report came back with db OK. I have been reading in another reader lately so I have not tried sleeping vs shut off - so that will be my next try. If it solves the problem I will post again so anybody having a similar problem now or in the future can also resolve the issue.