My notebook has an AMD Ryzen 5 3500U processor and I'm trying to use the emulator in Android Studio and I can't get it to work properly. Most of the time the emulator only works the first time it runs when it is created. Some of the recurring problems is that even when running, it does not appear in the flutter device selection. After some research I found out that the solution may be to activate two Windows features: virtual machine platform and windows hypervisor platform. However I am not able to activate because after clicking on the checkbox and giving ok. This message returns to me: "an error has occurred. Not all features have been successfully activated". Does anyone know how I can resolve to have these features activated?
I am using an AMD PC as well and had the same issue. There were drivers that had to be configured and didn't work as expected. The workaround I did was to use genymotion as an emulator. The setup didn't require major setting changes. Here is the link to it :
https://www.genymotion.com/
Related
Here are my PC Specs
Acer Aspire 5
Intel Core i3-8145U 2.1GHz with Turbo Boost up to 3.9GHz
RAM: 4GB DDR4
SSD: Kingston SUV500M8120G
OS: Windows 10
So I watched flutter tutorials...
I tried to do it with Android Studio... I installed it in hdd...
So I didn't care too much about the ram usage and the lag...
Two or three days ago, when the emulator was running, the machine suddenly froze...
After waiting for half an hour, I tried to get the task manager but it didn't, so I turned it off with the power button...
After that, I googled and said that it is difficult to run an emulator with my pc specs...
So I used my phone that day and connected it with a data cable...
Anyway, since the day of that freeze, the lap is slower than before...
The file explorer and also After pressing the windows key, it takes a while to open...
What is the reason for this???
I use Eset Internet Security...
I did a full scan of it and nothing...
I also tried the chkdsk command on all three partitions and there is no problem...
When I used Angular before, I used Webstrom...
It's not that bad as android studio, it wasn't slow...
Should I reset the pc???
There is no big case because only the software are uninstalled.....
Or should I install the android studio on the ssd...
The problem I have is that even after closing the android studio, it lags...
Even after restarting the PC, it is the same
Tell me some solution guys, it's a big help...
It is necessary to have good about of ram, 16 GB is good, less 8 GB might feel laggy.
Android studio consume more than Visual Studio Code. I will suggest you to switch on VS Code, and upgrading your component, increase the ram. Resetting Pc won't help that much. Try to kill every background process, just use vs-code. If you like to build for android use real device.
As for learning, you can try on dart.dev
I am using Android Studio 4.1.1 on Windows 10 20H2 with Hyper-V enabled on a computer with high DPI. Recently whenever I launch an AVD, the UI of the emulated device window becomes extremely large and impossible to use (as in the following screenshot). Other windows (including the AVD manager and the Android Studio itself) remains normal.
I have not used the emulator for a while, but I can make sure that the UI issue did not exist before I update my Windows to 20H2. I have also found similar questions on Stack Overflow (including this question), but the existing answers suggesting overriding its high DPI behavior does not work for me, because when I apply this setting, the emulator screen becomes so blurry that I cannot even recognize the texts on the screen.
How can I solve (or work around) this issue? Any help will be appreciated.
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy. Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86). To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot. locate the .exe file using task manager
In my case it was in this location:
C:\Users[Username]\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe
I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.
Actually I have a problem with my Android application in eclipse. When I run my program, it gives me a message which is concluded of many errors.
So I copied and pasted them here to show you what is the exact problem with the emulator. Any ideas?
Starting emulator for AVD
Failed to create Context 0x3005
could not get wglGetExtensionsStringARB
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
could not get wglGetExtensionsStringARB
Try setting the RAM to 512 Mb. It worked for me.
It may be too late to answer this question,but I solved the problem (could not get wglGetExtensionsStringARB) by installing the latest version of my graphics (video) driver.
also from device properties, I have checked 'use host GPU' option. it is working now with the following settings:
Try updating your graphic card driver
Graphics acceleration for the emulator takes advantage of your development computer's graphics hardware, specifically its graphics processing unit (GPU), to make screen drawing faster. To use the graphics acceleration feature, you must have the following versions of the Android development tools installed:
Android SDK Tools, Revision 17 or higher
Android SDK Platform API 15, Revision 3 or higher
Please check this link http://developer.android.com/tools/devices/emulator.html#acceleration
This is slightly edge case but my emulator started fine when I was physically at the computer that ran it but when I remoted into that computer (via RDP) and attempted to start the emulator, it failed with these errors.
I believe this is a limitation with the emulator software over remote connections because I went to the physical location of the computer and started the emulator and it worked fine.
I have the tools installed for windows phone 7 development.
But, when I run the any of the sample apps I have to manually refresh my emulator's app window to see any changes.
Any ideas what I'm doing wrong? Or maybe a setting is wrong?
Thanks
I've got it on every machine I've tried- but they all have various Nvidia cards (desktop and mobile).
When I posted about this on the wp7 forums, they talked about wdm 1.1 (which I've got) and so far I have no fix.
My machines are all 64bit, so I'm wondering if this isn't some issue with them or the nvidia drivers- but I don't experience any other problems with the drivers outside of the emulator.
I think we're stuck for a while anyway...