My android emulator is running MAUI app extremely slowly - visual-studio

Spent all weekend updating Visual Studio to 17.4.3. Removed my old Android Simulator -- had to clear up space for the upgrade because my 128GB SSD got filed up.
Anyways, trying out the Maui framework, run the new Welcome app on Android Simulator (pixel 5 api 31). It takes a whopping full minute just for the emulator to boot up, and then another 1.5 minutes to deploy and finally see the welcome screen.
I do not think this is normal. I spent all night trying to enable hardware acceleration on the emulator, but I believe the HAXM options was always turned on.
Any tip for how I can tune up my android emulator performance? It was really fast before my MAUI upgrade when I used good-old Xamarin.

Related

Running on Android Studio on my Mac is becoming impossible

I have a 2019 MacBook Pro 13" with a 10th gen i5 and 8 gb of ram. Whenever I try to run android studio on my Mac. My life becomes a nightmare. If I even try to change some of the preferences, it just stops responding, and the weird part is that everything else keeps running perfectly, there are absolutely no issues with any other app running while android studio is frozen I am learning how to code and use such programs and I have no idea why this is happening when I've seen people use 6-7 year old MacBook Airs to run it and it works. I have no plugins installed, just the basic out-of-the-box settings. Can someone please help me.
Android Studio freezes on macOS Big Sur
On machines running macOS Big Sur, Android Studio 4.1 might freeze when you open a dialog.
To work around this issue, do one of the following:
Go to the Apple Menu, select System Preferences > General. In the
Prefer tabs when opening documents option, select "never". Then
restart Android Studio.
Upgrade to Android Studio 4.2, currently available in the Beta channel.
As mentioned by Android Studio Itself

Macbook Air reboots on closing Android emulator

Macbook Air crashes whenever I close my Android emulator and reboots with error message. I have latest version of HAXM (7.3.2).
I don't find any proper answer on this topic but as my personal experience this happens due to extra load on memory while working on big Android projects and can be checked in memory monitor while building your app. So, now I am using real device instead of emulator and it's working fine.

xamarin studio android emulator starting take infinite time

I am using xamarin studio community edition on my macbook pro. when I try to run any sample project on android emulator it takes infinite time.
Can you please suggest. FYI It was working previosuly . Please check screen shot Android emulator error
I would highly suggest using the Xamarin Android Player instead of Google's default emulator manager.
The Xamarin Android Player is much faster and more reliable in my opinion although I have also heard that choosing different Google Play emulator images can make a big difference. Installing HAXM can also speed up the default Intel Google Play emulator images.
Download the Xamarin Android Player from here.
*Edit: Thanks to #SushiHangover for pointing out the fact that Xamarin deprecated the Xamarin Android Player. SushiHangover suggests using the Genymotion Android emulator which I have heard good things about but have not tried yet.

Basic Android App not working on Xamarin Android Player via VS2015

I have been trying to run basic Android App provided by Visual Studio 2015 via XAMARIN Android Player. Program gets build and deployed successfully, yet, App or anything does not appear on screen. Xamarin Player takes more than 20 mins to start and then nothing happens. Find Screenshots as well.
WIthin the Android SDK Manager look under Extras there is an package called Intel x86 Emulator Accelerator (HAXM Installer). Installing HAXM will increase the speed of the emulator when you use the Intel Atom CPU/ABI
Also when creating the emulator device check Use Host GPU for increaded performance.
I ran into few issues with Xamarin Android Player as well. Currently I am using Genymotion Emulator and it is much faster.
Well, Well, Well, I got my thing up and running. Following are the steps I performed:
After installing Xamarin for VS2015, I checked for latest Android SDK via SDK Manager. Got all the necessary updates installed.
Installed Xamarin Android Player and used emulator Nexus 5 KitKat API level 19.
Earlier I was using Nexus 5 Lollipop, was the reason why, it was not working. May be its not fixed for buil yet.
As, described by Mr.Pilatus in above answer, the particular HAXM things surely does help in accelerating emulator.
Got my Android app running.
Thank you all for all the necessary suggestion and guiding my in my baby steps in XAMARIN development. Gracias. NAMASTE!

Strange windows phone app crashes only from the store

I am trying to update a 7.1 app from the store. For some reason it crashes only when installed from the store and only on 7.1 or 7.8 devices. My Lumia 920 with the latest updates works fine. The app runs fine if installed from VS 2010 or VS 2012. Of course all emulators worked fine. I put a Messagebox at Application_UnhandledException and it displayed this:
The type 'MyApp.MainPage', specified in the x:Class of
'/MainPage.xaml' could not be found in any loaded assembly.
Of course the MainPage class is there.
The app uses GPS and bing map and has capabilities:
ID_CAP_LOCATION
ID_CAP_NETWORKING
Can anyone shed some light on this?
I have just solved a similar problem where I had this error message when running from Visual Studio on my phone but not in an emulator. My problem was that I had different versions of the Microsoft.Live Assemblies in my 'main' app and the Assembly which contained the 'MainPage.xaml'.
I had a weird issue where my app worked differently from the store than on my device and the emulator. In my case it was because of trial mode. Apps run as though they are purchased when deployed to the emulator or device. It worked on my device from the store too, but that's because I bought it. Any other device which had not bought it ran in trial mode, and that's why it worked differently. I am betting that is why you are experiencing this crash. If it is not then we'll need more information.

Resources