Lines Matching refs:nanoapps

11 low-power hardware. Typically, nanoapps integrate with a component on the
14 as the nanoapp’s “client”. Since nanoapps are not limited to the same power
29 nanoapps. In other words, the system only runs nanoapps that possess a digital
32 able to interact with nanoapps and the Context Hub in general. However, this
33 does not mean that third-party APKs cannot benefit from CHRE - nanoapps can be
38 While nanoapps are nominally dynamically loadable modules, they can be loaded
44 Static nanoapps are, as the name suggests, statically compiled into the CHRE
45 framework binary. Static nanoapps are automatically initialized after the CHRE
48 Static nanoapps typically aren’t used in production, because this monolithic
52 nanoapps (described later) are typically built as static nanoapps.
54 Static nanoapps are typically unconditionally compiled as part of the framework
56 (using the `--gc-sections` option, or equivalent). Static nanoapps are
67 Preloaded nanoapps are built as a separate binary from the CHRE framework, but
75 While the mechanism for loading prebuilt nanoapps is platform-specific, the CHRE
80    the list of nanoapps that should be automatically loaded.
88 4. CHRE initialization proceeds (it is important for all preloaded nanoapps to
93 This path is most commonly used to deploy nanoapps to production, as the entire
95 also preserving the ability to update nanoapps independent from other components
103 cases, preloaded nanoapps will use a separate `.napp_header` file with metadata
109 Instead of being stored on the device filesystem, fully dynamic nanoapps can be
111 `ContextHubManager.loadNanoApp()` Java API. This allows nanoapps to be
114 This mechanism is used to dynamically load and unload test nanoapps, but can
115 also be used for production nanoapps.
119 Some platforms support loading nanoapps into multiple tiers of memory, for
126 purely beneath the HAL level. System nanoapps are therefore hidden from the
132 Some basic nanoapps can be found in the `apps/` folder, which are used for test
137 The *FeatureWorld* nanoapps each exercise a part of the CHRE API, and print
139 nanoapps is given below:
159 These nanoapps help stress test the CHRE framework. They include:
186 unloading all other nanoapps in the system (which can be done via
199 associated with these nanoapps can be found in the `java/` folder.