The Windows 10 references there are to minimum versions. There aren't any significant differences in enabling or troubleshooting hardware acceleration between Windows 10 and Windows 11 or between VS 2019 and VS 2022. If you've gone through those and still need help then I recommend opening a support case and somebody can work this out with you one on one.
The documentation I linked walks you through enabling and troubleshooting hardware acceleration, assuming that you have a system that supports it. Without hardware acceleration, emulators are generally unusably slow. You wouldn't get as far as you have if you didn't have the Android SDK and emulator installed - whether they were installed by VS or you installed them separately and pointed VS at them, VS doesn't build Android apps without the SDK.Īs yagmoth555 points out, the error you're getting is that the emulator is running unaccelerated. This time the emulator this time gave an error that I could see:ĭevice error: Could not get emulator name after starting AVD pixel_5_-_api_30 = Deploy: 0 succeeded, 1 failed, 0 skipped = = Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped = Ģ>C:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE -no-boot-anim -no-accel -avd pixel_5- api_30 -prop monodroid.avdname=pixel_5- api_30Ģ>Emulator pixel_5-_api_30 cannot be started. The "output" shown now is:ġ>- Build started: Project: AwesomeApp, Configuration: Debug Any CPU -ġ>AwesomeApp -> C:\Visual Stuido Stuff\XAMARIN\AwesomeApp\AwesomeApp\bin\Debug\netstandard2.0\AwesomeApp.dllĬ:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE -no-boot-anim -no-accel -avd pixel_5- api_30 -prop monodroid.avdname=pixel_5- api_30Įmulator pixel_5- api_30 cannot be started.Ģ>Starting deployment to pixel_5- api_30.
I then closed the emulator and restarted the app. I have not installed HAXM at least knowingly. Emulator is "running" that I can see in that there is a sim phone on my PC.
0 kommentar(er)
