Recently I experienced that Android Studio is hanging a lot. Right in the middle of typing in any editor it will hang and block me from doing anything else for a couple of seconds. Restarting or killing adb wouldn't help.
After a while I realized that this happens if the documentation is being loaded and displayed. This happens mostly for Android documentation, which is quite verbose and also seems to contain images and formatting.
I already tried switching off the Auto-update from source option, but that doesn't change anything.
Any ideas what could cause Android Studio to block while it's loading or displaying (or doing whatever with) the documentation?
I'm using Android Studio 2.1.1, the latest build with the security fix.
you can check this solution: https://stackoverflow.com/a/26149069/2133585
Here's what fixed it for me:
Make sure you have the Documentation package downloaded in SDK Manager.
Exit Studio if it's running.
Delete the file named "jdk.table.xml" located in ~/.AndroidStudioX.Y/config/options/ (remember to take a backup
first!).
Relaunch Android Studio. should work correctly now and it should regenerate the file automatically.
Note:
This worked for me on Ubuntu 14.04 & Android Studio 0.8.11 (EDIT: Several users are reporting this solution also works for
newer versions of Android Studio).
If it still doesn't work, try deleting and re-downloading the Documentation package from inside Android SDK Manager then try the
above steps.
If you're running Windows, the file is located at "%UserProfile%.AndroidStudio\config\options", and if you're running
OS X, it's located at "~/Library/Preferences/AndroidStudio/options"
(credits to #Gero and #Alex Lipov).
Fix still works for AS 2.2.3 and MacOS 10.12.2 Sierra
Related
I'm currently running Android Studio Bumblebee 2021.1.1 in windows 10.
The problem I have is each time I start android studio the device list is stuck in loading devices.
I tried these solutions
android studio device list stuck on loading/51101178
android device list showing in android studio got stuck/65177069
The soulutions provided in the threads sometimes work and sometimes don't but the real problem is even if I did fix it in the run time, The next time I open android studio it's still there.
I already tried updating android studio to latest version, reinstalling android studio, deleting all the caches and plugins and resetting it to default. Completely Deleting Sdk folder and downloading again. But nothing helped I don't know where this problem could be originate from
In my case deleting the "platform-tools" folder as Dyenal said didn't work because it said that the folder was open elsewhere (even when I had shut down android studio). If that's your case too, do this.
Close android studio
Go to your task manager
Go to the "Details" tab and look for "adb.exe" as seen in the image below.
Right-click on it and "End task".
Open android studio and pretend you weren't interrupted. Cheers :)
Go to SDK folder delete platform-tools folder.. invalidate and restart the studio..works for me!
After hours of research and try and error I finally figured out what was going on.
Turns out my adb configuration was conflicting with genymotion's. Nothing could have done at the side of android studio. I went to the genymotion settings ADB tab and changed from Use Genymotion Android Tools to Use custom Android SDK Tools and it went away at last
This is a temporary solution. Open terminal and type adb devices. Once your device starts showing up in terminal, it will start showing up in loading devices too.
This problem occurs due to Windows folder accessing especially when you change the AVD folder.
Windows prevent access to Windows partition root. you have multi options for solving this problem.
Move AVD folder to another driver. Then define it on the Environment variable
Move the AVD to C:\Users\<User>\.android\avd folder. this folder is accessible for Android studio.
Run emulator from device manager, then type adb devices in cmd prompt
Restarting my computer fixed the problem for me
When using Android Studio, or any other IDE which use their own ADB, it is necessary to set Genymotion to use the correct ADB instead of its inbuilt one. It is documented here: https://docs.genymotion.com/desktop/02_Application/#use-third-party-adbsdk
I only opened task manager and there were a bunch of adb.exe open so i ended all of them while android studio is running in the background so then adb.exe started again and then i go to android studio and find out that the issue was resolved.
I know there are a multitude of questions across various forums that touch on this issue but nothing has helped thus far.
I use Eclipse Photon for my IDE.
I installed the Android SDK via Android Studio.
I recently moved to a new machine and since then I get these errors when trying to build the project. Actually, the first image occurs when I first open Eclipse. The second image is what I see when building (I cleaned beforehand).
Many solutions suggest reinstalling platform tools/build tools/the entire SDK etc.
So, I did this:
1) Closed down Eclipse
2) Opened Android Studio and went to SDK Manager
3) Unchecked and uninstalled all the options highlighted in the images below.
4) Once uninstalled I restart Android Studio and reinstalled all of them.
5) The errors noted at the start of this post persist.
Any ideas what I can try next? It seems every machine move/upgrade causes build issues. It's the main reason I dislike coding for phones, it's not the coding, it's the dev environments!
I have just updated my Android Studio from 1.4 to 2.0, on startup it freezes on splash-screen. is it possible to fix it or i have to download it again?
Its very strange. I have also updated to 2.0 in my MAC, Ubuntu and Windows 10. I didn't feel any issues till now in any of these.
Please note that 2.0 is still a preview. You may have to wait till Google releases the stable version.
Which operating system are you using?
For Windows, check the log of
C:\Users\<Username>\.AndroidStudioPreview2.0\system\log\idea.log
and paste here the last relevant entries on the bottom with a recent timestamp, containing an error message or indication of a possible freeze.
Also, check that you don't have any Android Studio, IntelliJ, or java-processes running before you start Android Studio.
This is an answer for my question, after trying many methods now it works fine.
This is how i resolved my problem by:
Updating Android SDK Tools and the latest SDK Platform
Removing the Android Studio cache folder situated in
C:\Users\<username>\.AndroidStudioPreview2.0
Running android studio again
At First Update Your Android SDK Tools (Support Repository )
Actually Android Studio creates a local directory . AndroidStudio to
cache its own data. In most environments, this is acceptable. However,
the size of the directory can easily exceed 300Mb and, if you have a
space constraint on your home drive (or a roaming profile in windows),
this may be better off in some other place.
The location of this directory is placed in an idea.properties file in the bin/ directory of your AS is installed.
I have a problem with creating Android Application project in Eclipse on my Mac. When I start Android Application Project Wizard after clicking "finish" in the last step, this window appears:
I've been trying to solve this for hours, but none of the solutions I've found on the internet worked for me (including this). I didn't try to reinstall eclipse itself, but to I don't want to do this. What's the solution to my problem.
UPDATE:
I removed Eclipse and sdk from my computer and downloaded the whole ADT Bundle from here and switched workspace but actually I am still getting the same Errors.
What I found up on the internet was that you could have upgraded your java. So this occurred. The solution to this problem for Mac is to edit the Eclipse.ini file to use java 1.6 .The code Below will work :
-vm/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java
Start with a clean slate. Unistall Eclipse and redownload - Eclipse is a very big program and can be very buggy at times for no reason. While it is not the quickest solution, ensuring that Eclipse was properly downloaded and installed will provide a good foundation for the future development of you Android applications. Did you install Eclipse just for Android, or did you have a pre-existing copy and want to install the Android SDK?
I recently updated my version of eclipse from 3.6 to 3.7
(Using Mac OS X 10.6.8 & Eclipse 3.7). I did this to install EGit. Since, then I have noticed that none of the changes to my App are being reflected in my AVD's.
When setting up EGit I realized that it had moved my working location to another location on my system. I figured this might be the issue, so I removed my EGit repository and restored my App from a backup. The problem continue leading me to believe the problem likely lies (I could be wrong) with the upgrade to Eclipse 3.7.
I have tried many other things, but none seem to work. So far I have..
Uninstalled my App from the AVD, and then re-ran application. This made no difference.
I have tried creating a new fresh AVD. Same deal here, same un-change version of app is applied.
I tried stop and restarting the adb.
I have tried to 'Clean up' the Project.
All attempts so far have failed.
Has anyone else out there seen this problem or have any suggestions?
I think the next thing I might try is updating my Android plug-ins. If this fails I Afraid my next option is to uninstall Eclipse completely and start from scratch.
Any suggestions would be great.
I solved the problem.
My guess of updating the Android SDK was correct.
In Elipse I went to Window -> Android SDK Manager.
I installed the available updates:
Android SDK Tools 22.0.1,
Android SDK Platform-Tools 17,
Android SDK Build Tools 17. After the install restarted Eclipse and then boom! My AVD was back and showing my newest changes. Hope this helps some one.