View Single Post
Old 07-13-2023, 07:30 AM   #33
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 11,126
Karma: 77213683
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Quote:
Originally Posted by ownedbycats View Post
Interesting thing I've noticed: Sync was stalling out. So I deleted a suspect collection (recently reached a certain number of books) and this fixed it. Then I let KoboTouchExtended re-create the collection - the sync issues didn't reoccur. Perhaps something similar to that 'differing case' mentioned earlier?

I wonder if it has trouble with collections made up of entirely sideloaded books. This would match certain patterns I've noticed.
It's happened twice more since (including today). Doing the same process fixes it; deleting the collections, syncing, then letting KoboTouch regenerate.

As usual, it mostly affects my sideload-only collections. Maybe the sync process doesn't like 'empty' ones?

The tricky part is identifying which collection is the glitchy ones. Nuking them all is easier.

Last edited by ownedbycats; 07-13-2023 at 07:33 AM.
ownedbycats is offline   Reply With Quote