Quote:
Originally Posted by tshering
Thank you. That looks promising! Doesn't it?
After some seconds I realised that I was over enthusiastic. It seems we can prevent the rotation, when we know that the rotation has been destabilised. However, when we take the same measures without the rotation already being destabilised, we will produce the destabilisation ourselves. That means before each call of a KSM application we would have to know whether the rotation is stable or unstable. The only solution that comes to my mind now is to record whether nickel has been run in this session, and if yes presume that the rotation is unstable.
Any ideas?
|
@tshering
Finally update FW from a factory reset and installed KSM09, lastest KOReader, CoolReader and Plato.
Make all test to proposed and obtained the same results than nook_nerd.
About the rotation issue:
May be write a token (inside a file or an empty file) and toggle/delete whenever KSM is run (or only the first run), what do you think?
Edit: I mean write a file token when KSM run the first time. The check if that file exist when KSM need to change rotation and if the file don't exist don't do anything but if it exist change the rotation value (and delete the token).
Also note that rotation occurs whenever an option is pressed, alternately upside and downside, since nickel (and only with nickel) is used once.