Thread: Firmware 4.32.19501
View Single Post
Old 05-02-2022, 11:07 PM   #412
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: 47303826
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ownedbycats View Post
I did a bit more testing and connecting from within kepub does seem to cause issues (scan&fix prompts, and database changes made with Kobo Utilities during one of those connects often don't seem to take -- but I'd expect some kind of error if it was mounted read-only).

Thankfully that's well easily avoidable and I haven't been able to repeat the database corruption from earlier.
From what I can see, the frequency of Windows prompting to scan the device is back to the pre-4.31 status. It happens, but, nowhere near every time. I think I had one yesterday and a couple over the weekend when I did a lot of connections.

As to Kobo Utilities updating the database, I honestly haven't used any of those functions for a while. All of my updates are done by the driver. If something is failing in the plugin, report it in the thread with the details so I can look at it. It might be a change I hadn't noticed.

And the readonly mounting that has been discussed is after the device is ejected. If that is happening, it is possible that the database has been updated, but, not reread by nickel. Restarting the device should remount the partition correctly and reread the database. That might show the changes.
davidfor is offline   Reply With Quote