contexthub: Clarify nanoapp persistence
Add documentation to loadNanoApp() detailing the expected behavior
surrounding persistence of nanoapps across context hub reboots.
Test: none, documentation change only
Change-Id: I17db7d024cf7486749aff3816cc58b50f2f44fac
diff --git a/contexthub/1.0/IContexthub.hal b/contexthub/1.0/IContexthub.hal
index 8c792fd..2c864a2 100644
--- a/contexthub/1.0/IContexthub.hal
+++ b/contexthub/1.0/IContexthub.hal
@@ -62,6 +62,13 @@
*
* Loading a nanoapp must not take more than 30 seconds.
*
+ * Depending on the implementation, nanoApps loaded via this API may or may
+ * not persist across reboots of the hub. If they do persist, the
+ * implementation must initially place nanoApps in the disabled state upon a
+ * reboot, and not start them until a call is made to enableNanoApp(). In
+ * this case, the app must also be unloaded upon a factory reset of the
+ * device.
+ *
* @param hubId identifer of the contextHub
* appBinary serialized NanoApppBinary for the nanoApp
* transactionId transactionId for this call