Open dustinrue opened 12 years ago
The update interval is already stored in the settings key "UpdateInterval". This only influences the update loop of CP itself, not the evidence sources, which all use different timings.
Depending on what evidence sources are being used, I've seen a 2+ hour improvement if I quit CP. Even doing from a number of evidence sources to just the WiFi ES helped a lot. On Nov 12, 2011, at 8:24 AM, David Jennes wrote:
Dunno, are you up to it for measuring the difference in power consumption? Kinda hard with all the other processes running amok on the system. The only evidence sources ones that consume most of the power are the wifi/bluetooth ones (and those based on it such as core location).
Anyway, the update interval is already stored in the settings key "UpdateInterval". This only influences the update loop of CP itself, not the evidence sources, which all use different timings.
Reply to this email directly or view it on GitHub: https://github.com/dustinrue/ControlPlane/issues/83#issuecomment-2717619
Seconding the request for the option to skew towards low power consumption (including possibly disabling some high-drain evidence sources) while on battery.
Maybe a preference area with checkboxes that says: "While on Battery: X Disable Bluetooth Polling X Reduce update interval X Disable Location tracking"
Seems a nice way to take advantage of CP's approach using multiple streams of evidence.
It would be possible to reduce power consumption while on battery by reducing how often CP loops/polls evidence sources.