Quote:
Originally Posted by Sefiriot
Do you get logs submitted through normal Android error reports when the app crashes?
|
It depends. If the user allows the device to send a report then we get it. It also seems to be the case that we get them sometimes "just in case".
Quote:
|
The CC crash that wiped the database, or seemed to at least had some rather interesting error info when I looked at it on the phone, which I didn't think to screenshot at the time. I'm not too sure now, but I believe that error message indicating empty metadata happened when CC was sending information for that book where calibre had previously timed out whilst in mid-transfer during session 1-- and the crash promptly wiped the database.
|
Wiping the database is not good (what a fatuous statement that is.
). It is very hard to explain why this could happen. Perhaps Kovid's pointer is very relevant, because records get re-created every time metadata comes from calibre to the device.
Quote:
|
If CC's database is corrupt, is there anyway to force a rebuild? Would uninstalling, reinstalling and then letting CC match against calibre for books already on device do the trick?
|
The easiest way is to go to settings -> apps and "clear memory". That blows away the DB and all the settings but leaves the books. You would then redo the important settings, such as "use UUID" (which you seem to be using), ensure "scan" is on, and then connect. CC will extract metadata from epubs and send that up to calibre. Almost certainly the metadata will contain the UUID, greatly facilitating book matching. For other formats, CC sends the books themselves up to calibre for analysis.
As part of my testing I frequently nuke the DB and rescan. But then, my test machine has only 600 books on it...