Quote:
Originally Posted by NiLuJe
@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. |
I don't have anything wierd about my K3W that I am aware of. I did enable verbose mode and I seem to stop seeing messages from the watchdog when it stops working. Is there a way to check the logs and status of the watchdog from a myts session?
I had assumed that the framework restart in KUAL and launchpad were equally functional, I will start using the KUAL one next time.
Let me know of anything further I ca do to help you sort this out. I guess K3 support is of lesser importance at this point as they are no longer made, but there are still quite a few out here. In terms of function I can do more with my K3W than with the new basic kindle I received as a Christmas gift, which has no audio support and requires major work to enhance. In many ways the new kindles are a step backwards.
Dave