Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4. For building and contributing to AOSP, we recommend utilizing android-latest-release instead of aosp-main. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. For more information, see Changes to AOSP.
APEX signing
Stay organized with collections
Save and categorize content based on your preferences.
Each APEX file is signed twice:
Manage APEX keys
Every APEX uses two unique keys: one for its mini file system image and another
for the entire APEX file.
Test keys are used for development builds, while release keys are used to sign
public builds. For best practices on release key management and the signing
process, see Key management.
Non-pre-installed APEX
As described in pre-install trusted public keys, the public signing key for
a non-pre-installed APEX's mini file system image must be pre-installed on the
target partition. The OEM build server must populate the
/partition/etc/brand_new_apex/ directory with the necessary release public
keys for all potential non-pre-installed APEXes and ensure any test keys are
removed.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2026-06-17 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-17 UTC."],[],[]]
