I think the problems with installing Duokan on already jailbroken Kindles that have been popping up occasionally are actually due to incompatibility with the screensaver hack. Today I tried installing Duokan for the first time - none of the other readers parsed CK-12 textbooks properly (even those that are available from Amazon - there's a lot of in-line pictures of formulas there that either get all garbled-up or break the lines, depending on the reader). Anyway, after installing Duokan 2014 (and later on trying my luck with 2013) it looked just like here:
Quote:
Originally Posted by jation
|
What I noticed, though, is that this broken screen was preceded with SS hack notifying of starting in cover mode. And when Duokan's loading process is stuck like this, in truth the KindleOS is already partially loaded. You can put it in sleepmode and a custom screensaver will appear; lauchpad shortcuts work to the point where you can do Shift-Shift-A and restart the framework and use Kindle normally. So, after I uninstalled only the screensaver hack Duokan installed and loaded just fine.
Long story short: screensaver hack's cover mode won't allow Duokan to load (was that common knowledge? I couldn't find this anywhere on the forum). It seems to run its python scripts before Duokan. I have no idea about the inner workings, but from the outside it seems that this triggers some parts of KnindleOS to load before Duokan has a chance to take control. This happens both with Duokan's boot selector and KUAL extension. It does not happen when the screensaver hack is in simple gallery mode, but you can't have cover and Duokan at the same time. And, of course, it's not NiLuJe's problem, given Duokan guys' track record with other people's code (hence I'm not suggesting this as a bug on that thread), but I just thought maybe this post will save someone several hours of rebooting the device over and over again.
K3G 3.4.1, SS 0.45.N