Thread: Firmware 4.30.18838
View Single Post
Old 11-20-2021, 10:22 PM   #76
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Haesslich View Post
Are we sure this patch includes the fix for the comic reader? I started having sync issues (won't connect, clock stops working, battery suddenly goes from full this morning to 1% this evening despite not being used most of the day) after opening a CBZ file with this version.

I'm doing a factory reset now after five failed WiFi syncs in a row. Also, it stopped connecting to my WiFi, even after the factory reset.
4.30.18838 definitely fixes an issue with the handling of CBZs and CBRs. But, that issue was causing problems when connecting to a PC via USB. It is unlikely to have changed anything related to syncing. But, if it did, it is more likely to reduce issues. And syncing doesn't sync anything about sideloaded books.

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.
davidfor is offline   Reply With Quote