On Sat, Jun 30, 2012 at 1:29 AM, Kumar Rangarajan <[email protected]> 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. > Looks like the Trepn profiler is currently being redesigned and is not > available > (https://developer.qualcomm.com/mobile-development/development-devices/trepn-profiler), > but then as u mentioned it needs to be used with their expensive MDP > devices. That's odd. Trepn Profiler is built into the MDP firmware -- it isn't something you run on the development desktop or something. But, yes, the MDP is crazy expensive. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- 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
