Lines Matching refs:will

42 inside the android shell. This will replay the full trace and then exit. Running this command
43 outside of the shell by prepending `adb shell` will not allow for manual control and will not turn
46 The replay will not fill surfaces with their contents during the capture. Rather they are given a
47 random color which will be the same every time the trace is replayed. Surfaces modulate their color
60 When replaying, if the user presses CTRL-C, the replay will stop and can be manually controlled
61 by the user. Pressing CTRL-C again will exit the replayer.
98 - replayManually - **True**: if the replayer will immediately switch to manual replay at the start
99 - numThreads - Number of worker threads the replayer will use.
114 And the trace will start replaying. Once the trace is finished replaying, the function will return.
115 The layers that are visible at the end of the trace will remain on screen until the program
197 corresponding Event base on its time stamp. After completing an increment, the main thread will
236 **SettingUp**, in which the main thread will wait, or the worker will be **Waiting**, in which the
237 main thread will **Signal** it to complete. The worker thread changes itself to the **Running**
248 During a **BuferUpdate**, the worker thread will wait until **Signaled** to unlock and post a
250 **BufferUpdates** that act on the same surface, both threads will try to lock a buffer and fill it,
251 which isn't possible and will cause a deadlock. The BufferQueueScheduler solves this problem by
261 arguments. Executes `replay()` on the Replayer. If there are no errors while replaying it will exit
262 gracefully, if there are then it will report the error and then exit.