It is the app called, aptly, Battery Life by Kdan Mobile Software. This is one of the only apps I've see display a time series of information which gives me at least a moderately better understanding of the rate of change of battery life, especially if I change the conditions on the iPhone which can affect this.
At our company, apparently they want to block all iOS versions prior to 6.1.2 as it created some high usage and havoc with the Exchange Server. I don't know if this is a great idea as this could cause more user grief. I don't think that Apple's latest patch has solved the root problem. The poster who suggested perhaps another effect of the patch affecting the IR sensor might be important as well - I dunno, but am interested in checking this out.
So in light of the upgrade, here is an update to my original post. As previously mentioned, it was thought that the 6.1.2 upgrade might fix those battery draining problems from the 6.1.1 problem. I've noticed a spectrum of symptoms from the latest patch which can be categorized as follows:
- No previous battery drain issues after the 6.1.1 upgrade, experienced issue in 6.1.2.
- Previous battery drain issues after 6.1.1, the 6.1.2 patch had no effect in resolving the battery drain.
- Previous battery drain issues after 6.1.1, users rolled back properly to factory setting, helped the battery issue, and upgraded to 6.1.2 directly with no ill effects on battery drain.
--------------- Soabox on-----------------------------
It's obvious that a number of components relating to how the iPhone sends/listens to a number of devices or environments may be part of the problem. AFAIK, the genius folks don't have a comprehensive and robust diagnostic tool that can tell when the usage of a particular component is abnormal (i.e. software inducing super frequent calls to an exchange server, or perhaps an IR sensor that is misbehaving) causing battery drainage.
As a matter of quality control and streamlining the diagnostic process, it would seem to me that Apple, allegedly a tech company trying to plow the frontier of innovation, would have this capability and leverage the simple compute power of what it already produces to deploy more robust diagnostic software. Yet it has not. And frankly, I don't get that.
Have they not collected sufficient data on product issues to drive something actionable? Or do they just not know how to effectively use it to provide sound interpretations that translate into solutions, and even better, a proactive strategy in QC of their rather pricey products? While I think they (Apple) do a pretty good job in general, they could indeed do far better.
WIth Google now jumping into play with things like the Pixel - the playing field may be a bit more crowded. So serious and thoughtful QC (particularly in the analytic space) will be essential.
------------- Soapbox off -------------------------