An activity has essentially four states:
①If an activity in the foreground of the screen (at the top of the stack), it is active or running.
②If an activity has lost focus but is still visible (that is, a new non-full-sized or transparent activity has focus on top of your activity),
it is paused. A paused activity is completely alive (it maintains all state and member information and remains attached to the window manager),
but can be killed by the system in extreme low memory situations.
③If an activity is completely obscured by another activity, it is stopped. It still retains all state and member information, however,
it is no longer visible to the user so its window is hidden and it will often be killed by the system when memory is needed elsewhere.
④If an activity is paused or stopped, the system can drop the activity from memory by either asking it to finish, or simply killing its process.
When it is displayed again to the user, it must be completely restarted and restored to its previous state.
The following diagram shows the important state paths of an Activity. The square rectangles represent callback methods you can implement to perform operations when the Activity moves between states. The colored ovals are major states the Activity can be in.
