| /system/sepolicy/private/ |
| D | runas.te | 3 # ndk-gdb invokes adb shell run-as.
15 # run-as reads package information.
23 # run-as checks and changes to the app data dir.
27 # run-as switches to the app UID/GID.
30 # run-as switches to the app security context.
43 # run-as cannot have capabilities other than CAP_SETUID and CAP_SETGID
|
| D | simpleperf.te | 3 # simpleperf_app_runner (with shell as its origin). Certain other domains
21 # consistent if simpleperf is marked as an app domain as well (as, for example,
22 # it will then see the same set of system libraries as the app).
38 # profiler runs as when executed by the app. The signals are used to control
44 # the same domain as their respective processes, most of which this domain is
|
| /system/media/audio_utils/tests/ |
| D | audio_mutex_tests.cpp | 273 android::audio_utils::atomic_stack<int, int, 2> as; in TEST() local
276 EXPECT_EQ(0UL, as.size()); in TEST()
277 as.push(1, 10); in TEST()
278 EXPECT_EQ(1UL, as.size()); in TEST()
279 as.push(2, 20); in TEST()
280 EXPECT_EQ(2UL, as.size()); in TEST()
283 as.push(3, 30); in TEST()
285 EXPECT_EQ(2UL, as.size()); in TEST()
287 EXPECT_EQ(3UL, as.true_size()); in TEST()
289 const auto& bot = as.bottom(); in TEST()
[all …]
|
| /system/chre/apps/nearby/location/lbs/contexthub/nanoapps/nearby/ |
| D | README | 8 the discovery notification as soon as a user turns on the screen.
18 applications above (Fast Pair, Presence, as well as Offload Extension).
|
| /system/extras/pinner/tests/ |
| D | Android.bp | 52 "-O0", // as some tests rely on compiler keeping code as is
91 "-O0", // as some tests rely on compiler keeping code as is
|
| /system/tools/aidl/ |
| D | aidl_to_cpp_common.h | 82 std::vector<T> Append(std::vector<T> as, const std::vector<T>& bs) { in Append() argument
83 as.insert(as.end(), bs.begin(), bs.end()); in Append()
84 return as; in Append()
88 std::vector<T> Append(std::vector<T>&& as, std::vector<T>&& bs) { in Append() argument
89 std::vector<T> appended = std::move(as); in Append()
|
| /system/secretkeeper/ |
| D | README.md | 4 It is specified as [a HAL][secretkeeperhal] and must be implemented in an environment with
6 such as ARM TrustZone.
10 clients as well as deletion of some or all data.
18 In the key exchange protocol, the client acts as P1 (source) and Secretkeeper as P2 (sink). The
50 Android provides a reference implementation of Secretkeeper as well as the required AuthGraph Key
65 5. [./dice_policy/][dice_policy_dir]: Contains code for building dice_policies as well
66 as well as matching them against Dice chain. As explained [here](#Policy-Gated-Storage), this
114 Secretkeeper appears as a HAL service in userspace, and so an executable that registers for and
130 one for AuthGraph), as encapsulated in the `authgraph_hal::channel::SerializedChannel` trait.
132 This trait has a single method `execute()`, which takes as input a request message (as bytes), and
[all …]
|
| /system/sepolicy/ |
| D | README.apps.md | 7 `appdomain` as any app started by Zygote. The macro `app_domain()` should be
12 most recent SDK version will be typed as `untrusted_app`. This is the default
17 with `targetSdkVersion = 32` in its manifest will be typed as `untrusted_app_32`.
38 SDK runtime apps, installed as part of the Privacy Sandbox project. These are
52 Apps shipped as part of the device and installed in one of the
54 com.google.android.apps.messaging is an example of an app running as priv_app.
|
| D | NOTICE | 6 non-commercially developed program that may contain "bugs" (as that
7 term is used in the industry) and that it may not function as intended.
8 The software is licensed "as is". NSA makes no, and hereby expressly
|
| /system/chre/chpp/ |
| D | README.md | 11 …nly used sensors and peripherals, and also allows vendor-specific services as necessary. CHPP allo…
19 …otocol is designed such that endpoints can both provide services and serve as clients of remote se…
33 …h a 4-byte packet footer. Defined as a structure (ChppTransportHeader in transport.h), the CHPP tr…
50 …as the packet start delimiter. If the receiving side is not actively within a packet, it assumes a…
54 Up to 8 flags are supported as a bitmap as follows
70 … A non-zero explicit NACK code indicates an explicit NACK. The code provides the reason as follows:
82 - 0x1: Reset. The reset code is used at bootup to indicate that readiness, as well as to reset the …
85 - 0x2 Reset-ack. Similar to reset, but sent as a response to reset, as described above.
90 The ack may be sent as part of a packet with or without a payload. In the latter case, the payload …
137 …serial interface. The data is provided through a pointer to *buf, with its length specified as len.
[all …]
|
| D | QUICKSTART.md | 55 …y), as well as three standard services that follow the CHRE PAL API to simplify integration and te…
61 … services using the CHRE PAL API, please refer to each service's interface as provided in include/…
|
| /system/extras/simpleperf/demo/SimpleperfExampleCpp/app/src/main/cpp/ |
| D | CMakeLists.txt | 12 # Creates and names a library, sets it as either STATIC
20 # Sets the library as a shared library.
26 # Searches for a specified prebuilt library and stores the path as a
40 # can link multiple libraries, such as libraries you define in this
|
| /system/core/init/ |
| D | README.ueventd.md | 5 built on the same parser as init.
23 directory, each file in the directory is parsed as a config file. It is not recursive, nested
33 1. Block devices are created as `/dev/block/<basename uevent DEVPATH>`. There are symlinks created
37 2. USB devices are created as `/dev/<uevent DEVNAME>` if `DEVNAME` was specified for the uevent,
38 otherwise as `/dev/bus/usb/<bus_id>/<device_id>` where `bus_id` is `uevent MINOR / 128 + 1` and
40 3. All other devices are created as `/dev/<basename uevent DEVPATH>`
75 Indicates that all uevents with `SUBSYSTEM=sound` will create nodes as `/dev/snd/<basename uevent
129 The handler will be run as the given user, or if a group is provided, as the given user and group.
134 Will launch `/vendor/bin/led_coeffs.bin` as the system user instead of serving the default firmware
138 `/dev/*/red` will match `/dev/leds/red` as well as `/dev/lights/red`. The pattern matching follows
[all …]
|
| /system/sepolicy/public/ |
| D | system_app.te | 3 ### com.android.settings. These are not as privileged as the system
|
| D | su.te | 1 # Domain used for su processes, as well as for adbd and adb shell
|
| /system/core/fs_mgr/libfstab/ |
| D | Android.bp | 25 // Do not ever make this a shared library as long as it is vendor_available.
51 // process as the config file is in /system_ext.
|
| /system/sepolicy/microdroid/system/public/ |
| D | su.te | 1 # Domain used for su processes, as well as for adbd and adb shell
|
| /system/tools/aidl/tests/lazy_test/ |
| D | README | 16 If the service has multiple interfaces, each can be entered as a separate argument to be tested
25 Because it represents the bare minimum requirements for implementing a service, it also serves as
26 an example of how to add a new service. The required files are as follows:
35 instantiated and added (either to servicemanager as a standard service or to LazyServiceRegistrar
81 as the second argument to this function.
|
| /system/security/mls/mls-rs-crypto-boringssl/ |
| D | LICENSE-apache | 10 and distribution as defined by Sections 1 through 9 of this document.
36 Object form, made available under the License, as indicated by a
43 represent, as a whole, an original work of authorship. For the purposes
60 designated in writing by the copyright owner as "Not a Contribution."
76 (except as stated in this section) patent license to make, have made,
87 as of the date such litigation is filed.
106 (d) If the Work includes a "NOTICE" text file as part of its
112 as part of the Derivative Works; within the Source form or
119 or as an addendum to the NOTICE text from the Work, provided
121 as modifying the License.
[all …]
|
| /system/chre/doc/ |
| D | framework_overview.md | 14 The CHRE reference implementation (hereafter referred to just as "CHRE" or "the
18 code as well as CHRE system callbacks. Per the CHRE API, nanoapps can’t execute
29 rather an overview of key points to serve as an introduction.
54 object as needed, and passes it to `EventLoop::startNanoapp()` - this marks a
58 common and platform-specific data and functions, as described in the Platform
126 associated with accelerometer data, and sets `sensorDataEventFree()` as the
133 function is invoked (via `PlatformNanoapp`, as with `nanoappStart`) for each
146 Each framework module as described in the previous section is represented by a
147 C++ class in `core/`, which serves as the top-level reference to the module and
150 `SensorRequestManager` class as an example, its role is to manage common
[all …]
|
| D | nanoapp_overview.md | 12 Android side, such as a privileged APK, in order to provide complete end-to-end
14 as the nanoapp’s “client”. Since nanoapps are not limited to the same power
44 Static nanoapps are, as the name suggests, statically compiled into the CHRE
52 nanoapps (described later) are typically built as static nanoapps.
54 Static nanoapps are typically unconditionally compiled as part of the framework
59 the device variant makefile, as in `variant/simulator/` for example.
61 Some boilerplate is needed to enable nanoapp to be built as a static nanoapp -
67 Preloaded nanoapps are built as a separate binary from the CHRE framework, but
71 as a “prebuilt” binary, and integrated into the Android build system so as to
93 This path is most commonly used to deploy nanoapps to production, as the entire
[all …]
|
| /system/memory/lmkd/ |
| D | README.md | 67 - `ro.lmk.swap_free_low_percentage`: level of free swap as a percentage of the
68 total swap space used as a threshold to consider
69 the system as swap space starved. Default for
72 - `ro.lmk.thrashing_limit`: number of workingset refaults as a percentage of
73 the file-backed pagecache size used as a threshold
78 - `ro.lmk.thrashing_limit_decay`: thrashing threshold decay expressed as a
96 milliseconds to consider the system as stuck in
|
| /system/core/fs_mgr/libfiemap/ |
| D | README.md | 10 - Creating images that will act as block devices. For example, gsid needs to
12 - Mapping the image as a block device while /data is mounted. This is fairly
14 - Mapping the image as a block device during first-stage init. This is simple
34 - `/dev/block/by-name/data` may be marked as in-use.
54 unencrypted as well.
60 we create a device-mapper device as well. For each loop device it will have one
|
| /system/extras/squashfs_utils/ |
| D | NOTICE | 23 and distribution as defined by Sections 1 through 9 of this document.
49 Object form, made available under the License, as indicated by a
56 represent, as a whole, an original work of authorship. For the purposes
73 designated in writing by the copyright owner as "Not a Contribution."
89 (except as stated in this section) patent license to make, have made,
100 as of the date such litigation is filed.
119 (d) If the Work includes a "NOTICE" text file as part of its
125 as part of the Derivative Works; within the Source form or
132 or as an addendum to the NOTICE text from the Work, provided
134 as modifying the License.
[all …]
|
| /system/extras/libfscrypt/ |
| D | NOTICE | 23 and distribution as defined by Sections 1 through 9 of this document.
49 Object form, made available under the License, as indicated by a
56 represent, as a whole, an original work of authorship. For the purposes
73 designated in writing by the copyright owner as "Not a Contribution."
89 (except as stated in this section) patent license to make, have made,
100 as of the date such litigation is filed.
119 (d) If the Work includes a "NOTICE" text file as part of its
125 as part of the Derivative Works; within the Source form or
132 or as an addendum to the NOTICE text from the Work, provided
134 as modifying the License.
[all …]
|