Compatibility Definition

Recommendations

Info

perhaps on the wrist, and: MUST have a screen with the physical diagonal length in the range from 1.1 to 2.5 inches. MUST declare the feature android.hardware.type.watch. MUST support uiMode = UI_MODE_TYPE_WATCH [Resources, 4]. Android 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. Android Automotive implementations: MUST declare the feature android.hardware.type.automotive. MUST support uiMode = UI_MODE_TYPE_CAR [Resources, 5]. All 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 6.0 compatible, unless the requirement is explicitly described to be only applicable to a specific Android device type from above. 2.1 Device Configurations This is a summary of major differences in hardware configuration by device type. (Empty cells denote a “MAY”). Not all configurations are covered in this table; see relevant hardware sections for more detail. Category Feature Section Handheld Television Watch Automotive Other D-pad 7.2.2. Nontouch Navigation MUST Input Sensors Connectivity Output Touchscreen Microphone Accelerometer 7.2.4. Touchscreen input 7.8.1. Microphone 7.3.1 Accelerometer MUST MUST SHOULD MUST SHOULD MUST MUST SHOULD SHOULD SHOULD SHOULD GPS 7.3.3. GPS SHOULD SHOULD Wi-Fi Wi-Fi Direct Bluetooth Bluetooth Low Energy USB peripheral/host mode Speaker and/or Audio output ports 7.4.2. IEEE 802.11 7.4.2.1. Wi-Fi Direct 7.4.3. Bluetooth 7.4.3. Bluetooth SHOULD MUST SHOULD SHOULD SHOULD SHOULD SHOULD SHOULD MUST MUST MUST SHOULD SHOULD MUST SHOULD SHOULD SHOULD 7.7. USB SHOULD SHOULD SHOULD 7.8.2. Audio Output MUST MUST MUST MUST Page 6 of 74
3. Software 3.1. Managed API Compatibility The managed Dalvik bytecode execution environment is the primary vehicle for Android applications. The Android application programming interface (API) is the set of Android platform interfaces exposed to applications running in the managed runtime environment. Device implementations MUST provide complete implementations, including all documented behaviors, of any documented API exposed by the Android SDK [Resources, 6] or any API decorated with the “@SystemApi” marker in the upstream Android source code. Device implementations MUST NOT omit any managed APIs, alter API interfaces or signatures, deviate from the documented behavior, or include no-ops, except where specifically allowed by this Compatibility Definition. This Compatibility Definition permits some types of hardware for which Android includes APIs to be omitted by device implementations. In such cases, the APIs MUST still be present and behave in a reasonable way. See section 7 for specific requirements for this scenario. 3.2. Soft API Compatibility In addition to the managed APIs from section 3.1, Android also includes a significant runtime-only “soft” API, in the form of such things as intents, permissions, and similar aspects of Android applications that cannot be enforced at application compile time. 3.2.1. Permissions Device implementers MUST support and enforce all permission constants as documented by the Permission reference page [Resources, 7]. Note that section 9 lists additional requirements related to the Android security model. 3.2.2. Build Parameters The Android APIs include a number of constants on the android.os.Build class [Resources, 8] that are intended to describe the current device. To provide consistent, meaningful values across device implementations, the table below includes additional restrictions on the formats of these values to which device implementations MUST conform. Parameter VERSION.RELEASE VERSION.SDK VERSION.SDK_INT VERSION.INCREMENTAL Details The version of the currently-executing Android system, in humanreadable format. This field MUST have one of the string values defined in [Resources, 9]. The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 6.0, this field MUST have the integer value 23. The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 6.0, this field MUST have the integer value 23. A value chosen by the device implementer designating the specific build of the currently-executing Android system, in human-readable format. This value MUST NOT be reused for different builds made available to end users. A typical use of this field is to indicate which build number or source-control change identifier was used to generate Page 7 of 74
Page 1 and 2: Compatibility Definition Android 6.
Page 3 and 4: 6. Developer Tools and Options Comp
Page 5: 1. Introduction This document enume
Page 9 and 10: ID MANUFACTURER MODEL PRODUCT SERIA
Page 11 and 12: MUST provide the user with per-app
Page 13 and 14: present, only the corresponding fun
Page 15 and 16: Android follows the package and cla
Page 17 and 18: 120 dpi (ldpi) 48MB 160 dpi (mdpi)
Page 19 and 20: applications to end users in some h
Page 21 and 22: Android includes support for Roboto
Page 23 and 24: device setup. An open source implem
Page 25 and 26: Format/Codec Encoder Decoder Detail
Page 27 and 28: H.265 HEVC REQUIRED 5 See section 5
Page 29 and 30: Video bitrate 600 Kbps 1.6 Mbps 4 M
Page 31 and 32: implementations that declare the fe
Page 33 and 34: connectivity over Bluetooth LE, SHO
Page 35 and 36: The units referenced by the require
Page 37 and 38: Device implementations MUST support
Page 39 and 40: MAY omit a non-touch navigation opt
Page 41 and 42: pointer device only) MUST NOT repor
Page 43 and 44: as appropriate when applications at
Page 45 and 46: atch mode at 10 Hz. 7.3.3. GPS Devi
Page 47 and 48: MUST have a measurement range betwe
Page 49 and 50: implementations that cannot place c
Page 51 and 52: SHOULD be capable of reading the ba
Page 53 and 54: possibly dual-stack) on cellular da
Page 55 and 56: If an application has never called
Page 57 and 58:
Device implementations MUST be conf
Page 59 and 60:
Device implementations MAY omit a m
Page 61 and 62:
Random read. Device implementations
Page 63 and 64:
permissions used by the application
Page 65 and 66:
already launched on an earlier Andr
Page 67 and 68:
skipped or omitted. Every device an
Page 69 and 70:
Sensor 7.4.2. IEEE 802.11 (Wi- Fi)
Page 71 and 72:
43. Unicode 6.1.0: http://www.unico
Page 73 and 74:
105. Android NFC Sharing Settings:
show all

Compatibility Definition

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?