why "onPause" is not called in following situation?

android android-activity lifecycle timing onpause
Henry picture Henry · Feb 10, 2012 · Viewed 9.9k times · Source

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

Answer

MobileCushion picture MobileCushion · Feb 10, 2012

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.

Related questions

How to check if an activity is the last one in the activity stack for an application?

I want to know if user would return to the home screen if he exit the current activity.

Read More
How to check if my activity is the current activity running in the screen

I used Toast to make notification, but it seems it will appear even its activity is not in the current screen and some other activity has been started. I want to check this situation, when the activity is not the …

Read More
android finish() method doesn't clear app from memory

I have an activity and I call the finish() method and the activity is not cleared from memory. After calling finish() , I see that the method onDestroy() is executed successfully (and I clear all my variables and stuff in there). …

Read More