Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [115/118] Data deletion

KeyGenParameterSpec.Builder.setUserAuthenticationRequired(true) ).

9.12. Data Deletion

All device implementations:

[C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset".

[C-0-2] MUST delete all user-generated data. That is, all data except for the following:

The system image

Any operating system files required by the system image

[C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards

such as NIST SP800-88.

[C-0-4] MUST trigger the above "Factory Data Reset" process when the

DevicePolicyManager.wipeData() API is called by the primary user's Device Policy Controller

app.

MAY provide a fast data wipe option that conducts only a logical data erase.

9.13. Safe Boot Mode

Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled

system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot

Mode", provides the user the capability to uninstall potentially harmful third-party apps.

Device implementations are:

[SR] STRONGLY RECOMMENDED to implement Safe Boot Mode.

If device implementations implement Safe Boot Mode, they:

[C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is

uninterruptible from third-party apps installed on the device, except when the third-party

app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag

as true.

[C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe

Mode.

SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a

workflow that is different from that of a normal boot.

9.14. Automotive Vehicle System Isolation

Android Automotive devices are expected to exchange data with critical vehicle subsystems by using

the vehicle HAL to send and receive messages over vehicle networks such as CAN bus.

The data exchange can be secured by implementing security features below the Android framework

layers to prevent malicious or unintentional interaction with these subsystems.

10. Software Compatibility Testing

Device implementations MUST pass all tests described in this section. However, note that no

software test package is fully comprehensive. For this reason, device implementers are STRONGLY

RECOMMENDED to make the minimum number of changes as possible to the reference and preferred

implementation of Android available from the Android Open Source Project. This will minimize the

risk of introducing bugs that create incompatibilities requiring rework and potential device updates.

Page 115 of 118