Run apps on a hardware device

When building an Android app, it's important that you always test your app on a real device before releasing it to users. This page describes how to set up your development environment and Android device for testing and debugging over an Android Debug Bridge (ADB) connection.

Set up a device for development

Before you can start debugging on your device, there are a few things you must do:

On the device, open the Settings app, select Developer options, and then enable USB debugging.

Note: If you do not see Developer options, follow the instructions to enable developer options.
Set up your system to detect your device.
- macOS: No additional configuration required.
- Ubuntu Linux: Use apt-get install to install the adb package. This gives you a community-maintained default set of udev rules for all Android devices.
  
  Make sure that you are in the plugdev group. If you see the following error message, adb did not find you in the plugdev group:
```
error: insufficient permissions for device: udev requires plugdev group membership
```
  Use id to see what groups you are in. Use sudo usermod -aG plugdev $LOGNAME to add yourself to the plugdev group.
  
  The following example shows how to install the Android adb tools package.
```
apt-get install adb
```
- Windows: Install a USB driver for ADB. For an installation guide and links to OEM drivers, see the Install OEM USB drivers document.
- Chrome OS: No additional configuration required.

Connect to your device

When you are set up and plugged in over USB, you can click Run in Android Studio to build and run your app on the device.

You can also use adb to issue commands, as follows:

Verify that your device is connected by running the adb devices command from your android_sdk/platform-tools/ directory. If connected, you'll see the device listed.
Issue any adb command with the -d flag to target your device.

Troubleshoot device connection with the Connection Assistant

The Connection Assistant provides step-by-step instructions to help you set up and use a device over the ADB connection.

To start the assistant, choose Tools > Connection Assistant.

The Connection Assistant provides instructions, in-context controls, and a list of connected devices in a series of pages in the Assistant panel. Use the Next and Previous buttons at the bottom of the Assistant panel to work through the pages as needed:

Connect your device over USB: The Connection Assistant begins by prompting you to connect your device over USB, and it provides a Rescan USB devices button with which you can start a new scan for connected devices.
Enable USB debugging: The Connection Assistant then tells you how to enable USB debugging in the on-device developer options.
Restart the ADB server: Finally, if you still don't see your device on the list of available devices, you can use the Restart ADB server button on the last page of the Connection Assistant. Restarting the ADB server also causes ADB to scan for devices again. If you still don't see your device on the list of available devices, try the troubleshooting steps in the next section of this page.

Resolve USB connection issues

If the Connection Assistant is not detecting your device over USB, you can try the following troubleshooting steps to resolve the issue:

Check that Android Studio can connect to the Android Emulator

To check if the issue is being caused by a connection problem between Android Studio and the Android Emulator, follow these steps:

Open the AVD Manager.
Create a new AVD if you don't already have one.
Run the emulator using your AVD.
Do one of the following:
- If Android Studio can't connect to the emulator, download the latest SDK Platform Tools and then try again.
- If the emulator starts successfully, check the USB cable.

Check the USB cable

To check if the issue is being caused by a faulty USB cable, follow the steps in this section.

If you have another USB cable:

Connect the device using the secondary cable.
Check if the Connection Assistant can now detect the device.
If the device is not detected, try the primary cable again.
If the device still isn't detected, assume that the problem is with the device and check if the device is set up for development.

If you don't have another USB cable but you do have another Android device:

Connect the secondary device to your computer.
If the Connection Assistant can detect the secondary device, assume that the problem is with the primary device and check if the device is set up for development.

If the secondary device is not detected, the problem might be with the USB cable.

Check if the device is set up for development

To check if the issue is being caused by settings on the device, follow these steps:

Follow the steps in the Set up a device for development section.
If this does not resolve the problem, contact the device OEM's customer support for help. Tell the customer support representative that the device won't connect to Android Studio using ADB.

RSA security key

When you connect a device running Android 4.2.2 (API level 17) or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.