Quote:
Originally Posted by davidfor
That is expected behaviour when the database on the device is corrupt. When that happens, the database file cannot be updated. When something happens to force a reread of the database, it is basically reading an old version of the database. That means it doesn't have any changes since the last successful write, so no new books or reading status.
The device can run for a while with a corrupt database. Most of what you see displayed when looking for books is from in-memory structures. If the write to the database fails, the device will generally keep working.
|
Well, *I* know the database was corrupt, but getting Kobo to agree was another matter. They have stopped responding to my emails, and starting today, new notebooks have started to disappear. Four full factory resets later, I thought maybe I had finally got things turned around, but each time some new feature starts to behave erratically. It was never the same corruption.
Quote:
|
If you are using calibre, it can show an error when getting the list of books. But, the driver only reads a couple of tables, and depending on exactly where the corruption has occurred, it might not see it. You can do a check of the database to see if there are errors using any SQLite database manager. Or my Kobo Utilities plugin has a function to do it.
|
I didn't realize that was built into your plug-in. I'll try it out. I do recall seeing calibre errors in previous incarnations. The current one works fine with calibre.
…and a check of the database provided the following data:
Quote:
As to how the the database gets corrupted, the only way I know is not safely ejecting the device when the database is being updated. There has to be other times as people report problems and swear they always eject safely. There are almost definitely some mistakes, but, there are two may reports for it not to happen at some other time.
Signing out of the Kobo account on the device should fix this as a new database is created. And of course, a factory reset will do that as well.
|
In this case, considering that I factory reset from the dev menu four times, there was not an instance of me ejecting the device inappropriately, something I don't do. No amount of repairing the account, or logging out then back in, has made these glitches go away. There is a serious issue with my unit. Perhaps a bad memory module? I really can't say.
Quote:
|
When importing sideloaded books, they should be added in alphabetical order using the file name, which, for me starts with the title. When the books is added to the device, a timestamp is set in the database. For sideloaded books, the same timestamp is used for all books imported in the same batch. The "Recent" sort uses this timestamp or the last read timestamp and it probably sorts by title within these.
|
Although I often rely on this alphabetization when importing books to be added to a collection, when ALL books are reimported as if they hadn't been imported before, finding a dozen books alphabetized amidst 400+ books is a chore. This is what I was referring to. All books, including previously imported books, were being reimported without regard to that timestamp. However, I no longer have that problem. A full factory reset fixed it. Now I have disappearing journals, something that is frustrating since I drew on those pages and put a lot of effort into them.
FYI, I ran an undeleting program on the Kobo Elipsa when it was mounted on my Desktop, and it found all the missing *.nebo files. The only problem was that they were all 0 bytes large. They never properly saved to the internal memory. Here I thought I finally fixed it, then the glitch moved yet again. This time to an area I hadn't tested in over a week: notebooks. I have requested a new Elipsa pack from Kobo. Things are complicated since the US store showed that it was sold out earlier today.
Thanks for all your feedback.