So here's the issue:
Regardless of which Android device I choose, my emulator always looks like the screen's been scratched. When I try to run my app, the screen then becomes so distorted and scratched that it's unrecognizable. I have tried, what I think to be, everything including: deleting all android studio files and redownloading the application and wiping data of each emulator. Regardless of what I do, the screen still ends up looking like that.
Here's the details of my emulator:
I'm using a OSX Yosemite 10.10.5.
How do I fix this?
I had same issue and finally just solved it
try to install Oreo system image (API 27) and use it to create new AVD insted of API 28
I had the same issue with Pie in the emulator. I went to the AVD Manager, clicked Edit for the Pie AVD, clicked advanced settings, found the Graphics and changed it to 'Software'. Then it worked!
Well that is strange indeed. Does it happen with emulators from all API levels?
Have you updated your Android SDK tools to version 27 already? Also, check out the Android Blog post with important SDK tools release notes to help you with the emulator setup. Emulator installation is becoming more and more cumbersome in each SDK release and API level, now they even depend on your type of processor... anyway, if you follow the instructions it should eventually work fine.
Related
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'm using Xamarin Studio and Xamarin Android Player on my windows 10 PC.
I'm having trouble starting Lollipop/Marshmallow (API 21/23) devices using the XAP, but on the other hand, launching Kitkat (API 19) works prefectly.
I've downloaded the required android SDK, tried reinstalling everything again and again but nothing works.
It seems wired, because it is not a problem with Virtual Box, nor with my PC or my XAP installation (if it was, than why Kitkat works?).
I've tried every solution I could possibly find, but nothing works.
Any ideas on what could cause this problem?( If further information is required, I will be happy to add :)
EDIT
It does not matter whether I start the devices through VS/XS/XAP. It all comes down to the same problem, but for the sake of simplicity, let's say I'm running them directly through XAP. Here is a screen shot of what happens when I launch Lollipop (which is API 22, and not 21, for a strange reason) :
For like 5 minutes, the following occur:
Than, forever:
And after a few hours it says booting or something like that, and than restarts to the first position.
With Kitkat, it just starts :).
you probably missed the intel HAXM update.. may be a possible duplicate: Android 5.0 (API Level 21) AVD not launching Intel Atom x86_64
First off, it's difficult to determine the problem without more information. Please list or screenshot the build error(s) you receive when you try to debug your app on a XAP emulator.
But on a hunch... within the past week, I had a problem with similar symptoms. In my case, I had to update project packages in order for my Xamarin Forms project to run on the higher Android APIs.
Reference on how to update packages: https://developer.xamarin.com/guides/cross-platform/application_fundamentals/nuget_walkthrough/#Package_Updates
It might be that hyper-v is causing the problem: "VirtualBox and Hyper-V cannot co-exist on the same machine".
Try to disable it using bcedit as explained in the link.
For further reference, see this discussion
After launching xamarin android player, manually launch virtual box.
You should see the device listed on the left. There is a good chance it will say "stalled." If it says anything other than "Running," try reseting it or starting it.
I also had problems with XAP and my solution was to use Genymotion instead.
Did you try Genemotion
I think it is best Android emulator.
I would post a comment but my reputation is too low.
I don't know if this emulator works with Xamarin studio but if you use Visual Studio it may be an option for you.
Here is the solution:
I had the similar issue and fix the issue as follows.
delete the existing device simulator
reinstalled the simulator again
deploy the solution again.
I'm having issues trying to put my own apps on my phone. A bit of background information, I'm using the latest version of eclipse IDE, trying to get apps onto my galaxy s. I tried installing apps through gmail. When I go to install the app I get a parse error and it doesn't install. I have also tried using this method to install my app onto a htc wildfire s however I get the same issue. Is there a quick fix for this? Thanks for your time; any insight into what the problem is will be great.
Things I've tried:
Ok I still have a parse error when I try installing my app. The min sdkversion was set to 9 which seems right to me as that is the api level for gingerbread which galaxy s uses (i think). I haven't set a target sdkversion yet as according to the android developer guide it if not stated it defaults to the minsdkversion. I also tried setting the minsdkversion to 1 and still no luck. Any ideas?
try to check unknown source in settings==>applications if you are installing non-market application..
I've downloaded Eclipse Classic 3.5 Galileo, the last version of Android SDK, downloaded and installed Eclipse Android 1.6 platform.
I've created first (and the only) AVD with Android 1.6 and the default skin.
The log may show more:
I've filtered only neccessary messages (warnings, errors).
-http://www.clipboard.cz/63c
As you can see, my new AVD has started in 16:17 and it was still loading in 17:35...
The emulator looks like this:
alt text http://img130.imageshack.us/img130/3540/androidloading.png
PS: The restrictions about number of links for new accounts are REALLY annoying...
In Eclipse Galileo running in Linux I lowered the version of the Android emulator. In the AVD config menu I lowered the Target to 1.5. I think the project Build target API level, entered when you create a project, needs to match the API level of your emulator.
I had same problem. It was always not responded when started, tried from eclipse, directly (windows vista home).
But it work if I set compatibility mode to windows xp service pack 2 and select to run as administrator.
Try recreating the avd through the android tools gui. Helps for me sometimes...
Finally I've reinstalled the whole system (Windows Vista) and now it's working. Perhaps there was installed some bad software, which Eclipse, or sth from Android SDK do not like... ;-)
All you got to do is while creating a Virtual Device, add a new hardware -
"Device Ram Size" & set it to "512" or whatever is enough as per your requirement. Basically you have to reduce the RAM size so that your computer can provide it to the emulator. If you have already created one, you can do above steps in edit mode.