05-10-2021

Avd Manager Mac

Question or issue on macOS:

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 don’t have an idea why.

Studio

Crash log: http://pastebin.com/04MjCqaS

Terminal log in verbose mode: http://pastebin.com/L6y6rUr0

4# Andyroid Emulator. It is the trending Mac Android emulator which liked by the most. With open GL hardware support, this emulator is the one that is too easy to install. With the help of Andyroid Emulator, the phone can be turned into a remote control for gaming. With quick customer support, you will never find yourself deserted. No emulators at this point. IntelliJ has some lags in performance on M1 (because it is not native, and Intel built), but feels pretty usable. Yes, Android Studio and the M1 emulator are working. However keep in mind that sometimes Android Studio will start pushing to Swap massively about 1 hour of work in. These are the best password managers for Mac as rated by our top cybersecurity experts. Compare plans, find deals, and secure your logins now.

If you have installed Android Studio on your Mac or PC then you have access to the AVD Manager. This program permits you to create and run different Android Virtual Devices, and if you have followed the Android Setup Guide and used a custom install for Android Studio then it should be installed and ready to use, so you can skip down to the. When I try to launch Android emulator, it crashes on Mac OS X. It was working some time. I moved to IntelliJ and I’m able to launch AVD manager but none.

How to solve this problem?

Solution no. 1:

Same issue here, I’m running a mac mini with 8GB of RAM and MacOS Lion. It used to work with the old AVD with some random crashes every now and then but since the last update to APi 17 it’s a pain in the neck.

The ADT bundle doesn’t work at all. After tweaking the memory limits on eclipse.ini file it throws random memory errors. Also it’s not been able to download and install the m2e (maven to eclipse) plugin.

I moved to IntelliJ and I’m able to launch AVD manager but none of the “old” created devices work. If I create a new one and I launch it it works until I close it, then I have to restart the Mac and create a new device. Also it randomly shows errors when I want to delete those old created virtual devices.

Also the DDMS fails to start. I launch it, shows its icon on the Dock but it doesn’t respond until I force close.
What a Nightmare.

** EDIT **
I found at android dev bug tracker this issue when you’re running 2 screens: here

This is happening to me with the android emulator. I solved it like this:
cd ~/.android/avd
ls *.avd

Now choose the emulator that is crashing and

And now reset window.x, that’s window.x=0
exit and run the emulator.

If you move and close the emulator to the secondary screen it will crash the next time you want to run it.

Solution no. 2:

Kill your Docker process

One problem I have seen multiple time is with Docker. Android Emulator crashes when Docker is running on Mac.

Solution no. 3:

I was following the PhoneGap “Getting Started” guide for Android, and when I got to “Deploy to Emulator,” after I created a new AVD, my Mac would crash and reboot. I stumbled on this thread, but thought it worth mentioning that what actually solved the problem for me was an Intel patch for the Hardware Accelerated Execution Manager located here: http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager

Solution no. 4:

This is because Android SDK use some deprecated libraries of Mac OS X. I have the same problem (sometimes even kernel panic) before I start use android device. Maybe in future versions of Android SDK this problem will be fixed.

Solution no. 5:

I just updated the Android SDK manager to the latest Android 4.2 (API 17) level updates, and now all my old AVD’s crash. The newly created one using API 17 works, however.

Solution no. 6:

I have the same issue. You can try to create a new AVD with the appropriate API level. I am able to run these the first time(s) after creating. That seems to be a memory error.

My AVDs are able to run the first time after reboot. After this they keeps crashing.

Solution no. 7:

I had the same issue using mac 10.6 and 2 monitors one through a usb adapter to HDMI.
I have tried all of this suggestions and nothing did work.
I ended up creating a new user into my mac and with the same android sdk and same eclipse with a new workspace did work.

I’m not sure whether just creating a new workspace would do the tweak, I didn’t try it.
for those who come across to this annoy issue worth to try it before switch to a new account.

Solution no. 8:

You can delete your emulators from ~/.android/avd

Then create new emulators.

Hope this helps!

If you've been looking for a way to develop your Xamarin Android apps in a Parallels Desktop Windows VM, but run the app in an Android emulator on your Mac, this post is an attempt to distill the information from across multiple sites to get you started.

Mac

Many thanks to James Montemagno for pointing me to Paul Batum's post on the Xamarin forum.

My Configuration

  • Intel MBP running OS X Mavericks
  • Parallels Desktop running a Windows 8 VM

Set up your Mac

1. Download & Install the Android SDK

Nothing can get done until the Android SDK is installed, so let's start there.

Install the Android SDK

You should end up with an SDK directory somewhere on your Mac with subdirectories like: extras, platform tools, tools, etc.

Yeah? -- Okay. Next.

2. Install the Intel HAXM

Intel HAXM - What?

Intel Hardware Accelerated Execution Manager. In short, it speeds up Android app emulation on Intel host machines. This step is necessary if you plan on creating custom AVDs that leverage the much faster Intel x86 images.

Install the Intel OS X HAXM Zip

Do you use OS X Mavericks + Parallels Desktop 9 ?

Avd Manager Mac M1

Install the OS X 10.9 HAXM Hotfix

If you don't do this, when you launch an Intel x86 emulator image, your entire computer will freeze up forcing you to perform a hard reboot. No one wants that.

3. Configure your Mac for SSH sharing

In OS X Go To:
System Preferences > Sharing > Enable Remote Login

Leave the other options set to their defaults.

4. Start the Android emulator

Several AVDs came pre-configured when you installed the Android SDK. For the sake of this tutorial, we'll use one of those devices which use ARM images. To view the configured devices, start the AVD Manager:

  • Open a command line

  • Navigate to the tools directory of your Android SDK: yourandroidsdkdirectory/tools

  • Enter the following command:

    ./android avd

  • The AVD Manager will open

Start an Android device:

  • select a device with a green check
  • press Start...
  • the Launch Options dialog will appear. Press Launch

Earlier, we installed HAXM which allows the use of the Intel x86 images which run much faster than their ARM counterparts. If you'd like to try those out: open the SDK Manager, download the x86 images, then configure devices in the AVD Manager to use the x86 images instead of the ARM images.

  • Open a command line

  • Navigate to the tools directory of your Android SDK: yourandroidsdkdirectory/tools

  • Enter the following command:

    ./android

  • download the x86 images

  • edit a device in the AVD Manager to use an x86 image instead of an ARM image

5. Kill the ADB Server

  • Open a command line

  • Navigate to the platform-tools directory of your Android SDK: yourandroidsdkdirectory/platform-tools

  • Enter the following command:

    ./adb kill-server

Okay! -- Your Mac is ready.

Set up you Windows VM

1. Start your Windows VM in Parallels Desktop

2. Download and install PuTTY SSH Client

Install the PuTTY SSH Client

3. Create a new connection to your Mac

Let's connect to the Mac.

  • Start PuTTY SSH Client
  • Select Session from the Category panel on the left
  • In the Host Name (or IP Address) field, enter the IP Address of you Mac (found at: System Preferences > Sharing)
  • Leave the Port set to its default (should be 22)
  • Make sure SSH is selected under Protocol

4. Configure port forwarding

Select Connection > SSH > Tunnels from the Category panel on the left side of the PuTTY SSH Client. From here add two forwarding configurations.

First

  • Source Port: 5555
  • Destination: localhost:5555

Second

  • Source Port: 5554

  • Destination: localhost:5554

  • Click on Open

You will be presented with a command line console. When prompted, enter your Mac admin username and password to open a connection from your Windows VM to OS X.

5. Kill then Start the ADB Server

Macos Avd Manager Unable To Locate Adb

  • Open a command line

  • Navigate to the platform-tools directory of your Android SDK: yourandroidsdkdirectory/platform-tools

  • Enter the following command:

    adb.exe kill-server

  • Then enter the following command:

    adb.exe start-server

  • Confirm that your Mac emulator device has been picked up by entering the following command:

    adb.exe devices

  • You should see a device listed something like: emulator-5554

6. Open a Xamarin Android project

Install Avd Manager Mac

Now for the big test!

Avd Manager Mac Download

Launch your Xamarin IDE of choice and open a Xamarin Android project. Once the project initializes, you should see your already running Mac emulator listed in the device dropdown.

And that's it! -- You can debug all day long from Parallels over to your Mac.

The Bonus Round - Genymotion Emulator

The AVD emulator that comes with the Android SDK is fine, but it could be better. Enter Genymotion.

The Genymotion emulator is noticably faster, but it requires some baggage: VirtualBox - which doesn't play well with Parallels Desktop 9 out of the box.

Install Avd Mac

[Detailed tutorial coming soon]