Re: Black Ops 2 Android
Brandi Baylon
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.
I am just trying to start development in Android.So, the problem is that when I try to launch an emulator by issuing the command emulator @A2, an emulator comes up on the screen. But even after waiting for as long as 2-3 hrs, all it shows is a black screen. Not even the Android home screen or the Android logo. Just a black screen. And while initially "adb devices" shows the emulator as offline.after 2-3 minutes the list of attached devices becomes blank.
Additional notes:My system is a Windows 7 (64 bit) machine. Earlier I had installed 64 bit version of jdk, but the problem was present that time too. Now after searching on internet, I uninstalled that and installed 32 bit version of Java. But, again no use. One thing, though, this 32 bit version of Java (jdk 7 update 3), first install jre as part of jdk installation and then installs jre 7. So now I have 2 folders: jre and jre7 in the C:\Java32BitInstallation directory. Could this have to do anything with my emulator not turning up. Do I need to specify additional environment variables or modify the existing one?
The latest Android Studio version does not have this option anymore.If the problem persists try to switch between the values of the "Emulated Performance" dropdown in the Verify Configuration dialogue (if available) or refer to the Configure Emulator graphics rendering and hardware acceleration.
I had issues with getting the larger devices to emulate (Nexus7 and 10), while the phone sized emulators worked great. Would just keep getting a black screen with nothing for hours with the tablets. What helped was actually the OPPOSITE of what most people here are recommending: after setting the tick box for 'Use Host GPU' and setting the target to the highest android (4.4.2 at the time of this writing) the 7 and 10 work as expected!
Have you tried the power button :) ... it really worked for me. Actually emulator saves the device state before closing so at the last run if you switched off the device & closed the emulator then in the next run it will load previous state & display switched off phone aka blank screen. Although there might be many other causes of this issue.
HAXM driver does not support emulating a 64 bit system image on Intel systems based on Core microarchitecture (Core, Core2 Duo etc.). All systems based on Nehalem and beyond are supported. (Corei3, Core i5 and Core i7 machines).
I spent a day trying to figure this problem out when I came upon this quote. The only thing that works is to use the non-x86 version of the latest OS (e.g. Lollipop Android 5.0.1 armeabi-v7a) in your AVD
Make sure that you've installed the latest HAXM revision. I had the same blank screen problem with version 1.0.1 while 1.0.8 was already available. The installer can be downloaded via the SDK tools, to actually install the module you would have to execute
I'd recommend creating a new device using one of the default "Device Definitions" available in the AVD Manager. It's as easy as highlighting the device type you want in the "Device Definitions" tab and clicking the "Create AVD..." button, then filling out a few details. I'd start by adjusting "Internal Storage" to around 8GB and (maybe) an "SD Card" of 2GB while leaving everything else the same. Try starting the device and if you see "Android" pop up onscreen you're running. The first boot usually takes awhile so just hang on and watch Logcat for any issues (the "DDMS" perspective helps here).
If you still see a black screen with a default device definition you've got problems elsewhere that are causing the device to fail. Digging through logs may be your only chance if that's the case. You can always try re-downloading the ADT and re-installing the SDKs if nothing else works.
The goal here is to get you up and running with a (very) basic device, so don't shoot for uber impressive specs at this point, just shoot for trying to make it run. Once that happens try adjusting the settings one-by-one until you have it spec'd out the way you like. Just keep in mind that the emulator has its limitations and its no substitute for a real device (Although it works most of the time ;)
Actually, while the emulator booted ok, it crashed after opening an app. So the emulator team must have disabled hardware graphics for a reason. Unfortunately, it appears to be impossible to get the emulator to work.
I also had the same problem. I figured out that the HAXM hardware accelerator was recently updated but not reinstalled since the update manager just updates the installer package which get saved to your hard drive. You will need to remove HAXM and then run that installer package to complete the update. Usualy this gets installed into ANDROID-SDK-ROOT\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager. Where ANDROID-SDK-ROOT is the location where your android sdk is located.
I use Microsoft's lightning fast Android Emulators utilizing Hyper-V, and I had the same black screen for every Android emulator that I created no matter how I set the GPU Mode (auto, host, mesa, angle, swiftshader, off). Though my situation is apparently different form that of the OP, I thought it might be useful for those using Microsoft Android emulators and coming here after searching "android emulator black screen".
As of today (2019-02-01), Android emulators would have this black screen problem if you have a fresh install of Visual Studio 2017. VS shows notifications automatically for updates of NuGet packages, extension tools, etc., but NOT for Android tool updates. You have to check and update them manually.
I was having this problem after I got the blue screen of death while running my emulator. Here's my solution (for Windows at least). My solution is too completely re-install the AVD. The problem with the normal un-installation process for Android Studio is that it doesn't remove everything, so if your AVD files are corrupted, they will remain corrupted on re-install.
Another source of error could be the length of the PATH system variable (on Windows systems). Running intel based images with a PATH variable longer than 2047 characters, seems to pass an empty value of this variable to the console / emulator, so it cannot start correctly.
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Hi ! My spotify premium account used to work fine on my 4.2 Android on my Blu Life Min smartphone but suddently it would't open a and it only shows a black screen. I tried to uninstalled it and install il again and nothing ! Besides, I tried to update my ANdroid but it says that everything is updated...The SD card is internal...I deleeted cach...can anyone help me? I'm paying premium for nothing ! Thanks
The Spotify app needs at least 500 MB free space for it to run smoothly. If you have enough space and the Spotify is showing blank screen, try restarting your device first before accessing the app (a couple of seconds will do).
If the screen is still blank, you may want to coordinate with Spotify to see what else can they recommend in your situation. You can reach out to them here, on Twitter with the @SpotifyCares handle, or on their Facebook page.
I have exactly the same problem as manatop and nirwanda360. My phone is also a Xiaomi Redmi Note 3 snapdragon, 2GB memory and 16GB, though I'm running Android 5.1, or MIUI 8.0.5.0(LHOMIDG) to be more exact. Until yesterday Spotify was working fine and suddenly I have a black screen when I'm trying to open it. Here is some stuff I did trying to fix it:
Hi i'm having the exact same issue on my Mi Note Pro Running Beta Miui 8. It was workng perfectly until yesterday. Really don't want to have to wipe phone. Hopefully there will be a fix soon. Are spotify aware of the issue?
unfortunately I ran into a problem when trying to play certain episodes on my android devices (Tab S7plus and LG Vevlvet). When playing this exact series every episode has a black screen but I can hear the audio track. I can't replicate the same problem with other series or movies. However it happens with both my mobile android devices (which is a bummer because those are my main way of consuming content). The same episode works flawless on the webui or if I enable an external media player on android. I have attached the Log File from the webui. I hope that's the right one.
I don't know if it helps at all - but on the external display basically everything works except the video itself. The GUI / program prior to starting the video works all normal on the display - and even during the video - the controls/overlay and logos all display, just over a black screen.
I have the same problem... I just installed the latest Beta-Version on my Synology and looked if there is a later Version on Google Play. As long as I'm watching on my build in screen, it works, but as soon as I attach a monitor to it, the video output stays black. I guess it's quite common as it's not the first smartphone with that problem, maybe it's also cause by Samsung DEX as both were from Samsung. The Screens I used were NReal Air Glasses and ViewSonic TD1655. Both are connected via USB-C. But using HDMI via a Docking Station, doesn't matter. (The problem persists even without said station in between)
59fb9ae87f