On Feb 8, 2013, at 12:18 AM, David Anderson wrote: > Maybe a better policy is: > start computing only when the battery is 95% charged. > stop computing if the charge goes down > resume computing then the charge returns to its max level
I think that people want their phones to charge to 100% as quickly as possible, and that they will be annoyed if it charges slower than optimum or if it is ever at less than 100% after being let to charge overnight. So the ideal situation would be: Don't compute at all unless battery is at 100% and on the charger Ensure somehow that BOINC and its project applications never use more power than is supplied by the charger, so that the battery is not depleted at all by BOINC; i.e., so that BOINC does not draw paower from the battery at all. This would also solve the temperature issue, though it might decrease BOINC's throughput. Of course, I don't know how we could accomplish this ideal situation, given the limited amount of data available. Perhaps BOINC could somehow increasingly throttle the project app until the battery never goes below 100% (i.e., using trial and error.) Cheers, --Charlie _______________________________________________ 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.
