The managed Dalvik bytecode execution environment is the primary vehicle for Android applications. Not all configurations are covered in this table see relevant hardware sections for more detail. This is a summary of major differences in hardware configuration by device type. Android Automotive implementations MUST support all public APIs in the android.car.* namespace.Īll Android device implementations that do not fit into any of the above device types still MUST meet all requirements in this document to be Android 7.0 compatible, unless the requirement is explicitly described to be only applicable to a specific Android device type from above.MUST support uiMode = UI_MODE_TYPE_CAR. MUST have a screen with the physical diagonal length equal to or greater than 6 inches.MUST support uiMode = UI_MODE_TYPE_WATCH.Īndroid Automotive implementation refers to a vehicle head unit running Android as an operating system for part or all of the system and/or infotainment functionality.MUST have a screen with the physical diagonal length in the range from 1.1 to 2.5 inches.MUST declare the features and .Īndroid Watch device refers to an Android device implementation intended to be worn on the body, perhaps on the wrist, and:.MUST have an embedded screen OR include a video output port, such as VGA, HDMI, or a wireless port for display.MUST have a power source that provides mobility, such as a battery.Īndroid Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user interface”).MUST have a touchscreen embedded in the device.Starting from Android 5.0, the Android Open Source Project aims to embrace a wider variety of device types as described in this section.Īndroid Handheld device refers to an Android device implementation that is typically used by holding it in the hand, such as mp3 players, phones, and tablets. While the Android Open Source Project has been used in the implementation of a variety of device types and form factors, many aspects of the architecture and compatibility requirements were optimized for handheld devices. 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. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. 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 7.0, 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 7.0. This document enumerates the requirements that must be met in order for devices to be compatible with Android 7.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |