falocolorado.blogg.se

For anyĬase where this Compatibility Definition or the Compatibility Test Suiteĭisagrees with the SDK documentation, the SDK documentation is consideredĪuthoritative. Many of the resources listed in section 14 are derived directly or indirectly from the Android SDK, and will beįunctionally identical to the information in that SDK's documentation. Modifications are explicitly forbidden by this document. Finally, note that certain component substitutions and The standard Android implementation, including and beyond the Compatibility The implementer's responsibility to ensure full behavioral compatibility with Replaced with alternate implementations this practice is strongly discouraged,Īs passing the software tests will become substantially more difficult. While some components can hypothetically be Greatest extent possible on the "upstream" source code available from theĪndroid Open Source Project. Implementers are strongly encouraged to base their implementations to the Implementer to ensure compatibility with existing implementations.įor this reason, the Android Open Source Project is both the reference and preferred implementation of Android. Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device The requirements presented in this Compatibility Definition, including any

To be considered compatible with Android 5.0, device implementations MUST meet "device implementation" or "implementation" is the hardware/software solution

Or organization developing a hardware/software solution running Android 5.0. "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" is per the IETF standardĪs used in this document, a "device implementer" or "implementer" is a person The use of "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", This document enumerates the requirements that must be met in order for devices Legacy Application Compatibility Modeħ.4.2.2. Developer Tools and Options Compatibilityħ.1.5.