Introduction This document enumerates the requirements that must be met in order for devices to be compatible with Android 9. The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in.
Get It for 97% off. The Complete Six Sigma Training & Certification Bundle $59 $2300. The Complete Adobe Mastery Bundle: Lifetime Access $39 $2189. IOS Soft Dev Pack for iPhone 4 Tecnologia do Blogger. Nenhuma postagem. Nenhuma postagem. Assinar: Postagens (Atom) TemplateParaDownload.
As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 9. A “device implementation” or “implementation' is the hardware/software solution so developed.
![Pack Pack](/uploads/1/2/5/4/125482968/680261179.png)
To be considered compatible with Android 9, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. Where this definition or the software tests described in are silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations. For this reason, the is both the reference and preferred implementation of Android.
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. 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. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document. 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. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative.
Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition. 1.1 Document Structure 1.1.1.
Requirements by Device Type contains all of the requirements that apply to a specific device type. Each subsection of is dedicated to a specific device type. All the other requirements, that universally apply to any Android device implementations, are listed in the sections after. These requirements are referenced as 'Core Requirements' in this document. Requirement ID Requirement ID is assigned for MUST requirements. The ID is assigned for MUST requirements only.
STRONGLY RECOMMENDED requirements are marked as SR but ID is not assigned. The ID consists of: Device Type ID - Condition ID - Requirement ID (e.g.
Each ID is defined as below:. Device Type ID (see more in ). C: Core (Requirements that are applied to any Android device implementations). H: Android Handheld device. T: Android Television device. A: Android Automotive implementation. Tab: Android Tablet implementation.
Condition ID. When the requirement is unconditional, this ID is set as 0. 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. Requirement ID. This ID starts from 1 and increments by 1 within the same section and the same condition. Requirement ID in Section 2 The Requirement ID in starts with the corresponding section ID that is followed by the Requirement ID described above. The ID in consists of: Section ID / Device Type ID - Condition ID - Requirement ID (e.g.
Device Types While the Android Open Source Project provides a software stack that can be used for a variety of device types and form factors, there are a few device types that have a relatively better established application distribution ecosystem. This section describes those device types, and additional requirements and recommendations applicable for each device type.
All Android device implementations that do not fit into any of the described device types MUST still meet all requirements in the other sections of this Compatibility Definition. 2.1 Device Configurations For the major differences in hardware configuration by device type, see the device-specific requirements that follow in this section. Handheld Requirements An Android Handheld device refers to an Android device implementation that is typically used by holding it in the hand, such as an mp3 player, phone, or tablet. Android device implementations are classified as a Handheld if they meet all the following criteria:. Have a power source that provides mobility, such as a battery.
Have a physical diagonal screen size in the range of 2.5 to 8 inches. The additional requirements in the rest of this section are specific to Android Handheld device implementations. Note: Requirements that do not apply to Android Tablet devices are marked with an. Hardware Handheld device implementations:.1.1/H-0-1 MUST have a screen at least 2.5 inches in physical diagonal size.1.3/H-SR Are STRONGLY RECOMMENDED to provide users an affordance to change the display size.(Screen Density) If Handheld device implementations claim support for high dynamic range displays through, they:.4.5/H-1-1 MUST advertise support for the EGLEXTglcolorspacebt2020pq, EGLEXTsurfaceSMPTE2086metadata, EGLEXTsurfaceCTA8613metadata, VKEXTswapchaincolorspace, and VKEXThdrmetadata extensions.
Handheld device implementations:.5/H-0-1 MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.1/H-0-1 MUST include support for third-party Input Method Editor (IME) applications.3/H-0-1 MUST provide the Home, Recents, and Back functions.3/H-0-2 MUST send both the normal and long press event of the Back function to the foreground application. These events MUST NOT be consumed by the system and CAN be triggered by outside of the Android device (e.g.
External hardware keyboard connected to the Android device).4/H-0-1 MUST support touchscreen input.4/H-SR Are STRONGLY RECOMMENDED to launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the on long-press of or if the foreground activity does not handle those long-press events.1/H-SR Are STRONGLY RECOMMENDED to include a 3-axis accelerometer. If Handheld device implementations include a 3-axis accelerometer, they:.1/H-1-1 MUST be able to report events up to a frequency of at least 100 Hz. If Handheld device implementations include a gyroscope, they:.4/H-1-1 MUST be able to report events up to a frequency of at least 100 Hz. Handheld device implementations that can make a voice call and indicate any value other than PHONETYPENONE in getPhoneType:.8/H SHOULD include a proximity sensor. Handheld device implementations:.12/H-SR Are RECOMMENDED to support pose sensor with 6 degrees of freedom.3/H SHOULD include support for Bluetooth and Bluetooth LE. If Handheld device implementations include a metered connection, they:.7/H-1-1 MUST provide the data saver mode. Handheld device implementations:.1/H-0-1 MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a.
'/data' partition).1/H-0-2 MUST return “true” for ActivityManager.isLowRamDevice when there is less than 1GB of memory available to the kernel and userspace.