JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-421  -  Android node: ability to throttle/suspend/kill the node based on battery state
Posted Oct 27, 2015 - updated Jan 13, 2016
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Android
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.2
Issue description
Currently, there is no way for the Android node to stop processing when the battery on the device is in a critical state. This is definitely a problem since battery life is a critical factor on mobile devices.

We propose to add configuration options to specify the node's behavior based on the state of the battery. An idea is to allow specifying 2 thresholds for the battery's charge level, e.g. "warning" and "critical", and have the node behave as follows:
  • when a "warning" level is reached, the node will stop taking new jobs, and will simply monitor the baterry charge until the alert disappears or the "critical" level is reached. We may add an option to have the node attempt to cancel the currently executing job, if any
  • when a "critical" level is reached, the node will send a notification to explain the situation, then terminate itself, i.e. the node app will terminate
Some useful references:

#3
Comment posted by
 lolo4j
Jan 13, 09:52
Implemented in trunk revisions 3943 and 3944