Changes between Version 3 and Version 4 of AndroidBoincImpl


Ignore:
Timestamp:
Oct 10, 2012, 1:58:00 PM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • AndroidBoincImpl

    v3 v4  
    1010enabling volunteers to contribute CPU time of modern smartphones and tablet computers.
    1111
    12 Projects 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.
     12Projects are free to download the sources of AndroidBOINC from UCB's BOINC repository and configure the client.
     13Projects are in charge of their version's distribution e.g. on Google's !PlayStore.
     14Note that AndroidBOINC currently supports only a single project.
    1315
    1416
    … …  
    3133The Client and Manager run as two separate processes.
    3234
    33 Talking 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.
     35Talking Android, AndroidBOINC consists of a Service (called Monitor),
     36which interacts with the BOINC Client and holds data (!ClientStatus, !AppPreferences)
     37which is accessed from various Activities.
    3438
    3539
    … …  
    4751 *  Permissions:
    4852  Android restricts access to certain features with its permission system.
    49   Required permissions have to be declared in the AndroidManifest file at compile-time,
     53  Required permissions have to be declared in the !AndroidManifest file at compile-time,
    5054  the user then gets prompted to grant access upon installation.
    5155  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.
     56  transmit workunits and setup socket for the RPC communication in-between Manager and Client.
     57  The permission "RECEIVE_BOOT_COMPLETED" is used to start the BOINC Client upon boot.
    5358  Permissions get granted to the App-specific Linux User ID,
    5459  and therefore also applies to its child-processes.