[StoneRyno]

Originally Posted by mespiff

1) the suggestion -- is there away for the ap to sense when the pre is on a charger? and if so could the ap be set to either pause or start reading when removed from the charger?

2) the question -- where will i be able to get the updated ap?


additionally i agree with the run in the back ground sug. +1

thanks

Yes I can use mA to know if it is being charged or not. mA is a positive number when charging and negative when charging stops. And I will assume I can stop and start polling again based on that. However if left on the charger once it has completely charged it would stop and start during the top 5% discharge/charge cycle. Not that it would be an issue unless it partially powers the device from the charger reducing the discharge rate (mA consumed). And in that case it could skew the data collected. But it is worth looking into.

I was rather hoping for dev access by now but I'm guessing details are being worked out for that. So in the mean time I guess I'll post it here. I was preferring to have it in the feed so that preware et al could have access to it and the original listing. For now I guess I'll post it here. I've tested it on my pre and everything seems to be working fine. While I wouldn't say it is a beta, but since the new feature has only been tested on my pre it is possible bugs could be found as other use it.

Updating Info

You may need to uninstall the previous version. I added a space in the name so that the name under the icon is Battery Monitor instead of BatteryMonitor. When I installed it to my pre from eclipse during testing it was treated as a different app even though the only change to the app info was the space in the name and version number the app id is the same.

Battery Monitor 1.04 changes

New settings scene for settings and settings are now remembered. Note if uninstalled settings will revert to defaults. Note changes to settings apply to the main as soon as you gesture back to the main scene. Polling isn't interrupted and doesn't reset just as before.

Main scene now contains details formerly in the detailed battery info scene. The detailed battery info scene is still present and may likely be used to provide other details in the future.

In addition it tracks the average consumption (mA). Best use is average consumption of all use, but is als a good way to measure how much a certain app or task consumes. For example running pandora for an hour. Best to restart Battery Monitor for that sort of tracking since the more polls already averaged the multiple more needed to accurately measure the average consumption of a specific task. Note 60 polls minimum for decent accuracy, 90 for better, and at least 120 for greater to best accuracy.

Added 1 second and 15 second intervals for polling. Test results pending but initial testing indicates 1 and 5 second intervals consume much more battery and are only suited for testing specific things like how much does listening to pandora consume. But you will need to test how much the interval itself consumes to subtract from the results. I may remove these two once test results are done because preliminary tests indicate 15 and 30 second intervals consume marginally more if any increase at all vs 1 minute.