Docs: NEW CHANGE#21 for Android automotive changes to cdd
OTA download requirement is allowed but not mandatory
for Android Automotive implementations.
Bug: 19951915
Change-Id: I58ee0d19a4c8bf3df9a15bfbfab363e53d196920
diff --git a/src/compatibility/5.1/android-5.1-cdd.html b/src/compatibility/5.1/android-5.1-cdd.html
index d6239c3..cc7cc8d 100644
--- a/src/compatibility/5.1/android-5.1-cdd.html
+++ b/src/compatibility/5.1/android-5.1-cdd.html
@@ -4270,14 +4270,20 @@
approaches will satisfy this requirement:</p>
<ul>
- <li>Over-the-air (OTA) downloads with offline update via reboot</li>
+ <li>“Over-the-air (OTA)” downloads with offline update via reboot</li>
<li>“Tethered” updates over USB from a host PC</li>
<li>“Offline” updates via a reboot and update from a file on removable storage</li>
</ul>
<p>However, if the device implementation includes support for an unmetered data
-connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, the
-device MUST support Over-the-air download with offline update via reboot.</p>
+connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile:</p>
+
+<ul>
+<li>Android Automotive implementations SHOULD support OTA downloads with offline
+update via reboot.</li>
+<li>All other device implementations MUST support OTA downloads with offline
+update via reboot.</li>
+</ul>
<p>The update mechanism used MUST support updates without wiping user data. That
is, the update mechanism MUST preserve application private data and application
@@ -4617,7 +4623,9 @@
<tr>
<td>11. Updatable Software</td>
<td>If a device supports 802.11 or Bluetooth PAN (Personal Area Network) profile,
-then it MUST support Over-the-air download with offline update via reboot.</td>
+then it MUST support over-the-air (OTA) download with offline update via reboot. Clarified
+the OTA download requirement is allowed but not mandatory for Android Automotive
+implementations.</td>
</tr>
<tr>
<td>14. Resources</td>