Quote:
Originally Posted by thomass
 Thanks. It seems that problem is solved on one way. When I switch to DLite, Kindle doesn't accept input anymore. However Dlite still does. Fortunately I solved this by changing 14th line of stopdk.sh from
Code:
dstop=$(killall -STOP KindleApp)
to
Code:
dstop=$(killall -9 KindleApp)
Now it shuts down DuokanLite when I switch back to the Kindle.
There is another thing:
I installed both Duokan and DuoakanLite and try to use launchpad way described on this thread on this installed Duokan. Unfortunately it doesn't work correctly especially when I try to switch back to Kindle(It continually reboots). Could you solve this,too? |
well, sending signal 9 to KindleApp is something that I wanted to avoid, I'd rather keep looking for a way to block input to KindleApp so that it will keep your place in the book you have open, and you don't have to keep resetting the chinese for english... but you are right that it starts up quickly, that is not so bad to re-load it from scratch.
I suspect the problem with the duokan vs dklite is one of different libraries, (as they are really two different projects) and with dklite running, trying to load duokan will link to the dklite libraries instead and raise an error ... I don't have duokan installed on mine, can you point me to the most recent version?