Bump min_sdk_version for all launched apex modules

Increase the minimum value for q-launched-apex-module to avoid targeting EoL'd dessert releases as part of
stopping mainline updates for Q "Sunset plan for Mainline on Android Q"

Previous-Platform-Support: (minSdkVersion=29)
Apex-Size-Increase: 0
Aosp-First: Aosp
Test-Info: No behavior change.

Test: m
Bug: 254749391
Bug: 265172663
Ignore-AOSP-First: submitted the change in aosp/2390852
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:3340b711f4656a45850c0883811ab7f2acfab578)
Merged-In: I3f53796448c28dcc03d4be488d78214818894e06
Change-Id: I3f53796448c28dcc03d4be488d78214818894e06
2 files changed
tree: 5d4e045984f23163e49da2b9d4a7e0e4dc05ee94
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.