#13818 thread forming tap full
#13818 thread forming tap android
#13818 thread forming tap software

The Requirement ID in Section 2 starts with the corresponding section ID that is followed by the Requirement ID described above.

This ID starts from 1 and increments by 1 within the same section and the same condition.

When the requirement is conditional, 1 is assigned for the 1st condition and the number increments by 1 within the same section and the same device type.

When the requirement is unconditional, this ID is set as 0.

#13818 thread forming tap android

C: Core (Requirements that are applied to any Android device implementations).

The ID consists of : Device Type ID - Condition ID - Requirement ID (e.g.

STRONGLY RECOMMENDED requirements are marked as but ID is not assigned.

The ID is assigned for MUST requirements only.

Requirement ID is assigned for MUST requirements. These requirements are referenced as 'Core Requirements' in this document. Each subsection of Section 2 is dedicated to a specific device type.Īll the other requirements, that universally apply to any Android device implementations, are listed in the sections after Section 2. Section 2 contains all of the requirements that apply to a specific device type. Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK’s documentation. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document.

#13818 thread forming tap full

It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite.

#13818 thread forming tap software

While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the “upstream” source code available from the Android Open Source Project. Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations.įor this reason, the Android Open Source Project is both the reference and preferred implementation of Android. To be considered compatible with Android 11, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. A “device implementation” or “implementation' is the hardware/software solution so developed. The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in RFC2119.Īs used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 11. This document enumerates the requirements that must be met in order for devices to be compatible with Android 11.