#SUPERTUXKART WORLD RECORD FOR ANDROID#
#SUPERTUXKART WORLD RECORD ANDROID#

gatord -c configuration.xml -s session.xml -o c1.apc -wait-process _dbg Make sure to kill the previously run gatord before starting to capture the actual application profiling data. $ adb shell run-as _dbg cp /data/local/tmp/session.xml session.xml Starting a local capture This is a good time to optionally edit the session.xml to set values such as the duration of the capture, but there is no requirement to change anything.

The session.xml needs to be pushed from the host to the application data directory on the device. $ adb shell run-as _dbg cp /data/local/tmp/configuration.xml configuration.xml The configuration.xml is already on the device, but it needs to be copied to the application data directory. This will launch a dialog to save the session.xml on the host computer.īoth files need to go in the data directory for the application to be profiled. To get the session.xml file use the Capture & Analysis options button (gear) and click Export at the bottom.

#SUPERTUXKART WORLD RECORD ANDROID#

This will generate a configuration.xml file in /data/local/tmp on the Android device. Without the flag the CPU counters won't appear. As long as the -wait-process flag was used the CPU counters should be visible so they can be selected. Use the Counter Configuration button (chip) to select the counters. $ adb shell /data/local/tmp/gatord -wait-process _dbgĬonnect Streamline by clicking the “Browse for target” button (eyeball). $ adb push $DS5_HOME/sw/streamline/bin/arm/gatord /data/local/tmp I will continue with the SuperTuxKart application, but change the package name as needed for the application you would like to profile. This is possible because the adb shell permissions are different than the permissions of the user id for the application to be profiled. To create the two xml files, put gatord in /data/local/tmp and make a normal Streamline connection. A review of the gatord command line arguments is also useful to get started. A session.xml file and a configuraton.xml file. To capture data on the device two files are needed.

Streamline gatord version 670 (Streamline v6.7)Įrror creating server TCP socket Setting up for local capture mode Local capture mode can be used instead to profile the application. If you followed the article and experienced the error below, it indicates the Android device doesn’t allow a TCP connection. A future version of Streamline will provide a better solution to the problem, but until then local capture mode can be used. The problem is device specific and is not related to the Android version.

#SUPERTUXKART WORLD RECORD FOR ANDROID#

With local capture mode data is stored on the target system and the files are later copied to the host computer for analysis by Streamline.Īfter writing Streamline performance analyzer for Android application profiling it turns out some Android devices restrict the use of TCP sockets and this causes gatord to fail in daemon mode. Local capture mode is used when it’s not possible to send live data back to the host. It’s normally used in daemon mode to capture and send data over a network or USB connection from the target system to the host computer. The Streamline daemon, gatord, has two modes of operation, daemon mode and local capture mode.

Supertuxkart world record