Thread: Battery experience with firmware v4.1.7729
View Single Post
Old 10-24-2016, 09:11 PM   #78
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 pickyaxe View Post
Actually, today I found out that it's not database corruption. I'm using OS X and for some reason, ejecting the device sometimes doesn't trigger a database refresh (regardless if ejecting via Calibre or via OS X's diskutil).

Then the Aura One starts thinking it has an empty database. The calibre KoboTouch driver will report that the database is corrupt. At that point no amount of connecting USB/mounting/dismounting would trigger a refresh. This can be solved by rebooting, then mounting/dismounting, which finally refreshes. However, this database "loss" happens quite a lot. At one point I did not do the reboot+refresh thing and Nickel eventually did a spontaneous factory reset.
That all sounds "normal" for when something has messed up the database. If it is bad enough, then nickel will decide to cut it's losses and reset.
[QUOTE]
Could it be an issue with fmon?

Sorry, I don't use fmon, so I am not sure. Removing it and checking would be a good idea.

Do you use KSM? The description reminds me of a problem KSM had a while ago. I'm sure the problem was fixed, but if you have an old version of KSM, it might still be happening.

Something you should try is to take calibre out of it. Connect without calibre running and manually sideload a book. If that works, then it isn't the connection to the MAC. Then using the Kobo desktop while manually sideloading a book. Or changing something in the database by some other mechanism. This would help demonstrate if it is the database being change by something other than nickel and it is not being reloaded properly when the device is disconnected.
davidfor is offline   Reply With Quote