I'm using a WakeLock to keep the CPU alive for a few minutes while my timer runs.
However, the CPU still seems to go to sleep after 5 minutes if I use PARTIAL_WAKE_LOCK. If I use SCREEN_DIM_WAKE_LOCK, it works as expected. In fact, I can't tell if PARTIAL_WAKE_LOCK does anything at all; the CPU still sleeps, and if I wake it up I can see that the timer was stopped too. I know I could convert to using Alarm, but the timer duration is subject to GUI control and may need to be changed often (or may not). How much advantage is there to using Alarm? Does a WAKE_LOCK for say 5 minutes really consume that much power? It's just the CPU and screen, not the GPS or Wifi. Jim On Jul 29, 5:55 am, Mark Murphy <[email protected]> wrote: > Ne0 wrote: > > I wasn't 100% clear, its location updates from telephony manager, so > > when the phone gets a new LAC code rather then GPS location updates. > > Well, I have even less experience with the behavior of all of that under > a WakeLock, so I have no particular guidance there. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training in Germany, 18-22 January 2010:http://bignerdranch.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
