Home
last modified time | relevance | path

Searched refs:different (Results 1 – 25 of 138) sorted by relevance

123456

/system/sepolicy/prebuilts/api/26.0/public/
Dhal_configstore.te5 # As opposed to the rules of most other HALs, the different services exposed by
6 # this HAL should be restricted to different clients. Thus, the allow rules for
/system/core/code_coverage/seccomp_policy/
Dcode_coverage.policy.def11 // coverage tool uses different operations on different passes
/system/sepolicy/prebuilts/api/27.0/public/
Dhal_configstore.te7 # As opposed to the rules of most other HALs, the different services exposed by
8 # this HAL should be restricted to different clients. Thus, the allow rules for
/system/sepolicy/prebuilts/api/28.0/public/
Dhal_configstore.te7 # As opposed to the rules of most other HALs, the different services exposed by
8 # this HAL should be restricted to different clients. Thus, the allow rules for
/system/tools/aidl/build/
Dmessage_check_integrity.txt4 Above AIDL file(s) has changed, resulting in a different hash. Hash values may
/system/sepolicy/private/
Dmlstrustedsubject.te5 # data files must use a different label.
/system/sepolicy/prebuilts/api/29.0/public/
Dmediaswcodec.te6 # mediaswcodec may use an input surface from a different Codec2 service or an
/system/sepolicy/public/
Dmediaswcodec.te6 # mediaswcodec may use an input surface from a different Codec2 service or an
/system/sepolicy/prebuilts/api/30.0/public/
Dmediaswcodec.te6 # mediaswcodec may use an input surface from a different Codec2 service or an
/system/bt/gd/docs/architecture/
Dstyle_guide.md65 different platform or hardware. When doing this:
67 * Avoid #define macros as much as possible. Instead put code into different
68 source files and selectively compile them for different targets.
100 different source files based on compile time target
111 different source files based on compile time target
Darchitecture.md75 to bind handlers to different threads and that should not affect the overall
80 its threading module is completely different. Therefore, we put a thread
100 Function invocations between different components are abstracted as control
164 does not gurantee sequential execution of code across different `Handler` even
/system/core/libunwindstack/
DAndroidVersions.md3 unwinder works on different Android versions. It does not describe
4 every change in the code made between different versions, but is
6 on different versions. It also describes the different way an unwind
7 will display on different versions of Android.
/system/libufdt/tests/
DREADME5 * run_tests.sh: The main entry to run test cases. Using different
/system/sepolicy/vendor/
Dmediacodec.te12 # mediacodec may use an input surface from a different Codec2 or OMX service
/system/update_engine/
D.clang-format26 # are different in AOSP and CrOS. Keep in sync with the original file if
Dupdate_metadata.proto72 // the extents are in different partitions.
122 // many signatures to support many different types of client. Then client
133 // different input of sha256 hash. However, we need the size of the
162 // the equivalent value above. They are normally only different for
252 // different keys. If the update_engine daemon requires vendor-signed images
/system/extras/simpleperf/doc/
DREADME.md57 4. It builds executables and shared libraries for different usages.
60 b. Builds executables on different hosts: Linux, Mac and Windows. These executables can be used
62 c. Builds report shared libraries on different hosts. The report library is used by different
142 2. Don't work well on ARM. Because ARM is short of registers, and ARM and THUMB code have different
/system/core/bootstat/
DREADME.md40 for aggregation and analysis of boot time across different devices and
/system/timezone/debug_tools/host/
DREADME.android17 from being the same as one major region to be the same as a different major
/system/extras/ANRdaemon/
DREADME3 logging. Trace are configured ahead by setting different modules in /d/tracing.
/system/core/fs_mgr/libsnapshot/
DPowerTest.md8 …at will be used as the pre-merge and post-merge state. You can take two different partition images…
/system/extras/memory_replay/traces/
DTRACES65 Trace from app start while looking at different photos, scrolling the
/system/update_engine/update_engine/
Dupdate_metadata.proto72 // the extents are in different partitions.
122 // many signatures to support many different types of client. Then client
133 // different input of sha256 hash. However, we need the size of the
162 // the equivalent value above. They are normally only different for
252 // different keys. If the update_engine daemon requires vendor-signed images
/system/apex/apexd/
DAndroid.bp242 // Generates an apex which has a different manifest outside the filesystem
258 // Generates an apex which has a different manifest outside the filesystem
/system/core/libutils/
DREADME67 * res/drawable: bitmap or xml graphics. Each file may have different
70 * res/values: integers, strings, etc. Each resource may have different
87 value may be different between packages.

123456