Exposing in-call API to other implementing classes. (3/4)
Adding "CONTROL_INCALL_EXPERIENCE" permission to in-call UI.
Bug: 16133960
Bug: 17007163
Change-Id: I96f590766599ae554cf8046c80f184eda080d264
diff --git a/AndroidManifest.xml b/AndroidManifest.xml
index fa13adf..05cd5b5 100644
--- a/AndroidManifest.xml
+++ b/AndroidManifest.xml
@@ -40,6 +40,7 @@
<uses-permission android:name="android.permission.USE_CREDENTIALS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.READ_SYNC_SETTINGS" />
+ <uses-permission android:name="android.permission.CONTROL_INCALL_EXPERIENCE" />
<uses-permission android:name="com.android.voicemail.permission.ADD_VOICEMAIL" />
<uses-permission android:name="com.android.voicemail.permission.WRITE_VOICEMAIL" />
<uses-permission android:name="com.android.voicemail.permission.READ_VOICEMAIL" />
@@ -294,7 +295,8 @@
</receiver>
<service android:name="com.android.incallui.InCallServiceImpl"
- android:process="com.android.incallui">
+ android:process="com.android.incallui"
+ android:permission="android.permission.BIND_INCALL_SERVICE" >
<intent-filter>
<action android:name="android.telecomm.InCallService"/>
</intent-filter>