You copied the Doc URL to your clipboard.
Start the Replay from the Command Line
Install the MGD Android application
Trace the OpenGL ES 3.2 application you want to replay using MGD. The Full Trace Process Configuration,
or a configuration that sends more types of assets than the Full Trace configuration (e.g. the
Everything configuration) must be used for the entirety of the trace.
See Process Configuration for more information. Also, make sure the trace contains only one process otherwise the replay may not work correctly.
Push the trace file you want to replay to /sdcard/mgd/replay/ on the target device.
adb push trace.mgd /sdcard/mgd/replay/trace.mgd
You can now launch the replay starting the Android activity.
adb shell am start -n com.arm.mgd.androidapp/.replay.ReplayActivity --es trace_file_path /sdcard/mgd/replay/trace.mgd
The command line interface supports two additional options:
--es force_res <WIDTH>x<HEIGHT>, it forces any EGL window surface size to the specified value.
--ei force_egl_config ID, it forces any EGL configuration to the one with EGL_CONFIG_ID equals to the specified value.
adb shell am start -n com.arm.mgd.androidapp/.replay.ReplayActivity --es trace_file_path /sdcard/mgd/replay/trace.mgd --es force_res 400x400
Please note that forcing the EGL window surface size or overriding an EGL configuration
parameter is an advanced feature that will modify the replay. Depending on what you have changed,
the replay may not work as expected, or not work at all.
The originally traced application may have made assumptions about the EGL window surface size and/or
the EGL configuration, and there is no way for the trace replayer to handle this.
If the forced EGL window surface size is very large the replay may not work due to not enough memory on the device.