Home | History | Annotate | Download | only in debugging

Lines Matching full:strong

59   <strong>Figure 1.</strong> An example {@code systrace} report on 5 seconds of process execution
119 <li>On the device connected for tracing, navigate to: <strong>Settings &gt;
120 Developer options &gt; Monitoring &gt; Enable traces</strong>.</li>
121 <li>Select the categories of processes to be traced and click <strong>OK</strong>.</li>
125 <strong>Note:</strong> The {@code adb} shell does not have to be stopped and restarted when
173 <strong>Figure 2.</strong> Excerpt from a trace of a smoothly running application with a regular
204 <strong>SurfaceFlinger</strong> process in the {@code systrace} report where your application is
210 <strong>Figure 3.</strong> Excerpt from a trace of an application showing interruptions in
215 device display. The section of the <strong>SurfaceFlinger</strong> process in top excerpt,
219 the <strong>surfaceflinger</strong> secondary thread is taking a long time (2). This delay
225 <p>Regular, rhythmic execution of the <strong>SurfaceFlinger</strong> process is essential to smooth
234 <strong>Note:</strong> When using {@code systrace} to analyze display problems, make sure
235 you activate the tracing tags for <strong>Graphics</strong> and <strong>Views</strong>.