Could not launch './qemu/linux-x86_64/qemu-system-i386': No such file or directory

Question

With 25rc1 of the SDK tools I am having a problem when starting the emulators from $PATH

➜  ~  which emulator
/home/ligi/bin/android-sdk/tools/emulator
➜  ~  emulator @M 
Could not launch './qemu/linux-x86_64/qemu-system-i386': No such file or directory
➜  ~  /home/ligi/bin/android-sdk/tools/emulator @M
console on port 5554, ADB on port 5555

Anyone knows a workaround? I could write a script to start emulators and cd in tools before but perhaps there is a better solution.

you are facing the consequences of **`rc`** in the version number ... — Selvin, Dec 14 '15 at 16:35
... and I will recommend [to fill the bug report,](http://tools.android.com/filing-bugs/emulator) write the script and forget about this (unless you would face the same bug in next "RC" release) — Selvin, Dec 14 '15 at 16:44
I think it is good style to sometimes consult stackoverflow before filing an issue — ligi, Dec 14 '15 at 17:02
I would rather say the other one is a duplicate of this one - look at the dates ;-) — ligi, Aug 18 '18 at 11:48

score 52 · Accepted Answer · edited Feb 13 '19 at 10:42

52

I encounter this one in android studio 2.3 which use new path for the emulator so try the following:

do not use emulator executable in the: sdk-path/tools/ directory but instead use the one found in the : sdk-path/emulator/

and also remove or rename the emulator found in the sdk-path/tools directory.

and because android sdk shipped with it's own libstdc++.so.6 you need to do the following to avoid the libGL error:

cd $ANDROID_HOME/emulator/lib64/libstdc++
mv libstdc++.so.6 libstdc++.so.6.bak
ln -s /usr/lib64/libstdc++.so.6 $ANDROID_HOME/emulator/lib64/libstdc++

edited Feb 13 '19 at 10:42

NickUnuchek

11,794
12
98
138

answered Apr 01 '17 at 08:38

Mustafa R.Mahdi

744
7
11

22

Launching `sdk-path/emulator/emulator` helped me without overwriting libstdc++. So I just added `$ANDROID_HOME/emulator` to $PATH before `$ANDROID_HOME – ENargit Apr 11 '17 at 14:47
13

I went for an alias. `alias emulator=${ANDROID_HOME}/emulator/emulator`. – kim3er Nov 30 '17 at 13:34
2

@kim3er Thanks. Add alias into ~/.zshrc or ~/.bashrc worked for me. – Long Nguyen May 29 '18 at 02:00
In the sdk path I do not found any emulator and it is only available inside the sdk/tools folder. What changes we need to make it – Ashok kumar Ganesan Jun 22 '20 at 03:44

score 25 · Answer 2 · edited Mar 26 '17 at 20:07

25

Try this, it work for me on Windows.

Tools -> Android -> SDK Manager -> SDK Tools -> Android Emulator

Then click on Apply.

edited Mar 26 '17 at 20:07

creativecreatorormaybenot

114,516
58
291
402

answered Mar 26 '17 at 13:50

Iaoceot

384
4
9

score 11 · Answer 3 · answered May 26 '17 at 19:43

11

If you're launching the emulator from command-line, try setting the current directory to your android sdk "tools" folder first.

This works for me as a workaround:

pushd ${ANDROID_HOME}/tools
emulator -avd ${EMULATOR_NAME} -wipe-data&
popd

answered May 26 '17 at 19:43

user597159

185
1
4

score 8 · Answer 4 · edited May 30 '18 at 11:50

8

This one works for me on MacOS Sierra.

Preference -> Appearance & Behavior -> System Settings -> Android SDK -> SDK Tools (tab)

Tick on Android Emulator and Apply

edited May 30 '18 at 11:50

Community

1
1

answered Jun 17 '17 at 16:39

Neo Nguyen

119
1
3

This was the culprit for me – X.Y. Nov 14 '18 at 19:55
Wow! I had installed emulator and it was now found it Android Emulator is unchecked – muhammad tayyab Mar 21 '19 at 17:47

Manoj Shrestha · Answer 5 · 2018-12-16T18:13:06.037

5

I had the Android Emulator up to date under SDK Tools. But I was still getting the error. Adding the following line to ~/.bash_profile solved the problem for me:

PATH=$ANDROID_HOME/emulator:$PATH

edited Dec 16 '18 at 18:13

answered Dec 16 '18 at 18:08

Manoj Shrestha

4,246
5
47
67

This actually worked perfectly. – JeremyF Feb 19 '22 at 17:36

score 2 · Answer 6 · answered Feb 18 '20 at 15:16

In Ubuntu 19.10!

With the environment variables already configured ($ANDROID_HOME), you should be able to list the AVDs, but if you are unable to start the AVD, do the following:

# Check the AVD target name

emulator -list-avds

# But to start do:

$ANDROID_HOME/emulator/emulator @avd_name

or

/home/$USER/Android/Sdk/emulator/emulator @avd_name

score 0 · Answer 7 · answered Aug 22 '16 at 13:36

0

Make sure that ANDROID_EMULATOR_FORCE_32BIT is not set in your environment

answered Aug 22 '16 at 13:36

Steve Bradshaw

827
7
10

score 0 · Answer 8 · answered Mar 26 '17 at 14:24

0

In Virtual device configuration, set Emulated performance to Software GLES 2.0

answered Mar 26 '17 at 14:24

rexxar

1,671
1
21
27

score 0 · Answer 9 · answered Jan 17 '19 at 15:15

yah my dns is blocked in the region i am visiting so i was searching for a way to add dns servers and start emulator at command line. default emulator in path did not work. instead go to your android SDK home and you'll see a emulator in there. use that emulator executable like this:

emulator -avd Nexus_5X_API_26 -dns-server 8.8.8.8,208.67.222.222,199.85.126.10,8.8.4.4

i think you can give 4 dns's. anyway this is a side note. back to the issue:

people here did not mention much that you need the -avd flag with it. wanted to point that out.

score 0 · Answer 10 · edited Nov 29 '19 at 06:40

0

Do not use $ANDROID_HOME/tools/emulator, it will cause error when you launch every time unless you change dir.

There is a another emulator in $ANDROID_HOME/emulator.It is a good choice

edited Nov 29 '19 at 06:40

Angel F Syrus

1,984
8
23
43

answered Nov 29 '19 at 05:11

LitileXueZha

512
6
11

Could not launch './qemu/linux-x86_64/qemu-system-i386': No such file or directory

10 Answers10

Linked