BroadcastReceiver Vs WakefulBroadcastReceiver

¿Alguien puede explicar cuál es la diferencia exacta entre BroadcastReceiver y WakefulBroadcastReceiver ?

¿En qué situaciones tendríamos que usar cada clase de Receptor?

Solo hay una diferencia entre BroadcastReceiver y WakefulBroadcastReceiver .

Cuando recibe la transmisión dentro del método onReceive() ,

Suponer,

BroadcastReceiver :

  • No se garantiza que la CPU permanecerá activa si inicia algún proceso de larga duración. La CPU puede volver a dormirse inmediatamente.

WakefulBroadcastReceiver :

  • Se garantiza que la CPU permanecerá encendida hasta que dispare completeWakefulIntent .

Ejemplo:

Aquí, cuando recibas la transmisión, estás comenzando un servicio, ya que estás usando WakefulBroadcastReceiver , mantendrá wakelock y no dejará que la CPU duerma hasta que termines el trabajo dentro del servicio y dispare completeWakefulIntent

Código:

 public class SimpleWakefulReceiver extends WakefulBroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { // This is the Intent to deliver to our service. Intent service = new Intent(context, SimpleWakefulService.class); // Start the service, keeping the device awake while it is launching. Log.i("SimpleWakefulReceiver", "Starting service @ " + SystemClock.elapsedRealtime()); startWakefulService(context, service); } } class SimpleWakefulService extends IntentService { public SimpleWakefulService() { super("SimpleWakefulService"); } @Override protected void onHandleIntent(Intent intent) { // At this point SimpleWakefulReceiver is still holding a wake lock // for us. We can do whatever we need to here and then tell it that // it can release the wakelock. This sample just does some slow work, // but more complicated implementations could take their own wake // lock here before releasing the receiver's. // // Note that when using this approach you should be aware that if your // service gets killed and restarted while in the middle of such work // (so the Intent gets re-delivered to perform the work again), it will // at that point no longer be holding a wake lock since we are depending // on SimpleWakefulReceiver to that for us. If this is a concern, you can // acquire a separate wake lock here. for (int i=0; i<5; i++) { Log.i("SimpleWakefulReceiver", "Running service " + (i+1) + "/5 @ " + SystemClock.elapsedRealtime()); try { Thread.sleep(5000); } catch (InterruptedException e) { } } Log.i("SimpleWakefulReceiver", "Completed service @ " + SystemClock.elapsedRealtime()); SimpleWakefulReceiver.completeWakefulIntent(intent); } }