Quote:
Originally Posted by Godzil
But why do you think theses bugs are related ? Maybe bookeen try something on that firmware update that totaly failed on the power managment but are totaly not related with buttons.
And explain me a thing, How can you poll a key when your device is sleeping and the only way to get wake the device is to generate an interrupt?
Since all eInk device stay for the majority of time in (deep) sleep mode, explain me how you will poll a key when the CPU is off
|
You are right, of course it *could* be two unrelated bugs. It's just that polling would be a fitting explanation for the symptoms (missing *a lot* of key presses like in the early FWs is hard to explain with an interrupt model plus the polling would also explain the battery drain) but it is not necessarily the only possible explanation.
Of course, polling is not possible when the device sleeps but as far as I know there is no sleep mode in the Cybook. If you refer to the On/Off button, that one obviously cannot be polled but for the rest of the buttons I see no problem. When you turn your Cybook on and leave it on without pressing any buttons it still uses battery and will eventually run empty. So there is, obviously, some code running at all times even if all unnecessary processes are shut off. I would think that that is the part of the code which does the polling and which - in turn - wakes up all the other functions as soon as it registers some user interaction.
I cannot talk about the majority of EInk devices because I haven't dealt with other devices in depth. I had to impression that all or most work like the Cybook which does not go into *deep* sleep (i.e. CPU off) but rather *light* sleep (if I may call it that) where the functions are reduced to a minimum and therefore only very little energy is consumed (althought there *is* still some energy consumed)