Lines Matching full:requirements
324 <p>This document enumerates the requirements that must be met in order for devices
336 the requirements presented in this Compatibility Definition, including any
364 compatibility requirements were optimized for handheld devices. Starting from
405 types still MUST meet all requirements in this document to be Android 5.1
552 MUST still be present and behave in a reasonable way. See <a href="#7_hardware_compatibility">section 7</a> for specific requirements for this scenario.</p>
565 documented by the Permission reference page [<a href="http://developer.android.com/reference/android/Manifest.permission.html">Resources, 6]</a>. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model.</p>
602 identifier was used to generate the build. There are no requirements on the
675 human-readable format. There are no requirements on the specific format of this
689 There are no requirements on the specific format of this field, except that it
696 marketed and sold to end users. There are no requirements on the specific
732 There are no requirements on the specific format of this field, except that it
935 <p>These requirements only apply when /proc/cpuinfo is read by 32-bit ARM
1259 home screen MUST meet the following requirements and declare support for
1402 <p>As the Recent function navigation key is OPTIONAL, the requirements to
1411 implementations including the recents function navigation key as detailed in <a href="#7_2_3_navigation_keys">section 7.2.3</a>, MAY alter the interface but MUST meet the following requirements:</p>
1507 <p>Device implementations include the following requirements:</p>
1542 MUST meet these requirements related to the Android TTS framework. </p>
1871 requirements in [<a href="http://www.webmproject.org/hardware/rtc-coding-requirements
2149 <p>While some of the requirements outlined in this section are stated as SHOULD
2151 to change these to MUST. Existing and new Android devices are <strong>very strongly encouraged</strong> to meet these requirements, or they will not be able to attain Android
2220 to the requirements in this section.</p>
2297 or exceed these audio output requirements:</p>
2305 <p>If a device implementation meets the requirements of this section after any
2310 android.content.pm.PackageManager class [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 53</a>]. Conversely, if the device implementation does not meet these requirements it
2314 these input audio requirements:</p>
2438 <p>A typical example of a scenario where these requirements apply is the telephony
2455 <p>The units referenced by the requirements in this section are defined as
2698 <p>Devices MUST support a touchscreen or meet the requirements listed in 7.2.2
2815 navigation keys, but if so, MUST meet these requirements:</p>
2822 applications that meets the requirements defined in <a href="#7_1_1_screen_configuration">section 7.1.1</a>.</li>
2867 meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p>
2877 meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p>
2903 MUST meet the requirements for faketouch above, and MUST also support distinct
3049 or tablet. The remote control MUST meet the requirements defined below.</p>
3414 future versions. Existing and new devices that run this version of Android are <strong>very strongly encouraged</strong> to meet these requirements now so they will be able to upgrade to the future platform releases.</li>
3857 new Android devices are <strong>very strongly encouraged to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li>
3862 the port at bottom. Existing and new Android devices are <strong>very strongly encouraged to meet these requirements</strong> so they will be able to upgrade to future platform releases.</li>
3876 as specified in the USB battery charging specification [<a href="http://www.usb.org/developers/docs/devclass_docs/USB_Battery_Charging_1.2.pdf">Resources, 99</a>]. Existing and new Android devices are <strong>very strongly encouraged to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li>
3915 <li>MUST meet the audio recording requirements in <a href="#5_4_audio_recording">section 5.4</a>
3916 <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>
3930 <li>MUST meet the audio playback requirements in <a href="#5_5_audio_playback">section 5.5</a>.</li>
3931 <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>.</li>
3993 implementations MUST meet the following requirements: </p>
4115 the following requirements related to multi-user support [<a href="http://source.android.com/devices/storage/">Resources, 104</a>]:</p>
4186 if using a kernel other than Linux and meet the following requirements, which
4425 <td>Added Android automotive requirements.</td>
4429 <td>Added Android automotive requirements.</td>
4437 <td>Added Android automotive requirements.</td>
4445 <td>Added Android automotive requirements.</td>
4453 <td>Added Android Automotive requirements.</td>
4457 <td>Added Android Automotive requirements.</td>
4469 <td>Added Android Automotive requirements.</td>
4477 <td>Updated minimum memory requirements for lower resulution screen devices
4482 <td>Updated requirements when support for host machine access is mandatory.</td>
4486 <td>Added Android Automotive requirements.</td>
4490 <td>Clarified requirements.</td>
4626 <p>51. RTC Hardware Coding Requirements: <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">http://www.webmproject.org/hardware/rtc-coding-requirements/</a></p>
