CODEWITHSUNDEEP
androidandroid-studioadb
Mark Mooibroek
Mark Mooibroek

Reputation: 7696

After Android Studio 3.3 upgrade, so my APK's will build but not not run

After installing i get a Disconnected emulator-5556 message, while im running a different emulator (on 5554).. Even when i don't have any emulators of devices running!

  1. I tried deleting all my AVD's
  2. Wiping AVD data
  3. adb kill-server && adb start-server
  4. AS restart
  5. Created a new user profile on my Mac to see if that helped..
  6. Re-installed SDK Platform tools

When i launch my app via run. The device selector shows this. Is this way since a long time and didnt interfere with my work in AS 3.2. But after upgrading to AS 3.3 i cant run apps anymore

But nothing works, anyone ran into this issue before?

enter image description here

Upvotes: 4

Views: 710

Answers (3)

ToddH
ToddH

Reputation: 2811

I had the same issue after upgrading to Android Studio 3.3. In my case I had the Videostream app on my Mac and it was competing for port 5556. Uninstalling /Applications/Videostream and killing the process freed up port 5556 and everything started working for me again.

Upvotes: 0

Mark Mooibroek
Mark Mooibroek

Reputation: 7696

For if someone runs into this in a couple of years. I tried a couple of commands and the ghost emulator magically disappeared...

First command (to see if a process is doing something with adb)

ps aux | grep adb

Second command (to see if files are opened by a process)

lsof -nP -i4TCP: 5556 | grep LISTEN

Shouldn't have worked, but it stopped the blinking emulator for me..

Upvotes: 1

Irfan Yaqub
Irfan Yaqub

Reputation: 140

No worries, just go to SDK manager and check if the Update is Available for the SDK Platforms, or SDK Tools. this usually happens when we use previous versions and sudden date to the new version of android studio and tools or platforms are not ready or updated with that version. Android has the version compatibility issues.image

Upvotes: 0

Related Questions