java.lang.Object | |
↳ | android.content.pm.PackageInstaller.SessionCallback |
Events for observing session lifecycle.
A typical session lifecycle looks like this:
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Active state for session has been changed.
| |||||||||||
Badging details for an existing session has changed.
| |||||||||||
New session has been created.
| |||||||||||
Session has completely finished, either with success or failure.
| |||||||||||
Progress for given session has been updated.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|
Active state for session has been changed.
A session is considered active whenever there is ongoing forward
progress being made, such as the installer holding an open
PackageInstaller.Session
instance while streaming data into place, or the
system optimizing code as the result of
commit(IntentSender)
.
If the installer closes the PackageInstaller.Session
without committing, the
session is considered inactive until the installer opens the session
again.
Badging details for an existing session has changed. For example, the app icon or label has been updated.
New session has been created. Details about the session can be
obtained from getSessionInfo(int)
.
Session has completely finished, either with success or failure.
Progress for given session has been updated.
Note that this progress may not directly correspond to the value
reported by
setStagingProgress(float)
, as the
system may carve out a portion of the overall progress to represent
its own internal installation work.