Not using a WakeLock so why does the device stay awake?

by MrChaz » Tue, 13 Apr 2010 17:16:57 GMT

Sponsored Links
 iirc, that flag means the system gets a wake lock for the life of the
activity for you.


Not using a WakeLock so why does the device stay awake?

by westmeadboy » Tue, 13 Apr 2010 17:19:20 GMT

 Oh I see.

So if the user presses Home and then uses the power button, then it
*could* fall asleep (in the case where the activity has been killed by
the system)?


Sponsored Links

Not using a WakeLock so why does the device stay awake?

by westmeadboy » Wed, 14 Apr 2010 15:45:23 GMT

 Just to confirm: the device is not plugged into USB and I'm not using
any broadcasts or broadcast receivers.

When I do plug in and start the service these are the wake locks:

  SCREEN_DIM_WAKE_LOCK           'StayOnWhilePluggedIn Screen Dim'
activated (minState=1)
  PARTIAL_WAKE_LOCK              'StayOnWhilePluggedIn Partial'
activated (minState=0)

and then when I homescreen, other app, turn the screen off (as
describe above) but leave the device plugged in, the third one

So I would assume that when I unplug the USB, the first two to
disappear also...

> >

Not using a WakeLock so why does the device stay awake?

by THill » Fri, 23 Apr 2010 03:51:12 GMT

 hanks Dianne, that makes sense.

I didn't realize there was essentially one wake lock that the kernel &
applications layer use, so when all apps give up the wake lock, they
will still get awaken when the cpu wakes to handle kernel processes.

This explains why the 1-second timer pops occurred at 1 second
intervals before & after the sleep, and at very erratic intervals
during the sleep.

I saw the same behavior on a similar test case with an AsyncTask
sending messages through a handler to the UI. Neither the task, nor
the handler, was completely frozen during the sleep, but the task was
taking longer to complete during that time.

Unfortunately, my production app has specific power usage constraints
imposed by the manufacturer/carrier (especially with the device
asleep), and it doesn't seem there is a good way to make sure the app
completely goes dormant when the device sleeps. Any suggestions are


On Apr 22, 10:58am, Dianne Hackborn <> wrote:
> >

Other Threads

1. TabHost Remove Tab problem

Hello All,

In my application, i am creating Tabs Programmatically and and i want
to remove them as well one by one.
I tried removeViewAt() and it works too.

But, after deleting my application gets crashed.
e.g. If i have three tabs Tab1, Tab2 and Tab3 and if i remove Tab2, it
gets removed but as soon as i click either of the tabs Tab1 or Tab2,
ithe application gets crashed and on Log Cat i see this Error
Message :

AndroidRuntime(766): Uncaught handler: thread main exiting due to
uncaught exception
AndroidRuntime(766): java.lang.NullPointerException
AndroidRuntime(766): at android.widget.TabWidget.onFocusChange
AndroidRuntime(766): at android.view.View.onFocusChanged(

AndroidRuntime(766): at android.view.ViewGroup.removeViewInternal
AndroidRuntime(766): at android.view.ViewGroup.removeViewAt

can anyone please please Help me?

2. voice call recording

I know allready there are some post on this topic.Thats why i am
shocked couse  telephony class is protected.n we cant do call
recording.playing audio files on call n lot many stuffs,this is a
really important there any way to access it of this is added
in new version cup cake?

is there any hopes in feature that is going to happen.Come on android
team your image is developer friendly platform.please do something &

3. Problem in sending the String url to local server

4. Facility to execute code before BOOT_FINISHED

5. How do I listen for contact change events ?

6. Two projects, One Service

7. Audio on Android : \frameworks\base\media\tests\mediaframeworktest