Lines Matching full:requirements
358 <p>This document enumerates the requirements that must be met in order for devices
370 the requirements presented in this Compatibility Definition, including any
398 compatibility requirements were optimized for handheld devices. Starting from
446 types still MUST meet all requirements in this document to be Android 6.0
593 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>
606 documented by the Permission reference page [<a href="http://developer.android.com/reference/android/Manifest.permission.html">Resources, 7</a>]. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model.</p>
643 identifier was used to generate the build. There are no requirements on the
716 human-readable format. There are no requirements on the specific format of this
730 There are no requirements on the specific format of this field, except that it
737 marketed and sold to end users. There are no requirements on the specific
774 There are no requirements on the specific format of this field, except that it
1036 <p>These requirements only apply when /proc/cpuinfo is read by 32-bit ARM
1426 home screen MUST meet the following requirements and declare support for
1586 <p>As the Recent function navigation key is OPTIONAL, the requirements to
1595 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>
1756 <li>MUST ensure that it satisfies all the security requirements applicable for a device
1771 <p>Device implementations include the following requirements:</p>
1806 MUST meet these requirements related to the Android TTS framework. </p>
1848 and meet the following requirements:</p>
1869 The EPG MUST meet the following requirements:</p>
2202 requirements in [<a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">Resources, 68</a>].</p>
2488 <p>While some of the requirements outlined in this section are stated as SHOULD
2491 to meet these requirements, or they will not be able to attain Android compatibility when upgraded
2568 to the requirements in this section.</p>
2648 or exceed these audio output requirements:</p>
2656 <p>If a device implementation meets the requirements of this section after any
2661 android.content.pm.PackageManager class [<a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">Resources, 70</a>]. Conversely, if the device implementation does not meet these requirements it
2665 these input audio requirements:</p>
2735 If a device implementation meets <em>all</em> of the following requirements,
2874 <p>A typical example of a scenario where these requirements apply is the telephony
2891 <p>The units referenced by the requirements in this section are defined as
3136 <p>Devices MUST support a touchscreen or meet the requirements listed in 7.2.2
3251 navigation keys, but if so, MUST meet these requirements:</p>
3258 applications that meets the requirements defined in <a href="#7_1_1_screen_configuration">section 7.1.1</a>.</li>
3303 meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p>
3313 meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>.</p>
3339 MUST meet the requirements for faketouch above, and MUST also support distinct
3485 or tablet. The remote control MUST meet the requirements defined below.</p>
3719 the requirements listed in this section MUST identify the support through the
3723 sensor types meeting the quality requirements as below:</p>
3746 <li>SENSOR_TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as
3757 <li>SENSOR_TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements as
3808 <p>Also such a device MUST meet the following sensor subsystem requirements:</p>
3828 <p>Note that all power consumption requirements in this section do not include the power
3874 data securely migrated to meet the above requirements or removed.</li>
4023 requirements now so they will be able to upgrade to the future platform releases.
4150 Wi-Fi and cellular data), it MUST simultaneously meet these requirements on
4515 new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li>
4520 the port at bottom. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to future platform releases.</li>
4538 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, 120</a>]. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases.</li>
4578 <li>MUST meet the audio recording requirements in <a href="#5_4_audio_recording">section 5.4</a></li>
4579 <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a></li>
4595 <li>MUST meet the audio playback requirements in <a href="#5_5_audio_playback">section 5.5</a>.</li>
4596 <li>MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>.</li>
4686 implementations MUST meet the following requirements: </p>
4863 the following requirements related to multi-user support [<a href="http://source.android.com/devices/storage/traditional.html">Resources, 128</a>]:</p>
4928 following requirements, which are satisfied by the reference implementation
5039 <p>All Android device implementations MUST meet the following requirements:</p>
5062 <p>Note that while the above TEE-related requirements are stated as STRONGLY RECOMMENDED, the
5066 requirements through a system software update and thus is STRONGLY RECOMMENDED to implement a
5202 <td>Section renamed from "Intent Overrides" to "Intent Resolution," with new requirements related to authoritative default app linking</td>
5218 <td>Updates regarding Assistant requirements</td>
5230 <td>New section with requirements for device support of managed profile functionality</td>
5234 <td>Added section to clarify TV App requirements for Android Television devices</td>
5238 <td>Added section to clarify EPG requirements for Android Television devices</td>
5242 <td>Added section to clarify TV App navigation requirements for Android Television devices</td>
5245 <td>Added section to clarify TV input app linking support requirements for Android Television devices</td>
5290 <td>Updated requirements for device implementations that include the Assist action</td>
5294 <td>New requirements for some sensor types</td>
5298 <td>New section with requirements for devices supporting high fidelity sensors</td>
5302 <td>New section on requirements related to fingerprint sensors</td>
5314 <td>Additions to requirements for Near-Field Communications (NFC)</td>
5318 <td>Added requirements for IPv6 support</td>
5334 <td>New section with requirements regarding the App Standby and Doze modes</td>
5338 <td>New section with requirements for tracking hardware component power usage and attributing that power usage to specific applications</td>
5342 <td>Addition to Permissions requirements</td>
5354 <td>Requirements related to full disk encryption</td>
5362 <td>New section of requirements related to keys and credentials</td>
5519 <p>68. RTC Hardware Coding Requirements: <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">http://www.webmproject.org/hardware/rtc-coding-requirements/</a></p>
