On Sat, Jun 30, 2012 at 4:36 AM, Mark Murphy <mmur...@commonsware.com>wrote:
> On Sat, Jun 30, 2012 at 1:29 AM, Kumar Rangarajan > <kumar.rangara...@gmail.com> wrote: > > That is true. Its still the same. But then as a developer (assuming u > have > > the N1), would'nt getting power consumption details on one model still > give > > u a fair and reasonably consistent view of how it would perform on most > > models ? If the intent is to understand the consumption pattern of ones > > application, this is reasonably good enough right ? > I certainly would not make that assumption. This gets to the heart of > Ms. Hackborn's comment: per-component power measurement is tricky > business without low-level hardware data collection (e.g., Qualcomm > MDP). It's all just guesswork. Chipsets vary in power consumption, > sometimes fairly widely, let alone differences in CPU and GPU. > Yeah, it's not true at all. For example we added tracking and measurement of wake locks in 2.3, because we were working with a chipset we hadn't before where just holding a wakelock caused power use; on previous chipsets the CPU could still go into full power collapse while a wakelock is held. I still consider the battery stats to be extremely experimental, and in need of a lot of improvement. What we have now is enough to provide a UI to users that will in some cases help them determine when apps are impacting their battery life. There are still a number of things it misses, and many approximations it does that means certain patterns of behavior can't be measured correctly. It is definitely not robust enough to present as a public API with guarantees we feel we can make about it. Honestly, it just sounds like people have bigger expectations for what is there than what it actually is. I definitely don't want people writing apps with the data and presenting it as some kind of strong information that has good guarantees about accuracy. It doesn't. And we have been very careful in the UI that presents the information to try to be conservative about what we show to the user, because of this. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
