[automerger skipped] Enable SdkExtension MTS tests to be included in mts-sdkextensions as am: e515568516 -s ours

am skip reason: Change-Id I309c46632c60381b9044edce6a221de54355b005 with SHA-1 23fe168a2f is in history

Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/modules/SdkExtensions/+/13383033

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: Ib7b4e923cf28f14c3b753861d36703efe97fad8f
tree: 60c8ecfd1fee9e70cd59af1cfbe1c3b81bdc1923
  1. derive_sdk/
  2. framework/
  3. gen_sdk/
  4. proto/
  5. testing/
  6. tests/
  7. Android.bp
  8. com.android.sdkext.avbpubkey
  9. com.android.sdkext.pem
  10. com.android.sdkext.pk8
  11. com.android.sdkext.x509.pem
  12. gen_sdkinfo.py
  13. manifest.json
  14. OWNERS
  15. PREUPLOAD.cfg
  16. README.md
  17. TEST_MAPPING
README.md

SdkExtensions module

SdkExtensions is a module that decides the extension SDK level of the device, and provides APIs for applications to query the extension SDK level.

General information

Structure

The module is packaged in an apex, com.android.sdkext, and has two components:

  • bin/derive_sdk: Native binary that runs early in the device boot process and reads metadata of other modules, to set system properties relating to the extension SDK (for instance build.version.extensions.r).
  • javalib/framework-sdkextension.jar: This is a jar on the bootclasspath that exposes APIs to applications to query the extension SDK level.

Deriving extension SDK level

derive_sdk is a program that reads metadata stored in other apex modules, in the form of binary protobuf files in subpath etc/sdkinfo.binarypb inside each apex. The structure of this protobuf can be seen here. The exact steps for converting a set of metadata files to actual extension versions is likely to change over time, and should not be depended upon.

Reading extension SDK level

The module exposes a java class SdkExtensions in the package android.os.ext. The method getExtensionVersion(int) can be used to read the version of a particular sdk extension, e.g. getExtensionVersion(Build.VERSION_CODES.R).

Developer information

Adding a new extension version

For every new Android SDK level a new extension version should be defined. These are the steps necessary to do that:

  • Add the new modules in this extension version to the SdkModule enum in sdk.proto.
  • Update derive_sdk.cpp by:
  • mapping the modules' package names to the new enum values
  • creating a new set with the new enum values
  • set a new sysprop to the value of GetSdkLevel with the new enum set
  • add a unit test to derive_sdk_test.cpp verifying the new extensions works
  • Make the SdkExtensions.getExtensionVersion API support the new extensions.
  • Extend the CTS test to verify the above two behaviors.
  • Update RollbackManagerServiceImpl#getExtensionVersions to account for the new extension version.