MobileRead Forums - View Single Post

xorlof · 08-26-2016, 05:59 PM

TESTING BEGINS!

For those following along, here's the status.

I've actually already done several short term tests and it's looking promising. I've just started the long-term test that will run until the battery is dead. Assuming I've done things correctly and the above test WAF app actually is running the Kindle at least as hard as the real thing will, I should have NOTHING to worry about. With a usable battery capacity of about 1350mah and an average draw of somewhere less than 50ma, we're talking about well over 24 hours of use (probably closer to 30 if I had to guess).

In the test I have several things happening every 10 seconds:
- about 15kb of network activity
- a full parse of the received data and dummy calculations done on that data.
- various calculations and branching in the code (in a way to help make sure branch predictions, assuming the ARM processor does them, are frequently missed).
- updating the clock at the top of the display.

And at every 10 minutes:
- lots more dummy cpu activity
- a dozen or so very expensive DOM operations
- full screen refresh
- reading of a bunch of internal variables from the system (various battery parameters, wifi signal strength, etc.)
- logging of status of those variables.
- other stuff I'm forgetting about without looking at the code.

All of this is done from a spot where the wifi is rather weak, just in case that consumes more battery on a Kindle (not sure if it adapts its Tx power in such situations).

I think this is a fair test of most everything other than my use of the speaker (which I just forgot to add until this very moment). Assuming this test works out, I'll add the speaker portion and retest.

While the test app isn't testing response to input, me having the app do operations in this simulation every 10 SECONDS all day, I think whatever battery life I come up with with be conservative. (Keep in mind, in the actually application, we're talking about our simple updates happening only once per minute). Wish me luck!

08-26-2016, 05:59 PM	#44
xorlof Member Posts: 17 Karma: 23936 Join Date: Aug 2016 Device: K5 Touch, K3 Keyboard, Nook ST	TESTING BEGINS! For those following along, here's the status. I've actually already done several short term tests and it's looking promising. I've just started the long-term test that will run until the battery is dead. Assuming I've done things correctly and the above test WAF app actually is running the Kindle at least as hard as the real thing will, I should have NOTHING to worry about. With a usable battery capacity of about 1350mah and an average draw of somewhere less than 50ma, we're talking about well over 24 hours of use (probably closer to 30 if I had to guess). In the test I have several things happening every 10 seconds: - about 15kb of network activity - a full parse of the received data and dummy calculations done on that data. - various calculations and branching in the code (in a way to help make sure branch predictions, assuming the ARM processor does them, are frequently missed). - updating the clock at the top of the display. And at every 10 minutes: - lots more dummy cpu activity - a dozen or so very expensive DOM operations - full screen refresh - reading of a bunch of internal variables from the system (various battery parameters, wifi signal strength, etc.) - logging of status of those variables. - other stuff I'm forgetting about without looking at the code. All of this is done from a spot where the wifi is rather weak, just in case that consumes more battery on a Kindle (not sure if it adapts its Tx power in such situations). I think this is a fair test of most everything other than my use of the speaker (which I just forgot to add until this very moment). Assuming this test works out, I'll add the speaker portion and retest. While the test app isn't testing response to input, me having the app do operations in this simulation every 10 SECONDS all day, I think whatever battery life I come up with with be conservative. (Keep in mind, in the actually application, we're talking about our simple updates happening only once per minute). Wish me luck!