justin
justin

Reputation: 290

Solve " Could not load OpenGLES emulation library: Could not load DLL!" for Android Emulator

There was a problem starting Android Emulator.The Error I got while starting the Android Emulator by executing the command emulator-arm @AVD_name is

Could not load OpenGLES emulation library:Could not load DLL!.

Could anyone help me to solve this problem.

Upvotes: 5

Views: 6661

Answers (5)

Mester Hassan
Mester Hassan

Reputation: 558

1- Open --> Android Virtual Device Manager

2- Click on button --> Edit

3- In --> Emulated Performance, Graphics:[Software - GlES 1.1] <-- Choose

Upvotes: 0

Cerini Pablo
Cerini Pablo

Reputation: 21

On the menu of Android Studio select :

Tools -> Android -> AVD Manager

It opens a list of the available Virtual Devices . Select the one you are experiencing this problem with . Click on the pencil ( Edit ) icon .

Click the "Show Advanced Settings" button.

Deselect the flag "Use Host GPU" under Emulated Performance.

This worked for me.

My Android Studio version is 1.5.1 .

Upvotes: 1

St&#233;phane B.
St&#233;phane B.

Reputation: 3280

I use the the BAT script below to start Android emulator on Windows system.

emulator_start.bat <AVD_FILENAME_WITHOUT_EXTENSION>

Content of emulator_start.bat file :

@echo off
set AVD_FILENAME_WITHOUT_EXTENSION=%1
title Android Emulator %AVD_FILENAME_WITHOUT_EXTENSION%
set PATH=%PATH%;%ANDROID_HOME%\tools;%ANDROID_HOME%\tools\lib;%ANDROID_HOME%\platform-tools
rem set EMULATOR_CMD=emulator
set EMULATOR_CMD=emulator-arm
%EMULATOR_CMD% -avd %AVD_FILENAME_WITHOUT_EXTENSION% -gpu on -no-boot-anim -wipe-data

Upvotes: 1

Digit
Digit

Reputation: 2113

There is a simpler solution: Use 'emulator' instead of 'emulator-arm'.

'emulator' is used to perform a few checks and modify the library load path, to ensure the GPU emulation libraries are found, among other things.

'emulator-arm' is being called by 'emulator' after this. If you want to call it directly, you will have to modify your PATH (or LD_LIBRARY_PATH) variable before doing so. Alternatively, copying the libraries to sdk/tools/ will have the same effect on Windows (but not other platforms). But all this hackery is not necessary when calling 'emulator'.

If for some reason calling 'emulator' doesn't work, please explain why. I'm curious why you would need to call 'emulator-arm' directly.

Upvotes: 4

justin
justin

Reputation: 290

At last I got how to start the Android Emulator.I think the problem in windows is that the android emulator while executing points to the sdk\tools\ directory instead of sdk\tools\lib directory as said in Android-open project Issue Tracker.

The things you have to do is:

  1. First copy all the files starting with lib and having the extension dll from the sdl\tools\lib directory into the sdk\tools\ directory.
  2. If you still can't get the emulator working after copying also place the -gpu off option in the command line while executing the command emulator-arm @AVD_name.

After doing these two things the Android Emulator started for me.

Upvotes: 9

Related Questions