After integrating Android Frame Pacing into your game, it's important to verify
that its functionality has provided more consistent frame pacing. The best tool
for confirming this improvement is the
[`systrace` command-line program](https://developer.android.com/topic/performance/tracing/command-line). In
particular, it's best to capture a trace for your game using the following set
of parameters:  

```bash
python systrace.py -a your-app-package-name -o mygametrace.html \
  sched freq idle am wm gfx view sync binder_driver hal input aidl
```

When viewing the output HTML report, you can find information relevant to
frame-pacing in the **SurfaceView** channel. This channel reports the number of
frames that are buffered within the display pipeline. By successfully
integrating Android Frame Pacing into your game, you should see any
inconsistencies in this counter (Figure 1) become stabilized (Figure 2).  
![Systrace
report showing SurfaceView channel](https://developer.android.com/static/images/games/frame-pacing-without-afp.png) **Figure 1.** Inconsistent frame-pacing before Android Frame Pacing integration

*** ** * ** ***

![Systrace report
showing SurfaceView channel](https://developer.android.com/static/images/games/frame-pacing-with-afp.png) **Figure 2.** Consistent frame-pacing after Android Frame Pacing integration