From 33d92c56781f6058c9e682737a06c41f3a2d2f3a Mon Sep 17 00:00:00 2001 From: Craig Mautner Date: Thu, 13 Nov 2014 16:17:17 -0800 Subject: [PATCH] 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 --- .../core/java/com/android/server/pm/PackageManagerService.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/core/java/com/android/server/pm/PackageManagerService.java b/services/core/java/com/android/server/pm/PackageManagerService.java index d402825442155..2b6ea5d23b75d 100644 --- a/services/core/java/com/android/server/pm/PackageManagerService.java +++ b/services/core/java/com/android/server/pm/PackageManagerService.java @@ -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;