Lines Matching full:requirements
168 <p>This document enumerates the requirements that must be met in order for
178 MUST meet the requirements presented in this Compatibility Definition,
301 <a href="#section-7">Section 7</a> for specific requirements for this scenario.
313 requirements related to the Android security model.</p>
350 identifier was used to generate the build. There are no requirements on the
412 human readable format. There are no requirements on the specific format of
428 There are no requirements on the specific format of this field, except that it
435 is marketed and sold to end users. There are no requirements on the specific
476 build. There are no requirements on the specific format of this field, except
820 home screen MUST meet the following requirements and declare support for platform feature <code>android.software.app_widgets</code>.</p>
960 the following requirements.</p>
985 Device implementations MUST meet these requirements related to the Android TTS
1030 <p>Note that these tables do not list specific bitrate requirements for
1410 <p><b>Note:</b> while some of the requirements outlined above are stated as "SHOULD"
1412 to change these to "MUST". That is, these requirements are optional in Android
1415 these requirements in Android 4.3</b>, or they will not be able to attain
1443 Device implementations SHOULD meet or exceed these output latency requirements:</p>
1448 <p>If a device implementation meets the requirements of this section
1457 implementation does not meet these requirements it MUST NOT report support for
1465 meet these input audio latency requirements:</p>
1547 <p>A typical example of a scenario where these requirements apply is the
1563 <p>The units referenced by the requirements in this section are defined as follows:</p>
1735 that they meet the requirements defined this Compatibility Definition.</p>
1738 device MUST meet the following requirements:</p>
1837 the navigation keys, but if so, MUST meet these requirements:</p>
1844 applications that meets the requirements defined in
1878 functionality. Device implementations that declare the fake touch feature MUST meet the fake touch requirements in <a href="section 7.2.5">Section 7.2.5</a>.</p>
1884 touchscreen feature, and MUST report only <code>android.hardware.faketouch</code> if they meet the fake touch requirements in <a href="section 7.2.5">Section 7.2.5</a>.</p>
1901 <p>Devices that declare support for <code>android.hardware.faketouch.multitouch.distinct</code> MUST meet the requirements for
1912 <li>SHOULD meet the audio quality requirements in <a href="section-5.4">Section 5.4</a></li>
1913 <li>SHOULD meet the audio latency requirements in <a href="section-5.5">Section 5.5</a></li>
1959 new devices that run Android 4.3 are <b>very strongly encouraged to meet these requirements
1998 new devices that run Android 4.3 are <b>very strongly encouraged to meet these requirements
2117 encouraged to meet these requirements in Android 4.3</b> so they will be
2393 new devices that run Android 4.3 are <b>very strongly encouraged to meet these requirements
2399 encouraged to meet these requirements in Android 4.3</b> so they will be able to upgrade to future platform releases.</li>
2411 Existing and new devices that run Android 4.3 are <b>very strongly encouraged to meet these requirements in Android 4.3</b>
2530 <p>Device implementations MUST meet these requirements related to multi-user support [<a href="#resources71">Resources, 71</a>]:</p>