Android Broadcast Receiver – Change in flow since API 3.1

Prior to API 3.1 we could have a broadcast receiver which could have been invoked by an implicit intent even if the application to which it belonged was in stopped state.

But this posed a security threat. Hence Google made it mandatory that for any broadcast receiver to receive an intent, there should be an activity and the application should not be in stopped state. Here is the
link for further reading.

When an application is launched, it is in stopped state and hence it mandates the user to activate the application which has the broadcast receiver. If the application is force stopped by the user, then again the broadcast receiver fails to receive the intent. Hence apk having only broadcast receiver and developed on version prior to 3.1 will no longer work for later versions.

However one can make use of
FLAG_INCLUDE_STOPPED_PACKAGES to activate components in stopped application. This will not require creation of another activity in order to use the broadcast receiver.

Intent intent = new Intent("com.custom.intent"); intent.addFlags(Intent.FLAG_INCLUDE_STOPPED_PACKAGES); 
this.sendBroadcast(intent);

The other way as I had mentioned earlier would be to write an activity which may or may not be a launcher activity.

 
PackageManager pm = getPackageManager(); 
Intent appStartIntent = 
pm.getLaunchIntentForPackage("com.your.broadcast.receiver.package");
if (null != appStartIntent)
{ 
     startActivity(appStartIntent);
}

If it is not a launcher app, then you need to mention the the category as
INFO in the intent-filter in the manifest file of the broadcast receiver.

 
<application
        android:icon="@drawable/ic_launcher"
        android:label="@string/app_name" 
        android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" <
       <activity
            android:name=".InvokedActivity"
            android:label="@string/app_name"<
            <intent-filter<
                <action android:name="android.intent.action.MAIN" /<                         
               <category android:name="android.intent.category.INFO" / <
<-- If the activity is a launcher then mention this instead 
             <category android:name="android.intent.category.LAUNCHER" /
                             < --<

             </intent-filter <
        </activity <
       <receiver android:name=".TestBroadCastReceiver" <
           <intent-filter <
           <action android:name="com.custom.intent" <
          </action <
        </intent-filter <
       </receiver <
<application <
    

Here is the code for BroadCastReceiver:

public class TestBroadCastReceiver extends BroadcastReceiver { 
 
    private static final String CUSTOM_INTENT = "com.custom.intent";
    
    public void onReceive(Context context, Intent intent) {
         if (intent.getAction().equals(CUSTOM_INTENT)) {
              //your code here 
         } 
    }
} 

The code for InvokedActivity:


 public class InvokedActivity extends Activity { 
      
       public void onCreate(Bundle b) { 
             super.onCreate(b); 
             /*Toast.makeText(this, "starting xyz receiver...blah blah :)", Toast.LENGTH_LONG) .show();*/
             finish();
      } 
}
  
  

Reference:
Broadcast receiver – a change in flow since API 3.1 from our
JCG partner Ashimita Adusumilli at the
My small world of Android blog.

Source : http://www.javacodegeeks.com/2012/05/android-broadcast-receiver-change-in.html

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s