I have a project which contains 15 classes. If I collapse the methods and restart Android Studio, everything works fine but if I sync the build.gradle file and restart Android Studio again, the methods from some classes are not collapsed anymore. This is happening not in all classes in my project just in those that are not opened. So, let's say I'm working on 5 classes and 10 are closed, it I sync the build.gradle file, the 5 opened classes are ok but the rest of 10 are not.
How to always keep methods collapsed in Android Studio, even if I sync the build.gradle file?
Thanks!
You can modify the configuration of Android Studio for this. Check below:
Environment:
Android Studio 3.1.3
Build #AI-173.4819257, built on June 5, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.4
Go to Preferences > Editor > General > Code Folding and check all the check boxes you want and click apply:
I hope it will work.
I am getting this error while updating Android Studio 3.0.1 some patch gets downloaded and following error comes,
Some of the conflicts below do not have a solution, so the patch cannot be applied.
Showing File : jre/bin/java.exe is Absent
If anyone is still having this issue, here's what worked for me. I checked a bunch of other responses but nothing worked & I didn't want to do a clean install.
Not sure how it happened, but within my Android_Studio\jre\ was another jre version. So, I went into Android_Studio\jre\jre\bin\, copied the java.exe from there & pasted it into Android_Studio\jre\bin.
Similar solution to the other poster, but it had to come from a different directory, otherwise it'll just change from "Absent" to "modified" & continue to not work.
I had the same issue. I've just copied java.exe from jdk installed folder (e.g. D:\Program Files\Java\jdk1.8.0_144\bin\java.exe) to Android_Studio\jre\bin, and Android Studio had upgraded successfully.
Opened Android Studio again and choose update and restart option. Once the download is completed, the android studio is closed automatically and an update window appeared on the screen. At that time I opened the terminal and entered the following command:
ps -A | grep java
That command showed all the running java related processes. Now I killed those processes using the following command:
kill -9 PID
Replace PID with the corresponding process id.
I had the same error, solved in that way: I just reinstalled my current Android Studio version (without losing any settings, etc) and then tried to update again. Everything went fine after that.
The error is due to modification of java installed files. Download the latest android studio and reinstall it. The previous configuration can be restored during the reinstall over existing version.
I have an xamarin android project. It worked and built so far. Now I changed the jdk1.8 from the x86 to the x64 since the Xamarin Forms designer needs this version to work properly according to Xamarin. Now I get this error on build:
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1965,3): error MSB6006: "java.exe" exited with code 2.
I read that this might be related to newer support libraries of google. But i have the newest version and had it already before I made the change. I also tried reboot my pc, clean and rebuild and delete all bin and obj folders without success. And so far I haven't found more information what this error could be and how to solve it besides switch back to the x86 version of the jdk.
I found the issue, while getting the diagnostic build log. I added the xamarin forms nuget package for embedded forms. With that package, the references exceed the max of what android is able to handle. So I had to enable multi-dex first. Then it built again.
In Android Studio I am facing bellow error
This popup shows when I press Alt+Enter for missing classes(symbols). When I click on setup SDK it shows two options
1.8(Java version "1.8.0_60")
Android API 23 Platform (Java version "1.8.0_60")
Nothing happens on selecting any of above options.
NOTE: My Java_Home path is correct and in android studio I have checked JDK path it's correct.
I am using Android Studio 1.5.0, Java 1.8 and windows 10
Simple Invalidate Cache and Restart doesn't work for me. So I have done following steps:
Check and verify Java path in Java_home variable
Start Android Studio and invalidate cache File--> Invalidate Cache and Restart
Start Android Studio and click File -> Invalidate Cache and Restart.
This has worked for me. Thanks
Well... In my case, setting up JDK in Project Structure didn't work. Invalidating and restart didn't work either. On further debugging, it led me to this:
Can-t-start-Intellij-after-update
Background of this problem:
I had installed Android Studio 3.6 and upgraded to Android Studio 4. Plugins like Mateial theme, Flutter, CSV viewer, JSON viewer etc weren't compatible with Android Studio 4. So I had disregarded those plugins after I upgraded to AS 4.
After some days, I got a notification that plugins which I had disregarded earlier were compatible with AS 4. So I installed those and restarted AS 4 and applied Material theme. I started to face problems like Set up JDK even though the path to JDK was proper.
So I closed AS 4, deleted caches from .gradle, .android, .AndroidStudio4.0\system\caches. Then I opened AS 4 and set up JDK error was gone.
Hope it helps...
P.S: If same problem persists, then I'm afraid that you've to unistall AS and download AS 4 directly and install it. I still can't figure out why it happened to me...
Close Android studio then again open it .
Go to File--> Invalidate Cache and Restart .
You are done.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200