The number printed is the time from when the activity manager first received the startActivity() call to right after the window manager shows the drawn window. I don't know what different you are looking for, but you could start by looking at the code in the activity manager that prints this log to understand that and then see how you want to adjust things to get whatever number you want.
Sorry I can't help with launchperf, I just know that there are some instrumentation tests to launch activities and perform timing of them. On Thu, Apr 23, 2009 at 9:49 PM, Chai <jandhyalachaita...@gmail.com> wrote: > > Hi Dianne, > > Thanks for your input .. We tried getting that info frm Logcat thru > DDMS. But there is a significant difference (we can notice it by eye > also) by the time the event shown that activity is launched and it is > actually shown on the display screen .. So we are looking for ways to > get the info right before the information is drawn on the screen.. Is > there way we can get this info from windowmanger or surfaceflinger ?? > > Also could you pls let me know how I can use "launchperf in the > samples directory " ? any pointers towards this is highly appreciated. > we are struck-up at this pt... > > Regs, Chaitanya > > On Apr 23, 9:35 pm, Dianne Hackborn <hack...@android.com> wrote: > > Good point, you can use that as an example of writing instrumentation > > against an .apk and how you can do timing with the operations. > > > > > > > > On Thu, Apr 23, 2009 at 9:31 PM, dan raaka <danra...@gmail.com> wrote: > > > dianne , what about launchperf in the samples directory > > > > > On Thu, Apr 23, 2009 at 8:29 PM, Dianne Hackborn <hack...@android.com > >wrote: > > > > >> There is a log printed with the time to launch an activity -- look at > adb > > >> logcat. I also think there is a more structured event log you can see > with > > >> adb logcat -b events. > > > > >> On Thu, Apr 23, 2009 at 6:56 PM, Chai <jandhyalachaita...@gmail.com > >wrote: > > > > >>> Hi , > > > > >>> For application UI performance measurement, We have a requirement to > > >>> know the time it takes to show the app on the display screen , after > > >>> the intent is fired to launch the application i.e. Letsay I have 1000 > > >>> contacts in my database, I want to know how much time does the > > >>> application take to lauch(or show it on the screen) when we launch > the > > >>> contacts app. We are launching the activity thru ADB and getting the > > >>> timestamp on when we launched, we wanted to know when it is rendered > > >>> on the screen.. Is there anyway that we can know this information > from > > >>> WindowManager or SurfaceFlinger ? If yes, how can we get this > > >>> information.. Pls let us know. > > > > >>> Regs, Chaitanya > > > > >>> On Mar 17, 4:34 pm, Dianne Hackborn <hack...@android.com> wrote: > > >>> > Because the window manager is responsible for organizing the > screen, > > >>> > applications don't get to decide that. The window manager > allocates > > >>> > surfaces and decides where they go and how they are layered; it > never > > >>> > touches their bits, which is up to the application. > > > > >>> > On Tue, Mar 17, 2009 at 3:21 PM, Videoguy <puri_mall...@yahoo.com> > > >>> wrote: > > > > >>> > > A surface is basically a pointer to block of memory. Why does a > > >>> > > separate process (i.e. Window Manager) have to create it? Why not > the > > >>> > > activity itself create it? > > > > >>> > > Does Window manager need access to that memory? > > >>> > > If so, why? > > > > >>> > > Just curious. > > > > >>> > > Thanks > > >>> > > Videoguy > > > > >>> > -- > > >>> > 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. All such questions should be posted on > public > > >>> > forums, where I and others can see and answer them. > > > > >> -- > > >> 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. > > > > -- > > 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. > > > -- 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-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
