Lines Matching refs:stopped
57 activity starts, the previous activity is stopped, but the system preserves the activity
65 <p>When an activity is stopped because a new activity starts, it is notified of this change in state
70 appropriate to that state change. For instance, when stopped, your activity should release any
86 the activity is being created, stopped, resumed, or destroyed. The two most important callback
105 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
367 "background"). A stopped activity is also still alive (the {@link android.app.Activity}
373 <p>If an activity is paused or stopped, the system can drop it from memory either by asking it to
413 // The activity is no longer visible (it is now "stopped")
504 <td>Called after the activity has been stopped, just prior to it being
607 when an activity is paused or stopped, the state of the activity is retained. This is true because
609 stopped—all information about its members and current state is still alive. Thus, any changes
640 the previously saved state, or the activity is stopped, then resumed and the activity state
739 to understand that the first activity is not completely stopped before the second one is created.