I followed this tutorial to create HelloWorld Android app.
I was able to start the emulator from eclipse.
But nothing seems to happen except this Android logo keeps flashing on.
Has anyone faced this issue ?
You'd better wait about 10-15 (it depends on your computer). But if it doesn't work, try in command prompt:
adb kill-server
adb start-server
If adb is not found, then you should move your directory to the folder, where adb.exe is located, for me it is
C:\Users\Andranik\android-sdks\platform-tools, therefore:
cd C:\Users\Andranik\android-sdks\platform-tools and after this execute upper commands.
This helps me.
It's working.. It is simply super slow ;)
Keep waiting a while longer and it will boot eventually. It helps to choose smaller devices with less ram.
Just a heads up, loading devices like tablets or the newest phones can easily take you 20-30 minutes.
If you planned not to use Google API as target of your emulator then u can use Intel x86 Hardware Accelerator(HAXM). Open your SDK manager then install Extras-->Intel x86 Hardware Accelerator(HAXM).Install it from
sdk_path\extras\intel\Hardware_Accelerated_Execution_Manager\IntelHaxm.exe (Windows)
Then on your emulator configuration choose Intel Atom (x86) as CPU/ABI rather than ARM.
Additionally you can set more ram to your AVD and check Use host GPU to speed up your emulator.
Related
This might seem to be a duplicate of it seems too many emulator instances are running on this machine. Aborting but that question was asked 5 years ago and nothing in the answers to it have helped me. I really think this is a different situation entirely.
I'm doing something very simple. I installed Visual Studio 2019 with Xamarin and the Android emulator.
I try to start the emulator from the command line and I get...
C:\Program Files (x86)\Android\android-sdk\emulator>emulator.EXE -no-boot-anim -avd VisualStudio_android-25_x86_phone -prop monodroid.avdname=VisualStudio_android-25_x86_phone
Windows Hypervisor Platform accelerator is operational
emulator: ERROR: It seems too many emulator instances are running on this machine. Aborting.
If I add the -verbose switch I get a huge list of messages, none of which seem relevant so I haven't included them.
This is what I know:
Windows Hyper Visor and the Platform features are enabled.
There are no other emulators active on the machine. Ports 5554, etc are not used.
HAXM acceleration is not enabled.
I have plenty of memory and disk on this machine and the emulator is configured for 512MB of memory
Genymotion emulators are not an option...I need to use Hyper V.
Windows version 10.0.17763.678
All patches to Android tools installed.
No special AV installed. Using Windows Defender.
Tried disabling firewall briefly. No help. I've never had any issue with firewall and local machine traffic.
Any ideas?
Ok...I got the emulator running. I'm really not sure what was wrong. I've spent a few days uninstalling, reinstalling, updating and finally the thing is running. To anyone else who has this issue...I feel your pain.
Here are some suggestions:
Get the code running on an actual physical phone. This worked straight away for me. This gave me some confidence that there was nothing wrong with the code or deployment.
Install and run the emulator on another dev box. Again this worked straight away. This gave me confidence there was nothing wrong with the dev box configuration that inherently prevented the emulator from running. Now I could put dev boxes side by side and investigate the divergent behavior. Did not discover any smoking guns this way, but again it built confidence.
Start the emulator directly from the command line using something like this...
c:\Program Files (x86)\Android\android-sdk\emulator>emulator -partition-size 512 -no-boot-anim -verbose -feature WindowsHypervisorPlatform -avd Android_Accelerated_x86_Nougat -prop monodroid.avdname=Android_Accelerated_x86_Nougat
Reboot/restart often. What I failed to detail in my original post is that I am using Xamarin. Long time users of Xamarin know that this stuff is really brittle. It has gotten a lot better in recent years, but this latest experience shows that it is still very tempermental and problems often disappear after restarting VS or rebooting your machine. Really demoralizing.
Good luck!
I have faced the same problem, i disabled the application control from the antivirus software i use and the problem solved the emulator started working properly.The port that the emulator uses is restricted by the application control feature that is enabled in antivirus software so try disabling it and relaunch the emulator.
I turned off Bluetooth in Windows 10 notification area and that helped me.
https://i.stack.imgur.com/7Qo1t.png
I just solved this by turning off windows hypervisor platform in turn windows features on off and restart your computer. When emulator works normally turn on it again.
Happy coding!
It seems, it takes place always with Intel x86 image. But my aim of this setting was using Inter HAXM.
I left emulator running on the whole night, but in the morning it still was booting
If I use arm, it works but I want to try HAXM
Any ideas?
It is just very slow, I recommend instead using Genymotion, but if you want to give a try fixing the speed take a look at this great topic: Why is the Android emulator so slow? How can we speed up the Android emulator?
I am pretty sure you will find your answer there.
What are ur configurations? Using host gpu sometime makes it work
Did you get the message
"HAX is working and emulator runs in fast virt mode"
If not, are you sure you installed HAXM? If you just flag it in the SDK Manager, it's not automatically installed.
To verify if HAXM is installed and running use these commands:
Windows (CMD):
sc query intelhaxm
Mac (Terminal):
kextstat | grep intel
You either get a response like this (Mac):
131 0 0xffffff7f8301d000 0x14000 0x14000 com.intel.kext.intelhaxm (1) <7 5 4 3 1>
Or if it's not working, no response.
The installer haxm installer is located in your Android SDK folder
android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager
All the information can be found here:
Windows:
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Mac:
https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x
When I run it from the SDK manager, the loading process works, but once it is done, a flash of the emulator appears then quickly disappears.
Sometimes after it loads, nothing happens.
At the worst when it loads, I get the "too many emulator instances are running on this machine. Aborting" message.
I want to start making apps, but this seems to be the only thing stopping me!
I had already turned off Windows Firewall.
pl'z, give me solution
Eclipse Indigo; r12, Windows 7 (64)
The Android emulator uses loopback ports (5554, 5556, etc) to communicate with the external ADB. If it can't do so, it assumes that other emulator instances are occupying these ports.
Failure to do so can be because:
A) Your ports are occupied? Try netstat -an | grep 5554
B) Your loopback interface is not configured - You said you're on Windows - Make sure Windows Loopback is configured (try pinging yourself). (On Linux the same would be achieved by "ifconfig lo", and see. It should be configured, with the right IP (127.0.0.1) and up.
Incidentally, it's MUCH easier to use Android SDK on Linux, because that way both target and host are Linux. Consider running the whole thing in a VM image - and your SDK Experience will be immeasurably easier. From experience.
I also had an error problem ERROR | It seems too many emulator instances are running on this machine. Aborting. in the emulator windows command.
I had a lot of virtual networks, all of which were active, because of the VirtualBox and vmware installation.
Solution: Disabling all those networks solved my problem.
For me, the reason is that I was using wsl-based docker on Windows.
Try disabling the option Use the WSL based engine in the docker settings (which resorts to using Hyper-V)
Enable Hyper-V in Windows Features.
Restart your computer and you should see it work like a charm.
My virtualbox VM, android emulator and docker now works together!
I have Hyper-V enabled (Intel CPU) for use with Docker and WSL2, on Windows 10 21H1.
Returning to Android programming after a hiatus, I reinstalled Android Studio today (4.2). It tried and failed to install HAXM (which is not surprising as it won't work with Hyper-V). I then was unable to open Android virtual devices.
After hunting around for answers (mostly people saying to disable Hyper-V which I was not ready to give up on), I found the exact process command line for the emulator and ran it in an admin window for good measure. Enter the "it seems too many emulator instances are running on this machine" error, previously invisible, which led me here. I checked ports and shouted into the void - nothing helped.
Then I rebooted, on the off chance something in all those attempts was somehow still holding resources (despite killing every related process).
The Android virtual device worked after that reboot, with Hyper-V still active. I hadn't changed anything that should have required a reboot, but evidently some resource(s) were locked along the way in my previous session.
(Also note that if you don't touch/edit \qemu.conf on whatever drive you run from (typically C:) you will see the incorrect Your emulator is out of date error if running from the command line.)
Just enable Hyper-V from Windows features
I am getting these error at console.
hax is not working and emulator runs in emulation mode eclipse.
So I am unable to run the app in emulator.
After spending a lot of time,I am come up with the answer.
If you are getting emulator-x86.exe has stopped working Error means:
Try these two steps:
Change the resolution of the device 1280X800 to 800X600.
Reduce the size of the Ram by 512 MB or less.
If you are getting Hax is not working Error means:
Try these three steps:
1.Hax software would be located
in
C:\Program
Files\Android\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager
Install the HAXM Driver by running "IntelHaxm.exe" in command Prompt.
2.. if the installer fails with message that Intel VT must be turned on,
you need to enable this in BIOS.
For Eg:
if You are using windows 7, press F12 key to enter into bios setting.
There you can see the Intel Virtualization Technology placed in System Performance.Turn it on as enabled
3.Then again run the "IntelHaxm.exe" in command Prompt.Everything will be works fine.
In Android Studio, AVD Manager, edit the AVD you want and disable Use Host GPU under Emulated Performance. This eliminated this problem for me.
In my case, I solved this by un-selecting Multi-Core CPU.
I am using DELL inspiron n4010 with i3 generation 1 processor. Its showing me VT- enabled but I am not able to run the HAXM driver in my android simulator. The drivers have been installed successfullly. Please help me out.
Actually I am not able to see this while running the avd with intel processor.
It should not supposed to run on android simulator(Emulator) actually YOu have to create an emulator with intel Atom(x86), and the driver will make this emulator run faster than the other emulator.
Check this link
you should check how much disk space you have allocated while installing HAXM and how much disk space your virtual devices (in AVD) use. Perhaps you allocate more disk space to the emulated devices than you have specified when installing HAXM.