| commit | aa9f6036b086298f7be1aa25a13ac01f87814088 | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Tue Jan 21 18:06:46 2025 +0000 |
| committer | Nikita Ioffe <ioffe@google.com> | Wed Jan 29 16:18:51 2025 +0000 |
| tree | ac3f3e1d8ae59c53d79e871105c5e3c3d101bd4d | |
| parent | 901083f783ce945ed45508a0f153e2cb9717b9f2 [diff] |
Support i18n apex in Microdroid environment The i18n APEX expects the ANDROID_I18N_ROOT and ANDROID_TZDATA_ROOT variables to be configured. The ANDROID_I18N_ROOT should be set to /apex/com.android.i18n, since this is where i18n libs are located. It is no-op if i18n APEX is not mounted. For now the ANDROID_TZDATA_ROOT is set to a non-existent path, since libicu seem to work correctly without it. We might need to also add tzdata APEX to support APIS that depend on tzdata. Bug: 390557313 Test: atest MicrodroidTests Change-Id: Id89bd26a9bcb7b6d0aa0935171be4a4bdf916a20
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: