The situation when the development environment Android Studio stops detecting a connected mobile device is one of the most common and annoying problems for beginners and experienced programmers. You connect the cable, expect to see the model name in the list of devices, but instead you see an empty list or a mysterious message “No devices detected”. This can happen for many reasons: from a simple bad cable to complex driver conflicts in the operating system.
Most often the problem lies not in the IDE itself, but in the operating system settings or parameters of the smartphone itself. USB debugging must be activated, and the computer must have the correct digital signatures to interact with the gadget. Sometimes it is enough to simply reconnect the cord, but in other cases, in-depth diagnostics of the protocol ADB (Android Debug Bridge) is required. In this article we will analyze all possible failure scenarios and provide a clear algorithm of actions to restore communication.
Don't panic if your device suddenly disappears from the list after a system update. This is often due to changes in Google's security policies or updates to platform tools. Below we will take a detailed look at the technical aspects of the setup that will help you restore the functionality of your working environment and continue developing applications without unnecessary delays.
Diagnostics of the physical connection and cable
First of all, it is necessary to exclude hardware faults. Many users make the mistake of using cheap cables designed solely for charging batteries. Such wires do not have internal data lines, so the computer sees the phone only as a power source, but not as a peripheral device. Make sure that you are using an original cable or a certified analogue that supports data transfer.
Try connecting the device to a different USB port on your computer. It is advisable to use ports located directly on the motherboard (at the back of the system unit), and not on the front panel of the case or through a USB hub. Front ports often have insufficient voltage or poor contact, which leads to unstable operation ADB. If you are using a laptop, check the operation of different connectors on both sides.
It is also worth paying attention to the condition of the connector itself in the phone. Over time, dust and lint accumulate in the port USB Type-C or Micro-USB which prevents full contact of the plug. Gently clean the connector with a wooden toothpick or compressed air. Even a small layer of dust can prevent the contacts responsible for data transmission from closing.
Use the cable that came with the device. If it is lost, buy cables from well-known brands with a declared support for data transfer speeds of at least 480 Mbit/s.
Setting up developer and debugging mode on a smartphone
The most common software reason for this Android Studio does not see the phone - this is a disabled developer mode. By default, this feature is hidden from regular users for security reasons. To activate it, you need to go to the phone settings, find the “About phone” section and quickly click 7 times on the “Build number” item. After this, a new section “For Developers” will appear in the main settings menu.
Inside this section you need to find the “USB Debugging” switch and activate it. When you first connect to a new computer, a system dialog box will appear on the smartphone screen asking for debugging permission Be sure to click "Allow" and check the box "Always allow from this computer." If you ignore this window or click "Cancel", the device will not be accessible to the IDE.
Modern versions of Android (starting from 11 and higher) have additional security measures. Now, when you connect the cable, the phone defaults to “Charge Only” mode. You need to manually change this behavior. Swipe down the notification shade, tap the USB connection notification, and select File Transfer or MTP mode. Without this step, the computer may not see the device correctly.
☑️ Checking phone settings
Installing and updating USB drivers in Windows
The Windows operating system often cannot automatically select the correct driver for specific smartphone models, especially when it comes to Chinese brands like Xiaomi, Oppo or Vivo. In Device Manager, this connection may appear as "Unknown device" or "Android" with a yellow exclamation mark. This means that there is a physical connection, but the system does not know how to work with it.
To solve the problem, it is recommended to install the universal Google USB Drivers via the SDK Manager inside Android Studio itself. Open menu Tools → SDK Manager, go to the SDK Tools tab and find the "Google USB Driver" item. Install or update it. If this does not help, download specific drivers from the official website of your smartphone manufacturer.
Sometimes manual driver installation through the device manager helps. Right-click on the problematic device, select "Update driver" → "Browse for drivers on this computer" → "Select a driver from the list of available drivers." In the list, select "Android Devices" and then "Android ADB Interface". This action will force the system to use the correct communication protocol.
| Manufacturer | Driver type | Where to download | Installation features |
|---|---|---|---|
| Google Pixel | Google USB Driver | Android SDK Manager | Installed automatically |
| Samsung | Samsung USB Driver | Official website Samsung | Requires a reboot after installation |
| Xiaomi | Universal ADB Driver | Third-party repositories | Often requires disabling signature verification |
| Huawei | HiSuite Drivers | HiSuite application | Installed with the app |
Working with ADB and restarting debug server
Sometimes the problem lies not in the drivers, but in a frozen process ADB Server. The debug server may have become confused in sessions or lost connection to the daemon on the device (adbd). In such cases, the most effective solution is to force a service restart. This can be done through the terminal inside Android Studio or through the operating system command line.
Open a terminal (in the bottom panel of Android Studio) and enter a command to stop the server, and then a command to start it. This will clear the current connections and initiate a new device discovery. If the server has been blocked by another process (for example, an emulator or a third-party phone management app), this procedure will free up the port.
adb kill-serveradb start-server
adb devices
After executing the command adb devices you should see a list of connected devices. If your phone status is displayed there device, then the problem is solved. If the status is unauthorized, return to the phone and confirm the debugging request. The status offline usually indicates that the device is busy or there is a platform version conflict.
What to do if ADB does not start?
If the commands do not work, check your PATH environment variables. The path to the platform-tools folder must be added to the Windows or Linux system variables. Without this, the system will not find the executable file adb.exe.
Conflicts between versions of the platform and build tools
Inconsistency between the versions Platform-Tools on the computer and the Android version on the phone can lead to the invisibility of the device. The ADB protocol changes periodically, and older versions of the tools may not work correctly with new versions of the OS, and vice versa. Always keep your update tools up to date via the SDK Manager.
It's also worth checking the settings of the project itself in Android Studio**. Make sure that the file build.gradle indicates the correct versions compileSdkVersion and targetSdkVersion. Sometimes the IDE ignores devices if their API level is below the minimum required to run the application. In this case, your phone may simply not be displayed in the list of devices, although it is physically connected.
Pay attention to the message in the bottom panel of Device Manager. If there are any incompatibility warnings, click the link to update the components. In rare cases, completely reinstalling the package helps. Android SDK Platform-Tools. To do this, delete the tools folder manually and download it again from the official developer resource.
⚠️ Attention: The Android Studio interface and the location of the settings may change with each major IDE update. If you do not find the described menu items, use the settings search (Ctrl+Shift+A) by entering the name of the desired option.
Specific problems of macOS and Linux
Users of Unix-like systems encounter access rights problems. Unlike Windows, Linux and macOS often require superuser rights or special rule settings to access USB devices. If you are running Android Studio as a standard user, the system may be blocking access to the I/O port. udev. If you are running Android Studio as a standard user, the system may be blocking access to the I/O port.
To solve the problem on Linux, you need to create a udev rules file. Create a file /etc/udev/rules.d/51-android.rules and add a line there with your Vendor ID. For example, for Google devices it looks like SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev". After this, you need to restart the udev service or reboot your computer.
On macOS, the problem may occur due to conflicts with synchronization apps such as Android File Transfer. This app hijacks the MTP connection and prevents ADB from accessing the device. Try closing the Android File Transfer app completely through Activity Monitor and reconnecting your phone. Also make sure that the terminal has rights to access USB in the system privacy settings.
In Linux and macOS, the problem of phone “invisibility” in 90% of cases is associated with the lack of access rights to the USB port for the current user.
Alternative methods of connection and debugging
If the wired connection stubbornly fails works, you can use the Wi-Fi debugging function. Starting with Android 11, this capability is built directly into the system without the need to use the command line for initial setup (though the first pair still often requires a cable). This is a convenient way to test applications without the hassle of wires.
To activate, go to developer mode, find the "Wi-Fi Debugging" item and turn it on. Click "Pair with pairing code." Then in Android Studio go to Device Manager → Physical → Pair using Wi-Fi and enter the code. After successful pairing, the device will appear in the list of those available for launch.
Another option is to use an emulator. If a physical device is critically needed only for testing layout or basic logic, the built-in Android Studio emulator often copes with this task faster and more stable. It allows you to simulate different screen resolutions, Android versions and even network parameters, which is sometimes even preferable to a real device in the early stages of development.
⚠️ Attention: Wi-Fi debugging only works on one local network. Make sure that the computer and phone are connected to the same router, otherwise they will not see each other.
Frequently asked questions (FAQ)
Why is the phone detected as a charger, but not as a storage device?
This is standard behavior in modern versions of Android for security purposes. When connecting the cable, the system defaults to “Charge Only” mode. You need to open the notification shade on your phone, click on the USB connection notification and manually switch the mode to “File Transfer (MTP)” or “PTP”.
What should you do if you see “ADB Interface” with error 10 or 43 in the device manager?
This indicates a driver conflict or a failure in their operation. Try completely removing the device from the manager (right button → Remove device), disconnecting the cable, restarting the computer and connecting the cable again. The system will try to reinstall the driver from scratch.
Can an antivirus block the phone's connection to Android Studio?
Yes, some aggressive antiviruses or firewalls can block the process adb.exe, considering it suspicious since it has access to the device's file system. Try temporarily disabling protection or adding the folder with the Android SDK to your antivirus exclusions.
Why does the device appear in the list as "unauthorized"?
A window should appear on your smartphone screen asking you to allow debugging from this computer. If you did not notice it or closed it, the connection will not be established. Disconnect and reconnect the cable to bring up the window again, and be sure to click "Allow".
How to check whether the computer sees the phone at the hardware level?
In Windows, open "Device Manager" and look at the "Portable devices" or "USB controllers" section. If your device is there (even with an error), then the port and cable are working and the problem is software. If the device is nowhere to be found, the problem is in the cable, port or connector of the phone.