|
That must be frustrating -
you will have to isolate the specific books that is causing the issue to return. i may case it was easy because reading beyond a certain page was crashing the reader.
also, I found that the "all notes" application was crashing but I could go into a book, then into notes for that book only & thus rule out that book if the latter setup worked OK.
I also found, prior to deleting the .db, that trying to create new note in a different book by same author as the problem book was causing a crash at the "create note" stage.
I have had no further problems after deleting the corrupt .db. At first I did carefully create noes - 1 per book, 1 at a time & kept going back to "all notes" to check everything as still ok. but recently I've begun trusting it again.
Try this:
if you load each suspect book into ADE v2 on PC then scroll quickly thru the entire book, that tests whether there's anything in that book that would crash the T3. you can scroll an entire book on PC in a few seconds, much quicker than turning every page on the T3
I suspect that because of how the /db works, using pointers into the books, if there is any issue with , say, calculating total length of a book, then the pointers don't get properly created.
but also I'd not expect the .db to corrupt unless a crash occured wile that file was in use
|