PendingIntent

Flag indicating that if the described PendingIntent already exists, the current one should be canceled before generating a new one. For use with getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , and getService(Context, int, Intent, int) .

You can use this to retrieve a new PendingIntent when you are only changing the extra data in the Intent; by canceling the previous pending intent, this ensures that only entities given the new data will be able to launch it. If this assurance is not an issue, consider FLAG_UPDATE_CURRENT .

Flag indicating that if the described PendingIntent does not already exist, then simply return null instead of creating it. For use with getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , and getService(Context, int, Intent, int) .

Flag indicating that this PendingIntent can be used only once. For use with getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , and getService(Context, int, Intent, int) .

If set, after send() is called on it, it will be automatically canceled for you and any future attempt to send through it will fail.

Flag indicating that if the described PendingIntent already exists, then keep it but replace its extra data with what is in this new Intent. For use with getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , and getService(Context, int, Intent, int) .

This can be used if you are creating intents where only the extras change, and don't care that any entities that received your previous PendingIntent will be able to launch it with your new extras even if they are not explicitly given to it.

Cancel a currently active PendingIntent. Only the original application owning a PendingIntent can cancel it.

Describe the kinds of special objects contained in this Parcelable's marshalled representation.

Comparison operator on two PendingIntent objects, such that true is returned then they both represent the same operation from the same package. This allows you to use getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , or getService(Context, int, Intent, int) multiple times (even across a process being killed), resulting in different PendingIntent objects but whose equals() method identifies them as being the same operation.

Like getActivity(Context, int, Intent, int) , but allows an array of Intents to be supplied. The last Intent in the array is taken as the primary key for the PendingIntent, like the single Intent given to getActivity(Context, int, Intent, int) . Upon sending the resulting PendingIntent, all of the Intents are started in the same way as they would be by passing them to startActivities(Intent[]) .

The first intent in the array will be started outside of the context of an existing activity, so you must use the Intent.FLAG_ACTIVITY_NEW_TASK launch flag in the Intent. (Activities after the first in the array are started in the context of the previous activity in the array, so FLAG_ACTIVITY_NEW_TASK is not needed nor desired for them.)

The last intent in the array represents the key for the PendingIntent. In other words, it is the significant element for matching (as done with the single intent given to getActivity(Context, int, Intent, int) , its content will be the subject of replacement by send(Context, int, Intent) and FLAG_UPDATE_CURRENT , etc. This is because it is the most specific of the supplied intents, and the UI the user actually sees when the intents are started.

For security reasons, the Intent objects you supply here should almost always be explicit intents , that is specify an explicit component to be delivered to through )">Intent.setClass

Like getActivity(Context, int, Intent, int) , but allows an array of Intents to be supplied. The last Intent in the array is taken as the primary key for the PendingIntent, like the single Intent given to getActivity(Context, int, Intent, int) . Upon sending the resulting PendingIntent, all of the Intents are started in the same way as they would be by passing them to startActivities(Intent[]) .

The first intent in the array will be started outside of the context of an existing activity, so you must use the Intent.FLAG_ACTIVITY_NEW_TASK launch flag in the Intent. (Activities after the first in the array are started in the context of the previous activity in the array, so FLAG_ACTIVITY_NEW_TASK is not needed nor desired for them.)

The last intent in the array represents the key for the PendingIntent. In other words, it is the significant element for matching (as done with the single intent given to getActivity(Context, int, Intent, int) , its content will be the subject of replacement by send(Context, int, Intent) and FLAG_UPDATE_CURRENT , etc. This is because it is the most specific of the supplied intents, and the UI the user actually sees when the intents are started.

For security reasons, the Intent objects you supply here should almost always be explicit intents , that is specify an explicit component to be delivered to through )">Intent.setClass

Retrieve a PendingIntent that will start a new activity, like calling Context.startActivity(Intent) . Note that the activity will be started outside of the context of an existing activity, so you must use the Intent.FLAG_ACTIVITY_NEW_TASK launch flag in the Intent.

For security reasons, the Intent you supply here should almost always be an explicit intent , that is specify an explicit component to be delivered to through )">Intent.setClass

Retrieve a PendingIntent that will start a new activity, like calling Context.startActivity(Intent) . Note that the activity will be started outside of the context of an existing activity, so you must use the Intent.FLAG_ACTIVITY_NEW_TASK launch flag in the Intent.

For security reasons, the Intent you supply here should almost always be an explicit intent , that is specify an explicit component to be delivered to through )">Intent.setClass

Retrieve a PendingIntent that will perform a broadcast, like calling Context.sendBroadcast() .

For security reasons, the Intent you supply here should almost always be an explicit intent , that is specify an explicit component to be delivered to through )">Intent.setClass

Return the package name of the application that created this PendingIntent, that is the identity under which you will actually be sending the Intent. The returned string is supplied by the system, so that an application can not spoof its package.

Be careful about how you use this. All this tells you is who created the PendingIntent. It does not tell you who handed the PendingIntent to you: that is, PendingIntent objects are intended to be passed between applications, so the PendingIntent you receive from an application could actually be one it received from another application, meaning the result you get here will identify the original application. Because of this, you should only use this information to identify who you expect to be interacting with through a send() call, not who gave you the PendingIntent.

Return the uid of the application that created this PendingIntent, that is the identity under which you will actually be sending the Intent. The returned integer is supplied by the system, so that an application can not spoof its uid.

Be careful about how you use this. All this tells you is who created the PendingIntent. It does not tell you who handed the PendingIntent to you: that is, PendingIntent objects are intended to be passed between applications, so the PendingIntent you receive from an application could actually be one it received from another application, meaning the result you get here will identify the original application. Because of this, you should only use this information to identify who you expect to be interacting with through a send() call, not who gave you the PendingIntent.

Return the user handle of the application that created this PendingIntent, that is the user under which you will actually be sending the Intent. The returned UserHandle is supplied by the system, so that an application can not spoof its user. See Process.myUserHandle() for more explanation of user handles.

Be careful about how you use this. All this tells you is who created the PendingIntent. It does not tell you who handed the PendingIntent to you: that is, PendingIntent objects are intended to be passed between applications, so the PendingIntent you receive from an application could actually be one it received from another application, meaning the result you get here will identify the original application. Because of this, you should only use this information to identify who you expect to be interacting with through a send() call, not who gave you the PendingIntent.

Retrieve a IntentSender object that wraps the existing sender of the PendingIntent

Retrieve a PendingIntent that will start a service, like calling Context.startService() . The start arguments given to the service will come from the extras of the Intent.

For security reasons, the Intent you supply here should almost always be an explicit intent , that is specify an explicit component to be delivered to through )">Intent.setClass

Returns an integer hash code for this object. By contract, any two objects for which equals(Object) returns true must return the same hash code value. This means that subclasses of Object usually override both methods or neither method.

Note that hash values must not change over time unless information used in equals comparisons also changes.

See Writing a correct hashCode method if you intend implementing your own hashCode method.

Convenience function for reading either a Messenger or null pointer from a Parcel. You must have previously written the Messenger with writePendingIntentOrNullToParcel(PendingIntent, Parcel) .

Perform the operation associated with this PendingIntent.

Perform the operation associated with this PendingIntent, allowing the caller to specify information about the Intent to use and be notified when the send has completed.

For the intent parameter, a PendingIntent often has restrictions on which fields can be supplied here, based on how the PendingIntent was retrieved in getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , or getService(Context, int, Intent, int) .

Perform the operation associated with this PendingIntent, allowing the caller to be notified when the send has completed.

Perform the operation associated with this PendingIntent, allowing the caller to specify information about the Intent to use and be notified when the send has completed.

For the intent parameter, a PendingIntent often has restrictions on which fields can be supplied here, based on how the PendingIntent was retrieved in getActivity(Context, int, Intent, int) , getBroadcast(Context, int, Intent, int) , or getService(Context, int, Intent, int) .

Perform the operation associated with this PendingIntent.

Perform the operation associated with this PendingIntent, allowing the caller to specify information about the Intent to use.

Returns a string containing a concise, human-readable description of this object. Subclasses are encouraged to override this method and provide an implementation that takes into account the object's type and data. The default implementation is equivalent to the following expression:

          getClass().getName() + '@' + Integer.toHexString(hashCode())
         

See Writing a useful toString method if you intend implementing your own toString method.

Convenience function for writing either a PendingIntent or null pointer to a Parcel. You must use this with readPendingIntentOrNullFromParcel(Parcel) for later reading it.

Flatten this object in to a Parcel.