Changes between Version 2 and Version 3 of AndroidBoincImpl


Ignore:
Timestamp:
Aug 10, 2012, 6:11:08 AM (12 years ago)
Author:
Joachim
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • AndroidBoincImpl

    v2 v3  
    99to Android-powered devices,
    1010enabling volunteers to contribute CPU time of modern smartphones and tablet computers.
     11
     12Projects are free to download the sources of AndroidBOINC from UCB's BOINC repository and configure the client. Projects are in charge of their version's distribution e.g. on Google's PlayStore. Note that AndroidBOINC currently supports only a single project.
    1113
    1214
    … …  
    2931The Client and Manager run as two separate processes.
    3032
     33Talking Android, AndroidBOINC consists of a Service (called Monitor), which interacts with the BOINC Client and holds data (ClientStatus, AppPreferences) which is accessed from various Activities.
     34
    3135
    3236=== Aspects of Android platform ===
    … …  
    4347 *  Permissions:
    4448  Android restricts access to certain features with its permission system.
    45   Required permissions have to be declared in the AndroidManifest.xml file by the developer,
     49  Required permissions have to be declared in the AndroidManifest file at compile-time,
    4650  the user then gets prompted to grant access upon installation.
    47   AndroidBOINC requires the "Network" permission,
    48   for transmitting workunits and also for the RPC communication in-between Manager and Client.
    49   This permission is granted to the App-specific Linux User ID,
     51  AndroidBOINC requires the "Network" and permission in order to
     52  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.
     53  Permissions get granted to the App-specific Linux User ID,
    5054  and therefore also applies to its child-processes.
    5155
    5256 * Lifecycle:
    53   Applications which are not visible at the moment can get killed by the system.
     57  Activities which are not visible at the moment can get killed by the system.
    5458  If the user navigates back to a destroyed application, it gets reactivated.
    5559  In most cases according lifecycle-methods are called, however those are not reliable.
    … …  
    7983
    8084
     85== Limitation ==
     86
     87The current version of AndroidBOINC can only be attached to a single project.
     88
     89
    8190== Acknowledgements ==
    8291