So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks
Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.
Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.
I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.
Related
I have a mid 2013 Macbook Air (so I should have the resources to make the emulator work) and I'm trying to get the Android Emulator working. It's been half an hour and the color pinwheel continues to spin. In the meantime I looked up and downloaded Andy and BlueStacks Android emulators but Andy was nothing more than a clock with no buttons and BlueStacks, while it had a number of options there was nothing that seemed evident that I could get 'Hello World' running from the basic tutorial.
http://developer.android.com/training/basics/firstapp/running-app.html
I want to progress but I'm stuck. Thanks.
I would look into Genymotion. They have a great android emulator that can spin up vms for different phones. Its free for personal use and easy to use. The VM image is download directly from their server so when it gets corrupted you can delete it and add it again.
It is also recognized by Eclipse and Android Studio.
There should be two downloads, one that includes Oracle VM and one that doesn't. I recommend the one that does so you do not need to install Oracle VM by its self.
If that doesn't work post a comment and ill see what I can do.
try restarting your computer..
When you start an emulator you should "Store a snapshot for faster performance" in the Android Virtual Device (AVD) configuration or the emulator won't start at all. After too much time troubleshooting, it was as simple as that.
So this is probably really simple and easy but I've been unable to find anything on the googles.
Once I've got an android emulator up and running from within IntelliJ Idea, and tested my project in it and then write a little more code, how do I push the new build onto the existing emulator?
I'm asking this because right now, I have to close the emulator each time and then relaunch the emulator again which takes forever to boot up.
For one thing take a look at the GenyMotion emulator it is way faster. There is a free version with a few of the bells and whistles disabled but it is way better than the AVD's provided with AS or Eclipse. Make sure you set a configuration for the app.
I am currently a QA intern at an app publisher and I use the AVD to test apps on various Android platforms and hardware builds. I touch nothing else within the Android SDK, just launch the android exec through the terminal and go from there.
I installed and started using AVDs with no issue about a month ago, installed the Intel HAXM with no issue, etc. It randomly stopped working for me about two weeks ago and I've been struggling with it since then. I've deleted everything from the Android SDK and reinstalled several times, tried using adb to no avail, nothing. I haven't been using Eclipse to get to the AVD Manager, but even when I do it makes no difference.
I've run into a dead end after trying every potential solution I could find on the Internet. Help me before I go insane.
Also using a Retina MacBook Pro, not that I think that'd make a difference, but just incase.
I am going to put this up as an answer just because I really found it to be the best solution to all of my native AVD issues (my default AVD emulators would creep even on my faster machines). I downloaded genymotion and must say that I am a million times happier with the emulation. It is faster, smoother, has more options, it just makes the native AVD look even worse than it already does on its own. Even if genymotion isn't for you, I highly recommend looking into third party emulators. It will make QA, development, etc. with Android that much easier. Assuming ARM isn't required (don't think it does ARM emulation)
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 have have been using the Android emulator both and the command-line and in Intellij for some weeks running ApiDemos and my own apps with no problems.
Now, without any exceptions or messages to indicate the reason why the emulator will only run the emergency call app and nothing more.
Is this a bug? If so, how do I create an issue for the Android SDK dev?
I'm cautious to load any .apk now into my handset to see if the condition is the same.
Particulars follow:
OS: Ubuntu 12.04
Android SDK: 4.1 (ICS).
JDK: 1.7.x
Maybe a stupid answer, but are you sure you didn't set a PIN code on the lock screen? This will load the PIN entry screen whenever you load the emulator but still allow you to make emergency calls.
You have to set a PIN on Android ICS when you save new security certificates, which caught me out.
You need to use 2 GB of RAM o avoid that problem in your android emulator.