Quote:
Originally Posted by Mrs_Often
7 seconds to render the next page?
|
Here we have misunderstanding caused by me knowing what I'm taking about and not explaining it in every detail, trying not to write too long text about what is actually going on.
7 seconds is time till H2O (device that was actually tested and has IR grid for determining where touch happens) goes in some deeper sleep state while still being on and waiting to serve next page.
Also, why 7 seconds, is it spent the whole time on rendering next page? Probably not, but it is 7 seconds.
Also, when talking about rendering, it is not that you wait 7 seconds to see next page. Process is:
A) You read page and touch display to have next page shown.
B) Next page is shown. You start to read it
C) 7 seconds after page is shown reader is in a state of a heightened activity, i.e. spends 13mA.
D) After 7 seconds reader goes in a deeper sleep state and reduced 1mA battery usage, which lasts till next touch.
With koreader device stays all time in 13mA battery usage state, while you read.
Hope it makes things a bit clearer. What exactly goes on within 7 seconds certainly isn't just rendering page, but also probably some "housekeeping" by nickel.
And yes, this measurement is actually done and reported on koreader's github page, where I get this info from.
So, nickel probably is a bit energy efficient while reading, but not that much and it certainly depends on many factors how much time you save with nickel versus koreader, but I'm pretty sure not that much it is that big issue with using koreader.