Repeating Periodic Tasks

Overview

Repeating periodic tasks within an application is a common requirement. This functionality can be used for polling new data from the network, running manual animations, or simply updating the UI. There are at least four ways to run periodic tasks:

1. Handler - Execute a Runnable task on the UIThread after an optional delay
2. ScheduledThreadPoolExecutor - Execute periodic tasks with a background thread pool
3. AlarmManager - Execute any periodic task in the background as a service
4. TimerTask - Doesn't run in UIThread and is not reliable. Consensus is to never use TimerTask

Recommended methods are outlined below.

Handler

We can use a Handler to repeat code at an interval by constructing a Handler and then "posting" Runnable code to the event message queue on the thread to be processed.

Using a handler to execute a periodic runnable task is demonstrated below:

// We need to use this Handler package
import android.os.Handler;

// Create the Handler object (on the main thread by default)
Handler handler = new Handler();
// Define the task to be run here
private Runnable runnableCode = new Runnable() {
    @Override
    public void run() {
      // Do something here on the main thread
      Log.e("Handlers", "Called");
      // Repeat this runnable code again every 2 seconds
      handler.postDelayed(runnableCode, 2000);
    }
};
// Kick off the first runnable task right away
handler.post(runnableCode);

Remove the scheduled execution of a runnable with:

// Removes pending code execution
handler.removeCallbacks(runnableCode);

Note that with a Handler, the Runnable executes in UIThread by default so you can safely update the user interface within the runnable code block. See this handler post and this other handler post for reference.

Refer to our threads and handlers guide for a more advanced breakdown.

ScheduledThreadPoolExecutor

A pool of threads which can schedule commands to execute periodically in the background. Useful when multiple worker threads are needed but generally not needed. See this guide on how they work or this stackoverflow post.

AlarmManager

This should be used if the periodic tasks need to run in the background even when the app is not in the foreground. This leverages the alarm service on the phone to cause periodic executions of a service which will run continuously until stopped. See the AlarmManager section of the services guide for details.

References

• http://www.mopri.de/2010/timertask-bad-do-it-the-android-way-use-a-handler/
• http://stackoverflow.com/questions/18605403/timertask-vs-thread-sleep-vs-handler-postdelayed-most-accurate-to-call-functio
• http://androidtrainningcenter.blogspot.in/2013/12/handler-vs-timer-fixed-period-execution.html
• http://stackoverflow.com/questions/8098806/where-do-i-create-and-use-scheduledthreadpoolexecutor-timertask-or-handler