From 517a3e07611657f36ec85b9cf52d9430edf38adc Mon Sep 17 00:00:00 2001
From: Phil Weaver <pweaver@google.com>
Date: Tue, 22 Mar 2016 17:54:37 -0700
Subject: [PATCH] Fix ACCESSIBILITY_ENABLED settings.

A typo meant that the setting reflected the exact opposite of what was
intended.

Bug: 27781201
Change-Id: Icb0d4d585399f147b319093be57d708af4c6dfdc
---
 .../server/accessibility/AccessibilityManagerService.java       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java b/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java
index b4b40ae046b49..9a2611e61c110 100644
--- a/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java
+++ b/services/accessibility/java/com/android/server/accessibility/AccessibilityManagerService.java
@@ -1544,7 +1544,7 @@ public class AccessibilityManagerService extends IAccessibilityManager.Stub {
         try {
             Settings.Secure.putIntForUser(mContext.getContentResolver(),
                     Settings.Secure.ACCESSIBILITY_ENABLED,
-                    userState.isHandlingAccessibilityEvents() ? 0 : 1,
+                    userState.isHandlingAccessibilityEvents() ? 1 : 0,
                     userState.mUserId);
         } finally {
             Binder.restoreCallingIdentity(identity);