View Single Post
Old 06-08-2010, 03:20 PM   #21
Dave_S
What Title ?
Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.Dave_S ought to be getting tired of karma fortunes by now.
 
Posts: 1,325
Karma: 1856232
Join Date: Jan 2009
Location: Bavaria Germany
Device: Sony Experia Z Ultra
Quote:
Originally Posted by theducks View Post
Poorly written "display time" code, that should be asleep unless a screen refresh is called for, may keep the other CPU from sleeping (or causing frequent wakeup's).

I am guessing the latter.
Frequent *unnecessary* wakeups from sleep mode *could* do it. I would hazard a guess that the system under full 400 MHZ clock would draw a couple of hundred milliamperes, but I know that in sleep mode the current draw is down in the microamp range. I seem to remember that the RTC clocks in systems I have dealt with in the past ran about 15 microamperes, but it may be even less with more modern smaller geometry chips? Normally the hundreds milliampere draw is only a very few seconds during a page turn, but being in that high power range more often than that would draw the battery down proportionately faster.
Dave_S is offline   Reply With Quote