|Module||From this drop-down list, select the module to apply the configuration to.|
|Do not launch activity||Select this option to run the application on a virtual or physical device without launching any activities.|
|Launch default activity||Select this option to have the activity marked as start-up launched on application start.|
Select this option to specify the activity to be launched upon the application start.
Type the activity name manually or click the Browse button
and select the desired activity in the Select Activity Class dialog box, that opens.
The list of available activities is determined by the choice of the module.
In this area, choose the type of device to run/debug the application on. The available options are:
Selecting the Show chooser dialog or USB device option may be helpful if you are going to run the application on a physical device which will be plugged in later and therefore the set of available devices cannot be foreseen.
|Prefer Android Virtual Device||From this drop-down box, select the virtual device configuration to run or debug the specified activity.
The drop-down list is available only if the Emulator check box is cleared.
|Browse||Click this button to open the Select Android Virtual Device dialog box, where you can appoint a device to launch upon the future session start-up with the configuration being specified|
In this tab, specify additional configuration settings for launching the Android emulator.
|Network Speed||From this drop-down list, select the network transfer rate to be simulated.|
|Network Latency||Use this drop-down list to specify the time delay between the initial input and the output.|
|Wipe user data||Select this check box to have the contents of the user-data image copied to the new user-data disk image while resetting the image. By default, the <system>/userdata.img is copied.|
|Disable boot animation||Select this check box if you do not want an animated boot screen displayed upon the emulator start-up.|
|Additional command line options||In this text box, type the additional options to be passed to the emulator via the command line. For lengthy command lines, click the button and type the text in the Additional Command Line Options dialog box, that opens.|
|Clear log before launch||Select this check box to have the data from previous sessions removed from the log file before starting the application.|
|InsertInsert||Click this button to add new configuration to the list.|
|DeleteDelete||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for the newly created configurations.|
|or||Alt+UpControl Up or Alt+DownControl Down||Use these buttons to move the selected configuration or group of configurations (folder) up and down in the list.
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
Select this check box to make the run/debug configuration available to other team members.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise.
If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared.
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.