Lines Matching refs:a
11 low-power hardware. Typically, nanoapps integrate with a component on the
12 Android side, such as a privileged APK, in order to provide complete end-to-end
19 which is standardized across all CHRE implementations. This means that a nanoapp
23 a nanoapp does not need to be recompiled to run on a device that exposes a newer
29 nanoapps. In other words, the system only runs nanoapps that possess a digital
31 hold a special privileged/same-signature permission (`ACCESS_CONTEXT_HUB`) to be
36 ## Methods for Loading a Nanoapp
39 into a device through a few methods, each of which has pros and cons elaborated
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
69 “preloaded” onto the device). The binaries associated with a preloaded nanoapp
70 (usually a `.so` and a `.napp_header` file) are checked in to the Android tree
71 as a “prebuilt” binary, and integrated into the Android build system so as to
83 from storage, and sends a message to CHRE requesting it to load the nanoapp.
90 avoid race conditions leading to clients believing that a preloaded nanoapp
100 At the binary level, a preloaded nanoapp and fully dynamic nanoapp are
103 cases, preloaded nanoapps will use a separate `.napp_header` file with metadata
104 and `.so` file for the actual binary, a fully dynamic nanoapp has the header
107 can be used to create a fully dynamic nanoapp file from these components.
112 updated/delivered by an APK, outside of a full Android system update (OTA).
120 example low-power tightly coupled memory (TCM, usually SRAM), versus a
124 CHRE also supports the concept of a *system nanoapp*, which is a nanoapp whose
137 The *FeatureWorld* nanoapps each exercise a part of the CHRE API, and print
138 results/output to `chreLog`. An overview of a few of the key FeatureWorld
141 * `hello_world`: While not technically a FeatureWorld nanoapp, it’s generally
142 the first nanoapp to be tried, and it simply outputs a log message when it
151 which sensors it will enable. It also supports a “break it” mode which
164 * `sensor_world`: Contains a “break it” mode which repeatedly enables, disables,
167 * `spammer`: Sends a constant stream of messages and events to stress test the
171 unloading a nanoapp with pending events/messages completes successfully. Note
183 5000000000` will configure the `power_test` nanoapp to request a WiFi scan every
185 power cost of performing a WiFi scan from CHRE. Typically this is done after
188 get a clean power trace of purely the functionality exercised by the
191 Refer to `chre_power_test_client.cc` for more details, including a full listing
196 Nanoapps under `apps/test` are associated with a test suite, for example Context
197 Hub Qualification Test Suite (CHQTS), which is used to test that a given device