Home | History | Annotate | Download | only in compatibility

Lines Matching full:requirements

356 <p>This document enumerates the requirements that must be met in order for
372 implementations MUST meet the requirements presented in this Compatibility
405 compatibility requirements were optimized for handheld devices. Starting from
456 device types still MUST meet all requirements in this document to be Android
606 <a href="#7_hardware_compatibility">section 7</a> for specific requirements for
625 9</a> lists additional requirements related to the Android security model.</p>
666 no requirements on the specific format of this field, except that it MUST
748 human-readable format. There are no requirements on the specific format of
763 product. There are no requirements on the specific format of this field,
770 the device is marketed and sold to end users. There are no requirements on
810 build. There are no requirements on the specific format of this field,
1085 <p>These requirements only apply when /proc/cpuinfo is read by 32-bit ARM
1495 widgets on the home screen MUST meet the following requirements and declare
1677 <p>As the Recent function navigation key is OPTIONAL, the requirements to
1690 the interface but MUST meet the following requirements:</p>
1867 <li>MUST ensure that it satisfies all the security requirements applicable for
1884 <p>Device implementations include the following requirements:</p>
1920 requirements related to the
1964 Channels</a> and meet the following requirements:</p>
1985 fields. The EPG MUST meet the following requirements:</p>
2341 <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">requirements</a>.
2640 <p>While some of the requirements outlined in this section are stated as SHOULD
2643 RECOMMENDED</strong> to meet these requirements, or they will not be able to
2722 conform to the requirements in this section.</p>
2811 STRONGLY RECOMMENDED to meet or exceed these audio output requirements:</p>
2819 <p>If a device implementation meets the requirements of this section after any
2826 class. Conversely, if the device implementation does not meet these requirements
2830 RECOMMENDED to meet these input audio requirements:</p>
2899 <p>If a device implementation meets <em>all</em> of the following requirements,
3020 <p>A typical example of a scenario where these requirements apply is the
3040 <p>The units referenced by the requirements in this section are defined as
3303 <p>Devices MUST support a touchscreen or meet the requirements listed in 7.2.2
3425 the navigation keys, but if so, MUST meet these requirements:</p>
3432 applications that meets the requirements defined in
3481 fake touch feature MUST meet the fake touch requirements in
3492 meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section
3525 android.hardware.faketouch.multitouch.distinct MUST meet the requirements for
3673 or tablet. The remote control MUST meet the requirements defined below.</p>
3716 <strong>STRONGLY RECOMMENDED</strong> to meet these requirements so they will
3941 meet all the requirements listed in this section MUST identify the support
3945 the following sensor types meeting the quality requirements as below:</p>
3969 <li>SENSOR_TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as
3980 <li>SENSOR_TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements
4035 <p>Also such a device MUST meet the following sensor subsystem requirements:</p>
4058 <p>Note that all power consumption requirements in this section do not include
4106 fingerprint data securely migrated to meet the above requirements or removed.
4277 strongly encouraged to meet these requirements now so they will be able to
4417 Wi-Fi and cellular data), it MUST simultaneously meet these requirements on
4802 requirements</strong> so they will be able to upgrade to the future platform
4809 are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they
4834 <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will
4882 <li>MUST meet the audio recording requirements in
4884 <li>MUST meet the audio latency requirements in
4901 <li>MUST meet the audio playback requirements in
4903 <li>MUST meet the audio latency requirements in
4996 implementations MUST meet the following requirements:</p>
5193 following requirements related to
5264 following requirements, which are satisfied by the reference implementation
5378 <p>All Android device implementations MUST meet the following requirements:</p>
5405 <p>Note that while the above TEE-related requirements are stated as STRONGLY
5409 the secure hardware, such a device might not be able to meet the requirements