[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-27 (世界標準時間)。"],[],[],null,["# Verify frame pacing improvement\n\nAfter integrating Android Frame Pacing into your game, it's important to verify\nthat its functionality has provided more consistent frame pacing. The best tool\nfor confirming this improvement is the\n[`systrace` command-line program](/topic/performance/tracing/command-line). In\nparticular, it's best to capture a trace for your game using the following set\nof parameters: \n\n```bash\npython systrace.py -a your-app-package-name -o mygametrace.html \\\n sched freq idle am wm gfx view sync binder_driver hal input aidl\n```\n\nWhen viewing the output HTML report, you can find information relevant to\nframe-pacing in the **SurfaceView** channel. This channel reports the number of\nframes that are buffered within the display pipeline. By successfully\nintegrating Android Frame Pacing into your game, you should see any\ninconsistencies in this counter (Figure 1) become stabilized (Figure 2). \n**Figure 1.** Inconsistent frame-pacing before Android Frame Pacing integration\n\n*** ** * ** ***\n\n**Figure 2.** Consistent frame-pacing after Android Frame Pacing integration"]]
