Quote:
Originally Posted by xorlof
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: |
That is an awful lot of questions and damn few line breaks. There is more electronics in the device than the SoC chip. That includes a low power micro-controller that watch the power button - among other things. Or you could start with the clock application to gain your basic measurements and then extrapolate from those. The screen saver is no indication that the device is asleep. "Idle" == No work to be done, as in "idle loop" (which in modern devices isn't a loop at all). "Sleep" == Read the ARM manual to see what that means - there are many individually controlled areas of the SoC chip. It is your project, who did you expect to do the work?