MobileRead Forums - View Single Post - Calibre Companion syncing experience: issues with a large ondevice library

Sefiriot · 08-26-2013, 04:29 AM

Yes, turned "Scan" back on. Was that what happened to the database? All I had was that CC crashed-- that's the end of the first log. Reopening CC after clearing device RAM showed a blank database with no books, so I turned "scan" back on, connected it to calibre and left it to do its thing. And yes, I am using the update cached metadata on device function. Is there any reason to avoid using it? I thought that since my device/connection don't seem to take well to sending big loads of metadata at once, sending it in smaller bursts where possible would be better.

You also asked why calibre'd be updating metadata for 292 books-- I believe it's to do with something that's cropped up in calibre 1.0 due to its database changes: updating my fanfic books with the FanfictionDownloader Plugin seems to be updating the author link field at the same time (see here), and thus changing the last_modified value on all books by that author whether needed or not. Thus I only updated some 20 books, but ended up with lots more that had their time in calibre changed. Since CC uses that value, I *think* that's what calibre was sending.

Hmm. I believe that the 2GB memory slot is system memory where apps live-- it has currently 700MB free. Task manager shows that the device's RAM is nearly always headed towards full, and looks pretty close to the limit considering how many apps seem to *love* running in the background. I'm going to see what cruft I can afford to get rid of and free up space; the phone isn't as snappish as it used to be back when I first got it, true.

Do you get logs submitted through normal Android error reports when the app crashes? 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.

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?

08-26-2013, 04:29 AM	#14
Sefiriot Bujavid tekikin Posts: 139 Karma: 40366 Join Date: Aug 2013 Location: Malaysia Device: LG G3 D855, Samsung Galaxy Note N7000	Yes, turned "Scan" back on. Was that what happened to the database? All I had was that CC crashed-- that's the end of the first log. Reopening CC after clearing device RAM showed a blank database with no books, so I turned "scan" back on, connected it to calibre and left it to do its thing. And yes, I am using the update cached metadata on device function. Is there any reason to avoid using it? I thought that since my device/connection don't seem to take well to sending big loads of metadata at once, sending it in smaller bursts where possible would be better. You also asked why calibre'd be updating metadata for 292 books-- I believe it's to do with something that's cropped up in calibre 1.0 due to its database changes: updating my fanfic books with the FanfictionDownloader Plugin seems to be updating the author link field at the same time (see here), and thus changing the last_modified value on all books by that author whether needed or not. Thus I only updated some 20 books, but ended up with lots more that had their time in calibre changed. Since CC uses that value, I think that's what calibre was sending. Hmm. I believe that the 2GB memory slot is system memory where apps live-- it has currently 700MB free. Task manager shows that the device's RAM is nearly always headed towards full, and looks pretty close to the limit considering how many apps seem to love running in the background. I'm going to see what cruft I can afford to get rid of and free up space; the phone isn't as snappish as it used to be back when I first got it, true. Do you get logs submitted through normal Android error reports when the app crashes? 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. 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? Last edited by Sefiriot; 08-26-2013 at 04:40 AM.