First post, and new developer.
I installed on my Mac (10.6.8) the complete package from Google and proceeded to open the SDK Manager and downloading everything. I then installed the IntelHAXM_1.0.8.dmg and rebooted. I created a couple of virtual devices (VD) in the AVDM and attempted to start them. They are not set to use GPU acceleration and have the skin to the first option (Skin with dynamic hardware controls).
When I click 'Start', the progress bar in that windows shows me its starting. Upon reaching the end, the window with the progress simply disappear, and I'm back at the list of my Virtual Devices. I thought, maybe its an update I did. So I deleted and started from scratch with no SDK updates. Same results. Tried Different devices, with or without GPU.
The virtual android never shows up.
I also installed the Android Studio and the same thing happened. On the virtual Windows 7 I have setup on that Mac, the virtual devices load up fast. But on the mac itself, they never appear?
Why?
I think it does not matter to be on mac or windows, it is related with android emulator configurations.
emulator takes a while, from 30 sec till few Minutes, so be patient.
if it did not work, try to use configurations like one of these to start up.
or
Related
Whenever I open the AVD Manager and launch any one of the virtual devices I created, the emulator starts and closes immediately. When I run the virtual device in AVD Manager for the first time I get an error message that QEMU has stopped working.
I have given the right path to the JDK. More over, I have tried to install Android Studio again and again, but still its not working. I am using Windows 7(32 bit, 2GB RAM, without graphic card).
Is there need of graphic card to run emulator? If not, what should I do the run the emulator?
In AVD manager open settings for your virtual device.
In the Emulated Performance section open the dropdown for Graphics.
Change it from Automatic to Software.
Hit the Finish button to save new setting and try starting the emulator again.
I finally found the solution here: https://www.bram.us/2017/05/12/fix-for-the-android-emulator-crashing-during-launch/
It seems to be an incompatibility with other software, such as Docker, Oracle Virtual Box and other products that use VCPU. In my case, it seems that VBox and/or DraftSight caused the issue. I don't get the error when I terminate those applications first.
After trying Vahid's answer, it stopped crashing. Unfortunately it was lagging badly. After installing the NVIDIA drivers for my card (I have a 1060), I was able to change the setting to Hardware again, and now it is much smoother.
In most cases the solution provided above by #Vahid would work but if for some reason you still want to use hardware for graphics. You can try upgrading graphics drivers and make sure to set your graphic profile aka GPU workload to Graphics instead of compute. This settings can be found in Nvidia control panel or AMD Radeon software settings, not sure if this would work for integrated graphics.
I'm using IntelliJ Idea 13 to develop Android applications on Ubuntu 12.04 64-bit. But my virtual device never starts despite there is no error.. its screen always stays like this:
My Android target level is 4.4 (API 19). How can I solve this issue?
Edit: Here is my AVD details:
I Recommend you look at this post to a similar question.
https://stackoverflow.com/a/5535532/2978914
they are using eclipse but you should be able to view the logcat, other posts say first load can be ridiculously long.
the spec of your PC may come into play as this post https://superuser.com/a/347298 explains the way the emulator converts to arm opcode: direct quote:
To use emulator more effectively, this is my experience:
Don't close emulator everytime you run your application.
Scale the emulator screen smaller.
Disable snapshot (Yes, it's useful but it takes time to close the emulator).
Specify a file path for SD card image file. I use only one SD card for many AVDs.
If you got any problems in adb, just reset adb, don't close emulator.
Open few programs in your operating sytem.
If you are using Windows, don't ever close emulator. Do it combined with Hibernate of Windows.
My AVD has started after I check "Use Host GPU" option from "Emulation Options".
I'm trying to run the very simplest app on MonoDroid though the MonoDevelop IDE - i.e. the one that is created as part of the new project (the one that increments the lable on button clicks - i won't post code as I don't think it is relevant unless someone really wants it).
When I press the run menu item then run (or debug) i get the emulator selection
I dutifully start the emulator - (I've tried API_7, API_10, API_12) and that works OK. But the IDE above never refreshes to show the currently running emulator so I can't launch the application. I have manually refreshed but the same list comes up. What I am expecting is the new emulator to appear in the list and the OK button becoming active.
I have tried running adb devices in the command line and I can see that the debug bridge has picked up the device i.e. it says emulator-5554 which matches the TCP/IP port that the emulator is running on.
I've also tried restarting the debug server i.e.
adb kill-server
adb restart-server
But I can't see the emulator appear on the above dialog. The debug server is running on port 5037. Could the IDE be listening to a different port?
Fundamentally I'm trying to get the simplest app running through MonoDevelop. And I'm failing. Please help good people.
I had the same problem initially when I tried running the emulators. My recommendations from my own experience would be to:
Run the Android SDK manager and retrieve all the latest SDK packages.
Create your own Android Virtual Device via the AVD Manager rather than running those that are listed when the IDE is intially run. You should then start the AVD manually via the AVD manager and ensure it is fully loaded before starting the de-bug.
This is the message I receive always (100%) if I try to start the emulator with an existing snapshot. The system is Windows 7 32bit, ADT14 and SDK14.
I need to start every emulator session with "wiped user data". Whenever I try to reload the emulator with a snapshot Windows prints this message (in German: emulator-arm.exe funktioniert nicht mehr) and the only option available is to close the application (emulator-arm.exe).
I can reproduce that at will. Even with fresh installs of Eclipse (Helios and Indigo), SDK, ADT. I could see that with all versions in the last year. I can reproduce that on three different machines in my house (all Windows 7 32bit) at will. There's not much software on my machines. On one machine is the Android Development environment only. All three computers are no gaming machines and don't have much power. I mean, just to use the Eclipse editor, it must be enough.
All applications (Eclipse, etc.) are not configured to special needs. I always use the Android development as is out of the box.
Any help is highly appreciated. It's not funny to always go for lunch or coffee just to switch from one emulator to the next one - lasts for approx. 10 minutes here.
Personally I suggest not to use Snapshot features. Just having a normal reboot is totally fine, it doesn't take much time, just one or two minutes.
The Snapshot thing really troubled me in the past, and resulted in a newly-fresh installation of SDK. Don't know why it is exactly but it is better not to use Snapshot, first, it doesn't speed up your emulator speed; second, it is a emulator stuff, not on a real device.
Correct me if I'm wrong or mistaken something!
Launch your AVD Device via the AVD Manager, ensure not to wipe user data or use launch from snapshot.
If your application is not deployed to AVD Device:
Right click your eclipse project select run as => run configuration. Ensure under the target tab deployment mode is set to manual. Click Run, from here you can select the current running AVD you started earlier.
To redeploy your application to AVD Device
Leave the AVD Device up and running, use the Application Manager on the AVD Device to uninstall the app from the AVD Device. Next, right click your eclipse project select run as => run configuration. Ensure under the target tab deployment mode is set to manual. Click Run, from here you can select the current running AVD you started earlier.
Trying to run the Android Emulator on Windows XP SP3 the Emulator will start, it will get to the point where I can see the "ANDROID" text on the screen on the emulator, then a series of 3 windows command prompt windows will open, the final of which will say "Error Reading Properties" which is similar to the problem here Android-AVD :error loading preferences
However after this dialog shows, XP crashes.
This was consistent across revision 10 and 13 of the emulator (I upgraded trying to get past the problem)
Has anybody had this problem? I haven't been able to reproduce it on any other machine than this one, I've done all the arbitrary updating of drivers etc. grasping at straws trying to make the emulator work...I can't think of what else to do
Forgot to add:
I've run the emulator with the -trace option, but all the files generated are empty.
It turned out to be a problem with my Audio driver. I had seen other people on forums reporting problems using LG headsets etc. and when they unplugged their microphones the emulator worked, but they were having different issues i.e. their system didn't reboot. I had also tried simply unplugging all my audio devices with no success. In the end I started in Windows Safe Mode, the Android emulator complained about no sound available, but didn't crash. So back in plain old Windows I just disabled my audio driver and it worked perfectly.