Should I use AlarmManager or ScheduledExecutorService? (pros/cons?)

by ccylan » Wed, 25 Jun 2008 03:58:23 GMT

Sponsored Links
 Hello Everyone,

Here is my dilemma.  I have several different timed operations that I
need to run on a daily basis, but at different times.  Currently I am
using ScheduledExecutorService, however having dabbled with
AlarmManager and its setRepeating function, I'm wondering if I should
use that instead?  What are the pros and cons of using either of these


Other Threads

1. Modifying and flashing the kernel on a Nexus One 2.2 Dev Phone

Hi everyone,

On the above phone, is there a proven procedure to obtain the correct
kernel source files (FRF91), modify the kernel configuration, rebuild
it, and flash
the phone with it?

In addition to not knowing where to look for the matching source tree,
I was also
concerned about mismatch with the radio image, and other horror
stories about
dead phones, etc., that are related on the web regarding this!

Thanks in advance for any info on this.



2. Null pointer in AppWidgetManager.getInstance()

I'm getting a null pointer in app widget manager. I believe it is when
the user is upgrading the app while a background intent service is
running, possibly right before the widget is updated. The background
service updates a database and the appWidgets right before it

This is from 2.2
        at android.appwidget.AppWidgetManager.<init>(

I've looked at the code above, and it seems to be
context.getResources.getSomething where it Null pointering. The
context is non-null, since the getInstance was called with "this". So
its probably the resources being null at that point

Is there a broadcast intent that I could catch to tell my intent
service to shut down? The docs are a bit confusing in the
seems to be sent to the new instance of the app only. Are any of these
sent to the old version of the app prior to it being upgraded? Is
Application.onDestroyed() guaranteed to be called on clean shutdown
due to upgrade?

I also get occasional database locked, also right around the time I
release the update.  Its probably caused by the same thing(old version
running concurrently).



3. Additional countries for paid apps

4. adding an external jar....

5. binder driver not found

6. Compile froyo source on Mac OS X

7. EXUS_Dock v10.6