Thread: Firmware 4.31.19086
View Single Post
Old 02-08-2022, 07:27 AM   #264
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 icallaci View Post
I suspect rebooting the reader might force it to reset or reread the database.

I am starting to see a pattern with this firmware. My problems seem to occur after I sideload one or more books, then eject the reader. The next time I connect the reader to the computer, I see the prompt to scan the reader for errors. If I let it scan and fix, no errors are reported. However, the reader then displays random weirdness, like not updating my reading position. So I did an experiment: I sideloaded an ebook, then ejected the reader and powered it off, then powered it back on and reconnected it to the computer. No scan prompt! I've done this several times now, and as long as I reboot the reader after sideloading an ebook, I have never yet had a prompt to scan the reader for errors. Also, the reader has not lost track of my reading position either.

Could it be the database is not being updated for sideloaded ebooks? I have also noticed problems when I delete a book, but I haven't yet tracked down the exact circumstances. For example, I don't know if deleting an ebook from the reader while connected to Calibre as opposed to deleting it from the reader while it is not connected to the computer makes any difference.

Anyway, I wonder if turning the reader off and then on again after sideloading books forces it to reread or reset the database. Just a thought.
The scan is triggered if the dirty flag on the filesystem is set. It's probably that the reboot is clearing the dirty. That should be checking the filesystem and if there are no issues clear the dirty bit. Or it could be cleared during the shutdown.

I have done some testing and it appears that when I sideload an epub, the next time I connect, I get the scan prompt. It doesn't happen with kepubs or PDF. I also tried downloading an epub using the browser, and had the scan prompt when I connected the next time.

That makes it look like the import of epubs is the culprit. My guess would be a process is left open that is keeping the filesystem open when connected to the device. The shutdown would close the process and let the filesystem close properly. That is also consistent with using calibre to replace a book. That avoids the import process.
davidfor is offline   Reply With Quote