Android Emulator Not Working On Mac

I know that similar questions have been asked before, but my problem is new only after installing Android Studio 2.3, the latest version in March 2017. I have several years experience developing Android applications, and I have never encountered this problem before. After upgrading to version 2.3 of Android Studio, my emulator is no longer able to access the internet. I even uninstalled/reinstalled Android Studio 2.3 from scratch and created a new emulator, and I am still getting the same error. This is not an app problem. I can’t even access the internet from Chrome, and I wasn’t having this problem last week. The message that I get says that the server DNS address could not be found — DNS_PROBE_FINISHED_BAD_CONFIG. The only thing that has changed on my computer in the last week is the new version of Android plus possibly updates to Windows 10. And yes, my computer has access to the internet. Below is an image of my emulator when I try to use Chrome to search for “Google”.

Jul 15, 2021 BlueStacks. BlueStacks is widely regarded as the best and most comprehensive Android emulator you can get. Not only does it work on both Mac and PC, but it also allows you to run multiple games. Feb 12, 2021 Here are some of the best Android emulators for Mac. Bluestacks is one of the most popular Android emulators for Windows and is probably the best Android emulator for macOS, as well. This emulator is built primarily for mobile gamers and claims to provide a “PC-like” gaming experience for your mobile apps. An Android emulator is a software application that allows your mobile to imitate Android OS features into your PC. It allows you to install Android Apps on your computer or laptop and use them natively. It is mainly used for debugging purposes. Following is a handpicked list of Top Android Emulator, with their popular features and website links. In Android Studio (Mac OS X) open up AVD Manager. Click the triangle pointing downwards on the offending Android Virtual Device to get a drop-down menu. Then, strike down upon Delete with great vengeance and furious anger. With that out of the way, click + Create Virtual Device.

Answers:
Working

I found a temporary solution on an old Stack Overflow thread at Upgraded to SDK 2.3 – now no emulators have connectivity. Note that this thread talks about Android SDK 2.3, not Android Studio 2.3. The problem seems to be that the emulator can’t find the DNS my computer is currently using, and the temporary workaround is to start the emulator from the command line and specify the DNS server. Whatever problem occurred back then must have reappeared in the latest version of Android Studio.

The temporary solution outlined below fixes the problem with the emulator accessing the internet. However, it does not fix the problem that occurs when trying to run Android Device Monitor. Doing so will still make the emulator go offline as described above.

Note that there are two files named “emulator.exe” in the sdk — one under sdktools and another under sdkemulator. Either might work below, but I use the one under sdkemulator.

The first step is to find where the SDK is located. Assuming a user name of “jdoe” and a default installation of Android Studio on Windows, the SDK is most likely in
C:UsersjdoeAppDataLocalAndroidsdk.

The second step is to determine the name of the AVD (emulator) that you want to run. The command
C:UsersjdoeAppDataLocalAndroidsdkemulatoremulator.exe -list-avds
will show the names of your AVDs. On my computer it shows only one, Nexus_5X_API_25.

To start the emulator from the command line with a specified DNS server, use something like the following:
C:UsersjdoeAppDataLocalAndroidsdkemulatoremulator.exe -avd Nexus_5X_API_25 -dns-server 8.8.8.8

In this case, 8.8.8.8 is a Google public domain name server.

The above commands can be shortened if you create appropriate environment variables and edit your PATH environment variable, but I recommend caution when doing so.

Answers:

I experienced this same issue after upgrade. Upon opening the Chrome browser in the emulator, google.com could no longer be reached.

I found a post on SO that suggested the problem was with the emulator trying to use a disconnected network adapter. For me the problem was occurring when I was connected to a LAN. Disabling the wireless LAN adapter fixed the issue.

To disable the adapter:

  1. Navigate to Network connections
  2. Find the adapter
  3. Right click and choose disable
Answers:

This was a problem for me last time the emulator updated itself and back then disabling other network adapters fixed it. Now it’s cropped up again but the only adapter that is enabled is a single wifi one so I have nothing to disable.

The issue only reappeared after I updated via a prompt the emulator tools to 26.1.1. I uninstalled and reinstalled the emulator via the SDK Tools update tab and thankfully the only option when installing again right now is to install 26.0.3 (which seems to be working okay).

Moral of the story is to be very wary of emulator updates.

Answers:

This happend to me when the emulator froze and I had to kill the process. The signal icon always showed the small “x” as in the screenshot and no internet connection was successful.

The only thing that helped was uninstalling and reinstalling the emulator (not the AVD images)

In Android Studio:

Android Studio Emulator Not Working Mac M1

Tools-> Android -> SDK Manager
Uncheck “Android Emulator” and let it uninstall then check again and let it install again.

Answers:

For me the problem was caused when I took my laptop home without restarting the emulator. From what I have read, when the emulator starts up it reads your PC’s DNS settings and uses them. When I was on my home network, my work DNS settings were failing.
So yeah. Just restarting the emulator solved my problem.

Answers:

After 10 days of trouble, I just deleted everything from C:Android.android and deleted all created AVDs. Now internet seems to work fine.

Android Emulator Not Working On Mac Computer

Answers:

Just recreating the emulator with another target API worked for me

Answers:

Simply open the AVD Manager and wipe the data of that emulator works for me.

Answers:
Questions:

I had this also and I solved it by creating new android emulator virtual device and chosen Nexus 4 api 27. Before I was creating Pixel device api 28, and it was not working even after recreating device. So I tried totally different configuration and Android Emulator has internet connection as is expected. Other solutions did not work for me but I did no try it all.

Answers:
Mac

I’ve faced the very and suddenly same problem on my MAC. After having tried everything, I’ve finally deleted the folder /Users/Philippe/.android and create a new emulator.

Tags: android