Home
last modified time | relevance | path

Searched refs:APK (Results 1 – 25 of 27) sorted by relevance

12

/frameworks/base/services/tests/servicestests/assets/PackageSignaturesTest/xml/
DREADME1 The XML files in this directory are taken from the packages tag of a test APK signed with the
4 1. Build the test APK:
7 2. Sign the APK with the first signer:
11 3. Install the APK on a device:
14 4. Pull the packages.xml file containing the new entry for the APK from the device:
18 the full entry when the APK is signed as above:
/frameworks/opt/gamesdk/samples/tuningfork/tftestapp/app/src/main/proto/
Dtuningfork_clearcut_log.proto46 // Package name from APK manifest.
49 // Version code from APK manifest.
66 // The APK contains hard-coded bucket ranges for each instrument_id.
/frameworks/opt/gamesdk/src/tuningfork/proto/
Dtuningfork_clearcut_log.proto46 // Package name from APK manifest.
49 // Version code from APK manifest.
66 // The APK contains hard-coded bucket ranges for each instrument_id.
/frameworks/opt/gamesdk/samples/tuningfork/prototest/proto/
Dtuningfork_clearcut_log.proto46 // Package name from APK manifest.
49 // Version code from APK manifest.
66 // The APK contains hard-coded bucket ranges for each instrument_id.
Dtuningfork_extensions.proto19 // to Play from the APK.
Deng_tuningfork_extensions.proto14 // to clearcut/Play either through initialization or through APK
/frameworks/opt/gamesdk/test/tuningfork/proto/
Dtuningfork_clearcut_log.proto46 // Package name from APK manifest.
49 // Version code from APK manifest.
66 // The APK contains hard-coded bucket ranges for each instrument_id.
/frameworks/opt/gamesdk/src/tuningfork/tools/validation/
DREADME.md3 This tool validates Tuning Fork proto and settings files in an APK.
7 The APK must contain *assets/tuningfork/tuningfork_settings.bin* file with
142 The APK must contain at least one file in assets/tuningfork folder with pattern
/frameworks/opt/photoviewer/sample/
DAndroid.bp16 // Build APK
41 // Build APK
/frameworks/opt/setupwizard/tools/gradle/
Ddist-library-instrumentation-tests.gradle2 * This script plugin is used to build and dist the test APK outputs of a library with multiple
15 // because the default output only supports one test APK output for libraries.
/frameworks/base/lowpan/tests/
DREADME.md14 `runtests.sh` will build the test project and all of its dependencies and push the APK to the
37 If you manually build and push the test APK to the device you can run tests using
/frameworks/base/wifi/tests/
DREADME.md14 `runtests.sh` will build the test project and all of its dependencies and push the APK to the
37 If you manually build and push the test APK to the device you can run tests using
/frameworks/base/tools/aapt2/
Dreadme.md69 the original package ID is safe. Collisions against the base APK are checked to ensure these
74 - aapt2 optimize can now split a binary APK with the same --split parameters as the link
89 since the resulting APK is post-processed by other tools anyways. Assets do not get processed
155 - Configuration Split APK support: supports splitting resources that match a set of
156 configurations to a separate APK which can be loaded alongside the base APK on
DResources.proto342 // Path to a file within the APK (typically res/type-config/entry.ext).
/frameworks/opt/net/wifi/tests/wifitests/
DREADME.md14 `runtests.sh` will build the test project and all of its dependencies and push the APK to the
27 If you manually build and push the test APK to the device you can run tests using
/frameworks/opt/chips/sample/
DAndroid.bp16 // Build APK
/frameworks/base/core/tests/hosttests/test-apps/SharedUid/32/jni/
DAndroid.bp18 // use by our example of how to bundle a shared library with an APK.
/frameworks/base/core/tests/hosttests/test-apps/SharedUid/dual/jni/
DAndroid.bp18 // use by our example of how to bundle a shared library with an APK.
/frameworks/base/core/tests/hosttests/test-apps/SharedUid/64/jni/
DAndroid.bp18 // use by our example of how to bundle a shared library with an APK.
/frameworks/base/packages/SystemUI/docs/
Dplugins.md98 …s on.  This ensures that the latest version will be included in the plugin APK when it is compiled.
107 …enerated for the plugin and can be used to inflate or get any resources included in the plugin APK.
183 …ded).  This is required to ensure you don’t actually include the plugin library in your plugin APK.
193 Whenever loading a code from another APK into a privileged process like SysUI, there are serious se…
217 …, they are done so by creating a PathClassLoader that points at the plugin APK.  The parent of the…
227 …f any of the classes in the stack trace are from the package of the plugin APK, then the plugin is…
/frameworks/base/core/tests/coretests/
DREADME29 Next, install the resulting APK and run tests as you would normal JUnit tests:
/frameworks/base/packages/CtsShim/build/
DREADME4 must specify the singular APK that can be used to upgrade it.
/frameworks/native/opengl/libs/EGL/
DGLES_layers.md55 3. External APK
56 …Determine the ABI of your target application, then install an APK containing the layers you wish t…
61 4. In the target application's APK
/frameworks/base/core/tests/coretests/src/android/app/
DDownloadManagerBaseTest.java89 APK, enumConstant
423 case APK: in getMimeMapping()
/frameworks/compile/libbcc/
DREADME.rst153 type (rather in APK or on the file system), and the SHA1 checksum.

12