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

by Mark Murphy » Tue, 13 Apr 2010 19:50:26 GMT


Sponsored Links
 


If you eliminate your parenthetical expression, then yes. The activity
being killed/not-killed has no impact -- the flag only affects the
device when the activity is in the foreground.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

Android Online Training: 10-14 May 2010:  http://onlc.com 

--



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

by Mark Murphy » Wed, 14 Apr 2010 19:31:52 GMT


 


You aren't, but unless you have a completely clean device (or have
hammered stuff into submission with a task killer), there might be other
apps using alarms.


Make sure your screen timeout setting is set to a low value (yes, I
know, you're manually turning off the screen, but humor me for a bit).

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

_The Busy Coder's Guide to Android Development_ Version 3.0
Available!

--


Sponsored Links


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

by Mark Murphy » Fri, 23 Apr 2010 04:07:54 GMT


 


I'd start by using AlarmManager without a _WAKEUP style alarm, instead
of having some Timer going. This would let you get rid of your process
from memory.

Those alarms will still get fired "the next time the device wakes up",
and I'm not sure if that's just the CPU being on or if that waits until
the screen is on.

If that is still too frequent, then you can watch for ACTION_SCREEN_OFF
and ACTION_SCREEN_ON broadcasts and disable/enable your alarms on that
condition. Unfortunately, I think those can only be caught via a
BroadcastReceiver registered via registerReceiver(), which brings you
back to having a service in memory all the time.

If the device you are running is going to be Android 2.1 or higher, you
have another option: isScreenOn() on PowerManager. Check that on your
alarms and use it to tune your alarm frequency back to as slow as you
can stand, bearing in mind that you won't know if the screen turns back
on until the next alarm.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

_The Busy Coder's Guide to Android Development_ Version 3.0
Available!

--



Other Threads

1. ApplicationContext.java and Activity.java. Is ApplicationContext not used ?

hi,

I was going through the code for Activity.java and ApplicationContext.

Both these classes define many functions of Context Interface. Take
for example startActivity.java

Activity Class has its own implementation of startActivity
ApplicationContext class also has an implemenetaion of startActivity.


Now there are 2 observations...

Observation 1: Regarding ApplicationContext.java

====================
/**
 * Common implementation of Context API, which Activity and other
application
* classes inherit.
 */
@SuppressWarnings({"EmptyCatchBlock"})
class ApplicationContext extends Context {
===================================

So the comments imply that Activity class should actually use
ApplicaitonContext.java. Infact Activity Class should inherit
ApplicationContext class.

Observation 2: Regarding Activity.java

But if you look at class Hierarchy of Activity class, it goes as:

Context ==> ContextWrapper ==> ContextThemeWrapper ==> Activity

So nowhere do I find ApplicationContext.


Questions:
1. Who uses ApplicationContext class?
2. Does Activity class ever deal with ApplicationContext class (as
given in the javadoc comments of ApplicationContext.java).

Thanks,
Amit
--~--~---------~--~----~------------~-------~--~----~

2. Can't i call a service function in activity's onStart/onCreate?

You need to wait until you actually receive the service connection
callback before you do anything with the service. You can't simply
assume that the callback has already happened when you reach your
onStart.





--~--~---------~--~----~------------~-------~--~----~

3. Application using service in different project

4. change key width runtime

5. building android from source code & running in emulator and measuring video playback performance using opencore

6. ScreenProtector AntiGlare

7. App for Storing Waypoints and Waytracks.......