[chaley]

Originally Posted by Sefiriot

Here's another log testing CC 3.0.6. This time the transfer was about 1k+ titles. Interestingly metadata did finish sending this time before calibre timed out.

Since this is yet another monster log at 1.05 MB and over forum limits, it's again in my Dropbox.

Thanks. I will look it over to see if I can identify why the timeout happened.

I think that the "scan on connect" feature is beginning to having a more noticeable adverse impact during the initial handshaking period when CC and calibre are syncing up, now that the ondevice library's gotten this big (11560 titles).

Turn it off.

Scan on connect is useful for cases where the user sideloads books into CC's folder using some other app, for initial or complete reinstallations, or if the DB gets corrupted and the user clears it. In the normal course of events it should add nothing.

We now default it "on" because of the number of emailed questions the original dialog box provoked.

Ondevice database was at 199MB after this transfer before cleaning. Size after cleaning remains at 199MB. Took about 30+ minutes.

This matches my experience -- that frequently the db size does not change. However, subsequent db queries can get much faster because of the db "defragging" that cleaning does.

I wish I had some way to measure the defragging, and (even better) some way to know if it is necessary. Sigh.

I'd also like to report something strange: CC had been open since the file transfer (at least, not stopped) for several hours. Th phone of course had gone to sleep in between.

I then started CC's cleaning function. It brought up the "wait" dialogue screen which almost instantly disappeared and didn't clean the database. I then did a force stop and restart through device settings, told CC to clean the database, and all went back to functioning as usual. Possibly my device is just having a hiccup in functioning, but I thought you should know.

My guess is that the database was closed by Android while the phone was idle. The code in 3.0.6 didn't tolerate that very well (or should I say, not at all). I have changed CC to verify that the db is actually open on every query/action. I had been worried that this verification would slow CC down, but Android takes care of caching open database handles so in the normal case it costs almost nothing. This change will be in the next release/beta.