Quote:
Originally Posted by davidfor
What are the actual symptoms of the sync failing? The sync popup shows the phase of the sync. Where was it getting to?
I did discover a syncing issue related to collection names. I had collections like "toRead" and "toRate". These are maintained via calibre. I changed the case of the values in the library to "ToRead" and "ToRate" to be consistent with the other values. After that, some of my devices would sync a couple of times, then start and never finish. After a bit of investigation, the issue turned out to be the change in case. One of the database updates in the firmware was failing because both "toRead" and "ToRead" existed and this caused a duplicate error in an index. There was also a bit of a loop as all my devices were syncing and different ones were hitting this at different times. Add in that I would connect one to calibre and that did some updates as well. The fix was to manually delete these collections on a device and sync them all. After that, syncing was fix, calibre was able to recreate the collections I wanted and there have been no problems since.
|
Plain old CBZ file without any metadata, synced over WiFi from Dropbox or from an HTTP server on my network. If you don't open the file, sync works fine (connects right away, doesn't hang trying to check for updates), but after reading more than 5-10 pages on, syncs fail to complete as they freeze on the "checking for updates" step.
This has happened with twenty different CBR and CBZ files, and it doesn't matter if there's only one on the device or if there are 50. I've seen it happen on the Libra H20 as well as my current Forma.
Back then, I'd be lucky to complete one sync in 30, waiting 20-40 minutes for a sync to finish. The only surefire fix was to do a factory reset (just repairing would fail, due to the sync issue) and to not open any CBR/CBZ files. Indexing the cover never triggered the issue - you had to get further into the file to do so.
The only collections they belonged to were the one created on the device itself, by the reader software. It's why, when you mentioned the bug with the sync was fixed on the Sage / Libra 2 firmware, that I had hoped I could sideload these again.
This NEVER happened on the older firmware, not up through to the Aura One. Only after that, when they stopped releasing devices with removable storage, did I start having issues. With CBZ and CBR files on the SD card, it never froze like this.