| commit | f7c742ac8abbe23d308e68a082c02d675f72b0ea | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Mon Sep 04 16:57:59 2023 +0100 |
| committer | Nikita Ioffe <ioffe@google.com> | Tue Sep 05 09:28:03 2023 +0100 |
| tree | 92284ca4e2b4a38b39529d783cea0924e40b3b6a | |
| parent | da1b273f4c8f0aa2a26649a0100d1676f6a36f0d [diff] |
Add support for checking whether feature is enabled on device In case of AVF development most of the features will be protected for build time flags, meaning that we need to provide a way for tests to query whether device build actually has the feature enabled. This is achieved by providing isFeatureEnabled @TestApi. As part of this change I've also switched the payloadIsNotRoot test to use this new API as an example of how the API can be used in tests. Bug: 298012279 Bug: 298008232 Test: atest MicrodroidTests Change-Id: If9afc013e178439f45627c1ac7dfe50242799f09
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:
How-Tos: