On Friday, June 29, 2012 3:22:28 AM UTC-4, Dianne Hackborn wrote: > > No. The way this is done is very complicated, using an ever-evolving set > of measurements of various operations applications are doing and computing > them against a device-specific power profile to construct the UI. This is > only intended to provide rough estimates as shown in the UI, this is not a > facility for applications to use. >
If the information is good enough to show to the user, it should be good enough for the user to gather up with an app to look at later. All this hand waving about "ever evolving" and "device specific" just pushes people to re-implement what they can see done by the UI in the AOSP code (which, IMO is worse because it won't be able to track the evolution/device specific changes.) Hiding it in dumpsys output or forcing the user to click through menus and not exporting it to the public API looks like either lazyness or some plot to put application developers at a disadvantage if they want to be able to let users have the choice to track things in a way Google may not have thought of. There are plenty of other APIs that provide "rough estimates" (like RunningAppInfo) so I don't see why there would be an issue with making it public and saying "rough estimate" in the docs. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
