On Apr 2, 9:56 am, Mark Murphy <[email protected]> wrote: > On Mon, Apr 2, 2012 at 9:50 AM, Dan <[email protected]> wrote: > >> > On screen-off, i.e. when it hits the sleep mode, are the wifi radios and > >> > CPU > >> > disabled/switched-off? > > >> The CPU stops running. > > > This is demonstrably wrong, as you can have a PARTIAL_WAKE_LOCK held > > and not have the screen on (or even just have ADB gathering logs even > > after the short/long power button press to turn the screen off.) > > The question was "when it hits the sleep mode", and a > PARTIAL_WAKE_LOCK prohibits the device from reaching sleep mode.
Note that even without the PARTIAL_WAKE_LOCK held, on many devices there is a period where the CPU is still active after the screen goes blank (call it PARTIAL_WAKE without the lock held) which makes defining a test case to be sure that a particular device will "do the right thing when an alarm goes off while the CPU is not running" difficult. > That being said, I neglected to correct the OP on equating "screen > off" with "hits the sleep mode", and for that I apologize. Given Dianne's view of: > On Android "sleep mode" is the screen being off. What do you mean by > "sleep mode"? it's easy to see how the OP might have made that assumption. I apologize for my tone as well, I've been fighting with issues on some firmware where a PendingIntent fed an Intent that has had the class set with Intent.setClass() doesn't make it from the AlarmManager to my receiver and was hoping for an answer that would make how to test this sort of thing easy instead of "we don't acknowledge any difference between screen off and cpu off". -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
