Qualcomm

This section allows that the user choose a directory to save the log file created after execution of the Workflow option.

Use this option when you want to check for errors on a log file, instead of the device.

The imported log file will be considered when clicking on "Analyze Logs" button

This option allows to create a screen picture of the device. It is enabled only when there is a device connected.

A window is shown after to select Screencap button if the option "Always ask where to save the image", in "Settings" menu, is selected. If the option is not selected, the picture is storaged in the default directory defined in Preferences menu.

This option allows to enable or disable the log output in workspace area.

The Systrace helps analyse the performance of your application by capturing and displaying execution times of your applications processes and other Android system processes. The tool generates an HTML report that shows an overall picture of an Android devices system processes for a given period of time.

In order to run Systrace, you must have Android SDK Tools updated, Python 2.7 installed and included in your development computer's execution path. In order to generate a trace, you must connect a device running Android 4.1 (API Level 16) or higher to your development system using a USB debugging connection.

Visit Android documentation for more details about Systrace.

To run Systrace, it is necessary to open Utility tab, go to "common" section and select Systrace option.

1. You need to select systrace.py file in your computer (e.g. <android-sdk-path>\platform-tools\systrace\systrace.py).

2. You need to select the destination and to define the name (e.g systrace_output.html) to save the HTML file with systrace values.

3. Choose the filters.

1. Install JDK 8 from Here.

2. After installing make sure the Java version is updated in your path like below:

1. Install Android SDK command line tools from Here.

2. Extract the downloaded package and run <android-sdk-path>\tools\android.

3. Install Android SDK Platform-tools and update others as needed.

4. Put both <android-sdk-path>\tools\ and <android-sdk-path>\platform-tools\ to your path environment variable.

5. Make sure adb is running like bellow:

1. Please run the sdtt-installer shared on Createpoint.

2. This will generate an exe, for example under: C:\Program Files (x86)\Qualcomm\Snapdragon Display Triage Tool or, C:\Program Files (x86)\Qualcomm\Snapdragon Audio Triage Tool

3. Please run the exe and you are all set !!!

1. To select an Chipset, it is necessary to select the android version.

2. The chipset list will be shown based on Android version.

This section shows the list of issues that the user can choose from.

The tool shall execute the commands and debug steps based on the issue chosen by the user.

This section shows the list of utilities that the user can choose from.

The tool shall execute the commands and debug steps based on the issue chosen by the user.

In order to execute a command you will need to have a connected device. For device selection, please follow the steps:

1. Access "File" menu.

2. Choose "Select Device" option.

3. A window is shown and the user can select the device to test.

After the user chooses a device and an item on Issues menu, the Workflow area shows options to analyze the device.

Now, select an item on Workflow with double click.

The commands available for selected option are shown.

There are some types of commands to be executed, for example:

1. Simple commands that can be executed with a double click.

2. Filter command, that can be used to enable or disable a log filter.

3. Checkbox command, that can be used to build a command using multiple parameters or to build multiple commands group.

4. Limit time command, this can be used to auto destroy a command after some seconds. For example:
Limit time set with 10 seconds, the running command will auto destroy after 10 seconds.

The tool has an option to analyze the log file generated by application or imported by the user (Import Log button on Workspace).

When the user click on "Analyze Logs" button, the tool searches keywords defined "expected_errors" tag of the json file.

If the su_log.txt file is empty a message is shown.

This section shows the list of commands that the user can choose from.

It is possible to select multiple commands and run it in parallel with other commands and areas.

To save a log file with the command output, it's necessary to check the follow option:

Limit time command, this can be used to auto destroy a command after some seconds. For example: Limit time set within 10 seconds, the running command will be auto destroyed after 10 seconds.

The play button is used to start all selected commands.

The stop button is used to stop all commands from Quick Commands.

These tabs are created dynamically for each command started from Quick Command area.

Each tab contains action buttons that are responsible to control the commands inside the tab.

The play and stop buttons are used to start and stop respectively the command that belongs to this tab.

The clear button is used to erase the tab content and if the command is also being saved on a log file, it will be cleared too.

In these tabs created by Quick Command area, it is enabled an option to close the tab. This action will stop the command and close it.

This area shows information about actions that the user needs to do.

This button is used to enable/disable autofocus between the tabs.

For example, if is selected 'Actions' tab, and it receives a message error, if it is enabled on 'Error' tab, the application will shown the error message automatically.

A console terminal that runs a bash where you can execute native commands. You should be fine to send commands and retrieve device information.

This area shows information about errors of the application.

This button is used to enable/disable autofocus between the tabs.

For example, if is selected 'Error' tab, and it receives a message error, if it is enabled on 'Actions' tab, the application will shown the error message automatically.

This area will show the status of connection. Such as:

- Disconnected: If no device have already been selected.

- Offline: If you choose to run the tool on offline mode.

- Green icon with device name: The device is connected and selected, all the commands will be targed to this device.

Please make sure the device is shown along with the green light before using the tool to debug an issue.

1. First please choose the required Chipset based on Android version so that the issues list is populated correctly.

2. Then please choose the device from the list of the connected devices.

3. Please choose the issue which you are currently experiencing.

4. For example, lets say there is a black screen issue, please click on black screen.

5. If you have a device connected , please choose "Yes" next like below:

6. Please follow the instructions shown in the "Actions" window and choose the right panel type.

7. Black screen can be due to no backlight or other reasons, hence check the backlight by using the "Check Backlight" option.

8. Based on the prev step result, choose the next step appropriately.

9. If the backlight was OFF, please make sure to reproduce the issue again after the Tool enables proper logs.