commit bbebba34974df8179da14999273bf47bbf8b691f
author Jeff Sharkey <jsharkey@android.com> Wed Nov 18 15:36:11 2015 -0700
committer Jeff Sharkey <jsharkey@android.com> Thu Nov 19 11:12:12 2015 -0700
tree 8ad2f41dc21e5a4b5432efc158814f70456ad7fd
parent 6377b9423b6638ceed0e4461b302d8bf9db93de4

Mark this coreApp as being encryptionAware.

Historically, apps marked with "coreApp" were prepared to run in a
limited boot environment, and were critical to booting the device, so
in the new file-based encryption world we're marking these apps with
both "forceDeviceEncrypted" and "encryptionAware" attributes.

Bug: 22358539
Change-Id: Ia40e2ab95132bccaf3fdb6484fdab3239258b2d0

AndroidManifest.xml

diff --git a/AndroidManifest.xml b/AndroidManifest.xml
index 30b9e4d..5b0f624 100644
--- a/AndroidManifest.xml
+++ b/AndroidManifest.xml
@@ -76,7 +76,9 @@
             android:allowBackup="false"
             android:supportsRtl="true"
             android:process="system"
-            android:usesCleartextTraffic="false">
+            android:usesCleartextTraffic="false"
+            android:forceDeviceEncrypted="true"
+            android:encryptionAware="true">
 
         <!-- CALL vs CALL_PRIVILEGED vs CALL_EMERGENCY
              We have three different intents through which a call can be initiated each with its