CDD: add requirement to enforce single runtime permission UI.

We would like to keep a consistent runtime permission user experience
across the Android ecosystem to avoid a world where app developers have
to code permission logic on a per target device basis.

bug:24003111

Change-Id: Id04f0d157f95027f952d74c634d78137ac1664a3

src/compatibility/android-cdd.html

diff --git a/src/compatibility/android-cdd.html b/src/compatibility/android-cdd.html
index ee588e1..057e214 100644
--- a/src/compatibility/android-cdd.html
+++ b/src/compatibility/android-cdd.html
@@ -4129,6 +4129,13 @@
 ignored. Implementations MAY add additional permissions, provided the new
 permission ID strings are not in the android.* namespace.</p>
 
+<p>Permissions with a protection level of dangerous are runtime permissions. Applications
+with targetSdkVersion > 22 request them at runtime. The system MUST show a dedicated UI for the
+user to decide whether to grant the requested runtime permissions and also provide a UI for the
+user to manage runtime permissions. On the system there MUST be one and only one
+implementation of both the UI for the user to accept runtime permissions and the UI for
+the user to manage runtime permissions.</p>
+
 <h2 id="9_2_uid_and_process_isolation">9.2. UID and Process Isolation</h2>