I am using android studio 2.3. After I updated my android sdk to the latest version, I noticed that my emulator stopped working. When I try to start the emulator it says "Waiting for target device to come online". But it goes nowhere and the emulator never shows up. After reading some posts, I installed some extra libraries Intel and ARM apis for each version of Android like 5.0, 6.0 but still that did not work. Restarted my machine, IDE, invalidated caches but that did not help.
Try rebuilding your emulator. I had a similar issue when I updated to an earlier version (2.2.2), and removing and rebuilding my emulators did the trick after installing the appropriate apis and packages. Hope this helps.
Related
I just upgraded my android studio to 4.1 version:
And tried to run some project on this emulator:
And for some reason, this specific emulator is crashing my android studio, I have noticed that I am getting an error:
After reading about the subject, I uninstalled "Riot Vanguard" but it did not solve my problem.
More info (and partially solving the problem ) can be found in "Update" at the bottom of the question.
In addition, moments after my android studio will get closed I will get a windows blue screen (happens every time).
I didn't have this problem earlier with android studio below 4.1 version, why is this happening?
Update (problem solved for others emulators)
I have run into the same problem on other emulators as well, but I could open those emulators so I could fix the problem:
Solution 1
According to most threads that I have run into, You will need to disable or uninstall "Riot Vanguard":
Open task manager, go to the startup tab, right click on Riot Vanguard, and press disable
Solution 2
If step 1 didn't fix the problem you may want to enable developer mode on your emulator.
For some reason with android studio 4.1 android studio could not find the emulator (It will tell you that there are "No connected devices") without enabling the developer mode
Before Android studio 4.1 version I didn't need to enable the developer mode to run projects on emulators and this is what solved the problem for other emulators for me.
BUT
Although I don't have any problems with other emulators at all I still can`t even open Pixel_3a_API_30c68 emulator without it crashing
How can I fix this problem on the specific emulator?
Update 2
The problem still occurs even After updating android studio to 4.1.1
Without having "Riot Vanguard" I also could not run any emulator in Android Studio since I upgraded to version 4.1. After some hours I finally found out what caused the problem (in my case):
"Android SDK Tools" have been replaced by other SDK tools (which ?) and is obsolete now. As soon as I UNINSTALLED "Android SDK Tools" the emulator worked again.
I would be interested to know if the java version makes a different. I moved from Windows to Linux because of problems running the emulator.
Linux worked great until I moved to Android Studio 4.1. So check java and it was version 11. Changed to java8 and it worked straight first time.
Seem to remember there was a setting in Android Studio to set the SDK which I think was version 8. But can no longer find this in settings in Studio 4.1.
Updating to the latest system image of the SDK helped me.
I am working with Ionic Cordova project and trying to run emulator. I am using trial version of windows 10 pro, till now didn't put license, it is trial only. though Android studio, Java sdk, and Android-SDK installed correctly but when trying to start emulator (for a correctly created virtual image) it is failing to start. It is visible for 1 seconds after that it is never visible. In-fact event viewer also not showing any error log. is it due to trial version of win 10 pro? I have no clue why it is happening?
I have tried by both installing hyper-v and once unstalling hyper-v, but none worked. I am not sure if hyper-v feature should be on or off. What is correct way?
How did you install the emulators and SDK exactly? What Android SDK version is the emulator based on? Are you really using Visual Studio and the Tools for Apache Cordova? What VS version, cordova and cordova-android versions?
If you see emulator icon, but don't see window, just recreate emulator. This is because of bugs with emulator position (when emulator window is off-screen).
Anyway, try recreating virtual device
I am new to Xamarin and ran into immediate trouble while doing a basic Hello World example. When I click Debug, the Android emulator starts but never finishes even after 20 minutes. The emulator just sits on a black screen. I never see the Android boot sequence. I can build the solution with no errors. I can also open the emulator by itself through AVD without any errors. My laptop is VS 2017 Community, Win10 Fall Creator, i5-6200, 8GB RAM, GeForce 940M, and 50GB free on SSD. I have tried:
Reinstalling VS
Reinstalling Java SDK and Android
Updating Android SDK packages
Changing registry location of SDK
Turning off Fast Deploy
Creating new AVD's
Try updating your SDK's its under Tools > Android > Android SDK Manager.
This happens to me before, i did reinstall only to find out it was the emulator issue. to avoid yourself in reinstalling the visual studio and save you time... you can try it on your actual android device. then let me know how it goes. hope it helps.
After wasting many hours on this, I finally can across the answer. You can't use the standard AVD and SDK managers. Google removed support for them after SDK Tools version 26.0.1. https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/
If you need to make an Oreo 8.0 or 8.1 emulator, install Xamarin Android SDK Manager. Caution, this will prevent you from using the built-in AVD and SDK managers. From then on, you will use this new SDK manager and the command line to create and launch AVD's.
I am using a MACbook. For one specific emulator its always showing offline. The emulator has a nexus 5 skin and is a api 24 build. When i try another emulator its fine and works. i tried re-creating the emulator. when i run adb devices it says the "unauthorized".
I tried the following:
I went into the developer settings of the emulator and allowed usb debugging if to see if that would help but it did not. this happened after i updated android studio to 2.3. i also tried to wipe user data from emulator. What is going on here ?
UPDATE: THIS IS OCCURRing for my other emualtors above api 22 also . i had to switch to genymotion for now which seems to work fine and shows as online. it has something to do with updating android studio. after i re-installed studio and did not take the 2.3 update, the problem was resolved.
Don't know the exact issue but it appears there are some bugs/issues with the latest updates.
Personally I am seeing my tests fail when run by ./gradlew commands, but not when run via Android Studio IDE.
I experienced your offline issue as well, I found I could at least rectify this by running:
adb kill-server
adb devices
More info on this in another post:
https://stackoverflow.com/a/21330228/5096103
-- UPDATE --
After investigating this one a little more, I found there to be compatibility issues between Qt version 5.7.0 which the new emulator uses, and Ubuntu 14.04 and it's version of Qt. Whatever system you will be using, you will have some version of Qt installed.
I'm guessing this may be the cause/related to the issues you are experiencing.
I was successfully able to fix my system by downgrading the SDK tools from version 25.3.1 to 25.2.3. I don't get the speed improvements of the new emulator, but at least I can run my tests reliably.
Going to try resolve the issues between Qt versions, and will update this if I can get the new emulator to work correctly again.
I had the same problem. I solved it by turning on USB debugging after unlocking developer options of the emulator by clicking 7x on the build number.
I am using Android Studio 2.0 Stable version. Whenever I click on the play button on the device to run it shows starting AVD progress in android studio and after completing it's progress nothing happened.The app window remains as it shown in screenshot and the emulator doesn't start. I can't find a solution for this issue. I have already tried many solutions which I found on the internet, changing HAXM version android SDK update, changed target API's. But nothing works.
Try edit AVD Settings -> Emulated Performance -> Graphics. Set Software - GLES 2.0.
Installing the Android Emulator (marked in to the image) solved my problem. If still you face face problem install API simulator and DHU emulator too. But only AE will solve the issue I guess.
I had exactly the same issue.
Windows 7 Professional SP1. Installed Android Studio 2.0, new HAXM ver 6.0.1 and updated to all new components like SDK tools 25.1.1.
When started - emulator do not shows up any window. 'emulator.exe' runs in the task manager and eats 25% of CPU.
Deleted all AVDs, re-created new; used AVD Manager directly; used ARM/Atom images (with/without HAXM); tried AVD with different API level - nothing helps.
Reverting to Android SDK Tools 24.4.2 helps - I can run emulator as usual - so, looks this is not the issue of new HAXM 6.0.1.
After day fighting finally got resolution:
I have removed C:Windows\System32\Wbem from system PATH variable.
I had the same problem. I just created the AVD with 768 MB RAM and it did run fine!
I have the same issues as you. I upgraded Android Studio to 2.0 stable which also updated the Android SDK.
I believe this issue is more of an Android SDK issue since using the SDK's AVD Manager directly I can replicate the issue.
As another data point, I've also modified the Virtual Device to only use 768MB RAM, to no effect. The Task manager shows the emulator using 2 threads and 13% CPU no matter how long I leave it running, but no window ever appears. I've tried with and without the HAXM. My virtual devices are running API level 21 (x86_64) and 19 (x86).
I've also reinstalled both Android Studio and the Android SDK without any affect. It could be a configuration issue due to the 2.0 and SDK upgrade, a broken SDK release, or something else entirely.
Reverting to Android SDK 24.4.1 allows the Emulator to start working again, but without the 25.1.1 functionality.
open cmd
type set and check if you can see C:\Windows\System32\Wbem in PATH variable
go to Control Panel -> System (on the left)->Advanced system settings -> (button at the bottom) Environment variables
Either in user variables (or more likely system variables) in variable PATH remove
%SystemRoot%\System32\Wbem (or C:\Windows\System32\Wbem)
restart studio
I stumbled upon the same problem. I checked SDK manager, turns out emulator has not been installed. After it's been installed, emulator start showing