I have installed andriod studio 3.6 latest version and then configured by setting environment variables.
When i actually run virtual device Pixel 3 emulator, my PC ran in to problem with blue screen.
Blue screen error message:
Your PC ran into a problem and needs to restart. Were just collecting some error info, and then you can restart.
How to resolve this ? what is the problem ?
Just remove from windows features:
HyperV
Virtual Machine Platform
Windows HyperVisor Platform
Install:
Intel(R) Hardware Accelerated Execution Manager (HAXM)
Install Intel x86 Emulator Accelerator(HAXM) solved my problem
I had the same problem and spend a lot of time trying to solve it. Finally find what was the problem - Windows update!
This Windows patches are causing the problem - KB4554354 and KB4549949
Updating the Windows to version 1909 (OS build 18363.836) fix the issue for me.
If you can't update windows to this version for some reason you can try to remove this patches.
You can rollback and uninstall your recent update follow these Steps:
Press Start button then click on the Gear icon which is the Settings
Press "Update and Security"
Press "View Update History"
Select "Uninstall Updates"
A pop up should appear then scroll down to the bottom then on the Microsoft Windows section, right click the recent or all of the "Update for Microsoft Windows KB4554354" then Click "uninstall".
wait for the process to be finished then restart the PC/Laptop there you should have the fix on your update problems.
This is just to share my experience that the blue screen has stopped for me too, by updating Windows 10 to the version 1909.
Though it is not talked about here, I have the impression that it is related to the Microsoft's Hyper-V and the Windows Hypervisor Platform (WHPX), made available in the year 2018.
For me, the emulator was working till late last year, without the Hyper-V acceleration (I cannot be more precise. I do not use it everyday).
Earlier this year, I installed the Docker desktop, which must have turned on Hyper-V. The Windows update(s) may have come around the time (though I do not find them here. They may be part of one of the cumulative patches). Then it must have become that the emulator wouldn't work anymore.
Hope it helps others who suffer from the same problem.
i think the emulator is not working properly ......uninstall the current emulator and install trusted emulators like blue stacks ........blue stacks will work in old pc's also
Related
I decided to install xamarin the other day so I could start coding in c#. So far it's been an absolute nightmare getting anything to work. I downloaded the xamarin bundle that visual studio offers and now I'm trying to simply run a test app and the emulator won't work.
I've looked at every video online, & tried to read through as many forums as possible but at this point I need direct help before I throw my computer into the pool(jk)
I've downloaded android emulator & installed almost all the devices & made sure to install all the packages in the android sdk. I created a new device from the vds manager but I STILL get errors.
this is the message I get waiting for the emulator to start, I don't see the android splash either
still waiting
I got stuck on this for a while until the basic issue was I simply was not waiting long enough. Keep an eye on your Visual Studio build window, and watch all the slow messages as the come up.. it takes around 3-5 minutes on a blank project for the first time on a intel i5 with 8GB ram.... so the trick really in my case was to be patient. I think it gets faster second time round as it remembers some of the hard work it did the fist time to get it to work.
When you create an Android Emulator (this can be done in the Xamarin Android Device Manager in VS or selecting 'Create Android Emulator' in the dropdown on the Run button), there is an option named hw.gpu.mode. In my case (using Hyper-v), changing the option from auto to mesa did the trick, although there are a number of different options.
I just reseted the emulator to factory defaults and it worked.
Have you tried to edit the emulator properties and to check the "Use Host GPU Option"?
I had that issue too and that option solves the problem
I enabled Hyper-V acceleration based on microsoft documentations: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows#accelerating-with-hyper-v
Basically you need to turn on these two windows features from the control panel (Turn windows features on of off):
Hyper-V.
Windows hypervisor platform.
then from visual studio go to: Tools >> Android >> Android SDK manager >> Tools >> make sure that "Android emulator" version is 27.0.1 or higher, if not, you will find in the same screen a button below to update it.
I did this on windows 10 64-bit, with VS 2017 Community 15.9.5
June, 2022.
I know that this is kind of an old question, but I've had the same issue, which I fixed by updating the Visual Studio (2022).
I'm unable to launch GenyMotion from eclipse in windows 10. This is happening to me after the recent windows 10 update. The system runs into blue screen error(system service exception) and the system restarts. Please help.Thank you!
I had same issue, but I solved it. SOLUTION is DISABLING HYPER-V.
Windows button -> type Turn Windows Features On/Off -> Uncheck “Hyper-V” -> Click OK -> Wait Until Things Done -> Click Restart
Works like charm…
What version of Genymotion/VirtualBox are you using? More details will help. Also, have you tried running Genymotion from itself instead of the eclipse plugin?
Sounds to me the best solution here might simply to update the plugin, Genymotion, and VirtualBox. If all 3 are up to date, reinstalling them each might help.
Well,to fix the System_Service_Exception error in Windows 10:
Solution 1:
Try To Start The Computer In SafeMode
Windows loads the least amount of drivers and services when it starts in safe mode. This prevents most blue screen errors from triggering, and gives the user a suitable environment to fix the problem, and copy important data.
Upgrade Device Drivers To Fix The System_Service_Exception Error
Most blue screen errors like the System_Service_Exception error occur due to driver issues. The driver might be corrupt or it might not be designed for Windows 10. While many older drivers will work with Windows 10, some do not.
You can upgrade drivers by going to your computer manufacturer’s website and looking for your computer. Once you find your computer’s model, download all the latest drivers and install them one-by-one. Restart the computer if prompted to do so. You can also use a third-party software like DriverDoc to find, download, and install drivers for you.
Windows 10 System Recovery Options
The Windows 10 system recovery options are used to reinstall Windows 10 without losing user data. The recovery options can be used to reset Windows from within Windows 10, and by using a bootable Windows 10 installation or recovery, DVD or USB as well.
Press the Windows Key > click Settings
Click Update & Security > Recovery > Click Get Started under Reset this PC.
There can be other reasons for this error I recommended to check below links:
link1
link2
Hope this helps!! If you have any doubts feel free to ask..
Since I read the news about Xamarin now being "free", I immediately installed Visual Studio 2015 Update 2 and the Android tooling (NDKs, SDKs for 19-23, Visual Studio Emulator for Android dated January 2016) to start working on an Android application.
Excited I launched the emulator from Tools -> Visual Studio Emulator for Android and installed the profile that is the best match for my own phone. Since my phone is on Android 6, I decided to get a profile for API Level 23 / Android 6.
Since I had already enabled Hyper-V a few months ago, the installation for the profile only had to add me to the Administrators group and create 2 network adapters.
So far, so good.
Upon starting the emulator, it would stay at "OS is starting...". I figured I'd wait a while. I figured I'd wait a while longer too. After that, I gave up the possibility of it going to work and started investigating.
I also tried other profiles, a few others from API Level 23, one from 22 and one from 19. Only the ones from API Level 23 did not work.
The following steps are what I came up with so far by Googling etc. I tried them in all sorts of combinations:
Rebooting
Disabling / enabling Hyper-V
Removing vEthernet adapters (through the Hyper-V Manager).
Running XDECleanup
Allowing XDE through my Windows Firewall as application (incoming)
Restoring the emulator software in Programs and Features
Enabling / disabling "Processor Compatibility" in Hyper-V Manager.
This is the data I've gathered so far:
A screenshot of the error message that the emulator gives after waiting a long time (10 - 15 minutes, maybe a little longer)
A screenshot of the last part of the log when being connected to the Android 6 VM:
A screenshot of the last part of the log of a working VM (this one's from an Android 4.4 VM):
Responses I've got so far from Microsoft:
-Those errors are normal
-And the only step I've tryed which they told me to, and I don't see here, it's this one:
On Hyper-V Manager, check the option for compatibility under CPU section
Besides from this, just make sure that on Hyper-V you get only 2 switches, the one you use to connect to the internet and the one that the VS Emulator for Android creates, I haven't got any results, but if you try, maybe you will.
In my case, I was mucking around with the VS emulator's virtual switches and had the network adapters in the wrong order.
After I moved the Windows Phone Emulator Internal Switch (Created when first running the VS Emulator) to the first Network Adapter slot in my settings, the emulator started up just fine. Apparently, order matters.
Had the same problem but got mine to work after trying a lot of things from different threads.
In the end I think this did the trick for me:
I added "c:\Program Files (x86)\Microsoft XDE\10.0.10586.0\xde.exe" as an exception in the firewall.
(i also switched of the firewall, but was probably unnecessary)
Temporarly disabled the WiFi device
Uninstalled VirtualBox
Removed all Virtual Switches in Hyper-V
Executed XdeCleanup.exe
Started the emulator again and it started up successfully!
Swiched of the emulator and enabled Firewall, Wifi device.
The emulator still starts successfully every time!
Thanks to all for sharing!
If you're using Xamarin, it's recommended that you use Xamarin Player. It's not Xamarin exclusive, it's just a much faster Android emulator. I use Android Studio, and the Xamarin Player is still faster on boot and launch than the default. This is just my recommendation to you, I have no clue how to fix your Visual Studio emulator, sorry.
I've played a lot with this and realized that I have had manually configured paging file on Windows. After restoring it to default all worked perfectly without messing with the virtual switches or adapters.
Just make sure that you have all Windows memory etc. settings set to default.
Regards, Mladen
My problem was that the system image was missing for the emulator.
When I opened the android virtual device manager it had an exclamation mark next to actions(i had to download the system image via the download link).
I had the same error message. The solution for me was:
Uninstall all emulators in the Visual Studio Emulator for Android
Check in Hyper-V-Manager if there also no instances
Unistall Visual Studio Emulator for Android
Run xdecleanup.exe (C:\Program Files (x86)\Microsoft XDE)
Uninstall Hyper-V from Windows features
Removed virtual ethernet adapters through uninstalling in Device Manager
(be sure to display disabled devices too)
Install Hyper-V from Windows features
Install Visual Studo Emulator for Android again
Download and install your emulator/profile
Run the emulator and have fun :-)
It seems there was a problem with the virtual switches and Hyper-V. The correct settings for the adapter looks like these:
Hyper-V-Manager:
Device Manager:
Network adapter:
Ethernet:
vEthernet (Virtueller Switch: Intel(R) Ethernet Connection (2) I219-LM #2):
vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch):
Emulator network settings:
I cannot find an solution to my problem anywhere so please forgive me by asking this question here.
I've recently upgraded Windows 7 to Windows 10. I'm half-way through the sunshine project and Android Studio WILL not run. I've uninstalled, reinstalled, ran in compatibility mode, everything all I briefly get is the splash screen and then nothing. No trace in Task Manager. No events logged in Windows event manager. Zip.
And as for Virtualbox hosting a genymotion Nexus 7 vm, don't even get me started.
Can someone please help me ?
Thanks
MM
btw Latest version of java installed.
With Genymotion, what version do you use ?. I upgrade my window from 8.1 to window 10 and my Genymotion alway get error, I uninstalling both VB and Genymotion (completely clear reg file, delete any log file or folder in C:\user\yourPC ) and Install the last version of genymotion without Virtual Box, install last version of Virtual Box then Run your genymotion in compatibility mode "Window 7/8/8.1". But some time Genymotion can crash, Window 10 not support completely Virtualbox.
With AndroidStudio, It work well in Window 10 then I think you not clean remove it.
I recently got into Xamarin development. I have a lot of experience in Xcode making iOS apps and the iOS side was very straight forward. Now I'm trying to implement Android. I downloaded a Hello World example to get my bearings. When I run it I have no problems getting the simulator to show up (MonoForAndroid_API_10 and MonoForAndroid_API_12) but the actual application doesn't run, and does not show up anywhere on the simulator. Essentially whenever I use run or run with in Xamarin on Android, it pulls up a fully functioning, albeit empty simulator.
How do I get my application to run on the emulator?
Like the other commenters, this is most likely just a symptom of slow emulator on your machine. I'm running Xamarin-Android development on my 2010-era OSX machine in mavericks with 8GB RAM, and it is slow-slow-slow, but usable. Try to find the Intel x86 speeds improvements (look for HAXM) and you will find that the emulator will be much much faster.
And yeah, get a real handset and plug it in to your computer: always much faster than emulation.
later edit Get Genymotion for Mac OSX or for PC/Windows or PC/Linux. It's way way way faster than the other emulators. I have since found that this is as fast, or faster, than running the App on my connected Android phone. It's certainly simpler in not having to have the device plugged into one of my USB ports, and allows me to code and test on the train. http://www.genymotion.com/
Don't know if my issue was the same but finally this troubleshooting helped me to run emulator https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB.
I was missing key Android SDK Tools with string value Path in registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
I've created it manually and it worked.
UPDATE
Before I got the issue with running emulator, I couldn't see it in Visual Studio. The reason was I've installed VS Android Emulator through standalone installation, not through VS Installer. It had to be installed there as well.
I had the similar issue, and then I deleted the existing device simulator and reinstalled again and it started working.
As I use a different SDK, in my case
Go to Tools > Options > Xamarin and set the Android SDK path.
Sometime Visual Studio changes this configuration;
2020 Update:
I followed the most voted comment, however, with Visual Studio 2019 updated recently, the steps have changed a little. Here is what previously worked:
WHAT WORKED BEFORE
"Don't know if my issue was the same but finally this troubleshooting helped me to run emulator https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB. I was missing key Android SDK Tools with string value Path in registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
I've created it manually and it worked."
WHAT TO DO INSTEAD
Nothing. Don't mess with the path.
WHAT WORKED BEFORE
"Before I got the issue with running emulator, I couldn't see it in Visual Studio. The reason was I've installed VS Android Emulator through standalone installation, not through VS Installer. It had to be installed there as well."
Previous instructions image
WHAT TO DO INSTEAD
a. Go to Tools located at the top of the VS window, Get Tools and Features, go to Individual components, using the search tool in the pop up box, search "emulator", once you get the result, make sure both Google Android Emulator (API Level 25)(local install) and Intel Hardware Accelerated Execution Manager (HAXM) (local install) are both checked.
b. Close the solution(s) and restart VS then reopen the solution(s).
c. To deploy the app on the emulator, click Start button to spin up the emulator, left click on your Android project, then click Deploy. You should be able to see your app on your emulator's app menu.
Updated Instructions image
Worked for ME
Sometimes you close the android Emulator but not POWEROFF the Emulator.
this problem happens when emulator shutdown un-properly.
Restart Your EMULATOR
First start your emulator
Then restart your emulator by pressing down the power button and select restart option in your android emulator.
I enabled Hyper-V acceleration based on microsoft documentations: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows#accelerating-with-hyper-v
Basically you need to turn on these two windows features from the control panel (Turn windows features on of off):
Hyper-V.
Windows hypervisor platform.
then from visual studio go to: Tools >> Android >> Android SDK manager >> Tools >> make sure that "Android emulator" version is 27.0.1 or higher, if not, you will find in the same screen a button below to update it.
I did this on windows 10 64-bit, with VS 2017 Community 15.9.5