I just found out that the issue I described happens only to collections that were
modified by CM. By modified I mean having items added to or removed from. I deleted all collections and recreated them using the Kindle's native interface and it works fine now. Probably CM has a bug when
writing the collection records, corrupting them in such a way that the Kindle firmware gets confused when it attempts to modify them. Probably it's the same issue referenced in the CM thread:
Quote:
|
On Firmwares >= 5.4.2, some functionality is unavailable (cf. the section about supported FW), and trying to maintain CM collections through the framework's UI instead of CM may lead to a soft deadlock.
|
I would guess it's related to that "cloud collections" thing.