Changes between Version 4 and Version 5 of AndroidBoincImpl

Timestamp:

Feb 19, 2013, 6:54:55 PM (12 years ago)

Author:

davea

Comment:

--

AndroidBoincImpl

@@ -51 +51 @@
  *  Permissions:
   Android restricts access to certain features with its permission system.
-  Required permissions have to be declared in the !AndroidManifest file at compile-time,
+  Required permissions have to be declared in the !AndroidManifest
+  file at compile-time,
   the user then gets prompted to grant access upon installation.
   AndroidBOINC requires the "Network" and permission in order to
-  transmit workunits and setup socket for the RPC communication in-between Manager and Client.
-  The permission "RECEIVE_BOOT_COMPLETED" is used to start the BOINC Client upon boot.
+  transmit workunits and setup socket for the RPC communication
+  in-between Manager and Client.
+  The permission "RECEIVE_BOOT_COMPLETED" is used to start
+  the BOINC Client upon boot.
   Permissions get granted to the App-specific Linux User ID,
   and therefore also applies to its child-processes.
 
  * Lifecycle:
-  Activities which are not visible at the moment can get killed by the system.
-  If the user navigates back to a destroyed application, it gets reactivated.
+  Activities which are not visible at the moment can get
+  killed by the system.
+  If the user navigates back to a destroyed application,
+  it gets reactivated.
   In most cases according lifecycle-methods are called, however those are not reliable.
   This behavior only applies to applications which are executed in Android's
@@ -108 +113 @@
  *  [AndroidBuildApp Build apps for AndroidBOINC]
 
+
+prefs.xml
+        "run at boot"
+        "seen welcome"
+
+client is started by "Monitor" (Java)
+        background thread
+        can be killed by OS
+
+Installation:
+        (can't do any logic)
+
+        if user chooses to run GUI:
+                GUI 
+                        prefs.xml doesn't exist
+                        show "Welcome" dialog
+                                BOINC will run all the time
+                                only will compute when plugged in and battery mostly charged
+                                Can changes these using Preferences tab
+                        create prefs.xml
+                                run at boot = true
+                                seen welcome = true
+                        starts client
+
+        if user doesn't choose to run app:
+
+"boot receiver" function
+        if not "seen welcome" (e.g. prefs.xml doesn't exist)
+                send notification:
+                "click to configure BOINC"
+        if "run at boot" set
+                starts the client (not GUI)
+
+GUI startup
+        if newer version of client (based on MD5)
+                if client process running
+                        kill it
+                copy executable
+                start client
+        else
+                if client process not running
+                        start client
+
+App shutdown by OS
+        GUI
+                if lose connection to client
+                        wait until system is not low on memory
+                                how to do this on 2.3?
+                        restart client
+        client
+                Is there a C++ func to find if low mem?
+                don't launch any app if low memory
+
+        wrapper
+                if task got SIGKILL
+                        temporary_exit(60)
+
+GUI exit
+        need an "exit all" button some