> I think this is possible. But what advantage would that have? Right now we > have two processes, > the BOINC client as a native process, and the virtual machine of the Android > application > (service that starts the client and runs the rpc calls as well as the UI > components).
Hopefully increase robustness in the development process: * Bugs in the UI wouldn't cause Android to kill the whole process. * We would have just one service instead of two, thereby reducing code maintenance overhead. * The stock UI then becomes example code for project specific versions of play store apps, thereby reducing documentation overhead. > The ComponentCallback2 is API Level 14. So it is not compatible with the API > version 9 we > are targeting. Unfortunately. If I am not mistaken, we can still implement the function and through Android's use of reflection it'll be called by Android for those versions of Android that support it. It should be inert code on those versions of Android that do not support it. ----- Rom ----- From: Joachim Fritzsch [mailto:[email protected]] Sent: Tuesday, February 19, 2013 3:10 PM To: Rom Walton Cc: David Anderson (BOINC); BOINC Developers Mailing List Subject: Re: [boinc_dev] Android Transition Portrait/Landscape mode On Mon, Feb 18, 2013 at 6:40 PM, Rom Walton <[email protected]> wrote: Well, the "Autostart" preference automatically launches the BOINC android application (which I mistakenly thought of as just the UI). The service components are hosted within the same JVM. When BOINC is automatically started at boot a little BOINC icon appears in the notification area. Joachim, is it possible to break out the monitor service into its own process like the Google Maps location service? I tried to tweak that in Eclipse and Eclipse kept ignoring the teak to AndroidManifest.xml. I think this is possible. But what advantage would that have? Right now we have two processes, the BOINC client as a native process, and the virtual machine of the Android application (service that starts the client and runs the rpc calls as well as the UI components). Should we try and take and special precautions when Android notifies the monitor service that it is running low on memory? http://developer.android.com/reference/android/app/Service.html#onTrimMe mory(int) http://developer.android.com/reference/android/content/ComponentCallback s2.html The ComponentCallback2 is API Level 14. So it is not compatible with the API version 9 we are targeting. Unfortunately. ----- Rom -----Original Message----- From: David Anderson [mailto:[email protected]] Sent: Saturday, February 16, 2013 2:34 PM To: Rom Walton Cc: Joachim Fritzsch; BOINC Developers Mailing List Subject: Re: [boinc_dev] Android Transition Portrait/Landscape mode On 16-Feb-2013 8:07 AM, Rom Walton wrote: > Just to clarify though, the current intent of the software is that the > BOINC client only runs when the UI us running in some form. Let's think carefully. Is this what we want? Probably not. It would mean that BOINC wouldn't run unless the user remembers to do something (i.e. launch the GUI). I think the goal is: if the user installs BOINC, it runs (invisibly) with no action on the user's part. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
