Fix SdkExt e2e test to pass on R/S

This test has only been running against HEAD platform in presubmit,
but it's going to be added to the backward-compatibility presubmits
next.

To achieve this:
1. Tweak the assertion on version based on platform
2. Stop verifying the java app can call new APIs on R, because it relies
   on the dynamic classpath feature which isn't available there.

Bug: 234114653
Bug: 234361913
Test: atest sdkextensions_e2e_tests (on R and S)
Change-Id: Iae29b09a16bef0135dc3da48ffef6d984e270fdf
(cherry picked from commit 9109148f25f960cd6d21c012cc7cede2385674b6)
Merged-In: Iae29b09a16bef0135dc3da48ffef6d984e270fdf
(cherry picked from commit 1cd095b02d09e2017605f75fcef968cae2f3ef77)
2 files changed
tree: f18e4123e53e0d426a7343bf2ed25ac9ef7e19e6
  1. derive_classpath/
  2. derive_sdk/
  3. gen_sdk/
  4. java/
  5. javatests/
  6. Android.bp
  7. com.android.sdkext.avbpubkey
  8. com.android.sdkext.pem
  9. com.android.sdkext.pk8
  10. com.android.sdkext.x509.pem
  11. manifest.json
  12. OWNERS
  13. PREUPLOAD.cfg
  14. README.md
  15. TEST_MAPPING
README.md

SdkExtensions module

SdkExtensions module is responsible for:

  • deciding the extension SDK level of the device;
  • providing APIs for applications to query the extension SDK level;
  • determining the values for the BOOTCLASSPATH, DEX2OATBOOTCLASSPATH, and SYSTEMSERVERCLASSPATH environment variables.

General information

Structure

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

  • bin/derive_classpath: a native binary that runs early in the device boot process. It reads individual classpath configs files from the system and other modules, merges them, and defines the definition of *CLASSPATH environ variables.
  • 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.pb 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).

Deriving classpaths

derive_classpath service reads and merges individual config files in the /system/etc/classpaths/ and /apex/*/etc/classpaths. Each config stores protobuf message from classpaths.proto in a proto binary format. Exact merging algorithm that determines the order of the classpath entries is described in derive_classpath.cpp and may change over time.

Developer information

Adding a new extension

An extension is a way to group a set of modules so that they are versioned together. We currently define a new extension for every Android SDK level that introduces new modules. Every module shipped in previous versions are also part of the new extension. For example, all the R modules are part of both the R extensions and the S extensions.

The steps to define a new extension are:

  • Add any new modules to the SdkModule enum in sdk.proto.
  • Add the binary "current sdk version" proto to the apexes of the new modules.
  • Update derive_sdk.cpp by:
  • mapping the modules' package names to the new enum values
  • creating a new set with the new enum values of the modules relevant for this extension.
  • 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 work
  • Make the SdkExtensions.getExtensionVersion API support the new extensions.
  • Extend the CTS test to verify the above two behaviors.