From c7fc742a3ff9e23673d219c9d73c9679af9b338a Mon Sep 17 00:00:00 2001
From: Yohei Yukawa <yukawa@google.com>
Date: Mon, 25 Jul 2022 18:38:49 +0900
Subject: [PATCH] Grant CONTROL_UI_TRACING permission to Settings app (2nd try)

We are going to guard the following IPCs with CONTROL_UI_TRACING
permission [1].

 * IWindowManager#startWindowTrace()
 * IWindowManager#stopWindowTrace()
 * IInputMethodManager#startImeTrace()
 * IInputMethodManager#stopImeTrace()

For QS DevelopmentTiles to continue being allowed to access those
IPCs, this CL gives CONTROL_UI_TRACING to the Settings app.

 [1]: Ibdeb38dc9a066cb8ed2904adcdac29014b166526
      2ad02a383b036b02a836a50a43c679a17c2fde6b

Bug: 172444310
Test: Manually verified as follows.
 1. build aosp_coral-userdebug and flash it.
 2. adb shell dumpsys package com.android.settings
 3. Verify that
      android.permission.CONTROL_UI_TRACING
    is granted.
Change-Id: Ic65176d34daebc2190c6009f70d99f8fcb725c00
---
 AndroidManifest.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/AndroidManifest.xml b/AndroidManifest.xml
index 2ff62cced30..1735a517e25 100644
--- a/AndroidManifest.xml
+++ b/AndroidManifest.xml
@@ -16,6 +16,7 @@
     <uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS" />
     <uses-permission android:name="android.permission.DEVICE_POWER" />
     <uses-permission android:name="android.permission.CHANGE_CONFIGURATION" />
+    <uses-permission android:name="android.permission.CONTROL_UI_TRACING" />
     <uses-permission android:name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS" />
     <uses-permission android:name="android.permission.VIBRATE" />
     <uses-permission android:name="android.permission.BLUETOOTH_ADVERTISE" />