I am using Android Studio on a Ubuntu virtual machine.
I not yet got to the point where I am debugging my code. I am only trying to launch the emulator in Android Studio. After learned that my computer could not handle a high resolution emulators, I picked the appropriate ARM image. But when I launched the device from teh Device Manager, I could see that it seemed the emulator was trying to load but it stopped after just a few seconds with this error.
Logcat is, of coure empty. I have not even gotten to the point where I am debugging code.
I am using Windows OS and when I get this error, I open the task manager, find the qemu-system-x86_64.exe process and kill it.
You can do something like this in Ubuntu.
Related
While running Emulator its shows Emulator was Killed.
In Activity Log I can see an error named as:
"Emulator: Process finished with exit code -1073741515 (0xC0000135)"
I have tried---->
To clean/wipe and cold reset
Even I have tried by creating a new Emulator with RAM size 4 Gb also. But still, I faced the same problem which I had encountered earlier.
My IDE and SDK are updated.
I had also tried to configure my AVD's Graphics from Automatic to Software-GLS 2.0 but that doesn't work too.
But the same project can be run on my Android Phone.
My PC's Virtualisation is "Enabled"
Please Help me with that...
There's some suggestions in here about running the emulator from the command line, so you get some more useful info.
Since you mentioned RAM size, make sure you have enough local storage on the virtual device too - I've had a lot of problems where I've tried to keep it low (it'll be fine! I'm only installing one small app!) and the emulator misbehaves and won't run properly
I was trying to test a xamarin app on an emulated android device so I set up hyperV, created the device and started it. However, as seen below, it fails to boot and it's unclear to me as to why. I'm guessing this has to do with hyperV but really not sure.
Update: After leaving it running for a bit it popped up the following:
Emulator error
Device error: Could not get emulator name after starting AVD pixel_2_pie_9_0_-_api_28
I am new to android studio, and I do not have an android phone, so the first thing I actually tried to do is to try out the emulator before I get any further into android studio, but I am facing alot of problems.
When I press on the RUN button, I do find a "Nexus 5X API 27 X86" by default, when I run it, well here comes the problems. Sometimes it runs and opens properly, but without being able to find my app on the device, sometimes the app opens automatically. The device is always so slow, most of the times when I try to open an app, I get a msg "APP(google most of the time) has stopped working" or "Android is starting.." out of nowhere, and that same msg sometimes pops out automatically when I first run the emulator. Sometimes I get "Application Installation Failed" error, found some solutions saying to trun off instant run, I turned it off and I still get the error sometimes.
Generally, it is just impossible to start coding with such device, I had an android phone before and it was much easier.
As far as I know, my laptop should easily support both the android studio and the emulator.
One more thing, whenever I try to set up a new device on kitkat or something, the device doesnt come alive, just a stuck black screen with a logo in the middle.
My laptop:
Intel Core i7-5500U 2.4GHz
4gb RAM + 8gb RAM
Nvidia GeForce 920m - 2gb
64bit
And yeah, HAXM is installed.
Android Studio 3.0.1
Any assistance would be appreciated.
You can try genymotion if you feel android emulator is slow. https://www.genymotion.com/
you can find the difference between the android emulator and genymotion.
android genymotion vs emulator
Emulator's now is much faster and better then genymotion,just create your own device going to avd manager and then try to run it,one more thing , did you turn on intel virtualization in bios ?
I have been running Android Studio 1.5.1 doing development on a WMWare copy of Windows 2012 R2 and everything works fine. I've been able to run the device emulator with no problems and start various versions of Android running in AVD.
Android Studio 2.x Change
I recently installed Android Studio 2.0 (see image below for exact version).
Now when I attempt to run the emulator nothing happens.
Well, actually I do see a message in the status bar of Studio when I attempt to start the device, but then that message disappears and nothing happens after that.
There is a warning that I need to turn off Hyper-V (see image below), but I don't believe that is possible since this is a VM.
No Longer Possible?
Is it not possible to run the emulator on the VM any more?
More recent versions of the Android Emulator require hardware virtualization support (Intel HAXM).
Unfortunately, most virtual machines do not provide HAXM instructions to the guest (a VM within a VM), so you will be unable to use the emulator within the virtual machine.
I just installed Android Studio 2.1 on my Windows 2008 R2 VM (running VMWare) and I'm happy to report that it is possible to run ARM based AVD (Android Virtual Devices) on the VM.
Steps To Run Arm-based Virtual Device on VMWare
Go to location where you've installed the Android SDKs (in my case it is at %appdata%\Android2\SDK\
If you are in the right place you should see a directory structure and directories like the ones shown in the first image below.
Start the AVD.exe by double-clicking it.
You will see a window like the one in the image below
Take a close look and notice that this is running an ARM(armeabi-v71) image. When you download images you have to download ARM-based images. (no x86 images will work on VM).
Also, you cannot start these images from AVD that launches from Android Studio 2.x
Make sure you have an environment variable named ANDROID_SDK_HOME set to path which is similar to the one at the top of the AVD manager (in image).
Once you do all of this and start an ARM-based image on a VMWare VM it will warn you that it is faster with HAXM but at least the image will run.
Finally, you can see if you attempt to launch your Virtual Device from the AVD Manager in Android Studio then it will warn you that Hyper-V needs to be turned off. Of course you cannot turn Hyper-V off on a VM.
EDIT -- Running Android 7 ARM Image
#mcflysoft asked about running an android 7 ARM image. At first I didn't think it worked, but if you open up your SDK manager and install the exact ARM OS image shown in the following picture, it will run on a Windows VM:
ARM image Containing Google APIs
I tried installing the ARM image that contained the Google APIs and that one would not ever start. There were failures logged which I could see in c:\> adb shell logcat.
Beware : It Is Really Slow
However, running Android 7 seems extremely slow and I don't see a web browser.
Not sure how helpful it may be to you, but you can get it working.
Good luck.
The simplest solution I've found so far is to use a device farm, for example Samsung's device farm:
https://developer.samsung.com/remotetestlab/galaxy/rtlDeviceList.action#444
It's free to use and you can deploy your apps just like in an emulator (Right Click -> Test -> Remote Debug Bridge -> follow the instructions).
And since those are real devices, the speed might be even better than on an emulator on your personal PC.
I've had the same problem so I'll post an answer in the hope that someone might find this useful in the future. I can run Android Studio in my VM but when I try to start up an emulator, I can't download an image due to "Your CPU does not support required features (VT-x or SVM)"
Although I didn't get a virtual device up and running, I got round the problem by using BlueStacks. You install BlueStacks on the VM. BlueStacks (at the moment) runs Android 7.1.1, SDK 25. Inside BlueStacks, go to Settings/Preferences and Enable Android Debugger Bridge (adb) following this set of instructions. Then you should be able to run your app on BlueStacks from inside Android Studio. Logcat can see any log statements from BlueStacks.
The alternative (without enabling the debugger bridge) is to locate the .apk file for your app and then open that with BlueStacks APK installer. Logcat still sees the traces.
It's slow on a VM. You also have to set android:testOnly="false" in your XML file
It was working fine till I updated the Android SDK tools from the SDK Manager to version 24.1.2. However a virtual device was running at the time of the update and it asked me to close 3 processes in order for the update to continue. I thought the virtual device was interfering so I closed it and tried to proceed with the update,it gave me the same error. Therefore I cancelled the update and closed the studio. After restarting the studio,it gave an error saying the SDK could not be found and would not let me do anything else. I uninstalled the studio after deleting the SDK folder and reinstalled it. I downloaded the system images needed for the virtual devices and some other packages and created a new virtual device. When I tried to run the application,it gave me the dialogue box to chose the virtual device,I chose the newly created one and it gave the command to start the device. Yet no emulator window for the device appeared.
D:\sdk\tools\emulator.exe -netdelay none -netspeed full -avd MTK
emulator: device fd:5500
HAX is working and emulator runs in fast virt mode
HAXM is installed and it worked fine before. On checking the task manager upon launching the application,an emulator-x86.exe process appears briefly before disappearing. Nothing happens after that. Launching the program again gives the same result. If I try to launch the device from the AVD manager,I get the same result. I have tried using the arm images,varying the ram size,snapshot enabled/disabled,use HOST GPU enabled/disabled,system restarted,removal of /.android content,setting up the SDK in a different drive and deleting the ANDROID_SDK_HOME system variable and resetting it.
I have also tried with Genymotion. The virtual device window briefly appears and I can the see the android logo at startup but then it says "player.exe has encountered a problem and needs to close. We are sorry for the inconvenience." I have tried it using both the Genymotion Android SDK tools and the custom Android SDK tools to no avail. If I try to delete the device it says please stop the virtual device before deleting it even though it is not running.
I spent most of my day trying to solve exactly the same problem until one of my colleagues remembered he had exactly the same issue and that was related to Docker.
Docker uses Hypervisor Framework which is incompatible with the HAXM used by the Android emulator. Therefore if you try to run the Android emulator while Docker is running it will just quit without a warning. Quitting Docker will allow to use the simulator - Docker for Mac conflict with Android emulator
Sometimes it is because you are low on memory, or it might be an AVD specific glitch. I had many (20) devices saved in my AVD and was lower than normal on memory on my laptop. The native emulator folder would disappear right away but genymotion worked fine.
I removed the old devices and create a new one from scratch in AVD and the problem disappeared.