Reputation: 456

Android Studio stuck on loading devices

I'm currently running Android Studio Bumblebee 2021.1.1 in windows 10. The problem I have is each time I start android studio the device list is stuck in loading devices.

I tried these solutions

android studio device list stuck on loading/51101178

android device list showing in android studio got stuck/65177069

The soulutions provided in the threads sometimes work and sometimes don't but the real problem is even if I did fix it in the run time, The next time I open android studio it's still there.

I already tried updating android studio to latest version, reinstalling android studio, deleting all the caches and plugins and resetting it to default. Completely Deleting Sdk folder and downloading again. But nothing helped I don't know where this problem could be originate from

Upvotes: 15

Answers (18)

Santiago

Reputation: 3

In my case I had already restarted and adb was not running.

Cold booting worked for me.

In the device manager tab click the 3 dots and then cold boot.

Upvotes: 0

tf z

Reputation: 61

On linux, you can try close AndroidStudio, then delete the build folder.

./app/build

Upvotes: 0

orhanuckulac

Reputation: 45

what worked for me is:

delete current platform-tools
download new platform-tools from the offical documents or go to android studio open sdk manager and download from there
then open environment variables and add user variable and system variable for platform-tools
restart pc
open cmd
change dir to your platform-tools path run adb start-server
open android studio and it works

Upvotes: 0

arkountos

Reputation: 23

A similar error for me occured when I connected my actual phone, a Google Pixel 5. But maybe this helps someone.

In my case, it was because my phone's USB preferences was set to "No data transfer". After changing it to "File transfer" the devices showed up normally in the drop down.

Upvotes: 0

Alper Öztürk

Reputation: 129

If you're using a VPN, try disabling it first. The VPN might be blocking local network access, preventing ADB from connecting.

Example ADB error message:

cannot connect to daemon at tcp:5037: Connection refused

Upvotes: 1

Lim

Reputation: 1

For my case, this issue was caused by adb not starting. After I opened my terminal and typed adb start-server, it showed the error:

main.cpp:52 cannot open C:\Users\..\AppData\Local\Temp\adb.log: Permission denied

I found the log file, right click open the properties and uncheck the read-only box then type adb start-server again in your terminal and then it will work!

Upvotes: 0

earizon

Reputation: 2238

None of the previous solutions worked for me.

I'm running in Fedora. SELinux permission do not allow adb to run as non-root when installed in $HOME. Next "fix" worked for me:

$ sudo dnf install android-tools # install adb in /usr/bin/
$ cd $HOME/Android/Sdk/platform-tools
$ rm adb
$ ln -s /usr/bin/adb ./adb

Upvotes: 1

Arpit Patel

Reputation: 8047

On a Mac I was missing step 3.

Close Android Studio.
Terminate ADB from the Activity Monitor under the Memory tab. OR Use adb kill-server
Restart the computer (this is crucial for resolving the issue).

As a last resort, reinstall the platform tools.

Upvotes: 0

d1mpis

Reputation: 1

adb kill-server

adb start-server

Fixed it for me

Upvotes: 0

Begmyrat Mammedov

Reputation: 376

Delete all adb tasks from activityMonitor (macOS) or taskmanager (windows). It will work then

Upvotes: 12

Haseeb Hassan Asif

Reputation: 885

I only opened task manager and there were a bunch of adb.exe open so i ended all of them while android studio is running in the background so then adb.exe started again and then i go to android studio and find out that the issue was resolved.

Upvotes: 1

Julien

Reputation: 631

When using Android Studio, or any other IDE which use their own ADB, it is necessary to set Genymotion to use the correct ADB instead of its inbuilt one. It is documented here: https://docs.genymotion.com/desktop/02_Application/#use-third-party-adbsdk

Upvotes: 0

jc12

Reputation: 1829

Restarting my computer fixed the problem for me

Upvotes: 0

Christophy Barth

Reputation: 477

In my case deleting the "platform-tools" folder as Dyenal said didn't work because it said that the folder was open elsewhere (even when I had shut down android studio). If that's your case too, do this.

Close android studio
Go to your task manager
Go to the "Details" tab and look for "adb.exe" as seen in the image below.
Right-click on it and "End task".
Open android studio and pretend you weren't interrupted. Cheers :)

Upvotes: 29

Dyenal Dinesh

Reputation: 81

Go to SDK folder delete platform-tools folder.. invalidate and restart the studio..works for me!

Upvotes: 4

Ali Doran

Reputation: 546

This problem occurs due to Windows folder accessing especially when you change the AVD folder. Windows prevent access to Windows partition root. you have multi options for solving this problem.

Move AVD folder to another driver. Then define it on the Environment variable
Move the AVD to C:\Users\<User>\.android\avd folder. this folder is accessible for Android studio.
Run emulator from device manager, then type adb devices in cmd prompt

Upvotes: 0

Hamed Heidari

Reputation: 456

After hours of research and try and error I finally figured out what was going on. Turns out my adb configuration was conflicting with genymotion's. Nothing could have done at the side of android studio. I went to the genymotion settings ADB tab and changed from Use Genymotion Android Tools to Use custom Android SDK Tools and it went away at last

Upvotes: 2

Sonal

Reputation: 1298

This is a temporary solution. Open terminal and type adb devices. Once your device starts showing up in terminal, it will start showing up in loading devices too.

Upvotes: 0

Android Studio stuck on loading devices

Answers (18)

Related Questions