View Single Post
Old 06-08-2016, 10:45 AM   #4
Josieb1
Grand Sorcerer
Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.
 
Posts: 5,090
Karma: 18051062
Join Date: Nov 2009
Location: UK
Device: Kindle Scribe, Coloursoft, PW SE, Kindle 6, Kobo Libra 2, Clara BW
Quote:
Originally Posted by davidfor View Post
The initial connection jobs taking a long time can be a sign that the database is corrupt. It depends on exactly where in the database the problem is as to whether it shows up during these jobs. Can you post the details of the error message? Exactly what and were in the driver the error is displayed can give some hints about what is happening.

As to the cause, I've never had proof that the driver can cause a corruption of the database. Usually, it is something else such as not ejecting the device properly. I've also seen corruption after a crash of the device, or a freeze followed by pressing the reset button to restart the device.
The last time I connected it (early today) it didn't generate an error message. It just look nearly 20 minutes to display the list of books on the device. If it happens again I'll factory reset again. I just wish I knew what caused it.
Josieb1 is offline   Reply With Quote