Quote:
Originally Posted by jswinden
Me too. I bought out the ads and bought the "official cover" so I can just open the cover and be at my book! Although I rarely use the PW2 now.
|
No ads & the magnetic cover here too--and that definitely makes the Kindle more appealing to use, at least for me. Looking very much forward to additional (darker) fonts with the JB though--the screensaver hack became less important once the dead authors were no longer an issue.
I'm actually going to update my PW2 this afternoon. Thanks to everyone's posted experiences, I decided to delete all existing cloud collections via the iOS apps--they were holdovers from my K2 & Touch, I redid them on the PW2 weeks ago. Since I keep 90% of my stuff on the device anyway, that should minimize the greyed out books issue. Purging the legacy device cloud collections beforehand *should* with any luck mean I'm left just with the collections that are already on the PW2. We'll see.
Hopefully they'll clean things up eventually so that those who keep their devices relatively empty aren't forced to look at it anymore. Or perhaps our fantastic JB devs can add a tweak that vanishes the greyed out books and stupid messages when side loading or moving books between collections while wifi is off.
Edited to add:
Well it looked good for about a minute, and then poof!
I can verify this much--the "clearing out legacy device collections from the cloud" trick isn't 100% effective either.
Any collections that I've either created from scratch on the PW2 prior to the update or imported AND renamed from the Touch appear to have survived intact.
Collections imported from the Touch to the PW2 prior to the update but NOT renamed apparently went away when I deleted the existing cloud collections from iOS--even though they were on the PW2 before. They vanished from the PW2 after updating.
The books, or course, are still there, but some 20 collections will have to be rebuilt. I at least took screenshots of the collections before updating, but yeah, couple of hours' worth or work to do now.
I stand by my original statement. Crappy code happens, and it doesn't take much experience to identify it.
