Android Studio does not detect Android device on Windows 10

Question

I am setting up a Android development environment on a new Windows 10 laptop. I have done this many times on other machines with other operating systems, but this is the first time with Windows 10. The problem is that Android Studio cannot detect my device (LG Zone 3) after I connect it via USB. Note that I have previously used this device for development on an Arch Linux desktop.

I have downloaded Android Studio and created several AVDs. I can run my app and tests on those just fine. However, my hardware device is not listed in the selection dialog.

Here are some things I have tried:

• Check that the USB drivers are installed.
• Restart ADB from the Android Monitor window in Android Studio
• Restart ADB from the command line with adb kill-server and adb start-server.
• Quit Android Studio and restart it.
• Unplug the device, turn off USB debugging, and turn it back on.
• Plug device into a different USB port.
• Switch device connection settings to Charge Only and then back to MTP.

What other trouble-shooting steps can I follow to get my device to work?

Dorwin

Switching to another USB port did it for me, thanks! – Zoology

Answer 1

Depending of your device you might be required to install the phone specific drivers. Also, sometimes it helps if you go to phone Developer settings and uncheck/disable USB debugging and enable it again.

Boroughenglish

> Unplug the device, turn off USB debugging, and turn it back on – Dorwin

Where do I get the device-specific drivers? – Dorwin

What device you have ? Ussualy from producer site – Boroughenglish

I found this download page. How do I know if it is legit? – Dorwin

For my LG I downloaded driver from tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 – Boroughenglish

p.s. I have an LG Zone 3. I edited my question to include that detail as well. – Dorwin

I have found that link using lg.com/us/support/software-firmware-drivers – Boroughenglish

After installing a driver from the link I gave above, my device prompted me to "allow usb debugging", so I think it worked. I rebooted my laptop just as that dialog apppeared so I am now in the process of restarting AS to check it out. – Dorwin

Installing LG-specific drivers solved the problem. Thanks. – Dorwin

Answer 2

There are few ways to resolve this problem.

Case 1. Enable the USB debugging option in your mobile.

Setting > developer > Check "USB Debugging"

Case 2. Change from MTP to PTP.(sometimes vise versa works)

Case 3. If nothing worked then try to Install PdaNet+ in your system. This Actually worked for me.

If it solved your issue then answer this question in the comment section > Which case solved your issue? it will help the coming people who are facing the similar problem.

Heterochromosome

changing from MTP to PTP helped me. stackoverflow.com/a/25974310 – Cleanshaven

Upon connecting the cable, I was prompted to allow access. Because I never chose the "Always" option, it defaulted to "Charging" or "File transfer". Enabling ""USB debugging" in "Developer options" and then going back to "USB options" (via notification tray at top) and changing it to "Photo transfer".... allowed my device (G6, Oreo/8.0) to be visible to Win 10 (via flutter devices) – Hermes

Answer 3

Try this also

1.Just change your cable & give try again

2.Uncheck "Tools" - "Android" - "Enable ADB Integration".

3.Re-Install Google USB drivers

GOTO - http://developer.android.com/sdk/win-usb.html#top Download the driver Reinstall it

Impractical

Thanks for the suggestions. After downloading and installing drivers specific to my device, AS can now find it. – Dorwin

Answer 4

In my case, an LG device, I just downloaded drivers from the lg site, and it fixed the problem without having to fiddle with any settings. LG site: http://www.lg.com/us/support/software-firmware-drivers

Ermin

Answer 5

In my case, I discovered that my device was paired via Bluetooth to my Windows 10 machine. This was preventing it from being listed as a portable device keeping it hidden from Android Studio so make sure the two are not paired.

Crapulous