CDD: Change to Enable Notification Listener on the lowRam device am: ca55e5cc15 am: 84d509b89a am: dbc15ca7d5
Original change: https://googleplex-android-review.googlesource.com/c/platform/compatibility/cdd/+/11300040
Change-Id: I8781a091e8a6f26cb4fcb886737a91301543f2f3
diff --git a/2_device-types/2_5_automotive-reqs.md b/2_device-types/2_5_automotive-reqs.md
index 9f14212..84077a4 100644
--- a/2_device-types/2_5_automotive-reqs.md
+++ b/2_device-types/2_5_automotive-reqs.md
@@ -114,6 +114,8 @@
* [[7.5](#7_5_cameras)/A-SR] Are STRONGLY RECOMMENDED to have a resolution
of at least 1.3 megapixels.
* SHOULD have either fixed-focus or EDOF (extended depth of field) hardware.
+* SHOULD support [Android Synchronization Framework](
+https://source.android.com/devices/graphics/sync).
* MAY have either hardware auto-focus or software auto-focus implemented in
the camera driver.
diff --git a/2_device-types/2_6_tablet-reqs.md b/2_device-types/2_6_tablet-reqs.md
index d5024d8..bbbb5f9 100644
--- a/2_device-types/2_6_tablet-reqs.md
+++ b/2_device-types/2_6_tablet-reqs.md
@@ -1,13 +1,13 @@
## 2.6\. Tablet Requirements
-An **Android Tablet device** refers to an Android device implementation that is
-typically used by holding in both hands and not in a clamshell form-factor.
+An **Android Tablet device** refers to an Android device implementation that
+typically meets all the following criteria:
-Android device implementations are classified as a Tablet if they meet all the
-following criteria:
-
-* Have a power source that provides mobility, such as a battery.
-* Have a physical diagonal screen size in the range of 7 to 18 inches.
+* Used by holding in both hands.
+* Does not have a clamshell or convertible configuration.
+* Physical keyboard implementations used with the device connect by
+ means of a standard connection (e.g. USB, Bluetooth).
+* Has a power source that provides mobility, such as a battery.
Tablet device implementations have similar requirements to handheld device
implementations. The exceptions are indicated by an \* in that section
diff --git a/3_software/3_8_user-interface-compatibility.md b/3_software/3_8_user-interface-compatibility.md
index f26fb1c..fafb1b8 100644
--- a/3_software/3_8_user-interface-compatibility.md
+++ b/3_software/3_8_user-interface-compatibility.md
@@ -563,11 +563,21 @@
* [C-3-5] MUST provide a user affordance to block an app from displaying in
PIP mode; the AOSP implementation meets this requirement by having
controls in the notification shade.
-* [C-3-6] MUST allocate minimum width and height of 108 dp for the PIP window
- and minimum width of 240 dp and height of 135 dp for the PIP window when the
- `Configuration.uiMode` is configured as [`UI_MODE_TYPE_TELEVISION`](
- https://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_TELEVISION).
+* [C-3-6] MUST allocate the following minimum width and height for the PIP
+ window when an application does not declare any value for
+ [`AndroidManifestLayout_minWidth`](
+ https://developer.android.com/reference/android/R.styleable.html#AndroidManifestLayout_minWidth)
+ and [`AndroidManifestLayout_minHeight`](
+ https://developer.android.com/reference/android/R.styleable.html#AndroidManifestLayout_minHeight):
+ * Devices with the Configuration.uiMode that is set other than
+ [`UI_MODE_TYPE_TELEVISION`](
+ https://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_TELEVISION)
+ MUST allocate a minimum width and height of 108 dp.
+ * Devices with the Configuration.uiMode that is set to
+ [`UI_MODE_TYPE_TELEVISION`](
+ https://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_TELEVISION)
+ MUST allocate a minimum width of 240 dp and a minimum height of 135 dp.
### 3.8.15\. Display Cutout
diff --git a/3_software/3_9_device-administration.md b/3_software/3_9_device-administration.md
index 714005f..983b125 100644
--- a/3_software/3_9_device-administration.md
+++ b/3_software/3_9_device-administration.md
@@ -120,9 +120,13 @@
applicable for a device with multiple users enabled
(see [section 9.5](#9_5_multi-user_support)), even though the managed profile
is not counted as another user in addition to the primary user.
-* [C-1-10] MUST support the ability to specify a separate lock screen meeting
+
+If device implementations declare `android.software.managed_users` and
+`android.software.secure_lock_screen`, they:
+
+* [C-2-1] MUST support the ability to specify a separate lock screen meeting
the following requirements to grant access to apps running in a managed
- profile.
+ profile only.
* Device implementations MUST honor the
[`DevicePolicyManager.ACTION_SET_NEW_PASSWORD`](https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_SET_NEW_PASSWORD)
intent and show an interface to configure a separate lock screen
