On Wednesday, February 22, 2012 7:28:59 AM UTC-5, Michael wrote: > > When comparing method traces on this test project, we noticed a > difference. On ICS we see lots of gaps in the execution of the native > function call (i.e. in the JNI function call). On Gingerbread, these > gaps are not present. > We cannot explain why these gaps are there, since nothing else seems > to be happening on other threads [that we can observe using > traceview]. But they account for a large difference between the > measured ‘excl real msec’ and ‘incl real msec’ on the ICS device. >
I think the most interesting question would be to figure out what is happening during that time - something in another process, something in the kernel, or something in a somehow invisible (?) thread in your process? One contrasting tool your might throw at the problem would be top - ie adb shell 'top -t -m 5' Should show the top 5 five cpu-hogging threads system wide regardless of the process they belong to. An interesting question would be what happens if you do the same processing, but on data not derived from the camera, ie without activating the camera. Perhaps something else is looking at the camera - is the platform trying to do something fancy like software focusing, face recognition, scaling? Is the new implementation broken? -- 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
