When I ran my android emulator, I got the following black window. I waited for a long time and nothing came up.
There is also no logs in the eclipse console.
I am sorry this is not informative.. If you point me to a location for log files I would love to prove more information.
[EDIT] sorry if I weren't clear. I meant to ask, for thsi sort of emulator problem, other than trial and error, how do I really diagnose it? where is the log file I can trace down to?
I had the same problem on OSX, I've solved that by :
Go to .android directory (in my case it was Users/<username>/.android
Go to avd folder
Find the emulator that won't start (directory name will be the same as emulator)
Remove all .img files from there. Do not remove .ini files.
Try to run the simulator again.
This can be because you do not have enough RAM. It does take up a lot of time to start up if you are running it for the first time. What I suggest is using Genymotion as it is way faster than Android stock emulator.
If you insist on using the stock emulator, make sure the save snapshot option is checked so that the emulator starts up faster the next time.
Related
I'm using Windows 10 64bit.
So I downloaded Android SDK for a project I need to do for college, and when I'm installing everything goes fine, until (what seems to be) the end.
When it's about to finish I get a blue screen saying something like "error occurred, collecting crash info, we will restart the computer for you when finished" or something like that. Below that it says something like "WHEA_UNCORECTABLE_ERROR". Also when it finishes collecting the info (it gets to 100%) it doesn't restart like it says it will, I have to shut down the computer my self and turn it back on.
Does any one know what is going on or how to fix it? I'm kind of screwed if I don't find a solution fast.
Thanks in advance.
You can try the following:
-Run the installer with compatibility mode for windows 7/8
-Re-download the SDK to avoid corrupted files in the installer
-Download the Android SDK from another source, or a different version of it.
If nothing works out, it might be a problem with your computer, which would require more research to specify whats the problem. You can try to run the Windows Recovery Tools to try and fix it.
My device is no longer allowing me to install apk files manually. The install screen shows up like normal, only it will not allow me to click the install button. I am allowed to click the cancel button, so the screen is still responsive and not lagging or frozen, but there are no error messages or any kind of UI element telling me what the problem is.
I've previously installed apps this way and I can't think of any settings I've changed since, especially not the kind that would break this. Any advice would be greatly appreciated!
Running Cyanogenmod 10.2/Android 4.3.1 (Jellybean), install from unknown sources is checked. Screenshot below:
Try these steps:
1). Goto the package installer app and clear data and then try to install the app.
2). Boot to recovery, wipe cache and dalvik cache, reboot and then try to install.
If you are able to install from playstore then this should fix your problem. I hope it helps.
So I finally figured this out. I was searching around and found someone with the same problem here. Their problem was Talkback, but I started experimenting with closing my running apps and Twilight turned out to be the culprit. Not sure what Twilight had to do with this...but can now install from unknown sources again.
NB: It's enough just to pause Twilight, you don't need to uninstall/disable/clear cache or even force stop it.
I am facing this problem from many day,i searched a lot but not found any convenient answer.
Whenever I start a emulator ,after some time when I see DDMS its show the emulator online but its File Explorer is show nothing . Its visible again when I restart my emulator again or restart Eclipse .but I dont want this ,I want a quick solution.
One more thing I have already set the device timeout to a higher value but its also not working. Here is Screen Shot of my DDMS .Can anyone have a Quick Solution.Thanks in advance.
I see that the question was posted back in 2013 so there was probably some other problem at play then... but for those seeing this problem today it's probably because of an issue with Emulators targeting Android 24 or 25. Currently it appears that the Android Device Monitor is not able to display the file contents for Emulators targeting Android 24 or 25. It is however able to show file contents for Emulators targeting Android 23. Try launching an Emulator targeting Android 23 and you should see the Emulator's file contents in the File Explorer tab as expected.
I've created an Android bug report here.
Edit: a couple more bug reports about this here and here.
from command prompt move to \sdk\platform-tools\
and type
adb kill-server
and then
adb start-server
I fixed it by the following steps: 1. Open windows task manager and kill adb.exe process. 2. Close eclipse and restart it. Then it works.
Hope it helps.
But i cant understand about online emulators. Do you mean virtual devices ?
What you have to do is first launch the emulator ,then go the Window->show view -> other -> Android -> devices.Then you will be able to select the device that is online,now go the file explorer,which which will show all the files related to that specific device.Another point need to be noted here is ,the files in the file explorer varies from device to device
You have to keep the device selected in the devices view.
I'm using the Android emulator running API version 15 from the SDK tools and in the console I'm getting this error:
[Date - Emulator] ##KBD: Full queue, lose event
I can't click on anything obviously. I googled it and the only solution is to delete the emulator and recreate it. This works for a while but then I have the same problem again.
Does anyone know what causes this error and how to fix it?
You can try the following to clear the old data and applications (your emulator will return to its default settings and data)
Tools --> Android --> AVD Manager
Then select your Emulator
From Actions column hit the arrow and select Wipe Data
I was facing same problem, There is Nothing RAM problem.
Solution is here's
Go to Tools -> AVD Manager ->Find the emulator which you are having this error -> Right click on your emulator and click on COLD BOOT NOW.
i probably figured it out. try this:
While creating the android virtual device, you must have given its size in KIBs or upto 32 mibs as shown in one of the tutorials on web.
now delete the previous device and make a new device giving its size as 512 MIB. It solved my problem.
Hope it'll work for you also, just give it a try.
I have ran into the same problem and I realized that I had dedicated only 256 MB of RAM for the virtual device. It had simply run out of memory.
Here's the solution:
-Go to Tools -> Android -> AVD Manager
-Find the emulator you are having this error on.
-Click to the "edit" button next to it. (In 3.0, this appears as a green pencil)
-Click "Show advanced settings"
-Scroll down and assign some more RAM to the device, 1GB should cut it, 2GB is definitely enough if you are running a simple app. I would also recommend assigning 512 MB of heap.
-Hit finish. Exit the emulator and restart it.
You should be good now, I hope it's been helpful. Happy coding!
this is a bug in android emulators. i also had the same problem. use 64bit linux for development to minimize such issues.
** freezing problem is there on 64-bit linux machines also, but the frequency of such problems is highly reduced. also emulators behave notably faster.
Sorry, I don't know whether this will help you... I had many problems when I try to run the emulator in Apple Mac mini. Whenever I run the emulator, machine asked me to restart. When contact Apple support, they told me it's a problem with less Memory. Just check and see how the memory is utilized by the emulator.
This is a common issue if you not provide enough resources to your virtual device or your virtual device is stuck some how.
Any one of these solutions should work
if you don't have anything useful in your virtual device, you can wipe it. by simply going to
Tools > Android > AVD Manager
Then select your virtual device
Right click select Wipe Data
Each time you start a virtual device it maintain state and pre installed apps in its memory so a cold boot will also be a good option.
to cold boot simple follow first two steps from above and select Cold Boot Now.
Now you are good to go!
I have a problem with the Android Emulator and its SD card. I am developing an application that writes files to /sdcard. Everything works fine, until I exit the emulator by clicking its close button. After restart the files are empty (size 0), but still in the directory. Of course, they have not been empty as long as the emulator runs.
This looks like a failed sdcard unplug, like with usb stick. But I am not sure, how the emulator treats the card exactly. I am starting the emulator from Eclipse, and get an error at exit, when I close the emulator.
The problem did not exist before I updated my Android plugin. I could use all my files after restarting the emulator. Moreover, the problem does not occur on the real thing. I am using the most recent Android stuff, and Eclipse 3.5.
I already tried deleting my emulators and creating a new one. I also tried shutting the emulator down with the red telephone button, but that did never complete. Of course, my app is not a service and has no threads pending at shutdown.
Any ideas, you friendly people out there?
I am currently seeing the same problem on mine using an API 4 emulator, but putting the apk on my actual android device it works fine. It only happens if I close the emulator and restart using "Debug As" or "Run As". My current workaround is to start the emulator before running / debugging my app... not shutting down the emulator prevents this from happening, although I wish I had a real fix.
The problem went away by itself. I have no idea, what caused the healing. I did not do anything particular. I just continued working.
Thanks for your attention.