IssueTracker

Note that the bug surfaced when I tried our app on android 5

I'm also seeing this problem with our library IOCipher (https://github.com/guardianproject/IOCipher).  It all builds and works fine, until I switch the test suite from targeting android-15 to android-21, then running the tests on a android-19 (4.4.4) ROM.  The NDK build uses r10d, and the IOCipher NDK build targeting android-7.

I found this workaround, which seems to work:

LOCAL_LDFLAGS += -fuse-ld=bfd

please reopen if you still see this with r12.

I'm executing the emulator from Android/sdk/tools on a Windows machine and it still fails to start.

C:\Users\Gonzalo\AppData\Local\Android\sdk\tools>emulator @Nexus_One_API_19
[7568]:ERROR:./android/qt/qt_setup.cpp:28:Qt library not found at ..\emulator\lib64\qt\lib
Could not launch '..\emulator/qemu/windows-x86_64/qemu-system-i386.exe': No such file or directory

Inside the Android/sdk/emulator folder I only have a .installer folder with a .installData containing this:

#Wed Mar 01 19:16:40 CLST 2017
class=com.android.repository.impl.installer.BasicInstaller
path=C\:\\Users\\Gonzalo\\AppData\\Local\\Temp\\PackageOperation04

Running from the {Android_SDK}/tools seems to work but it is annoying.

same here

same here...anybody got the solution

I am getting below error while trying to run from android-sdk/tools
android/avd/avd4.avd/../system-images/android-19/default/x86//system.img

This is the solution for linux

cd $(dirname $(which emulator)) && ./emulator @bla

If you use bash on macOS or linux, this function in your bashrc works great.

function emulator { cd "$(dirname "$(which emulator)")" && ./emulator "$@"; }

I found a temporary workaround as described in this link: http://jakzaprogramowac.pl/pytanie/27019,android-emulator-does-not-work-on-ubuntu-after-upgrading-android-studio-to-2-0-qt-library-not-found .

TL;DR

copy the lib and lib64 and qemu folders from your $ANDROID_SDK/emulator into $ANDROID_SDK/tools. It worked like a charm for me :)

Seeing something similar to this issue, thought I would add my 2c. It seems that the emulator command is no longer respecting environment variables or relative paths when looking for system images. Running custom emulators fails with "Not a directory: /Users/me/Library/Android/sdk//my/directory/here". It used to respect the value of ANDROID_SDK_ROOT as the prefix for emulator system images, now it seems to be hardcoded to the sdk location based on the relative location to the emulator command.

[Comment deleted]

Installing Android Emulator in SDK tools in Android Studio worked for me. I'm using macOS.

Installing Android Emulator was also the solution for me. This seems like a UI issue rather than a bug. The user should be properly informed that Android Emulator is missing and offer to install it.

Installing Android Emulator worked for me too :) I'm using android studio and using windows 8.1

Same problem for me... The emulator directory is empty, there is only a hidden folder .installation

Run in emulator folder.
 $ cd ~Android/Sdk/emulator
 $ ./emulator -list-advs
 $  api22
 $  avd_api23
 $ ./emulator @api22

Before:  whit $ emulator @api22
emulator @API22
[139733411895104]:ERROR:./android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '../emulator/qemu/linux-x86_64/qemu-system-x86_64': No such file or directory

After :D
$ ./emulator @API22
emulator: WARNING: encryption is off
warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
Your emulator is out of date, please update by launching Android Studio:
 - Start Android Studio
 - Select menu "Tools > Android > SDK Manager"
 - Click "SDK Tools" tab
 - Check "Android SDK Tools" checkbox
 - Click "OK"

if
$ ./emulator @API22
emulator: WARNING: encryption is off
emulator: ERROR: There's another emulator instance running with the current AVD 'API22'. Exiting...

I want the AVD Manager back (without having to open Android Studio).

:-(

From the EMULATOR folder /Users/pajakoo/Library/Android/sdk/emulator

run: emulator -avd <your-dev-name>

it works for me

Add path in environment variable for "sdk/emulator" folder also just like "sdk/tools". And Try emulator -avd Nexus5XAPI25_x86 it will work.

The problem is there are two emulators: one in $SDK/tools, another one in $SDK/emulator.
The one in $SDK/tools cannot start.
Place $SDK/emulator before $SDK/tools in your $PATH variable, it should fix the problem.

"Place $SDK/emulator before $SDK/tools in your $PATH variable, it should fix the problem." Confirmed, fixed it for me on Ubuntu 16.10 x64.

I solved!
Please Install Android Emulator

Installed Android Emulator 26.0.0 does not help.
Place $SDK/emulator before $SDK/tools in my .bash_profile does not help.

Only able to start the emulator by command when cd to $SDK/tools
I am using mac 10.11.16

I am updating the emulator to latest version because it inform me my version is outdated but ends up wasting time on this issue.
To Google team: Please roll out in beta before released as stable version

Same here, installing and reinstalling Android Emulator 26.0.0 does not help.

I had to quit Docker on my Mac for this to work
Ref - http://stackoverflow.com/a/36757666/906577

As someone else said, running emulator from the directory the binary is actually located in worked for me. It appears to be trying to resolve some files relative to the user's working directory that should be resolved relative to the binary's directory.

Same issues as #28. must be in $SDK/tools for it to work. just updated Android emu 26.0.0 still not helping :('

I'm also having this problem, after recently installing updates in Android Studio on my Mac....

#25 fixed the issue for me as well. Would it make sense to remove the emulator executable from tools ?

Not sure if it makes a difference but I'm using a Mac

#25 fixed the issue for me too. Ubuntu 17.04.

Fixed with changes: 188901fcdf, 68fb382430. These are merged into the next release.

Updated today to 26.0.2 patch of Android Emulator over Ubuntu OS, Android Studio 2.4 Preview 6. Starting Hardware GLES 2.0 enabled emulators from AVD broke again.

I reenabled doing this:

cd  /yoursdkpath/emulator/lib64/libstdc++$

mv libstdc++.so.6 libstdc++.so.6.bak

ln -sf /usr/lib/x86_64-linux-gnu/libstdc++.so.6  ~/Android/Sdk/emulator/lib64/libstdc++/libstdc++.so.6

#35 solution worked for me, your solution saved my job thanks!

ps: i also applied the solution of the #25.

#25 fixed the issue thanks

#26 fixed the issue thanks

i have problem of "Cannot launch AVD in emulator. Output: Could not launch 'C:\Users\Nageswar\AppData\Local\Android\Sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe': No such file or directory" what is that, how can we salve this problem can you please,

#34 says that this has been fixed, but I am still seeing it on 26.0.2.

Status "fixed" doesnt mean that it has been released. It has just been fixed in code but hasn't been published as a release.
Status "Fixed (verified)" means this fix has been released.

Nevertheless, Im struggling with this issue too on our CI, would love to see this released soon.

After update emulator to 26.1.2

[140736571958208]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/Users/ci/../emulator/qemu/darwin-x86_64/qemu-system-armel': No such file or directory

Please fix this, it is getting aggravating. People should not be required to change directory or run Android Studio (wasting lots of RAM which can be put to better use) just to boot an emulator image.

Error still persists:
output from command line

ERROR:./android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '../emulator/qemu/linux-x86_64/qemu-system-i386': No such file or directory

I ended up just making aliases in my bash_profile:

alias android-pixel22="cd $ANDROID_HOME/tools && emulator -avd Pixel_API_22"
alias android-pixel25="cd $ANDROID_HOME/tools && emulator -avd Pixel_API_25"

I copied all files from sdk >> emulator folder to tools folder
and sdk tools folder is in my system variables
then in cmd i write emulator -avd name_of_rom

I am also face this problem that is Emulator can not start

So guys,

 I tried to run virtual device , but still doesn't work.  I received the same problem mentioned before:

[4780]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ..\emulator\lib64\qt\lib:

I tried starting emulator manually. Emulator is getting launched but it responds with Description Unsuccessful. Please find the image(Error.png). And i am unable to Reset Phone. The Reset Button is not working and sometimes i am getting "Gboard has stopped"(Error1.png). Any solution for this

As of 12/25/2017. I see that you should only add below into the path to be able to launch emulator

C:\Users\Ram\AppData\Local\Android\Sdk\platform-tools C:\Users\Ram\AppData\Local\Android\Sdk\emulator.

This is after installing Android Studio 3.0 and higher.
I see that C:\Users\Ram\AppData\Local\Android\Sdk\emulator  has same thing as C:\Users\Ram\AppData\Local\Android\Sdk\tools tools.
But tools folder is missing some files, so remove tools folder from path.

You can use below emulator commands to launch emulator from command prompt:
emulator -list-avds
emulator @Pixel_2_XL_API_26 - Based on the avd that you have setup

i finally saw the problem android emulator was not installed, so i quickly checked the box and clicked on apply and it prompted to install the emulator and i hit ok. after the installation the problem was solved.

to see if your android emulator is installed on Windows go to :

Tools > Appearance & Behaviour > System Settings > Android SDK > SDK Tools

check the list of items there.

#45  fixed the issue thanks

I ended up just making aliases in my bash_profile:
alias a23_open="cd $ANDROID_HOME/emulator && emulator -avd a23"

its solved bro you need to just install android emulator

Issue is still reproducible with AS 3.0.1 with latest Mac OS

#46 it worked for me too

Windows 10
Android Studio 3.1.2

Deleted the PATH var that referenced Android\Sdk\tools and added the Android\Sdk\emulator instead

Emulator command works in command line

try to install android emulator using this command:

$ sdkmanager --install emulator

it works like charms..

Try to check "C:\Users\Admin\AppData\Local\Android\Sdk\emulator" directory there it should have some data. For me it is over 600MB.

The emulator not working is possibly because above folder is empty.

Fix:
1. Open tools->android sdk manager -> Android sdk
2. Select second tab sdk tools -> check Android emulator , version, installed/not installed.

If it is not installed then install it by marking the item from the list.

27.2.9 is current version for me on 7-Jul-2018. Emulator will start work.

Comment #51 worked for me with a charm :) Thank you.

I had bad value of $PATH:
/Users/<username>/.rvm/gems/ruby-2.4.1/bin:/Users/<username>/.rvm/gems/ruby-2.4.1@global/bin:/Users/<username>/.rvm/rubies/ruby-2.4.1/bin:/Users/<username>/bin:/usr/local/bin:/usr/local/share/android-sdk/tools:/usr/local/share/android-sdk/platform-tools:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/<username>/.rvm/bin:/Users/<username>/Library/Android/sdk/tools:/Users/<username>/Library/Android/sdk/platform-tools

When I removed /usr/local/share/android-sdk/platform-tools and /usr/local/share/android-sdk/tools I was able to launch emulator with command prompt. Hope it will help somebody.

#56 It worked for me in Ubuntu!

#57 thank you!!!!

I had the same issue on Ubuntu 18. Just now I got into my system dependencies and found that I had some mess in my Sdk's, emulators and Avd's. What I did was: removed everything I could find concerning android sdk from system, so none of the commands adb, emulator or any other worked, there were some system and android studio installations. After I just installed everything from scratch via android studio sdk manager and it all worked. I also put {PATH_TO_SDK}/emulator first in my PATH .bashrc

Try to run prompt with administrator
emulator -list-avds
emulator -no-snapshot -avd YOUR_EMULATOR_NAME

Via AVD manager in Android studio i can able to run emulator...while trying to open from Command prompt it is showing below mentioned error....can anyone plz suggest solution for this.....thnq

C:\Users\laksh>emulator -list-avds
Nexus_5X_API_28
UshaEmulator


C:\Users\laksh>emulator -avd Nexus_5X_API_28
[1716]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ..\emulator\lib64\qt\lib
Could not launch 'C:\Users\laksh\..\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe': No such file or directory

Same problem, same solution which doesn't work :(

Advice #57 worked!

Same problem, but executing the emulator command from absolute path /.../sdk/emulator/emulator it works.

Advice #25 worked for me.. Working on Win10

#25 solved the issue , windows 10