When I am try to open my android emulator, getting below error
distrib/android-emugl//host/libs/Translator/GLES_V2//GLESv2Imp.cpp:glAttachShader:187 error 0x501
distrib/android-emugl//host/libs/Translator/GLES_V2//GLESv2Imp.cpp:glAttachShader:187 error 0x501
TextureDraw: Could not create/link program:
creating window 79 106 321 535
emulator: emulator window was out of view and was recentered
emulator: UpdateChecker: skipped version check
draw: no program
Emulator details:
API 17
CPU armeabi-v7a
RAM - 746 MB
I have core 2 duo 1.4 GHz Dell Inspiron system
When I try to install HAX it says my system does not support Virtualization. I tried to start it from BIOS but I guess my system doesn't have it.
After trying many different things this is what finally worked for me.
Delete all existing AVDs
Uninstall Intel HAXM
Create a new AVD and it will make you install HAXM
Create a new AVD
Worked for following config:
Name: Nexus_5X_API_19 CPU/ABI: Google APIs (x86 System Image) Intel Atom (x86) Path: C:\Android\.android\avd\Nexus_5X_API_19.avd Target: google_apis_x86 [Google APIs (x86 System Image)] (API level 19) Skin: nexus_5x SD Card: 100M hw.dPad: no
However, similar config for API 21 still getting errors.
Same things happen with me when i format my PC and after install OS and install the Android Studio. I have tried #farrukh najmi answer and i have to extends the some more information on it.
1] Delete the avd from .../User/.android/avd/Nexus_5_API_26.avd folder and file
2] Restart android studio.
3] Create new AVD.
and start that new AVD and its work form me. I hope this information will help some one
My suggest is to have a look at Genymotion, it will offers you a better experience.
Related
Im trying to run an Android Emulator on Android Studio with Graphics: Hardware-gles 2.0, but when i turn it on, Android Studio shows me the following message:
But, when i set graphics: Software-gles 2.0 it works fine.
I would like to use hardware acceleration, but I am willing to work with software-GLES 2.0 if necessary.
My computers specs:
AMD ryzen 7 2700x (Hyper-V ON, SVN ON)
NVIDA 1660 super Gigabyte OC
16 GB RAM DDR4
Windows 10 21H2 64 bits
Motherboard is ASUS ROG-STRIX b-450f
Adittional info:
I have already updated the emulator and every option in the SDK manager
apparently, it does work correctly with API 28 devices, but not 29 or 30
I have tried to run the emulator via powershell, and this is the output:
PS C:\Users\andjo\AppData\Local\Android\Sdk\emulator> ./emulator -avd Pixel_XL_API_29
INFO | Android emulator version 30.9.5.0 (build_id 7820599) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO | added library vulkan-1.dll
Thank you for your attention!
I tried to start AVDs, but I always get following error:
Emulator: Process finished with exit code -1073741511 (0xC0000139)
I tried creating new AVDs and tried to switch usage of "Emulator performance" between "automatic, "hardware" and "software", but nothing helps, I always get the result from above.
The error comes instantly when I try to start an AVD.
Any ideas what could cause this? I think this issue came with the update to android studio 3.0...
Edit - Environment:
Windows 10 (high end business notebook, dell precisison 7510)
Android Studio 3.0
SDK Tools:
Android Emulator 26.1.4: installed
Intel x86 Emulator Accelerator (HAXM installer): installed
What I tried
deleted the complete Android SDK (SDK only, without android studio) and installed it again (without success).
tried using an emulator with auto/hardware/software graphics setting => same exception in every case
updated intel and nvidia driver (it may be related to this, as there exist driver problems with my notebook), but did not help either
deleted virtual device and created a new one => did not help either
Additional informations
Tried to start the emulator with "emulator #Name_of_AVD -verbose" from the command line, this gives me following informations (manually translated, so may not be 100% accurate):
Popup window with following:
Title: qemu-system-i386.exe - Entry point not found
Text: The procedure entry point "_Z4endlR11QTextStream" was not found in DLL "M:\AndroidSDK\emulator\lib64\qt\lib\Qt5Svg.dll".
Popup window with following:
Title: qemu-system-i386.exe - Entry point not found
Text: The procedure entry point "_Z11qt_assert_xPKcS0_S0_i" was not found in DLL "M:\AndroidSDK\emulator\qemu\windows-x86_64\qemu-system-i386.exe".
Complete console output:
emulator:Android emulator version 27.0.2.0 (build_id 4498654) (CL:f388734068bae38c6115263feea33c68eed531fe)
emulator:Found AVD name 'Nexus_5_API_25'
emulator:Found AVD target architecture: x86
emulator:argv[0]: 'emulator.exe'; program directory: 'M:\AndroidSDK\emulator'
emulator: Found directory: M:\AndroidSDK/system-images\android-25\google_apis_playstore\x86\
emulator:Probing for M:\AndroidSDK/system-images\android-25\google_apis_playstore\x86\/kernel-ranchu: file exists
emulator:Auto-config: -engine qemu2 (based on configuration)
emulator: Found directory: M:\AndroidSDK/system-images\android-25\google_apis_playstore\x86\
emulator:emuDirName: 'M:\AndroidSDK\emulator'
emulator:try dir M:\AndroidSDK\emulator
emulator:Trying emulator path 'M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe'
emulator:Found target-specific 64-bit emulator binary: M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe
emulator:Adding library search path: 'M:\AndroidSDK\emulator/lib64'
emulator:Adding library search path: 'M:\AndroidSDK\emulator/lib64/gles_swiftshader'
emulator:Adding library search path: 'M:\AndroidSDK\emulator/lib64/gles_angle'
emulator:Adding library search path: 'M:\AndroidSDK\emulator/lib64/gles_angle9'
emulator:Adding library search path: 'M:\AndroidSDK\emulator/lib64/gles_angle11'
emulator: Adding library search path for Qt: 'M:\AndroidSDK\emulator\lib64\qt\lib'
emulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=M:\AndroidSDK\emulator\lib64\qt\plugins
emulator:Quoted param: [M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe]
emulator:Quoted param: [#Nexus_5_API_25]
emulator:Quoted param: [-verbose]
emulator: Running :M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe
emulator: qemu backend: argv[00] = "M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe"
emulator: qemu backend: argv[01] = "#Nexus_5_API_25"
emulator: qemu backend: argv[02] = "-verbose"
emulator: Concatenated backend parameters:
M:\AndroidSDK\emulator/qemu/windows-x86_64/qemu-system-i386.exe #Nexus_5_API_25 -verbose
Emulator settings:
AvdId=Nexus_5_API_25
PlayStore.enabled=true
abi.type=x86
avd.ini.displayname=Nexus 5 API 25
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.forceColdBoot=no
hw.accelerometer=yes
hw.audioInput=yes
hw.battery=yes
hw.camera.back=emulated
hw.camera.front=emulated
hw.cpu.arch=x86
hw.cpu.ncore=1
hw.dPad=no
hw.device.hash2=MD5:1c925b9117dd9f33c5128dac289a0d68
hw.device.manufacturer=Google
hw.device.name=Nexus 5
hw.gps=yes
hw.gpu.enabled=yes
hw.gpu.mode=auto
hw.initialOrientation=Portrait
hw.keyboard=yes
hw.lcd.density=480
hw.lcd.height=1920
hw.lcd.width=1080
hw.mainKeys=no
hw.ramSize=1536
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images\android-25\google_apis_playstore\x86\
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=100M
showDeviceFrame=yes
skin.dynamic=yes
skin.name=nexus_5
skin.path=M:\AndroidSDK\skins\nexus_5
tag.display=Google Play
tag.id=google_apis_playstore
vm.heapSize=128
You've to check:
Your size on disk is not full - this's often happen due to creation of some virtual devices that are unused in AVD Manager (So delete unused if any)
The RAM size of Emulator should not minimum as your requirements
In work around steps (tested) :
Restart your Android Studio
Create new device in your AVD Manager
Increase the RAM size of the Emulator
Creating new AVD.
also
Get Android Studio 3.1 if 3.0 is still giving the issue, 3.1 has new DEX compiler D8 where as 3.0 has DX.
as CodeBulls said above instant run may also be an issue
As per my understanding. It will be bst to use Genymotion as compared to AVD. Link is HERE
Download Genymotion.
Download Virtual Box if its not with Genymotion.
Choose Any type device for testing in Android.
NOTE : At Least 4 GB RAM is required to use Both Android Studio and Genymotion.
By Applying some zip files you can also use Genymotion to test for Google Map testing and also you will be able to use Google Play Services
Just thinking of new features Multi-dex or Instant App Settings are messing up with your project. One last try:
Disable Instant Run
To disable Instant Run:
Open the Settings or Preferences dialog. Navigate to Build, Execution,
Deployment > Instant Run. Uncheck the box next to Enable Instant Run.
Ignore if you feel this is inappropriate.
The exit code -1073741511 (0xC0000139) Stands for Some Error with C or C++ Dependency File. That is Some DLL Files ae Missing For The Emulator.
So Update Android Emulator From SDK Tools
Update and Instal Google play Intel Atom x86 System Image for the SDK Platform which is Using to Run The Emulator (API 25).
Hope This Will Help You to Resolve Your Problem
Hi please check below things into your notebook.
This happens when you upgrade your windows and hyper-v virtual machine's configurations are not updated alongside.
Open Hyper-V Manager app (in windows 10) > choose your machine that's giving erros > on the right, click 'upgrade configuration' and choose 'upgrade'.
That should update your Virtual Machine configuration for that windows 10 phone emulator and the emulator should work fine.
This problem occurred on both of my laptops and doing this fixed it.
if your problem is still not solved then please follow below link it helps you.
http://www.itwriting.com/blog/9371-how-to-run-android-studio-on-windows-without-disabling-hyper-v.html
hope this helps you try it.
Cannot launch AVD in emulator.
Output:
emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored.
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAXM must be updated (version 1.1.1 < 6.0.1).?
[PS I have installed Intel 86 emulator accelerator(HAXM installer) 6.2]
Install HAXM and setup as detailed in the link below:
https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows
The Alternate Solution could be the Genymotion for personal use
https://www.genymotion.com/fun-zone/
you can use genymotion for your emulator
I am a newbie to android development and am running Ubuntu Linux with an AMD cpu. I installed Android Studio, JDK, SDK, etc, and have been trying to run the emulator. However, whenever I try launching the emulator, it stays a black screen. The message I repeatedly get in terminal is
WARN - run.EmulatorConnectionListener - Emulator not ready yet, dev.bootcomplete = null
I have tried waiting for a while, I have tried updating it, I have tried different APIs, I have tried setting emulated performance to software, and everything else I could find online. Help would be greatly appreciated!
Specs:
Ubuntu 16.04 LTS
Android Studio 2.3.3
Radeon R9 270x 4gb
AMD FX4100
32g ram
SVM is enabled in BIOS
This happened to me recently (emulator with black screen, with all AVDs, even those which worked previously), maybe after some system or Android SDK updates.
How I fixed it:
delete whole .android directory (is in your home directory) - backup this directory before deleting (it contains your AVDs, your debug signing key or other things you might wish to return to later) - yes, this was the thing that really helped
create new AVD - you have to do this after deleting that .android directory (it did not work if I copied backed up AVD back there)
For reference, here is AVD configuration which works for me now (created directly using Android SDK, not using the wizard in Android Studio):
Device: Nexus One (3.7", 480 x 800: hdpi)
Target: Android 7.0 - API Level 24
CPU/ABI: Intel Atom (x86_64)
Keyboard: [x] Hardware keyboard present
Skin: Skin with dynamic hardware controls
Front Camera: None
Back Camera: None
RAM: 1024
VM Heap: 64
Internal Storage: 200 MiB
SD Card: (empty)
[ ] Snapshot (unchecked)
[ ] Use Host GPU (unchecked)
Problem:
I'm using only command line tools. AVD just worked fine some time ago. Now with various configurations I get only "Starting emulator for AVD..." which simply closes without any error messages and leaving emulator.exe in Task Manager for eternity.
What I've tried:
Various devices, API's, RAM above and below 768, with/without Host
GPU etc;
Reinstall Java;
Reinstall Android SDK;
Run emulator from command line just launches emulator.exe without any errors;
Delete .android folder in User's folder;
Set ANDROID_SDK_HOME variable;
Run SDK Manager.exe/AVD Manager.exe with/without elevated Admin rights;
verbose key gives me the following log:
emulator:Found AVD name 'jkll'
emulator:Found AVD target architecture: arm
emulator:Auto-config: -engine classic (arm default)
emulator:Looking for emulator-arm to emulate 'arm' CPU
emulator:Probing program: C:\Soft\Android\android-sdk\tools/emulator-arm.exe
emulator:return result: C:\Soft\Android\android-sdk\tools/emulator-arm.exe
emulator:Found target-specific 32-bit emulator binary: C:\Soft\Android\android-sdk\tools/emulator-arm.exe
emulator:Adding library search path: 'C:\Soft\Android\android-sdk\tools/lib'
emulator: Found directory: C:\Soft\Android\android-sdk/add-ons\addon-google_apis-google-17\images\armeabi-v7a\
emulator: Found directory: C:\Soft\Android\android-sdk/add-ons\addon-google_apis-google-17\images\armeabi-v7a\
Configuration I am working on:
Windows 10 x64
Android SDK Manager 25.1.1
Java JDK 8 Update 91
i5 CPU with 24GB of RAM
Any suggestions? TY.
I tried all the mentioned solutions. But strangely, I reduced my windows 10 laptop's resolution (from 3840 x 2160 to 1360 x 768) and it worked.
With your verbose I found you are using arm architecture devices.As you are using i5 processor,Windows10 x64 I would Suggest you to use x86 or x86-64 architecture for your devices for this you have to Install Intel x86 Emulator Accelerator (HAXM) from SDkManager.
Hope this helps let me know.
After changed the CPU of my computer and updated sdk, I encounter this problem too.
Now I temporarily solve the problem emulator-x86 I get an error about missing Qt5Core.dll, Qt5Widgets.dll and Qt5Gui.dl:
copy *.dll files in sdk\tools\lib\qt\lib to sdk\tools where the emulator-x86.exe in.