Searched refs:nanoapp (Results 1 – 8 of 8) sorted by relevance
50 * The list of Android permissions held by the sending nanoapp at the time54 * of the permissions that the sending nanoapp is using.63 * The list of Android permissions used by this nanoapp. This list MUST67 * For example, if a nanoapp used location-based signals, the permissions
117 for (const std::unique_ptr<fbs::NanoappListEntryT> &nanoapp : response.nanoapps) { in handleNanoappListResponse() local118 if (nanoapp->app_id == kDropDetectAppId) { in handleNanoappListResponse()119 if (!nanoapp->enabled) in handleNanoappListResponse()
1026 * Logs an event indicating that a nanoapp loading has failed at the HAL.1036 // Dynamic loading of a nanoapp (e.g. code download).1052 // The 64-bit unique nanoapp identifier of the nanoapp that failed.1181 // The unique 64-bit ID for a nanoapp, only used if the module_type is NANOAPP.1222 * Indicates that a nanoapp has woken up the AP.1228 // The 64-bit unique nanoapp identifier that describes the entity that has caused an AP wake-up1229 // from CHRE. Whenever this event occurs, this means that the nanoapp sent a message to
149 for (const std::unique_ptr<fbs::NanoappListEntryT> &nanoapp : response.nanoapps) { in handleNanoappListResponse() local150 if (nanoapp->app_id == kCapoNanoappId) { in handleNanoappListResponse()151 if (nanoapp->enabled) in handleNanoappListResponse()
70 * Loading a nanoapp must not take more than 30 seconds.101 * Unloading a nanoapp must not take more than 5 seconds.122 * Enabling a nanoapp must not take more than 5 seconds.143 * Disabling a nanoapp must not take more than 5 seconds.
45 // Implementation-specific binary nanoapp data. This does not include the46 // common nanoapp header that contains the app ID, etc., as this data is
56 * This method must be called when a nanoapp invokes chreAbort(...)).
21 // The message types used in capo nanoapp. Some of them are H2C