Google Pixel 3 64Gb+4Gb LTE [26/132] Soft api compatibility
Макгруп McGrp.ru
Задайте вопрос
Зарегистрироваться

Google Pixel 3 64Gb+4Gb LTE [26/132] Soft api compatibility

Google Pixel 3 64Gb+4Gb LTE [26/132] Soft api compatibility
attribute of <uses-library> to org.apache.http.legacy .
The AOSP implementation meets these requirements.
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
[C-0-1] Device implementers MUST support and enforce all permission constants as
documented by the Permission reference page . 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 that are intended to
describe the current device.
[C-0-1] 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 Details
VERSION.RELEASE
The version of the currently-executing Android system, in human-
readable format. This field MUST have one of the string values defined
in 9 .
VERSION.SDK
The version of the currently-executing Android system, in a format
accessible to third-party application code. For Android 9, this field
MUST have the integer value 9_INT.
VERSION.SDK_INT
The version of the currently-executing Android system, in a format
accessible to third-party application code. For Android 9, this field
MUST have the integer value 9_INT.
VERSION.INCREMENTAL
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
the build. There are no requirements on the specific format of this field,
except that it MUST NOT be null or the empty string ("").
BOARD
A value chosen by the device implementer identifying the specific
internal hardware used by the device, in human-readable format. A
possible use of this field is to indicate the specific revision of the board
powering the device. The value of this field MUST be encodable as 7-bit
ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”.
BRAND
A value reflecting the brand name associated with the device as known
to the end users. MUST be in human-readable format and SHOULD
represent the manufacturer of the device or the company brand under
which the device is marketed. The value of this field MUST be
Page 26 of 132

Содержание

Похожие устройства

Скачать