Lines Matching refs:nanoapps

5 Since CHRE is an open platform, anyone can write nanoapps. However, deploying to
42 CHRE guarantees support for nanoapps written in C99 or C++11, though not all
86 * Restart CHRE to reload all nanoapps, including the new one
90 While not strictly enforced, nanoapps are recommended to follow the convention
101 `chre_api/include`, as well as usage of the APIs by sample nanoapps. The CHRE
108 but can be leveraged by nanoapps as well. In general, any source and header file
112 by nanoapps.
151 required, nanoapps are encouraged to batch their messages and opportunistically
166 While most nanoapps are only concerned with providing functionality for a single
168 nanoapps within CHRE. Similar to how nanoapps communicate with the host by
169 passing *messages*, nanoapps can communicate with one another by passing
173 Typically a nanoapp creates a *nanoapp client library* which other nanoapps can
182 Many nanoapps use machine learning techniques to accomplish their functionality.
212 As it requires collaboration from all nanoapps to optimize their resource usage
267 following standard library features are not meant to be used by nanoapps:
315 When running on CHRE v1.4+, nanoapps can also append information to the CHRE
337 To help catch programming errors or other unexpected conditions, nanoapps can