语音App的界面切换到后台后执行完onStop(),紧接着执行onDestory().正常情况下,应该只执行onStop,不执行onDestory。通过log发现如下:
03-29 16:52:49.458 768 1085 I am_stop_activity: [0,4688954,com.gwm.app.vrassistant/.SettingActivity]
03-29 16:52:49.477 15822 15822 I am_on_stop_called: [0,com.gwm.app.vrassistant.SettingActivity,STOP_ACTIVITY_ITEM]
03-29 16:52:49.488 768 1085 I am_destroy_activity: [0,4688954,81,com.gwm.app.vrassistant/.SettingActivity,always-finish]
03-29 16:52:49.505 15822 15822 I am_on_destroy_called: [0,com.gwm.app.vrassistant.SettingActivity,performDestroy]
后面的reason是always-finish,在AMS中有源码如下:
if (mAlwaysFinishActivities) {
// Need to do this on its own message because the stack may not
// be in a consistent state at this point.
mStackSupervisor.scheduleDestroyAllActivities(null, "always-finish");
}
--------------------
下面主要看看mAlwaysFinishActivities在什么情况下,设置为true,发现是通过如下函数设置的,这是个AIDL接口是由APP来设置的。该接口的作用就是当应用切换到后台,执行其finish方法,这样间接调用到onDestory了
public void setAlwaysFinish(boolean enabled) {
enforceCallingPermission(android.Manifest.permission.SET_ALWAYS_FINISH,
"setAlwaysFinish()");
long ident = Binder.clearCallingIdentity();
try {
Settings.Global.putInt(
mContext.getContentResolver(),
Settings.Global.ALWAYS_FINISH_ACTIVITIES, enabled ? 1 : 0);
synchronized (this) {
mAlwaysFinishActivities = enabled;
}
} finally {
Binder.restoreCallingIdentity(ident);
}
}
最后发现在开发者选项,应用模块中,第一项“不保留活动”打开后,就会出现用户离开后即销毁每个活动,App切换到后台回调onDestory方法。
进行debug SystemServer进程的时候,发现打开和关闭“不保留活动”开关后,就会调用到AMS的setAlwaysFinish(),传过来true或false.