Quote:
Originally Posted by Hopper333
Just an update on the screen inversion issue on H2O. This happened when I first installed the latest patched KSM and moved from Nickel->koreader for the first time. It also happened when I was working in KSM (for example, turning wifi on and off) and getting random screen orientations when I returned to the KSM menu.
|
What you describe here is what is expected on H2O without the KSM patch. If this happened after you installed the patch, then it is strange.
Quote:
Originally Posted by Hopper333
Another problem was that sleep in koreader using a screen cover was apparently failing as I opened the cover and found the KSM main menu instead and the battery significantly drained.  Before the firmware update and patched KSM, sleep had been working very well for months. |
KOReader crashed during suspend and gave control back to KSM. This sounds like the KSM patch was not yet installed at that point. When KOReader crashes, the expected behaviouris that KSM (with patch installed) informs you about the KOReader crach, and powers the device off after 20 secs or so, if there is no user input.
Quote:
Originally Posted by Hopper333
BUT, now I have moved from Nickel->koreader and from koreader->Nickel a few times, neither the sleep nor the screen inversion problem is happening anymore!  How can this be? Is it possible that there are some important 'system variables' that need to be initialised by these movements - so the new setup needs to be 'bedded in' somehow? |
The only thing that comes to my mind is that your successful installation of the patch might have happened at a later time as you thought. Do you think that this is possible?
Quote:
Originally Posted by Hopper333
Anyway, I'm happy again now as I have my e-reader back  but I think it would be very useful for our community if there was a description of how KSM interacts with Nickel and koreader - in particular any shared system variables. This would help us understand what is going on and therefore with debugging and development as the inevitable next issues arise over time. Does such a diagram/document exist? If not, is it feasible to create one? |
Unfortunately, the only way to see what is going on is currently to look at the scripts. Creating a detailed documentation is to much work for me, and a superficial description would not help much. You are right that there will be inevitably further issues to solve. One of the next issues might arise when KOReader switches to 32 bit color depth.