Android registered broadcast methods and their advantages and disadvantages

In android, to accept broadcast information, we have to implement this broadcast receiver. We can inherit BroadcastReceiver to have a broadcast receiver. There is not enough receiver. We have to rewrite the onReceiver method in BroadcastReceiver, and then register the broadcast.

There are two methods: one is dynamic code registration:

// Generate broadcast Processing
SmsBroadCastReceiver = new SmsBroadCastReceiver ();
// Instantiate the filter and set the broadcast to be filtered

IntentFilter intentFilter = new IntentFilter ("android. provider. Telephony. SMS_RECEIVED ");

// Register Broadcast
BroadCastReceiverActivity. this. registerReceiver (smsBroadCastReceiver, intentFilter );

Second, configure broadcast in AndroidManifest. xml

<! -- Broadcast registration --> <receiver er android: name = ". smsBroadCastReceiver "> <intent-filter android: priority =" 20 "> <action android: name =" android. provider. telephony. SMS_RECEIVED "/> </intent-filter> </Cycler>

The differences between the two registration types are:

1) The first is not a resident broadcast, that is, the life cycle of the broadcast following the program.

2) The second type is the resident type. That is to say, when the application is closed, if information is broadcast, the program will be automatically run by the system call.