22 ~ /Android/Sdk/emulator/lib64/libstdc++/libstdc++.so. 6 ~ /Android/Sdk/emulator/lib64/libstdc++ /libstdc++.so.6 deb, extract the files/binaries from inside it (the 2 binaries are in a folder named 'lib') and manuallly copy them on the recommended path.Ĭreate a simlink to the lib distributed with Ubuntu, which already is 6.0.22 version cd ~ /Android/Sdk/emulator/lib64/libstdc++ / Rm the previous non working Google's libs in /yoursdkpàth/emulator/lib64/libstdc++ĭownload and extract libs from libstdc++ official package in /yoursdkpàth/emulator/lib64/libstdc++ĭon't try to install the. They're distributing 6.0.18 version, but i found that the working one is 6.0.22.ĮDIT: There are reports that 6.0.21 version of libstdc++ works as well as 6.0.22. The real problem, at least over Ubuntu 16.10 and 17.04 and Andoid Studio 2.4 Preview 7 (but could happen with any Debian derivative and previous versions of Android Studio), is that Google is distributing a non working libstdc++ library with the emulator tools. In my particular case, I also had old values for $ANDROID_HOME that I had to clear out. NOTE: For most Mac users, you can edit your ~/.bash_profile to change these settings and then run $source ~/.bash_profile to load the updates. $ANDROID_SDK_ROOT/tools in your $PATH variable, it should fix the The one in $ANDROID_SDK_ROOT/toolsĬannot start.

The problem is there are two emulators: one in I noticed I periodically was seeing the console error 'Your emulator is out of date, please update by launching Android Studio:' so I decided to check: $ which emulator

UPDATE: Figured out the configuration problem! I hope someone else will be able to figure out what broke in the configuration. It's not ideal, but this was blocking my development so I had to get the emulator up and running again. SOURCE: /sdk/system-images/android-25/google_apis/x86/ĭESTINATION: ~/.android/avd/Pixel_XL_API_25.avd/Īfter that the emulator started right up. Android API 25 x86 w/ Google APIs), Android Emulator 25.3.1, and re-creating the AVD but nothing worked.įinally as a workaround, I just copied all of the system files from the SDK system images directory into the AVD directory:Įxample: Pixel XL (Android API 25 x86 w/ Google APIs) I tried re-installing the system image (e.g. You can get more information if you run emulator with the -verbose flag. I can't figure out what's causing the configuration problem but I did figure out a workaround.įirst, I tried to launch the emulator from the command line: $ emulator ERROR: This AVD 's configuration is missing a kernel file! Please ensure the file 'kernel-ranchu' is in the same location as your system image.Įmulator: ERROR: ANDROID_SDK_ROOT is defined (/sdk) but cannot find kernel file in /sdk/system-images/ sub directories

I ran into the same problem after upgrading.

Can't start android emulator on mac