Use package name as custom resolver process name
The process name was being assigned null. This meant that after the process attached we weren't matching the name in ActivityStackSupervisor.attachApplicationLocked(). That meant missing the call to realStartActivityLocked() and then the resolver didn't start until window manager timed out and resumeTopActivity was called five seconds later. Fixes bug 18301267. Change-Id: If3721caeebb309c6054150b2f707e3d6e38a74d2
This commit is contained in:
committed by
David Singleton
parent
cd22c3d67c
commit
33d92c5678
@ -6436,7 +6436,7 @@ public class PackageManagerService extends IPackageManager.Stub {
|
||||
mResolveActivity.applicationInfo = pkg.applicationInfo;
|
||||
mResolveActivity.name = mCustomResolverComponentName.getClassName();
|
||||
mResolveActivity.packageName = pkg.applicationInfo.packageName;
|
||||
mResolveActivity.processName = null;
|
||||
mResolveActivity.processName = pkg.applicationInfo.packageName;
|
||||
mResolveActivity.launchMode = ActivityInfo.LAUNCH_MULTIPLE;
|
||||
mResolveActivity.flags = ActivityInfo.FLAG_EXCLUDE_FROM_RECENTS |
|
||||
ActivityInfo.FLAG_FINISH_ON_CLOSE_SYSTEM_DIALOGS;
|
||||
|
Reference in New Issue
Block a user