i'm using Android Studio 2.3.3, and I'm having a issue. The emulator doesn't open. No signal, nothing. It just don't show me anything. When I try to open, it just load the bar in screen's bottom and disappears. Don't open any screen, any window, nothing.
I already tried to delete all SDK and reinstall, but didn't work.
Can anybody help me?
(I was using Android Studio 3.0 Canary 5 before it, if it helps).
EDIT:
I'm using Windows 10 64bit, 8gb RAM, Intel HD graphics 520, Intel Core
i5-6200U
I already had delete my AVDs and recreated. I also uninstalled and
reinstalled all the SDK, including all the tools, emulator and
anything else (as showed in the pic).
I want to run x86.
sdk
avd
Create a new simulator and see if it works.
I had the same Issue... maybe it happened after updating some build tools ..
It worked For me.
Related
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'm just new with Android Development, and running the default blank project. I have Android Studio 2.1.2.
The problem is the emulator stuck with the black screen although HAXM works well:
"HAX is working and emulator runs in fast virt mode"
Most solutions suggest to uncheck "use host gpu" in AVD Manager, yet it seems this feature no longer appear in the new version of Android Studio.
I run macOS El Capitan.
After an update to Android Studio this weekend (maybe Gradle?), the AVD emulator (Mac) suddenly started showing a black screen when I ran my installed app APK. Sometimes it showed a blue screen. Sometimes the emulator even showed a page of installed app icons. Sometimes upside down. Sometimes upside down and reversed! That smelled like a graphics problem.
Thanks to audio in my app, I realized I could still activate buttons in my app by clicking on a specific location of the black screen. Definitely a graphics problem.
Based on other ideas that I read, I edited my AVD device config in the Emulated Performance section, to change Graphics from "Automatic" to "Software - GLES 2.0".
It worked for me on the emulators for Nexus 9 and Pixel XL on API 25.
This solution does not work on Play Store-enabled devices because the Graphics setting can't be changed. For example the Nexus 5X API 25.
Environment: Android Studio 3.0.1, Gradle 4.1
Increase the RAM size to 2.5GB in Advance settings of Emulator. Black Screen will be gone.
It worked for me
The reason why I got stuck with black screen in the emulator is that I needed to update my Android SDK Tools. Hope this could help someone get the same issue.
I believe the emulator was updated in studio 2.1.3, can you update and see if you have the exact problem?
download is here, 2nd set of links:
http://tools.android.com/
Selecting CPU/ABI with Intel Atom(x86_64) (when creat a emulator or editing a emulator) worked for me.
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
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
I am trying to run the Android emulator on a 64 bit Windows 7 machine. I have installed the Android SDK, JDK, Eclipse, and the Android plugins for Eclipse. From the SDK Manager, I have installed the Android SDK Tools, as well as all of the files for Android 4.1 (API 16).
From Eclipse, when I want to open the emulator I select the AVD Manager and click on a device that I have created. The AVD Manager says that the virtual device is a valid device. When I launch the machine, a box pops up that says "Starting Android Emulator," and there is a loading bar right below it. The bar will get to about 95%, and then the box will disappear and nothing will happen. There will be no errors and no messages in the console output box in Eclipse. I get similar behavior when I try to launch the emulator by running an app from Eclipse.
I have tried uninstalling and reinstalling the SDK to a new directory, as well as downloading a different version of Eclipse (I am currently using Eclipse Java EE, earlier I was using Eclipse Classic 4.2). I also tried downloading the API 15 platform and using that as a virtual device, and I still have the same issues.
I have checked my task manager, and the only new process that is ever created is adb.exe, and this only happens when I try to run my app, but not when I start the emulator on its own.
Any idea what might be causing this, or what methods I might use to troubleshoot this that will actually give me some kind of error message, rather than just disappearing and not doing anything? Thanks.
Edit: When I try to run the emulator from the AVD Manager directly, I get the same behavior as when running through Eclipse (loading box pops up, then disappears, then nothing).
Try to use BlueStacks emulator instead standart. It work much more faster and reliably. You can download it from http://bluestacks.com. After installing reboot the system. I think all be fine.
I had the same problem. Enabling Host GPU emulation worked for me.