It is almost impossible to use systrace during the application start, because it is not possible to run it before application start. Much better is situation with MethodTracking which is possible to run from the code by Debug.startMethodTracingSampling() method. But file created by this method is not possible to open in the Android Studio, just in the Device Monitor tool. But bigger issue of method tracer in the Device monitor is that it is not possible to filter just methods in my code and exclude all Android internals code and then it is very complicated to find the right thing.
Do you have in the plan some improvements in this area? Like - possibility to start systrace before the application run to monitor application start possibility to start it from the code. - possibility to open .trace file created by Debug class in the Android studio method tracker - or some automatic analysis tool which is able for example found problematic calls on the main thread that cause animations slow down. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
