MobileRead Forums - View Single Post

xorlof · 09-01-2016, 01:29 PM

The second attempt at extended battery test is done and finished without incident. Here's the power consumption over time:

You'll see roughly 3 periods of time here where the power consumption varied. It started out at one level (until hour 11ish), sunk to a lower level for a while (to hour 22ish) and then was at a higher level, except at the very end. The start of these periods correlate with times that I restarted the app (just to be sure of no crashes even though knc1 identified the likely cause of crashing in the first round of testing).

The chart is anchored at 30mA because that's roughly the power draw of the Kindle awake, at idle, and with the wifi turned on at this location. That means the blue bars roughly show how much power MY app was using above the at-idle power use.

Key findings:
1) Test app was on average drawing about 8 to 13 mA (10.7 average). This is much lower than I expected given WAFs having a pretty big overhead (using the web browser rather than native code). Keep in mind, that's just an average. There was plenty of time the app was doing nothing but waiting for the next per-minute update.
2) Different launches of the app can result in different average power consumption.
3) Overall runtime was 35.5 hours.
4) The Kindle shuts down when 3% of reported battery life remains.

09-01-2016, 01:29 PM	#57
xorlof Member Posts: 17 Karma: 23936 Join Date: Aug 2016 Device: K5 Touch, K3 Keyboard, Nook ST	The second attempt at extended battery test is done and finished without incident. Here's the power consumption over time: You'll see roughly 3 periods of time here where the power consumption varied. It started out at one level (until hour 11ish), sunk to a lower level for a while (to hour 22ish) and then was at a higher level, except at the very end. The start of these periods correlate with times that I restarted the app (just to be sure of no crashes even though knc1 identified the likely cause of crashing in the first round of testing). The chart is anchored at 30mA because that's roughly the power draw of the Kindle awake, at idle, and with the wifi turned on at this location. That means the blue bars roughly show how much power MY app was using above the at-idle power use. Key findings: 1) Test app was on average drawing about 8 to 13 mA (10.7 average). This is much lower than I expected given WAFs having a pretty big overhead (using the web browser rather than native code). Keep in mind, that's just an average. There was plenty of time the app was doing nothing but waiting for the next per-minute update. 2) Different launches of the app can result in different average power consumption. 3) Overall runtime was 35.5 hours. 4) The Kindle shuts down when 3% of reported battery life remains. Last edited by xorlof; 09-01-2016 at 01:55 PM.