Revision history [back]

Battery performance over time degrades on all devices, and I know of no conventional, consumer-grade exceptions, though I hope the reader will forgive that at this point my awareness of the issues and actors involved is small enough to be without consequence. Typically, phone and laptop (G)UIs/APIs are able to indicate a few data points at any given time: percent (re)charged, time to full charge, time before maximum discharge.

From the shell or via (for example) the Lighthouse application users can see their battery's current status.

Is there a means by which to collect (or upload) these data points and graph them for closer analysis? I am less bothered about current battery performance and more interested in helping gather information so that future batteries in Jolla devices perform better, given than the leaps and bounds the battery manufacturers may claim seem like hot air some of the time, and so software and other aspects of hardware performance are more likely to bring more significant gains in the medium term. The sort of thing I'd like to be able to know range over things like eV usage per program and process, to how ambient temperature affects performace not in general but specifically for the battery in my device.

I realise that the measurement and storage of this data at intervals and at precision also affect battery usage and that useful statistics collected down at the CPU cycle may use battery much more than data collected per minute or hour or charge cycle.

Battery performance over time degrades on all devices, and I know of no conventional, consumer-grade exceptions, though I hope the reader will forgive that at this point my awareness of the issues and actors involved is small enough to be without consequence. Typically, phone and laptop (G)UIs/APIs are able to indicate a few data points at any given time: percent (re)charged, time to full charge, time before maximum discharge.

From the shell or via (for example) the Lighthouse application users can see their battery's current status.

Is there a means by which to collect (or upload) these data points and graph them for closer analysis? I am less bothered about current battery performance and more interested in helping gather information so that future batteries in Jolla devices perform better, given than the leaps and bounds the battery manufacturers may claim seem like hot air some of the time, and so software and other aspects of hardware performance are more likely to bring more significant gains in the medium term. The sort of thing I'd like to be able to know range over things like eV usage per program and process, to how ambient temperature affects performace not in general but specifically for the battery in my device.

I realise that the measurement and storage of this data at intervals and at precision also affect battery usage and that useful statistics collected down at the CPU cycle may use battery much more than data collected per minute or hour or charge cycle.

Battery performance over time degrades on all devices, and I know of no conventional, consumer-grade exceptions, though I hope the reader will forgive that at this point my awareness of the issues and actors involved is small enough to be without consequence. Typically, phone and laptop (G)UIs/APIs are able to indicate a few data points at any given time: percent (re)charged, time to full charge, time before maximum discharge.

From the shell or via (for example) the Lighthouse application users can see their battery's current status.

Is there a means by which to collect (or upload) these data points and graph them for closer analysis? I am less bothered about current battery performance and more interested in helping gather information so that future batteries in Jolla devices perform better, given than the leaps and bounds the battery manufacturers may claim seem like hot air some of the time, and so software and other aspects of hardware performance are more likely to bring more significant gains in the medium term. The sort of thing I'd like to be able to know range over things like eV usage per program and process, to how ambient temperature affects performace not in general but specifically for the battery in my device.

I realise that the measurement and storage of this data at intervals and at precision also affect battery usage and that useful statistics collected down at the CPU cycle may use battery much more than data collected per minute or hour or charge cycle.

Update: Looking at csd...