Android Emulator Mac Catalina

by

BEST ANDROID EMULATORS for PC 2020 (Windows, Mac and linux): Android emulators have always been a hot topic in the community, as it is still. When I try to launch Android emulator, it crashes on Mac OS X. It was working some time ago, but now it isn’t and I. Macos-catalina macos-high-sierra. Macintosh OS or popularly known as Mac OS used by Apple on its Mac PC’s and Macbook’s is an awesome OS, with its awesome user-interface, and great features, wouldn’t it be more awesome if we are. The emulator transparently rewrites the GET requests from the virtual device before talking to the proxy so it works. If your emulator must access the internet through a proxy server, you can configure a custom HTTP proxy from the emulator's Extended controls screen. With the emulator open, click More, and then click Settings and Proxy. Mumu App Player is an Android emulator for the macOS operating system. 10.12 Sierra,10.13 High Sierra,10.14 Mojave,10.15 Catalina; Other languages. Can install Android applications.

Question or issue on macOS:

Could anybody post a working solution for setting ANDROID_HOME via the terminal?

My path to the Android-SDK is /Applications/ADT/sdk.

How to solve this problem?

Solution no. 1:

Where the Android-SDK is installed depends on how you installed it.

  1. If you downloaded the SDK through their website and then dragged/dropped the Application to your Applications folder, it’s most likely here:

    /Applications/ADT/sdk (as it is in your case).

  2. If you installed the SDK using Homebrew (brew cask install android-sdk), then it’s located here:

    /usr/local/Caskroom/android-sdk/{YOUR_SDK_VERSION_NUMBER}

  3. If the SDK was installed automatically as part of Android Studio then it’s located here:

    /Users/{YOUR_USER_NAME}/Library/Android/sdk

Once you know the location, open a terminal window and enter the following (changing out the path to the SDK to be however you installed it):

Once you have this set, you need to add this to the PATH environment variable:

Lastly apply these changes by re-sourcing .bash_profile:

source ~/.bash_profile

  1. Type – echo $ANDROID_HOME to check if the home is set.

echo $ANDROID_HOME

Solution no. 2:

In Terminal:

Add lines:

Check it worked:

Solution no. 3:

Adding the following to my .bash_profile worked for me:

Android Emulator Mac Catalina

Solution no. 4:

quoting @user2993582’s answer

The ‘bin’ part has changed and it should be

Solution no. 5:

I am having MAC OS X(Sierra) 10.12.2.

I set ANDROID_HOME to work on React Native(for Android apps) by following the following steps.

  • Open Terminal (press Command+R, type Terminal, Hit ENTER).

  • Add the following 3 lines to ~/.bash_profile.

  • Finally execute the below command (or RESTART the system to reflect the changes made).

    source ~/.bash_profile

That’s it.

Solution no. 6:


Could anybody post a working solution for doing this in the terminal?

ANDROID_HOME is usually a directory like .android. Its where things like the Debug Key will be stored.

You can automate it for your login. Just add it to your .bash_profile (below is from my OS X 10.8.5 machine):

According to David Turner on the NDK Mailing List, both ANDROID_NDK_ROOT and ANDROID_SDK_ROOT need to be set because other tools depend on those values (see Recommended NDK Directory?).

After modifying ~/.bash_profile, then perform the following (or logoff and back on):

Solution no. 7:

To set ANDROID_HOME, variable, you need to know how you installed android dev setup.

If you don’t know you can check if the following paths exist in your machine. Add the following to .bashrc, .zshrc, or .profile depending on what you use

If you installed with homebrew,

Check if this path exists:

If you installed android studio following the website,

Finally add it to path:

If you’re too lazy to open an editor do this:

Solution no. 8:

I’m using React Native with Catalina mac os and zsh shell

1- touch ~/.zshrc

2- open ~/.zshrc

3- according to React Native android setup copy and past

to the opened text file then save and close the file.

4- run source ~/.zshrc
and make sure to restart your terminal.

5- run adb you will get something like


Android Debug Bridge version 1.0.41 Version 30.0.0-6374843

Catalina

thanks for this documented

Solution no. 9:

People, note that if you will use ~/.bash_profile then it will edit not your user’s bash profile, but global. Instead go to your users directory (/Users/username) and edit it directly:

And insert following two lines with respect to your Username and SDK directory

Solution no. 10:

Setup ANDROID_HOME , JAVA_HOME enviromental variable on Mac OS X

Add In .bash_profile file

For Test

Hope this helps!

Bluestacks Android Emulator Mac

This article is part of a three-part series on cross-browser testing Windows, iOS, and Android from macOS.

If you want to test your websites on an Android device, one option is to use an Android emulator to open a browser and navigate to your website. Android Studio, the official IDE of Android, ships with a built in emulator similar to the one we used in our previous post on cross-browser testing on iOS devices from macOS.

Android Emulator For Mac Os Catalina

Note: This article was written using the following operating system and software versions:
– macOS Catalina, Version 10.15.7 on a MacBook Pro (Retina, 15-inch, Early 2013)
– Android Studio 4.1.0

To get started download Android Studio for Mac and install the application.

After launching the application, you’ll be asked to set the emulator settings if your system can run the emulator in an accelerated performance mode. I like to bump up the RAM allocation slightly to at least 4 GB.

Android Emulator Mac Download

Once Android Studio is installed, you don’t actually need to create or run a project to run the emulator. At the home screen, you can select AVD Manager from the Configure Menu in the bottom right.

From this menu, you should see at least one emulator, with a green start button to run it, as well as a button to Create new emulator.

From here you can start any existing Virtual Devices that are already available to you by clicking the green play icon. After launching the device you will see it boot up on your screen, and eventually will be taken to the devices home screen.

With the emulator running, you can now access your websites running on the host machine’s localhost, on 10.0.2.2. For example, if you have a NextJS app running on http://localhost:3000, you would be able to access that on the emulator on http://10.0.2.2:3000.

From the Android Virtual Device Manager screen, click “Create Virtual Device” to bring up the Virtual Device Configuration Screen. You’ll see a number of virtual hardware devices to choose from, select one and click next.

From there, you’ll be required to select the operating system you want to install. If you don’t have the system image already available, you’ll need to download it by clicking the Download button.

Download and walk through the component installer.

Once downloaded, you’ll be asked to give your Android Virtual Device a name and can set a few more options like the default orientation. Click finish to finalize the virtual device configuration.

You should now see the newly created AVD in the Android Virtual Device Manager.

Click the green play icon to launch your newly created AVD.

Once you’ve created some Android Virutal Devices in the steps above, you may decide to launch them from the command line to save time in your workflow. In the examples below we’ll be using iTerm2, but you can use any terminal application.

First, enter the preferences by navigating to Android Studio > Preferences, and then Appearance & Behavior > System Settings > Android SDK.

From this menu we are looking for the “Android SDK Location”. Copy the location and head over to your terminal.

The emulator executable is located in the “emulator” folder and is also named “emulator”. So in my case, I want the full path to the emulator to look like:

For ease of use, we’re going to alias this in our bash_profile so we don’t need the entire path and can just type “emulator” into the command line.

Now, you can use the command emulator -list-avds to see which emulators are available to you.

Now that we have the emulator command aliased, and we can view a list of emulators. We can easily launch new emulators by running emulator -avd [EMULATOR]. For example:

Debugging with the Chrome Web Inspector

If you want to take your AVD testing and debugging a step further, you can connect it to your desktop version of Chrome and debug using the Chrome Developer Tools.

In order to do this, you must first run the Android Debug Bridge (“adb”) from the command line.

To use ADB, first ensure you have the Android SDK Platform-Tools installed. You can find this information from the Android SDK > SDK Tools menu of the Android Studio preferences.

The adb program will be in the Android SDK location under the platform-tools directory. In my case it would be found at:

Just like the editor, we’re going to alias this in our bash_profile so we don’t need the entire path and can just type “adb” into the command line.

Now you should be able to run adb in the terminal and see the program help screen. With the virtual device running, run adb devices, which will start the bridge if it’s not already running and print any devices found with their status. If its set up properly, you should see an emulator with “device” next to it.

Launch Chrome on the virtual device, and also on your host machine. On your host, navigate to chrome://inspect/#devices. You should see the emulator and an option to open a new tab from the list.

You can either open tabs on the device itself, or type the name of your host in the text input and click open. Remember your host machine localhost will be 10.0.2.2 on the AVD.

Any tabs found on the AVD will show up under the device, and you can open the Chrome Developer Tools by clicking the “inspect” link. From there, a familiar Chrome DevTools window will be available and should be connected to the browser on the Android Virtual Device.