| /system/extras/ioblame/ |
| D | ioblame-gmail-launch.example | 65 File: /framework/arm/boot-android.hidl.base-V1.0-java.vdex
68 File: /framework/arm/boot.art
71 File: /framework/arm/boot-core-libart.oat
74 File: /framework/arm/boot-core-libart.vdex
77 File: /framework/arm/boot-framework.oat
83 File: /framework/arm/boot-framework.vdex
89 File: /framework/arm/boot.oat
93 File: /framework/arm/boot-okhttp.oat
96 File: /framework/arm/boot-okhttp.vdex
99 File: /framework/arm/boot-org.apache.http.legacy.boot.vdex
[all …]
|
| D | ioblame-gmail-run.example | 602 File: /framework/android.hidl.base-V1.0-java.jar
605 File: /framework/android.hidl.manager-V1.0-java.jar
608 File: /framework/apache-xml.jar
611 File: /framework/arm/boot-android.hidl.base-V1.0-java.vdex
614 File: /framework/arm/boot.art
617 File: /framework/arm/boot-conscrypt.vdex
620 File: /framework/arm/boot-core-libart.oat
624 File: /framework/arm/boot-core-libart.vdex
628 File: /framework/arm/boot-ext.oat
631 File: /framework/arm/boot-ext.vdex
[all …]
|
| /system/libvintf/ |
| D | HalManifest.cpp | 356 if (!checkVendorNdkCompatibility(mat.device.mVendorNdk, framework.mVendorNdks, error)) { in checkCompatibility()
360 if (!checkSystemSdkCompatibility(mat.device.mSystemSdk, framework.mSystemSdk, error)) { in checkCompatibility()
365 for (const auto &range : mat.framework.mSepolicy.sepolicyVersions()) { in checkCompatibility()
381 ->getMatchedKernelRequirements(mat.framework.mKernels, kernel()->level(), error) in checkCompatibility()
411 matrix.framework.mSepolicy = Sepolicy(0u /* kernelSepolicyVersion */, in generateCompatibleMatrix()
446 return framework.mVendorNdks; in vendorNdks()
477 lft.framework.mVndks == rgt.framework.mVndks && in operator ==()
479 lft.framework.mVendorNdks == rgt.framework.mVendorNdks && in operator ==()
480 lft.framework.mSystemSdk == rgt.framework.mSystemSdk)); in operator ==()
613 framework.mVndks.insert(framework.mVndks.end(), other->framework.mVndks.begin(), in addAll()
[all …]
|
| D | CompatibilityMatrix.cpp | 46 auto it = framework.mKernels.begin(); in addKernel()
47 for (; it != framework.mKernels.end(); ++it) { in addKernel()
65 bool seenVersion = it != framework.mKernels.end(); in addKernel()
91 framework.mKernels.push_back(MatrixKernel(KernelVersion{kernel.minLts()}, {})); in addKernel()
95 framework.mKernels.push_back(std::move(kernel)); in addKernel()
258 for (MatrixKernel& kernel : other->framework.mKernels) { in addAllKernels()
274 bool success = mergeField(&this->framework.mSepolicy, &other->framework.mSepolicy); in addSepolicy()
280 bool success = mergeField(&this->framework.mAvbMetaVersion, &other->framework.mAvbMetaVersion); in addAvbMetaVersion()
317 (lft.framework.mKernels == rgt.framework.mKernels && in operator ==()
318 lft.framework.mSepolicy == rgt.framework.mSepolicy && in operator ==()
[all …]
|
| D | RuntimeInfo.cpp | 81 if (kernelSepolicyVersion() < mat.framework.mSepolicy.kernelSepolicyVersion()) { in checkCompatibility()
85 " but required >= " + to_string(mat.framework.mSepolicy.kernelSepolicyVersion()); in checkCompatibility()
94 if (mKernel.getMatchedKernelRequirements(mat.framework.mKernels, kernelLevel(), error) in checkCompatibility()
101 const Version& matAvb = mat.framework.mAvbMetaVersion; in checkCompatibility()
|
| /system/chre/doc/ |
| D | framework_debugging.md | 5 This section lists the methods that can be used to aid in CHRE framework
10 The CHRE framework invokes the `LOGx()` macros defined in
22 CHRE framework currently supports four levels, namely Error `LOGE()`, Warning
33 The CHRE framework currently only supports compile-time log level filtering.
43 a complementary function typically used to output a snapshot of the framework's
46 diagnose potential issues. The CHRE framework produces a debug dump when
53 `DebugDumpManager` is the framework module responsible for collecting debug
54 dumps from the CHRE framework and nanoapps. Refer to the associated
|
| D | vendor_extensions.md | 5 The CHRE framework is easily extensible with no modifications to the core
6 framework. Depending on the goals of the new API, one or more of the following
11 framework code and vendor-specific nanoapps.
13 2. Expose the new APIs from the framework to nanoapps, and connect them to a new
16 3. Integrate the new module with existing CHRE framework features, e.g. the
61 As part of the CHRE framework build system, the `CHRE_VARIANT_MK_INCLUDES`
65 additions needed to support the new vendor API. Refer to the CHRE framework
90 Since the new API will not be part of the core framework, it won’t be attached
102 Calls from a nanoapp into the CHRE framework first arrive in platform-specific
104 once an API call reaches the framework is usually to call
|
| D | framework_build.md | 6 building the CHRE framework for a variety of hardware and software architectures
10 variables. While the CHRE framework source code may be integrated into another
12 reduce maintenance burden when the CHRE framework is updated. Additionally, it
14 commonality across devices), and the CHRE framework build shares configuration
55 Compiling the framework for different devices is done by specifying the build
64 software that the CHRE framework builds on top of, such as the combination of
72 own CHRE framework implementation, targeting a CPU family called Potato, and a
133 CHRE framework for each supported platform. These must be added to Make
143 * `<build_target>/libchre.so` and `libchre.a`: the resulting CHRE framework
|
| D | framework_testing.md | 5 The CHRE framework can be tested at various levels to ensure that
40 of CHRE APIs that they are named after, and can be useful during framework
44 attempt to point out stress points in the framework or platform implementation.
46 These apps are usually built into the CHRE framework binary as static nanoapps
|
| /system/tools/hidl/test/java_test/ |
| D | hidl_test_java | 1 export CLASSPATH=/data/framework/hidl_test_java_java.jar
15 app_process /data/framework com.android.commands.hidl_test_java.HidlTestJava -c \
22 app_process /data/framework com.android.commands.hidl_test_java.HidlTestJava -s &
|
| /system/core/libprocinfo/testdata/ |
| D | maps | 2 …0000000 103:1d 639511 /data/dalvik-cache/arm64/system@framework@boot.art
3 …0211000 103:1d 639511 /data/dalvik-cache/arm64/system@framework@boot.art
4 …03:1d 639514 /data/dalvik-cache/arm64/system@framework@boot-core-libart…
5 …03:1d 639514 /data/dalvik-cache/arm64/system@framework@boot-core-libart…
6 …03:1d 639517 /data/dalvik-cache/arm64/system@framework@boot-conscrypt.a…
7 …03:1d 639517 /data/dalvik-cache/arm64/system@framework@boot-conscrypt.a…
8 … 103:1d 639520 /data/dalvik-cache/arm64/system@framework@boot-okhttp.art
9 … 103:1d 639520 /data/dalvik-cache/arm64/system@framework@boot-okhttp.art
10 …03:1d 639523 /data/dalvik-cache/arm64/system@framework@boot-bouncycastl…
11 …03:1d 639523 /data/dalvik-cache/arm64/system@framework@boot-bouncycastl…
[all …]
|
| /system/tools/hidl/test/ |
| D | run_all_device_tests.sh | 27 mkdir -p $ANDROID_PRODUCT_OUT/data/framework/hidl_test_java.jar || exit 1
29 $ANDROID_PRODUCT_OUT/data/framework/hidl_test_java_java.jar || exit 1
|
| /system/core/fastboot/fuzzy_fastboot/ |
| D | Android.bp | 41 "-framework CoreFoundation",
42 "-framework IOKit",
|
| /system/core/adb/proto/ |
| D | jarjar-rules.txt | 1 rule com.google.protobuf.** com.android.framework.protobuf.@1
|
| /system/sepolicy/prebuilts/api/28.0/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| /system/sepolicy/prebuilts/api/27.0/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| D | dex2oat.te | 8 # Access /vendor/framework
21 # Acquire advisory lock on /system/framework/arm/*
35 # the framework.
|
| /system/sepolicy/prebuilts/api/26.0/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| /system/media/audio_utils/tests/ |
| D | README.md | 1 primitive\_tests uses gtest framework
|
| /system/sepolicy/prebuilts/api/29.0/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| /system/sepolicy/prebuilts/api/30.0/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| /system/sepolicy/public/ |
| D | system_server.te | 3 # Most of the framework services run in this process.
|
| /system/core/fastboot/ |
| D | Android.bp | 66 "-framework CoreFoundation",
67 "-framework IOKit",
176 "-framework CoreFoundation",
177 "-framework IOKit",
|
| /system/chre/ |
| D | README.md | 12 The CHRE reference implementation (“CHRE framework”) is designed to be portable
24 * Documentation related to the CHRE framework:
52 supports building the CHRE framework and nanoapps using a configurable
58 - ``core/``: Common CHRE framework code, which is applicable to every platform
60 - ``doc/``: Contains documentation for the CHRE framework and associated topics
80 core framework implementation. Includes code that is usable by nanoapps.
|
| /system/apex/tests/ |
| D | README.md | 3 Presently, these tests require an unreleased version of the framework, and
|