10

I upgraded my Android Studio to v4.1.

But adb commands are doesn't respond. See:enter image description here

Therefore Android Studio Devices status stuck at "Loading Devices". Like this:enter image description here

Does anyone know about this issue?

b.erdi
  • 386
  • 3
  • 12
  • Do you use Flutter? Check these threads https://superuser.com/questions/1401980/android-studio-device-dropdown-stuck-on-loading https://stackoverflow.com/questions/51101178/android-studio-device-list-stuck-on-loading – Andrey Oct 16 '20 at 10:24
  • no i am using kotlin – b.erdi Oct 16 '20 at 10:28
  • I'm having this issue on Android Studio Canary as well but I didn't experience this problem on Android Studio 4.1. The project that I'm working on uses Jetpack Compose and the only way to use its preview features are supported at the Canary version. So I checked ADB and it seems to work fine. Do you guys have any other solution ideas? – Yekta Sarıoğlu Oct 18 '20 at 09:33
  • 1
    https://issuetracker.google.com/issues/170650367 – b.erdi Oct 19 '20 at 08:05
  • 1
    I have the exact same problem. It only works after restarting the computer, but the problem comes back again. I'm using MacOS – JoaoM Oct 22 '20 at 10:56

6 Answers6

8

On my situation, I had to delete the platform-tools folder found in SDK folder and replace it with the latest version.

Ex. C:\Users\ (computer name)\AppData\Local\Android\Sdk, from this path you should find a folder named platform-tools then delete it.

Hence, I had to install the latest platform-tools from the official site of android. Here is the link, https://developer.android.com/studio/releases/platform-tools. You only have to download the latest platform-tools specifically for your computer OS. After, unzip it to the path where you had deleted the old version of it.

By the way, platform-tools contains an executable file named adb.exe

4xMafole
  • 479
  • 1
  • 8
  • 20
1

This is an issue with the latest Android Studio version. The only way to overcome it right now is to open the Android Studio terminal and run the start-server command manually:

/Users/[YOUR_USERNAME]/Library/Android/sdk/platform-tools/adb start-server

enter image description here

André Sousa
  • 1,692
  • 1
  • 12
  • 23
1

I had been dealing with this bug as I stated in the comment section for a while in Android Studio Canary. But it seems like this is a general problem that newer Android Studio versions have. So, these steps would work for most people.

  1. Uninstall Android Studio including the user settings. (Don't delete the folder. Uninstall properly.)

  2. Download and install Android Studio 4.X or Canary as you prefer. And, do not accept old user settings if the Android Studio ask you to choose it. In my case, it did not ask but it worked like a charm.

  3. Open the project

And voila.

Yekta Sarıoğlu
  • 1,435
  • 2
  • 12
  • 20
0

Same, Took a while as there were a lot of processes running. Eventually my plugged in devices came up just as I was about to "File... Invalidate Caches and Restart"

Did it eventually come back up for you?

Berry Wing
  • 113
  • 1
  • 5
  • 2
    I tried "Invalidate cache and restart" before, but it didn't worked for me. When i restart my computer emulator works for one or two builds. It's a completely weird issue :) – b.erdi Oct 17 '20 at 07:15
  • I usally kill off adb process from task manager few times and it worked, but not always :) –  Nov 04 '20 at 12:45
0

For me, having environment path of adb set caused stuck at "Loading Devices". I removed the environment path and restarted Android Studio, my device could connect again

It still not work with Memuplay emulator. I have to launch another emulator called LDPlayer and reboot Memuplay while LDPlayer still running, it will now connect to adb

0

I met the same problem, and i solved it by:

  1. Try to reinstall Flutter
  2. Reset Flutter SDK path in [Android Studio] under "Preference > Languages and Frameworks > Flutter".
谢沛江
  • 1