Xiaomi Redmi Note 8 Pro 128Gb+6Gb Dual LTE [130/132] Updatable software

The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain

bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions

of the CTS may be released for Android 9.

Device implementations:

[C-0-3] MUST pass the latest CTS version available at the time the device software is

completed.

SHOULD use the reference implementation in the Android Open Source tree as much as

possible.

10.2. CTS Verifier

The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human

operator to test functionality that cannot be tested by an automated system, such as correct

functioning of a camera and sensors.

Device implementations:

[C-0-1] MUST correctly execute all applicable cases in the CTS verifier.

The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional.

Device implementations:

[C-0-2] MUST pass all tests for hardware that they possess; for instance, if a device

possesses an accelerometer, it MUST correctly execute the Accelerometer test case in

the CTS Verifier.

Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped

or omitted.

[C-0-2] Every device and every build MUST correctly run the CTS Verifier, as noted above.

However, since many builds are very similar, device implementers are not expected to

explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device

implementations that differ from an implementation that has passed the CTS Verifier only

by the set of included locales, branding, etc. MAY omit the CTS Verifier test.

11. Updatable Software

[C-0-1] Device implementations MUST include a mechanism to replace the entirety of the

system software. The mechanism need not perform “live” upgrades—that is, a device

restart MAY be required. Any method can be used, provided that it can replace the entirety

of the software preinstalled on the device. For instance, any of the following approaches

will satisfy this requirement:

“Over-the-air (OTA)” downloads with offline update via reboot.

“Tethered” updates over USB from a host PC.

“Offline” updates via a reboot and update from a file on removable storage.

[C-0-2] The update mechanism used MUST support updates without wiping user data.

That is, the update mechanism MUST preserve application private data and application

shared data. Note that the upstream Android software includes an update mechanism

that satisfies this requirement.

If the device implementations include support for an unmetered data connection such as 802.11 or

Page 130 of 132