I just downloaded and installed Android Studio (v 2.3.3), and am starting to teach myself programming for Android by following Google's tutorials. (I finished the Java MOOC courses offered by University of Helsinki a little while ago). However, I can't seem to get the emulator working (following the instructions here). I chose the Nexus 5x (same as my phone), but it seems to be frozen on the boot screen. The animation has stopped.
This is what it looks like
I've tried deleting the emulator and recreating it again, but that didn't change it. I can't close or stop the emulator. I can't even kill it with the Task Manager (I'm on Windows 10). None of the buttons next to the boot screen do anything, except the three dots on the bottom, which open up the Extended Controls. The Android Virtual Device Manager won't let me start, stop, or delete it. The only way I was able to remove it and create a new one was to kill it by restarting my computer.
It's a fresh installation, and I'm extremely new to Android development, so I have no idea what to try next.
Related
I am developing an Android app in Android Studio. When I try to run it on an AVD, the AVD screen shows nothing.
The device frame is visible, but there is nothing inside it. The message "waiting for target device to come online" doesn't show up either.
Furthermore, I am unable to edit the graphics in the AVD settings. I have tried running the program both normally and from the AVD manager, but it doesn't work either way.
Other solutions which I have tried (and failed) are removing C:\Windows\System32\Wbem from the PATH environment variable, ending the ADB process in Task Manager, and wiping data from the AVD in AVD manager. Oh, and I even uninstalled and reinstalled Android Studio but it still doesn't work, even for a basic Hello World program. Any help would be greatly appreciated.
https://imgur.com/a/rzMmz3E
I faced this problem due to my ram several times and even after upgrading I had to make several changes. The best solution is to set up a new avd. use Nexus S, and a light image. Start with API 16 and when it works go ahead and create your desired AVD. Keep your eye on the pop up errors AVD shows like HAXM
It may seem silly but have you checked if the emulator is not locked?
Ok, when Emulator is not displaying anything and saying like, waiting for online,
after click on power button then what you have to do is Go to,
AVD Manager then in Actions section click on bottom triangle button and click on "Cold Boot Now" to make working your Emulator.
I'm a complete newbie trying to learn how to write an app. I'm trying to run Hello World using the emulator in Eclipse on my Mac. I launch and unlock the emulator. Android Training then implies that I should click the Run icon in Eclipse. But the ADT Manager window is in front of the Eclipse window and Eclipse is disabled. If I minimize the ADT Manager window it just quits the ADT Manager, and then I must close the emulator window.
I did discover that I can run the app with the Run button without starting the emulator as a separate step, although that takes a long time to get going.
Another Answer implies that I can just rerun the app by clicking the run button again, but I can't do this because the Eclipse window is disabled.
I'm used to being able to use the IDE while a program (Yes, I'm an old programmer) is running. What am I missing?
Duncan
You're right - simply hitting run on the application cold turkey takes forever because the emulator has to initialize. When you click on your AVD Manager (where you can create, edit, and customize the android emulator you'd like to use), Select the emulator you'd like, then click Start.
After waiting for the emulator window to popup, just wait until the UI loads (when you can unlock the emulator).
At this point, it appears that the AVD Manager is still necessary (due to the "loading" type green bar along the bottom seemingly feeding the emulator), but you can just close the window, and the Eclipse window will become clickable again.
Now, you can just leave the emulator running. I typically leave it running for hours at a time (even overnight) and I can usually just click Run as Android Application and everything works perfectly.
I'm new to Java, haven't used Eclipse in probably 2 years. We're starting up a mobile dev team at work, and I'm just going over the tutorials on the Android site:
http://developer.android.com/training/basics/firstapp/running-app.html
Simply just created a project, launched the virtual device manager, have that emulator running, then click Run -> Run as Android application in Eclipse .
I've been staring at this screen for about 5 minutes now:
It says "Launching (100%)" in the bottom right corner of eclipse, and this Progres window just says Launching, but the emulator isn't doing anything.
I know emulators are generally pretty slow... But is this normal or did I do something wrong?
That happened to me too, and still does at times:
Close the emulator and execute the program again
If that didn't work, execute the program while the emulator is running. A new emulator will pop up, close the old emulator
If that didn't work, delete device and create a new one.
Also, is there anything at all popping up on the Logcat view?
I would recommand checking the list of process afterwards. Sometimes when i brutally terminate an app in eclipse, the process is still running.
But i'm on PC and i use an older version. Maybe it has been fixed.
I'm a newbie that needs some help on getting the AVD running with my app. I've been developing C code for decades, but I have to admit the Eclipse/AVD setup has me stumped! I'm following the 'HelloWorld' tutorials on the developer.android website (and some others) and everything seems to be working OK, up to the point where I try to run it on the AVD simulator. I'm not getting any warnings, the Eclipse build/run output window says that everything is installed OK and the AVD does startup and run. Eclipse says that my app is loading, but it never runs. All I get is the simulator window with "ANDROID" on the screen and the buttons on the right-hand side.
I've got Eclipse Indigo and r18 of the Android PlugIn (I tried to install Helios, but the Eclipse website directed me to Indigo!). Is Indigo OK for running the simulator, or do I specifically need Helios? I also have Java 1.7.
The API level I have installed is Level 15 (v4.xxx of Android, I think). Don't know if I need a lower version to get my tutorial app to run, but level 15 is the only one I can select when setting up a device in the AVD manager.
I've been trying to get this going for days, trying all sorts of switches and buttons, but to no avail. Before I start uninstalling everything and reinstalling, can anyone advise if there is anything I might be missing, or has tripped over this problem themselves and found a way around it? Something that always trips up new starters maybe? Or do I need to go back to scratch?
Any help would be much appreciated.
How long are you leaving your emulator running after you attempt to launch your application? The Android OS can take a long time to boot up in the emulator. If it's stuck on the "ANDROID" screen then you're either not waiting long enough or there's something wrong with your emulator. It should eventually boot into the normal Android lock screen or home screen just like a device.
You can launch your emulator ahead of attempting to run your app by opening the Android Virtual Device Manager (toolbar icon in Eclipse, if installed properly) and then selecting an emulator and clicking the "Start" button. If you don't have any emulators listed, then you need to create one by clicking the "New..." button.
I'm an Android newbie trying to learn how to port one of my apps to the Android platform. I've been following this tutorial:
http://www.vogella.de/articles/Android/article.html#overview
I'm stuck unable to boot up the emulator :( When I tell it to start, it would just stick at the "Android" boot animation for hours on end. I searched online and found some pages talking about disabling the boot animation. I did so and tried again. There's no boot animation (just the word "Android" flashing), but it's still hours with no sign of booting. 'top' shows an app called 'emulator' using a lot of CPU.
Am I doing something wrong? My system is an AMD Athlon X2 dual-core QL-60, 1900 MHz with 3GB ram.
Thanks for any help you can offer.
I had this problem and fixed it by deleting the emulator and creating a new one.
In eclipse:
Menu Window -> Android SVK and AVD Manager
Select Virtual devices (should be selected already)
Select the emulator giving you problems
Click edit to see the setting and remember them, click cancel.
Click delete to delete the emulator.
CLick create to create a new one that is the same as the old one.
Click start.
It started in about 30 seconds after I did that.
Normally the emulator starts in about 2-3 minutes for me. Then it mysteriously stopped working. I was seeing boot animation for 30 minutes before I gave up.
Note #1: Doing this will wipe your user data.
Note #2: As mentioned else where, it's a good idea to check "Enabled" for the snapshot, this lets you do faster startup next time.
Note #3: Also my new emulator came up in chinese. That's kinda of weird :)
Android emulator release 9 has new "snapshot" feature. You can save state of emulator (make image of emulator) and avoid booting when you start the emulator.
I see a similar problem while attempting to run applications on an emulator while the emulator isn't started yet. I find that starting the emulator manually via the "Window > Android SDK and AVD Manager" will load in just a couple minutes or faster, as expected. After the emulator is started manually in this way, you can load applications into it without issue.
I faced same problem on my laptop using I5 8GB RAM. The only solution that worked for me was connecting the laptop charger when launching the emulator. May sound wierd but this always works for me.