From 068c567fdda857e275fa424b766231b68b9a674f Mon Sep 17 00:00:00 2001 From: Jacky Kao Date: Thu, 7 Jan 2021 15:44:53 +0800 Subject: [PATCH] Allow services enabled after force close When an A11y service is enabled, it would be added into the list of the crashed services after doing force close. Then users can't enable this service until users disable this service again based on our crashed mechanism now. The A11y service would be removed from the list of enabled services after doing force close. We need to remove this service from the list of the crashed service at the same time to make sure users can enable this service next time immediately. Bug: 174616279 Test: a11y CTS & unit tests Test: manual testing by the steps in the bug Change-Id: Ie09a11dd2eb2ed7237b580e69c46751ef404b96a --- .../server/accessibility/AccessibilityManagerService.java | 1 + 1 file changed, 1 insertion(+) diff --git a/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java b/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java index c6919ad245723..9aa0aed06892a 100644 --- a/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java +++ b/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java @@ -508,6 +508,7 @@ public class AccessibilityManagerService extends IAccessibilityManager.Stub } it.remove(); userState.getBindingServicesLocked().remove(comp); + userState.getCrashedServicesLocked().remove(comp); persistComponentNamesToSettingLocked( Settings.Secure.ENABLED_ACCESSIBILITY_SERVICES, userState.mEnabledServices, userId);