Android Studio editing very laggy after update to Arctic Fox (windows) - android

After updating to Arctic Fox, the editing is very laggy. I was trying to narrow it down to when it happens (since it's not happening all the time, but still often enough to annoy the heck out of me), so I'm about to uninstall/reinstall to 4.2.2 (I hope that's the last one I had, not sure how to check).
Anyone else seeing this? (it's not related to M1, this is on windows). Also not related to emulator (off) or database inspector afaict.
btw, no easy way to rollback a studio version apparently?

Try switching your channel to Canary and download the Android Studio 2021.1.1 Bumblebee. You can install alongside also for testing out the preview build without hindering your existing installation. The link to preview and doc is here - https://developer.android.com/studio/preview/features.
P.S. - I've tested canary and performance is super fast.

Unfortunately seems there's no way to rollback the version of Android Studio.
You can find here an archive of all the past Android Studio versions for download, and I also found this post on superuser about checking the Uninstalled programs history on Windows 7
I hope it will be of some help, unfortunately I'm on mac and can't give you any advice for the slowdown

Related

Android studio 4.1 emulator crash

I just upgraded my android studio to 4.1 version:
And tried to run some project on this emulator:
And for some reason, this specific emulator is crashing my android studio, I have noticed that I am getting an error:
After reading about the subject, I uninstalled "Riot Vanguard" but it did not solve my problem.
More info (and partially solving the problem ) can be found in "Update" at the bottom of the question.
In addition, moments after my android studio will get closed I will get a windows blue screen (happens every time).
I didn't have this problem earlier with android studio below 4.1 version, why is this happening?
Update (problem solved for others emulators)
I have run into the same problem on other emulators as well, but I could open those emulators so I could fix the problem:
Solution 1
According to most threads that I have run into, You will need to disable or uninstall "Riot Vanguard":
Open task manager, go to the startup tab, right click on Riot Vanguard, and press disable
Solution 2
If step 1 didn't fix the problem you may want to enable developer mode on your emulator.
For some reason with android studio 4.1 android studio could not find the emulator (It will tell you that there are "No connected devices") without enabling the developer mode
Before Android studio 4.1 version I didn't need to enable the developer mode to run projects on emulators and this is what solved the problem for other emulators for me.
BUT
Although I don't have any problems with other emulators at all I still can`t even open Pixel_3a_API_30c68 emulator without it crashing
How can I fix this problem on the specific emulator?
Update 2
The problem still occurs even After updating android studio to 4.1.1
Without having "Riot Vanguard" I also could not run any emulator in Android Studio since I upgraded to version 4.1. After some hours I finally found out what caused the problem (in my case):
"Android SDK Tools" have been replaced by other SDK tools (which ?) and is obsolete now. As soon as I UNINSTALLED "Android SDK Tools" the emulator worked again.
I would be interested to know if the java version makes a different. I moved from Windows to Linux because of problems running the emulator.
Linux worked great until I moved to Android Studio 4.1. So check java and it was version 11. Changed to java8 and it worked straight first time.
Seem to remember there was a setting in Android Studio to set the SDK which I think was version 8. But can no longer find this in settings in Studio 4.1.
Updating to the latest system image of the SDK helped me.

Emulator not able to run on MacOs. Emulator claims that OS is out of date

After installing the latest update today I started to get this error:
Emulator: Sorry, "qemu-system-x86_64" can not be run on this version of macOS. Qt requires macOS 10.12.0 or later, you have macOS 10.10.5.
I'm trying to emulate it on a Noxia 4. I've deleted the virtual device, and recreated it a couple times to no avail. This is consistent with all my projects. I haven't found an answer to this issue anywhere, and I don't know if it is actually out of date, or if it is just saying that. I was wondering if anyone had this issue in the past.
My reported MacOS version is correct. I'm on 10.10.5 Yosemite.
I've encountered the same error a while back. My macOs was not so drastically outdated though. If you have installed the newest emulators - they are dependent on version of Qt different that is installed in your system(or maybe there is no Qt installed at all - I am not an expert in mac infrastructure).
To fix this issue you may try several approaches.
Try to install the old version of emulator you want to use - the one that is compliant with your current macOs version. Android Studio before 3.5 can work with ancient emulators. I haven't tried with 3.5 and up though.
Try to install needed version of Qt in your system. The current version is 5.12.
Update macOs to the newest one and use the newest emulator.
I haven't tried first two, but the third one fixed my issue.
The error message is pretty clear about it:
Qt requires macOS 10.12.0 or later, you have macOS 10.10.5.
This would be DMG image, which performs the necessary OS upgrade. Later versions would also work, but this one is the least required to run Qt. The fear-mongering in that deleted answer might not be justified (fear disables logical thinking - that's why fear is not a good adviser). It's just a minor version update, which is something else than installing the next major version on yesterday's hardware. The Inkscape installer claims to support version 10.7 (which is already elder than the current version 10.10.5), so that claim might be a hoax - and even if it's true, building from source should still be possible. If still in doubt, just use the time machine to create a snapshot before applying the OS update (in terms of: better safe than sorry).
I found that I still had an old version of Genymotion (v. 2.5) lying around. I hadn't used it for years as the built-in Android Studio emulators had become much better.
But it looks like Genymotion works! I don't dare upgrading it since IT WORKS now, so I don't know how helpful this answer is to others.
This is a solution for people who need to stick around with older versions of Mac OS (OSX). The rest of the mac users should abandon all their old software and embrace the new operating systems, happy that their workload will be greatly increased. Thank you Apple!

My mac suddenly freezes while using Android Studio 3.2

I am doing the Android Basics: Data Storage course on Udacity, and I have almost finished this course, but since about a week ago while using Android Studio and doing everything that the course teaches me to do, at some point Android Studio completely freezes my Mac OS and that forces me to reboot my computer.
This problem happens at any time, literally. There wasn't anything special that Android Studio was trying to do when this happened. Many times I have been just writing some code, and it freezes, not running the project, downloading something in the app or checking anything special, it just suddenly freezes.
I am using Android Studio 3.2 (latest version) in a MacBook Pro (13-inch, Early 2011). It also happened before I update it to Android Studio 3.2, when I had the previous version I thought I could be fixed by delete Android Studio and download the latest version, but it did not work.
I have a solution for this problem.
I seem to have a problem occurs with the Java version of Android Studio crashes
So check your Java version. I think you are using JAVA 1.8
Please remove all java on your system like below.
sudo rm -rf /Library/Java/JavaVirtualMachines/jdk1.8.0_80.jdk/
then download and reinstall latest java 1.8
https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I will hope you can resolve this problem
If your machine freezes, it could be due to either you open too many apps that consume much RAM with Android Studio, hence when Android Studio needs some more RAM to operate (i.e during gradle build or instant run), the machine could not provide sufficient RAM hence, Android Studio will freeze: or your machine does not meet minimum system requirements for Android Studio, for this information, you can check the official documentation https://developer.android.com/studio/ . Also, in order to manage memory usage, have a look on this link https://macpaw.com/how-to/reduce-memory-usage-on-mac
I had something similar after updating to 3.2.
Wasted 4 hours trying to fix it and eventually followed these instructions to totally wipe AS from my PC.
How to completely uninstall Android Studio from windows(v10)
I understand that you have MacOS but it wouldn't be too difficult to locate the directories there.
For those who are looking for a solution when is using tabs just is because
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.
Otherwise, wait for the Stable Android Studio 4.2

Android AVD Emulator Runaway CPU. Fix? Anyone else having the same issue?

Android Studio 1.2.1.1 on an Ubuntu 14.04 LTS 64 bit both fully update.
When run one Emulator the CPU runs real hard, about 4x times as before an upgrade a couple of weeks ago. Seems like each Emulator is using more RAM than before as well. Can only run at most 3 Emulator before the computer becomes overloaded and unresponsive, before could run at least 8.
I checked to make sure all the required Linux libraries are on the machine.
Filed a bug on Android Studio as:
Issue 173578: Race condition when running AVD Emulator since updating Android SDK Tools, revision 24.2
Just started UI tuning (Again) and this problem is killing me time wise since I can not open many emulators to check the UI.
Anyone else having the same or similar problem? If so star the bug report.
Anyone know of a fix?

Running new Android Studio Project restarts Windows 8.1 (Bad Pool Caller Error)

I've been using Eclipse + ADT for Android Developement. I just started with Android Studio and created the simplest "My Application" project. But when I run the Project every time a blue Screen Covers the whole screen saying the occurrence of Bad Pool Caller Error and restarts the Computer.
I'm using
windows 8.1
Android Studio 1.0
Ram 2 GB
My best guess...the last time I checked. Android Studio was on a beta version, which means it might have some compatibility issues. You must be using a beta version...if so that maybe your problem.
As you guys mentioned in comments that its a Windows problem. I think that I sort of sorted it out! Though not the right way.
I'm using Avast Antivirus. I disabled it for an hour and Ran the Project. The project ran fine. And even after I enabled avast, Android Studio is working fine.

Categories

Resources