[davidfor]

Originally Posted by msegt

Thanks for trying to help, but if I were you I wouldn't assume things that fast (just for the record, I know more about databases than what you might think).

If we are going to whip them out and compare, then the first relational database I used was DB2 V1. Though I might have used one of the last beta's. But, yes, I assume that people no nothing until they prove otherwise.

I'm a Calibre user indeed,

Yes I am to. And guess who maintains the KoboTouch driver?

and the database is not corrupt

You tested it? Don't rely on the driver reporting an error as it depends on exactly what parts of the database is corrupted.

it seems it has something to do with the update as the progress shown in the home page is the one that was at the time, and maybe a cache somewhere that is keeping that progress in the device for every specific book.

Yes, the data is cached while the device is running. But, that is discarded when the device is restarted. The database is reread at that time. If the database hasn't been updated properly, because the device crashed or the database is corrupt and couldn't be updated, then the last set of data written is read from the database. Hence, each time you restart, an old set of data is used. If you don't restart the device, you don't see this happening. That means a lot of people think the corruption was caused by a firmware update because that is the only time the device is restarted.

It doesn't have to do with my Kobo account either.

I never said it was. I said signing out of the device and back in was the way to fix the problem.

I'll probably try to play around with the reader in the summer to try to fix the issues, but it's definitely been caused by the update,

I'm willing to put money on it being a coincidence.

and it's very annoying that it's not an isolated case

Can you point to other similar cases so I can look at them? Maybe there's something going on that I haven't seen, or have seen and haven't connected to your symptoms.

and nobody at Kobo seems to care..

I'm also willing to put money on this being wrong. But, there's probably no way to prove it one way or the other. Unless maybe a fix for something that people say that Kobo don't care about suddenly turns up.

PeterT's suggestion about the time is something to check. I don't think your description fits this, but, it is a cause for why the book currently being read is not the first book on the home screen. Unless the book you are reading is a purchased kepub and the status is syncing to the Kobo server. That will cause this problem as it will use the reading position with the latest timestamp.

And if it is a purchased book, it could be that the time on the device was set far ahead at some point. I did this once where I accidentally set the date a year ahead. The book I was reading was a purchased kepub and it synced with that time. When I fixed the date, the book kept trying to reopened to the point I was reading when I fixed it. When I finished the book, I had to delete it from the device as otherwise it always appeared at the first book on the device. If this is the case, you can look at the timestamps in the database, or turn WiFi off and see if it happens while the syncs can't happen.

And just to be clear, you reported a problem. I gave you the most common reason for that problem to occur. Plus a fix. If that isn't the reason, then we need more details so we can work out what is wrong. And those details could include, "I teste the database and it isn't corrupt."

In my reader it doesn't matter what lighting level you are using, it goes to 1% when in sleep mode always, and to turn it off I need to use the slider from the top menu (but it'll go back to 1% on it's own eventually, so I just decided to give up and power it off when I finish reading).

I was asking for information to try and work out the pattern. I don't see the problem on my devices no matter what I try. The reports here haven't been detailed enough to come up with a pattern, but what I asked seemed to be a common behaviour. Thanks for giving a counter example.