If you're only considering methods available in the API you're probably right. However, if you're the one writing an OS you're not restricted to only use API calls ;-) Even thought I haven't spent too much time looking around, there are a few things I was thinking of:
- Battery usage: There's a menu option in "Settings - Application settings - Battery use" which seems to read out just that information. - Crash statistics is obvious, since this information is already available to the developers, today. - For connection/data usage you can use iptables to collect accurate statistics about who the apps are talking to. There are also various virtual files in the /proc/ file system which could be used to collect statistics. - For speed measurement I was thinking of measuring the cpu time that passes inside the vm from the moment an action intent was fired until the respective screen has finished building up. All of these statistics could be gathered by letting each application run on an emulator or collect the data from real devices through the data collection facility already in place. -- 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
