C disk space is a serious shortage
First of all bloggers notebook environment: Windows 10 | Android Studio 3.5
Bloggers today find themselves less than the rest of the C drive notebook 1G, even micro-channel PC side can not be used. In desperation, several bloggers uninstall the software installed on the C drive, but found little effect, because of time shortage 10G C drive but it is still cause a lot of problems or system Caton software functions can not be used. Therefore, bloggers point into the C drive to check it out and see in the end is what "troublemaker" I'm taking up valuable disk space C.
Then: under "C / user / linch" directory found .android and .gradle two hidden folder:
Then right-view footprint the size of each folder, shocked me:
Note that, with the folder because .android 9 G is mainly the simulator AVD, above screenshot has been moved to the disk D, the path is not the C drive.
> Mobile .android
As mentioned above, .android folder mainly avd simulator takes up space, and more than 9 G very impressive! Here to talk about how to properly secure the mobile emulator files to the D drive without causing other problems.
Step one: the movement simulator in .android / avd / directory "xxx.avd" file corresponding to the disc to position D
Step two: modify the path to the configuration file address .android / avd / under "xxx.ini" are as follows:
Step three: Open the Android Studio test to determine whether the simulator can start and operate properly avd
> Mobile .gradle
Step a: The .gradle .AndroidStudio3.5 and moved to a position corresponding to the D drive.
Step Two: Then find \ bin \ idea.properties files in Android Studio installation directory, open and find "idea.config.path =" and "idea.system.path =":
The address path right of the "=" number corresponding to the address of the disk D, and the front of the "#" removed:
Step Three: In the above file open idea.properties bottommost plus Gradle path configuration:
Step four: Open the Android Studio setup interface, find Gradle on the left and check whether Gradle path has been modified over:
Step Five: compile and run the project and see Gradle to run correctly.
