View Single Post
Old 03-16-2015, 07:50 PM   #3487
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@dhdurgee: Oh, launchpad. Yep, that'll never do the trick . The KUAL button will, though (in the snapshots, that is).

As for the root cause of the issue, if switching between books (and waiting the appropriate amount of time) doesn't help, then it's still probably a bug. Do you happen to have a weird USB setup? Or can pinpoint a significant (or not) detail before the desync happens?
If you can, when that happens, try to check the logs and/or check that the cover watchdog is alive (remember, house of cards, I might have missed a corner case).

Also keep in mind that there's a known race condition (in this branch of the code) where rarely, the first sleep cycle on a new cover will either use the previous cover, or a mangled mix of the two. There's a KUAL button to enable a workaround, which isn't the default because it has worse cosmetic downsides (IMHO) . That race condition *might* have been fixed in the latest snapshots, but I wouldn't hold my breath.

Last edited by NiLuJe; 03-16-2015 at 07:57 PM.
NiLuJe is offline   Reply With Quote