By the document, "onPause" is called, when:
when the system is about to start resuming a previous activity.
Compared to "onStop", the difference is:
Called when the activity is no longer visible to the user, because another activity has been resumed and is covering this one.
But when I long-press HW-Home key and the "recent apps" shows up, the "onPause" is not called.
At this moment, I can no long able to interact with the original activity, but it is still visible.
I am confused by this situation. Please help to explain.
Thank you very much. BR, Henry
Even if your activity slips into the background when another activity starts or when the screen switches off, onPause() is always called even if the other two methods aren't called. So even if activity ceases, onPause() will be called and your thread will be killed.
Unfortunately the onPause() method is called immediately after onCreate.
onPause() is always called. This is guaranteed. If you need to save any state in your activity you need to save it in onPause() . onStop() may be called after onPause() , or it may not.
During this time, the activity is in front of all other activities on screen and has user input focus. An activity can frequently transition in and out of the foreground—for example, onPause() is called when the device goes to sleep or when a dialog appears.
This actually happens because when the Home key is long pressed, there is no activity being launched. The onPause/onStop will only be called if you select one of the apps present in the "Recent Apps" list.
The docs of onPause() are pretty clear:
Called as part of the activity lifecycle when an activity is going into the background, but has not (yet) been killed.
In a lot of modern phones, the recent apps list is an activity, and does trigger onPause
. I've tested this on a couple of Samsung and LG phones, and the packages are com.android.systemui
and com.lge.launcher2
respectively.
That said, it seems like you can't rely on recieving an onPause when you open the recent applications screen. I'm curious to see how many device don't give you the onPause
...
public class MainActivity extends Activity
{
String tag="my result";
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
Log.v(tag,"I am in oncreate");
}
@Override
protected void onDestroy() {
// TODO Auto-generated method stub
super.onDestroy();
Log.v(tag,"I am in onDestroy");
}
@Override
protected void onPause() {
// TODO Auto-generated method stub
super.onPause();
Log.v(tag,"I am in onpause");
}
@Override
protected void onRestart() {
// TODO Auto-generated method stub
super.onRestart();
Log.v(tag,"I am in onRestart");
}
@Override
protected void onResume() {
// TODO Auto-generated method stub
super.onResume();
Log.v(tag,"I am in onresume");
}
@Override
protected void onStart() {
// TODO Auto-generated method stub
super.onStart();
Log.v(tag,"I am in onstart");
}
@Override
protected void onStop() {
// TODO Auto-generated method stub
super.onStop();
Log.v(tag,"I am in onstop");
}
}
Run it and check logcat.press back button and then check.after again start application and
Press call button then check logcat now press Back button and again check logcat. you can easily understand life cycle of Activity.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With