I am new to android just installed Android sdk with eclipse & ADT plugin, these stuff are working fine, but my emulator doesn't display anything after 30 minutes.
My target virtual device(AVD)
Android 4.0.3, API level-15
CPU/ABI: armeabi-v7a
I have tried tweak from stack overflow
"Hardware section:Device RAM Size=15", It helped because before trying it, emulator was crashing. Now emulator appears but nothing is displayed
Please help it is depressing start this way
There is an intermittent problem with the emulator that we've encountered in our testing. It seems to happen the first time an AVD is run.
If you don't see the main screen within a few minutes, you should force-kill the emulator, stop adb with 'adb kill-server' from a command line. Restart adb with 'adb start-server' and then restart the emulator with your AVD. Suggest also to turn off the snapshot until the first time it loads correctly. If you're using the GPU feature, turn it off as well.
I have found the solution, the problem was i haven't set environment variable, which was "C:\Program Files\Android\android-sdk\platform-tools\" in my case,
I was facing same problem. I solved it as below steps.
Go to AVD manager, select the corresponding AVD, then click on edit then select the device from the drop down menu. I forget to select the device, so there was nothing on my AVD. Only black screen was there.
Related
A couple of days ago (15th April 2017) I updated Android Studio with all the latest updates. Now when I try to run an app, the emulator window opens but I just get a message "waiting for device to come online". Eventually this times out and I get a message "installing APK", where it just seems to get stuck. I have searched the site and tried various advice including:
Deleting all the emulators and re-creating
Turning off the emulator in SDK manager, re-starting Android Studio and turning the emulator on again
turning off instant run
re-booting my PC, in case some update needed a re-start
The emulator I have is Nexus5X API23.5554
I have also deleted my app and created a completely new "hello World" app that does nothing but display one line of text, but I still get the same problem.
Has anyone any other ideas?
I ran into this issue too. It seems to be a bug with recent changes to the Android emulator. There is a workaround:
Launch the emulator independently from the Android Virtual Device (AVD) manager (there's an icon in the main Android Studio window)
Run your app. You'll notice the device name has changed from whatever the emulator is called to some generic name like 'Android x86 API 25'.
The app will run correctly on the emulator. You'll notice in logcat that the device name is 'emulator unknown'.
Hopefully Google will fix this over the next few days.
I couldn't get any emulator going at all, with no error messages, just 'waiting for device to come online'.
When tried to stop and start adb.exe in terminal:
adb kill-server
adb start-server
it said that adb is outdated. I had latest adb version downloded but Android Studio was trying to use some other file which was older version.
Finally, I checked environment variables and removed paths to:
C:\NVPACK\android-sdk-windows\platform-tools
and
C:\NVPACK\android-sdk-windows
as the newest version of SDK platform-tools I had on drive E: not C:, and is all working now.
Enzokie - Thanks. Nothing there seems to work, though. As a novice, I always assume that if something is wrong, it's my fault, but maybe not this time! I shall do as you suggest and raise it with Android unless anyone else suggests something that works.
My work around was to use a Nexus 5 instead of Nexus 5X.
If you don't know how to make an new emulator its tools>android>AVD manager> create new virtual device. Then just pick a new emulator and hit next until you're finished or customize it.
Resetting the ADB did the trick for me.
For Mac, In Android Studio -> Tools -> Android -> Android Device Monitor -> Under devices -> Down arrow there will be reset ADB option.
What worked for me was to wipe the emulator data. You can do this from AVD manager:
Tools -> AVD Manager -> Right click on virtual device - > Wipe Data
Hi I had the same Problem...so I did this:
Start your emulator, you will get the "wating for device to come online" error msg.
Wait till the emulator boots, then stop the process.
Now, on the emulator go to settings and make your "device" (emulator) to a developer device.
Check this, if you dont know how to do it -> https://www.digitaltrends.com/mobile/how-to-get-developer-options-on-android/
Then go on "Developer options" (in settings) and switch on the "usb-debugging" option. Remeber you PCs fingerprint.
Hope this was helpfull....
I just installed Intel HAXM and updated my Android SDK Tools to revision 24.1.2 successfully. Then I restarted my PC, and ran the emulator. Unfortunately, I my emulator won't starting up, always stuck. Waiting for ~1 hour, the emulator still getting stuck. Sometimes the screen was black, didn't show anything even the ANDROID logo while emulator was booting (full of black color). My screenshot:
The second problem is, as you can see in the figure, this is an abnormal behavior. There's no title bar, because it hides on the top of my desktop. So I can't move the emulator window to the center of my desktop.
From the Console, it seems that Android Studio is waiting for the emulator to finish its start up:
What have I tried:
Restarted my PC.
Followed this answer.
Check and uncheck Use host GPU option in AVD.
Re-build my emulator in AVD.
Closed the emulator and ran it again.
Changed CPU/ABI to ARM and Intel Atom x86 in AVD.
Can you help me to solve these problems?
Have you tried with a different\more recent Android version?
I suggest you to switch to Genymotion.
It's free for personal use and it very better than AVD: it's faster, you can drag and drop files and much more.
I asked my mom to pray for me to solve these problems, and I found the solution then, hehe :P
So these problems happened because of the skin of emulator I selected in AVD was WQVGA432. Then I changed (edited) the emulator's skin in AVD to WQVGA400 and WQVGA800 to test the result, and it really works for both of them. I think, the only skin which has broken is WQVGA432. If you also had these problems, I suggest you to never select WQVGA432 skin or try another skins.
Now, I can move the emulator window normally and debug my app.
Try updating Android Studio and re-download the image file from SDK
[2012-02-14 11:57:59 - HarshaBoston] Android Launch!
[2012-02-14 11:57:59 - HarshaBoston] adb is running normally.
[2012-02-14 11:57:59 - HarshaBoston] Performing com.boston.harsha.startPoint activity launch
[2012-02-14 11:57:59 - HarshaBoston] Automatic Target Mode: launching new emulator with compatible AVD 'Droid8'
[2012-02-14 11:57:59 - HarshaBoston] Launching a new emulator with Virtual Device 'Droid8'
[2012-02-14 11:58:05 - Emulator] emulator: WARNING: Unable to create sensors port: Unknown error
Ok so this is what the console is showing. My emulator was working fine until a couple of days ago, then my projects were not updating the changes made to the main.xml file even though the changes were saved.
Now, I wanted to see if a new project would work, but no dice. The emulator runs fine, but my app is not loaded, I have no idea what to do to rectify this.
I'm using API Level 8, with ADT plugin Android SDK on eclipse on Windows XP.
Android beginner here. I was making a Hello World program, which ran fine a couple of days ago, but now nothing runs, and existing projects don't show the changes made to them. Please help!
Now when I run the emulator, the emulator runs fine but my app isn't even loaded!
I've already tried reinstalling the ADT, reinstalled the Android SDK,etc. nothing happpened
Also, the emulator doesn't seem to be showing up on the DDMS.
FIXED IT!! SOLUTION FOR ANYONE FACING THIS PROBLEM
Apparently a lot of people in here seem to have this problem and only one of the threads had a good solution.
Firstly if this is happening to you, check the DDMS to see if the emulator is shown. This is the a red flag. Apparently the adb server does not refresh or restart every time you restart eclipse.
Run the emulator. Chances are your app may not run on the emulator. Now, while the emulator is still running go the DDMS tab and next to the Screen Capture icon there is a dropdown menu with 'Reset ADB', click on it. Now your emulated device should be shown in the DDMS devices.
Run your app now. hopefully this solved your problem. Mine did!
FIXED IT!! SOLUTION FOR ANYONE FACING THIS PROBLEM Apparently a lot of people in here seem to have this problem and only one of the threads had a good solution.
Firstly if this is happening to you, check the DDMS to see if the emulator is shown. This is the a red flag. Apparently the adb server does not refresh or restart every time you restart eclipse.
Run the emulator. Chances are your app may not run on the emulator. Now, while the emulator is still running go the DDMS tab and next to the Screen Capture icon there is a dropdown menu with 'Reset ADB', click on it. Now your emulated device should be shown in the DDMS devices.
Run your app now. hopefully this solved your problem. Mine did!
I had the same problem with developing my android app on an emulator. I would rebuild and install my application and it would keep installing an older version of my app (reinstalling app, and the answer above didn't help). Turns out running ant clean and rebuilding the project fixed it!
I am using SDK on Windows Vista. Everytime I start the emulator it just hangs at the android animation. On log cat it displays Waiting for HOME ('android.process.acore') to be launched...
After this nothing happens. I have gone through all related posts on this forum but nothing works for me. I have even reinstalled everything twice but nothing works.
Can anyone please help? I have tried on target 2.1, 2.3 and 3.0
I had similar problem. All I did was delete the emulator and created another emulator targeted at the appropriate API Level.
Yeah! Somehow it worked for me this way....
I had this exact same issue on windows 7 64 bit and tried many of the solutions that I found on this site including deleting my AVD and recreating it but nothing seemed to work. In the end, I resolved this by editing the AVD and setting the "Max VM application heap" from the default of 24 to 32. This instantly resolved my problem on windows 7. The android screen that previously appeared to hang now launches up in under 1 minute.
I hope this is helpful.
click on the button "Opens android device manager" on the menu icons, delete all the virtual devices, create new ones (without the snapshot checked).
try again
worked for me
I used to have the same issue. I tried uninstalling & reinstalling several times. I'm guessing that you're using Eclipse and starting the emulator from within the IDE. My solution was to try it from the command line; type android (assuming that the PATH is set correctly), choose an AVD, start it & wait. Another suggestion would be to create a smaller AVD (smaller screen). this will have a great impact on the emulator performance.
I had this same issue using Windows 7 64-bit. Here's how I fixed it:
HelloAndroid emulator problem
If you are having this problem with an SDK Version higher than 22.3, see my answer in the post referred to above by walkerk:
https://stackoverflow.com/a/22800240/2326613
You will get "floating point exception" in Intel API 19, and the behavior described by the OP in this post for Intel versions prior. The ARM APIs should still work (slowly).
In the earlier APIs, "adb shell logcat" command (run in shell) on the "stuck" emulator will show a loop around an error involving " SSLCertificateSocketFactory " failing.
after long time try and error and a lot of time waist in different fourm , this problem ( Black page on SDK boot or maintain in boot animation, easily solved by selecting different skin in emulator ( insted of first chois that was dynamic skin , ) I select last skin "wxga " . emulator boot in less than 1 min
I had same problem only with API Level 15
Solution worked for me:
from SDK Manager i remove and reinstall System Images related to API-15
and next i create new Virtul Device
I am an Android Newbie! please help.
I have been following googles introduction tutorial and managed to install everything with no problems. but whenever i try to run the HelloAndroid example the avd launches but doesnt show anything.
cone somebody help please?
After you create an AVD it really does take a long time to initialize. On my less than year old Core2Duo 2.8 GHz running Win7x64 and 4Gb of RAM, initializing a 2.2 version took at least 5 to 10 minutes (if not longer). Once it starts initializing you can watch the logcat in the DDMS panel of eclipse and watch it unpack and install all of the apps in the emulator.
It is quicker to export the file to your phone using USB cable, install it by selecting the .apk file with a file manager and run it from your phone. This also gives you "real" simulations of the app. It is quicker also. If your app has flaws, it is quicker to find them on your phone then wait for the AVD to load only to find your app doesn't work!
Goto File -> Export, select android folder then android application.
On the next page, select the application you want to export.
Create a keyfile and an alias.
Eject your phone, then open your file manager of choice, and click on the app.
Run using android package installer, you will need to enable no market application install in your settings
Open the app after the install is complete.
You can always run 'adb shell' or 'adb logcat' from another window to see what is happening...
I had the same problem but I fixed it by deleting .android folder from C:\Users\User\
Now everytime I start Eclipse or AVD, I delete that folder. After that everything works charm.
OPTIONAL : If the problem still persists, try to clone the NEXUS S AVD.
How long did you wait for it? On my (admittedly older and slower) home computer, it can take some time for the AVD to initialize the first time. I've just tried it and it takes about 90 seconds for the "ANDROID" in the center of the screen to be replaced with the home screen, then about another 30 seconds for the application to run.
I had the same problem. It was because i hadn't restarted my system after installing ADT plugin. It worked fine after restarting my system.
Occasionally i've found that it just hangs up on the loading screen, and if you restart it, it comes right. Also, from memory it can take awful long to load first time.
For Ubuntu (I use Xubuntu):
Mine Android Virtual Devices didn't started because i used NVIDIA drivers for ubuntu. After changing drivers to Nouveau it booted in 15sec.
Go to "Settings Manager" -> Software & Updated -> Additional Drivers chose: "Using X.org x server -- Nouveau display driver (open source)"
NVIDIA F# U http://www.youtube.com/watch?v=55XVnJ_0qhg
Yeah It took too much time to start....
Try Switching on Visualization in the system BIOS Settings....
For me before switching it didn't show up anything. After changing it took 3 mins to initiate
System Specs:
i5 Dual Core
4Gb
Nvidia 2G
Stop the emulator --> Open ADV Manager --> Edit the Virtual device --> Click Show Advanced Settings --> Set the Ram size 512mb --> Start the emulator