MbmsDownloadReceiver


public class MbmsDownloadReceiver
extends BroadcastReceiver

java.lang.Object
   ↳ android.content.BroadcastReceiver
     ↳ android.telephony.mbms.MbmsDownloadReceiver


The BroadcastReceiver responsible for handling intents sent from the middleware. Apps that wish to download using MBMS APIs should declare this class in their AndroidManifest.xml as follows:

<receiver
    android:name="android.telephony.mbms.MbmsDownloadReceiver"
    android:permission="android.permission.SEND_EMBMS_INTENTS"
    android:enabled="true"
    android:exported="true">
</receiver>

Summary

Public constructors

MbmsDownloadReceiver()

Public methods

void onReceive(Context context, Intent intent)

This method is called when the BroadcastReceiver is receiving an Intent broadcast.

Inherited methods

Public constructors

MbmsDownloadReceiver

public MbmsDownloadReceiver ()

Public methods

onReceive

Added in API level 28
public void onReceive (Context context, 
                Intent intent)

This method is called when the BroadcastReceiver is receiving an Intent broadcast. During this time you can use the other methods on BroadcastReceiver to view/modify the current result values. This method is always called within the main thread of its process, unless you explicitly asked for it to be scheduled on a different thread using Context.registerReceiver(BroadcastReceiver, IntentFilter, String, android.os.Handler). When it runs on the main thread you should never perform long-running operations in it (there is a timeout of 10 seconds that the system allows before considering the receiver to be blocked and a candidate to be killed). You cannot launch a popup dialog in your implementation of onReceive().

If this BroadcastReceiver was launched through a <receiver> tag, then the object is no longer alive after returning from this function. This means you should not perform any operations that return a result to you asynchronously. If you need to perform any follow up background work, schedule a JobService with JobScheduler. If you wish to interact with a service that is already running and previously bound using bindService(), you can use peekService(Context, Intent).

The Intent filters used in Context.registerReceiver(BroadcastReceiver, IntentFilter) and in application manifests are not guaranteed to be exclusive. They are hints to the operating system about how to find suitable recipients. It is possible for senders to force delivery to specific recipients, bypassing filter resolution. For this reason, onReceive() implementations should respond only to known actions, ignoring any unexpected Intents that they may receive.

Parameters
context Context: The Context in which the receiver is running.

intent Intent: The Intent being received.