aboutsummaryrefslogtreecommitdiff
path: root/en/compatibility
diff options
context:
space:
mode:
Diffstat (limited to 'en/compatibility')
-rw-r--r--en/compatibility/5.1/android-5.1-cdd.html16
-rw-r--r--en/compatibility/6.0/android-6.0-cdd.html13
2 files changed, 16 insertions, 13 deletions
diff --git a/en/compatibility/5.1/android-5.1-cdd.html b/en/compatibility/5.1/android-5.1-cdd.html
index 3fcff269..77448964 100644
--- a/en/compatibility/5.1/android-5.1-cdd.html
+++ b/en/compatibility/5.1/android-5.1-cdd.html
@@ -2096,18 +2096,20 @@ devices only when supported by hardware.</p>
<p class="table_footnote">2 STRONGLY RECOMMENDED for Android Television device implementations when
supported by hardware.</p>
-<p>Android device implementations, when supporting H.265 codec as described in <a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the Main Profile Level 3 Main tier and the following SD video
-decoding profiles and SHOULD support the HD decoding profiles. Android
-Television devices MUST support the Main Profile Level 4.1 Main tier and the HD
-1080p decoding profile and SHOULD support Main10 Level 5 Main Tier profile and
-the UHD decoding profile.</p>
+<p>Android device implementations, when supporting H.265 codec as described in
+<a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the Main Profile Level 3 Main tier
+and the following SD video decoding profiles and SHOULD support the HD decoding profiles. Android
+Television devices SHOULD support Main10 Level 5 Main Tier profile and the UHD decoding profile.
+Android Television devices are STRONGLY RECOMMENDED to support the HD 1080p decoding profile.
+If the HD 1080p decoding profile is supported, it MUST support the Main Profile Level
+4.1 Main tier</p>
<table>
<tr>
<th></th>
<th>SD (Low quality)</th>
<th>SD (High quality)</th>
<th>HD 720p </strong>1 </td>
- <th>HD 1080p </strong>1 </td>
+ <th>HD 1080p </strong>2 </td>
<th>UHD </strong>2</td>
</tr>
<tr>
@@ -2140,7 +2142,7 @@ the UHD decoding profile.</p>
<p class="table_footnote">1 Required for Android Television device implementation, but for other type of
devices only when supported by hardware.</p>
-<p class="table_footnote">2 Required for Android Television device implementations when supported by
+<p class="table_footnote">2 STRONGLY RECOMMENDED for Android Television device implementations when supported by
hardware.</p>
<h2 id="5_4_audio_recording">5.4. Audio Recording</h2>
diff --git a/en/compatibility/6.0/android-6.0-cdd.html b/en/compatibility/6.0/android-6.0-cdd.html
index d3e7d4ce..ba8ea512 100644
--- a/en/compatibility/6.0/android-6.0-cdd.html
+++ b/en/compatibility/6.0/android-6.0-cdd.html
@@ -2446,17 +2446,17 @@ supported by hardware.</p>
<a href="#5_1_3_video_codecs">section 5.1.3</a>, MUST support the Main Profile
Level 3 Main tier and the following SD video decoding profiles and SHOULD
support the HD decoding profiles.
-Android Television devices MUST support the Main Profile Level 4.1 Main tier and
-the HD 1080p decoding profile and is STRONGLY RECOMMENDED to support the UHD
-decoding profile. If UHD decoding is supported, then it MUST support Main10
-Level 5 Main Tier profile.</p>
+Android Television devices are STRONGLY RECOMMENDED to support the UHD decoding profile
+and the HD 1080p decoding profile. If the HD 1080p decoding profile is supported, it MUST support
+the Main Profile Level 4.1 Main tier. If UHD decoding is supported, then it MUST support
+Main10 Level 5 Main Tier profile.</p>
<table>
<tr>
<th></th>
<th>SD (Low quality)</th>
<th>SD (High quality)</th>
<th>HD 720p<sup>1</sup></th>
- <th>HD 1080p<sup>1</sup></th>
+ <th>HD 1080p<sup>2</sup></th>
<th>UHD<sup>2</sup></th>
</tr>
<tr>
@@ -3495,7 +3495,8 @@ remote or can be a software-based remote that is accessible from a mobile phone
or tablet. The remote control MUST meet the requirements defined below.</p>
<ul>
- <li><strong>Search affordance</strong>. Device implementations MUST fire KEYCODE_SEARCH when the user invokes voice search either on the physical or software-based remote.</li>
+ <li><strong>Search affordance</strong>. Device implementations MUST fire KEYCODE_SEARCH (or KEYCODE_ASSIST if the device supports an assistant)
+ when the user invokes voice search on either the physical or software-based remote.</li>
<li><strong>Navigation</strong>. All Android Television remotes MUST include Back, Home, and Select buttons and
support for D-pad events [<a href="http://developer.android.com/reference/android/view/KeyEvent.html">Resources, 88</a>].</li>
</ul>