My PC becomes unusable with high CPU usage every time when I close an Android emulator. At least two of the 3 monitors are automatically put to sleep (as if the video cable is unplugged) in this case. The only way to get out of it is resetting the computer. I waited as long as half an hour for the finishing of closing the emulator to no avail. It is an x86 emulator using HAXM.
Related
I try to run my app in android emulator. From the begining, everythigs works fine. I create new device in Android Vrtual Device Manager, then i run the device. After a while i can see an emulator with mobile skin - that's all, nothing else happens. The device has black screen and in the Android Monitor I see this:
screen from Android Monitor
When i try to run my app I recive this:
screen from selecting deployment
When I try to run app from this window, somethig is going to happen. I have to wait long long time but finally, android is started on the device but meanwhile i recive error "Session 'app':Error Instaling APK. Sometimes app will run, sometimes not, but everything works very very slow. When i run app directly (without running device from AVD Manager), app is bulided and then i see a process "Waiting fro target device to come online", emulator runs but with black screen.
I have no idea what to do now. I reinstaled Android Studio twice - always the same result.
I have to add that a few days ago everythings works perfect - very fast and without problems. Recently I was installing Ubuntu on a new partition, I've done some changes in widows driver manager. Maybe this is a reason?
What I should do now? Thanks in advance
Each time I wake up my host computer from hibernate, Visual Studio Emulator for Android keeps old time (the one from hibernating moment) - so I'm forced to re-run emulator to keep it actual. Any chances to workaround this?
I using AMD processor. I have installed everything related to eclipse perfectly. But I'm unable to start the emulator. program is hang and keep waiting for adb forever. The same issue in android studio also. Please give a solution.
I'm using a Android Studio on an HP x360, which is a nice little laptop but has a puny processor:). I spent ages getting the Intel Hax virtual machine thingy installed on my machine, as well as configuring bios (which I found AVAST blocked changes to, so had to uninstall it).
After probably hours this week (I'm new to Android) waiting for the emulator to do it's thing, start up, load program, and eat memory, I decided to plug in my phone (Moto-e).
This has made a massive improvement! Only takes a minute to compile and run now! You also have piece of mind that your app will run in the real world.
So as a newb to Android, I'd say don't bother with the emulator.... plug a real device in.
See here for setting up HAXM, if you have trouble installing, it may be antivirus etc blocking it....
Intel HAXM
All the best.
try these threads Virtualization threads
While doing programs I normally use AVD Manager to open the emulator, but nowadays while I am running a program a new emulator is being opened automatically, it also takes a long time almost 10-15 minutes. Can somebody please help to avoid this problem?
If ou press run in eclipse and it cannot see a connected device, sometimes devices/emulators fail to connect to the adb daemon so even if they are open they are not connected it will automatically launch an android emulator to fulfil the request which will be the default emulator in the AVD list. The reason it is slow is because you are using an arm image and that emulator is just really really slow, what you will want to do is set up an AVD to use an x86 image, you might need to download this through the android sdk manager first if you haven't already and then follow the information at: http://developer.android.com/tools/devices/emulator.html to get it set up to work as fast as possible (HAXM, graphics acceleration etc)
Just starting with Android development. Have installed Android SDK several times on a Windows XP machine following several sets of online directions and can't find the answer to my problem.
When I launch my AVD from AVD Manager, the emulator appears followed by 3 Java console windows. The Java windows close leaving a white rectangular area over the emulator and I'm left with the hour glass icon. It hangs at that point. I've let it run for a long time (~30 minutes) to see if it would ever get its head out of its butt, but no luck.
Any ideas?
This has happened to me a couple of times, and the solution -as bleak as it may be- was always to try it again. So I start the emulator, it hangs, I kill it, and start it right away. Most of the times it DOES work after this "have you tried turning it on and off again" method :)