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

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


Sponsored Links
 Hmmm, so in that case, why does the device not sleep after the user
has used the power button to turn off the screen? Or do you mean that
the activity is still considered in the foreground even after that?






--



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

by westmeadboy » Wed, 14 Apr 2010 15:19:10 GMT


 So I tried this:

Start service
Press Home
Start some other 3rd party app (so that activity is in the foreground)
Press power button to blank screen

A few minutes later, I press the power button to unblank the screen
and discover the service finished successfully.

This means the phone never went to sleep...

Any ideas why?






--


Sponsored Links


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

by THill » Fri, 23 Apr 2010 01:52:44 GMT


 I've seen similar behavior as the OP.

I have a simple activity that starts a timer in onCreate, logging a
message every second.  No wake lock is requested, so after the time
indicated in setting, the device sleeps (allowed to dim, then sleep
naturally, not with power button press).  After letting it sit like
that for a few minutes, I plug it in via USB & check the logs, where I
can see the timer continued running through the sleep.

If I then do 'adb shell dumpsys power', the only wake locks shown are:
mLocks.size=2:
  SCREEN_DIM_WAKE_LOCK           'StayOnWhilePluggedIn Screen Dim'
activated (minState=1)
  PARTIAL_WAKE_LOCK              'StayOnWhilePluggedIn Partial'
activated (minState=0)

which makes sense since the device is now plugged in via USB.

Is this expected behavior?  Seems to go against the idea that all
threads are suspended during the sleep...

Thanks for any clarification,
Tim






--



Other Threads

1. How to make a listview with selectable children stop scrolling on touch event?

Hey Alexander did you ever get a solution to this i'm stuck with the
same issue damn listView will not stop on touch even tried override
the on touch event but it seems the touch event is immediately passed
to it's children form which I can not pass it back up successfully.




-- 

2. GPS on Droid issues

When I run the following code on a HTC G1, I get the behavior that I
am expecting.

myLocationManager.requestLocationUpdates("gps", 60000, 10,
                                        this);

It will grab a GPS location for me, and then sleep until it needs to
send me an update. On the Droid though, the GPS stays on the entire
time without sleeping feeding me an update every minute. This is
killing the battery when my application is running, I need it to sleep
just like it does on the G1 to conserve.

Anyone have any thoughts/ideas?

Robert

-- 

3. how to send image over socket, knowing its URI?

4. Task life cycle and activity launch mode question(s)

5. Is there a list of standard Intent specifications?

6. Android Jail Break Redux

7. Definitive Ad Mob