Quote:
Originally Posted by knc1
Why don't you just try it and let us know what you found tomorrow?
|
Ha! Because I haven't written the app and won't (it's reasonably complex) if I don't think this will work. However, I'm getting the feeling I may end up having to do what I wrote in my first post: "I could determine the answer to that question by making a dummy web app to try and mimic the approximate amount of cpu/screen refreshing that the real app would have, but if you all already know that my expectations are clearly reasonable or clearly unreasonable, that would save me a step." It sounds like there aren't hard and fast rules so I'm gonna have to put in the work. Darn!
Any clarification on the following? Because that makes a big difference in how I will approach this thing:
Quote:
Originally Posted by xorlof
I understand that the display doesn't take any electricity except when changing its image, but I didn't understand that the device is completely asleep between changing book pages. I thought it was idling and only went to sleep when the screen saver kicked in. (Assume an unmodified Kindle here). If that's the case, how does the touchscreen and home button work when reading, but don't after the screen saver comes on. If they use the same power and there isn't a sleep mode where things are more powered down, it seems like you'd want to be able to use the touchscreen or home button to wake up the device. Is that just a UI decision Amazon decided to make?
Secondly, when is it not asleep then? I haven't jailbroken my kindle, but I assumed I could SSH into anytime after I "turned it on" but before the screen saver kicked in (even with a book image on display). If sleeping I couldn't, right? Is that wrong too? Or maybe I am misunderstanding your distinction between idle and asleep?
Thanks again for the help here, guys. (I keep saying that, but I mean it!)
|