How to build an Android development environment on a single machine

How to build an Android development environment on a single machine

Old saying: to do good deeds, you must first sharpen your tools. To learn about Android development, I lost my blood and changed my computer. As the saying goes, it is a bit paranoid to sharpen the knife without mistake and make good use of the steel on the knife. In order to maximize the potential of the new book, I spent a long time doing configuration and optimization. However, the old saying goes completely correct from the past few days.

The configuration information of the new notebook is as follows:

CPU: Intel Core i7-4710MQ 2.50 GHz

RAM: 32 GB

DISK: samsung ssd 850 EVO 500 GB, ST2000LM003 HDD 2 TB

OS: Windows 7 flagship edition, 64-bit, Single System

As we all know, SSD reading and writing speed is fast, but there is a life limit, haogang must be used in the blade, so SSD is divided into two zones, one is used to install Windows 7 system, about 64 GB, there is only one partition left for creating virtual machines and installing Android Studio. This is also true for HDD, which is divided into two zones, one for software installation and SSD optimization. The remaining space is divided into one zone for data storage and backup. I think it is easy to use SSD or HDD partitioning or not. There is no need for too many partitions. The system has a single partition, mainly for the convenience of system backup and migration. The earliest machines were not equipped with SSD. Later, when Deng saw that it was too slow for me to compile the Android system, he bought me a gb ssd. Because the system is partitioned separately, Ghost backup and restoration are used, and the system is migrated from HDD to SSD in less than an hour. If there is no partition, it will be very troublesome.

There are many optimization operations on SSD, such as disabling disk fragment, migrating page files to HDD, and disabling hibernation. For convenience, install 360 security guard directly for optimization, install the SAMSUNG Magician software officially provided by Samsung for further optimization, mainly Over Provisioning (Reserved space) configuration. It is said that it can optimize performance and prolong the service life of SSD. These optimizations actually reduce unnecessary write operations on SSD as much as possible. Based on this consideration, in order to further reduce the write operations on SSD by the system and applications, I migrated the directories of many systems and applications to HDD, that is, using the mklink command to create a link, after a long period of practice, it is proved that this mechanism is no problem and the write operation on SSD is effectively reduced. WinPE is used to create a link to the system directory. A useful version, 64-bit micro-PE toolbox, built-in Ghost, system installation, and other practical tools are recommended.

Shows the link between SSD and HDD.

In this optimization Process, we mainly use the Everything and Process Monitor software to help determine which directories need to be migrated. Among them, Everything is an essential tool for Windows Search and will also be used in daily work. Process Monitor is used to Monitor all write operations on the file system.

After SSD optimization, the memory is optimized. For 32 GB memory, RamDisk must be used; otherwise, it will not be wasted? Put the temporary directories of the system, 360 speed browser, WinRAR, and other software into RamDisk. As for the page files, there is no need to put them in RamDisk. 32 GB memory, directly disable page files, although a small impact, but not in the way. The Ramdisk tool recommends ImDisk Toolkit, which is easy to use without registration! Considering that the simulator running on Android Studio requires much space, Ramdisk is allocated 3 GB. After creating a RamDisk, you can still use mklink to create a link, as shown in.

The above is mainly for SSD and memory optimization, reduce unnecessary write operations on SSD, prolong its service life, create Ramdisk, and maximize the memory performance. This is not only applicable to building an Android development environment, but also to machines with SSD and large memory.

Mklink is used as follows:

copy "C:\HaxLogs.txt" "D:\SSD\HaxLogs.txt"  /Yren "C:\HaxLogs.txt"  "HaxLogs-BAK.txt"mklink "C:\HaxLogs.txt" "D:\SSD\HaxLogs.txt"attrib "C:\ProgramData" -hxcopy "C:\ProgramData" "D:\SSD\ProgramData"  /I /E /H /C /K /Yren "C:\ProgramData"  "ProgramData-BAK"mklink /d "C:\ProgramData" "D:\SSD\ProgramData"xcopy "C:\Users\HE" "D:\SSD\Users\HE"  /I /E /H /C /K /Yren "C:\Users\HE"  "HE-BAK"mklink /d "C:\Users\HE" "D:\SSD\Users\HE"

For more details, please continue to read the highlights on the next page:

1 2 3 4 5 Next Page