Lines Matching full:requirements
177 <p>This document enumerates the requirements that must be met in order for
187 MUST meet the requirements presented in this Compatibility Definition,
294 <a name="resources86"></a><li id="resources86">RTC Hardware Coding Requirements: <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">http://www.webmproject.org/hardware/rtc-coding-requirements/</a></li>
325 <a href="#section-7">Section 7</a> for specific requirements for this scenario.
337 requirements related to the Android security model.</p>
374 identifier was used to generate the build. There are no requirements on the
436 human readable format. There are no requirements on the specific format of
452 There are no requirements on the specific format of this field, except that it
459 is marketed and sold to end users. There are no requirements on the specific
501 build. There are no requirements on the specific format of this field, except
882 home screen MUST meet the following requirements and declare support for platform feature <code>android.software.app_widgets</code>.</p>
1046 the following requirements.</p>
1071 Device implementations MUST meet these requirements related to the Android TTS
1116 <p>Note that these tables do not list specific bitrate requirements for
1356 requirements in [<a href="#resources86">Resources, 86</a>].</li>
1521 <p><b>Note:</b> while some of the requirements outlined above are stated as
1523 is planned to change these to "MUST". That is, these requirements are optional
1526 requirements</b>, or they will not be able to attain Android
1559 Device implementations SHOULD meet or exceed these output latency requirements:</p>
1564 <p>If a device implementation meets the requirements of this section
1573 implementation does not meet these requirements it MUST NOT report support for
1581 meet these input audio latency requirements:</p>
1669 <p>A typical example of a scenario where these requirements apply is the
1685 <p>The units referenced by the requirements in this section are defined as follows:</p>
1858 that they meet the requirements defined this Compatibility Definition.</p>
1861 device MUST meet the following requirements:</p>
1992 the navigation keys, but if so, MUST meet these requirements:</p>
1998 applications that meets the requirements defined in
2029 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>
2035 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>
2052 <p>Devices that declare support for <code>android.hardware.faketouch.multitouch.distinct</code> MUST meet the requirements for
2063 <li>SHOULD meet the audio quality requirements in <a href="section-5.4">Section 5.4</a></li>
2064 <li>SHOULD meet the audio latency requirements in <a href="section-5.5">Section 5.5</a></li>
2110 new devices that run Android are <b>very strongly encouraged to meet these requirements
2149 new devices that run Android are <b>very strongly encouraged to meet these requirements</b>
2285 to meet these requirements now</b> so they will be able to upgrade to the
2588 new devices that run Android are <b>very strongly encouraged to meet these requirements
2594 encouraged to meet these requirements in Android</b> so they will be able to upgrade to future platform releases.</li>
2607 meet these requirements</b>
2726 <p>Device implementations MUST meet these requirements related to multi-user support [<a href="#resources71">Resources, 71</a>]:</p>
2765 <p>Devices MUST implement SELinux and meet the following requirements, which
2973 for devices with less than 512MB of memory. Increased storage requirements
