Complete Installation and Configuration Guide for Android Studio Panda 4

Introduction

With the release of Android Studio 2025.3.4 (codename Panda 4), many developers need to perform a fresh installation or upgrade. Since 2020, Android Studio has adopted animal codenames (from Arctic Fox to Bumblebee, and now Panda), with each major version accompanied by a synchronized upgrade of the underlying IntelliJ IDEA platform, bringing improvements in code editing, indexing performance, and UI rendering. This article provides a complete installation and configuration guide covering everything from download and installation to SDK configuration, Gradle setup, emulator creation, and common troubleshooting — with practical solutions specifically tailored for developers dealing with network restrictions in China.

Downloading Android Studio Panda 4

Official Download Method

Open your browser and visit the Android developer website (developer.android.com). Navigate to the Android Studio download page and select Panda 4 (version 2025.3.4) to download. The version number 2025.3.4 actually corresponds to the underlying IntelliJ IDEA platform version, meaning this release inherits IntelliJ's latest code analysis engine and editor optimizations. Understanding this correspondence is particularly important when choosing third-party plugins — some IntelliJ plugins may need to be updated to support the new platform version before they work properly.

If the official download is slow, you can also obtain the installer via cloud storage services, which is a practical alternative for developers in China.

Installation and Directory Planning

Creating a Well-Organized Directory Structure

Before installation, it's recommended to plan your directory structure. Create a development folder at the root of your drive, then set up the following subdirectories:

• studio — Android Studio installation directory
• sdk — Android SDK directory
• gradle — Gradle cache directory
• avd — Emulator virtual device directory

Note: Avoid spaces and non-ASCII characters (such as Chinese characters) in your paths to prevent unexpected build issues. This is because some command-line tools in the Android build toolchain (such as aapt2, d8, etc.) may encounter errors when parsing paths containing special characters, especially on Windows where non-ASCII paths can also cause character encoding problems.

Running the Installation

Double-click the installer and install Android Studio to the development/studio directory. After installation, you can find the shortcut in the Start menu — it's recommended to drag it to your desktop for easy access. If you have multiple versions installed, you can add version numbers to the shortcut names to distinguish them.

SDK Configuration

Offline SDK Installation Method

When launching Android Studio for the first time, you'll be prompted to configure the SDK path. If you downloaded the SDK package from cloud storage, simply extract it and place it in the development/sdk directory you created earlier.

The Android SDK is not a single installer but rather a modular toolkit composed of multiple independent components. Its core components include: Platform Tools (command-line debugging tools like adb and fastboot), Build Tools (the aapt2 resource compiler, d8/r8 bytecode compilers, etc.), Platform packages for specific API levels (i.e., android.jar, which provides Android API interfaces at compile time), and System Images (system images required for running the emulator). The SDK Manager uses XML manifest files to manage versions and dependencies of these components. Offline installation essentially means manually placing these components into the corresponding subdirectories within the SDK directory (such as platforms/, build-tools/, system-images/), and the SDK Manager recognizes installed components by verifying the directory structure and package.xml files.

In Android Studio's SDK configuration screen, select "Choose another location" and point the path to the development/sdk folder, then click OK to complete the configuration.

Handling Common SDK Errors

If you encounter errors like "SDK is already in use" or download failures, try the following:

1. Delete corrupted files in the SDK directory
2. Reconfigure the SDK path
3. Check your network proxy settings

Gradle Configuration

What Gradle Does

Gradle is the build tool for Android projects, responsible for dependency management and project packaging. More precisely, Gradle is a general-purpose build automation framework based on Groovy/Kotlin DSL, and Android projects extend its functionality through the Android Gradle Plugin (AGP). AGP handles Android-specific build processes: resource compilation (AAPT2), code compilation (javac/kotlinc), DEX bytecode conversion (D8), code shrinking and obfuscation (R8), APK/AAB packaging and signing, and more. There is a strict compatibility relationship between AGP versions and Gradle versions — for example, the latest AGP typically requires a specific minimum version of the Gradle runtime.

Android Studio automatically downloads the corresponding Gradle version (e.g., 9.4.1) during the first project build, but download speeds are usually very slow in China.

Offline Gradle Configuration Method

Gradle uses a Wrapper mechanism (the gradlew script in your project), where each project specifies the required Gradle version via the distributionUrl in the gradle-wrapper.properties file, ensuring all team members use a consistent build environment. When the Wrapper runs for the first time, it downloads the corresponding Gradle distribution from that URL to the .gradle/wrapper/dists/ directory under the user's home folder.

Gradle's cache is located in the .gradle folder under your user directory. After downloading the corresponding Gradle package from cloud storage, place it in the wrapper/dists subdirectory within that folder to skip the online download step. The principle behind offline configuration is simple — when the Wrapper detects that the zip file already exists in the corresponding hash directory, it will extract and use it directly instead of downloading.

Creating an Android Emulator

Choosing a Device and System Image

The Android Emulator is based on QEMU virtualization technology and achieves hardware-accelerated virtualization on x86/x64 hosts through Intel HAXM or Windows Hypervisor Platform (WHPF), allowing the Android system to run at near-native speed. When creating an emulator (AVD) in Android Studio, keep the following in mind:

1. Choose a device template (such as Median Phone or Small Phone)
2. When selecting a system image, avoid images labeled "16K" as they may be incomplete — choose the full version instead
3. For example, Android 16 corresponds to the version 36.1 image

A note about "16K images": These refer to system images using a 16KB memory page size. Traditional Android uses 4KB page sizes, but starting with Android 15, Google has been pushing 16KB page size support to improve memory management efficiency and performance on devices with large amounts of RAM. However, 16K images are currently intended primarily for app compatibility testing (especially for apps using JNI native libraries), and some of these images may not include complete components like Google Play Services. For everyday development and testing, choosing standard 4K page size full images is the safer option.

Choosing the Right API Version Based on Your Hardware

• Lower-end hardware: Choose a lower version like API 26 (Android 8.0 Oreo) for smoother performance
• Higher-end hardware: You can choose the latest version like API 36 (Android 16)

The API level is the numeric identifier for an Android platform version, incrementing with each new Android release. Choosing a lower API level image not only runs more lightly but also helps developers test app compatibility on older system versions.

Network Troubleshooting Solutions

Core dependencies in the Android development toolchain (SDK components, Gradle distributions, libraries from Maven Central and Google Maven repositories) are all hosted on Google or overseas servers. Developers in China typically face two types of network issues: DNS pollution preventing resolution of domains like dl.google.com, and TCP connections being interrupted or throttled. Here are two main solutions.

Configuring a Proxy to Resolve Download Issues

If you encounter network download problems, you can set up a proxy in Android Studio:

1. Go to Settings → Network Proxy settings
2. Enter the proxy address: 127.0.0.1, port: 7897 (use your actual proxy port)
3. Save and re-sync the project

Android Studio's proxy settings affect both the IDE's own network requests and dependency downloads during Gradle builds. Additionally, domestic mirror sources are a commonly used alternative. For example, the Alibaba Cloud Maven mirror (maven.aliyun.com) can be configured in your project's settings.gradle or build.gradle to replace Google Maven and Maven Central repository URLs with domestic mirror addresses, fundamentally solving the slow dependency download problem.

Modifying the Hosts File

Another way to resolve network issues is to modify the system Hosts file:

• Path: C:\Windows\System32\drivers\etc\hosts
• Append the provided hosts content to the end of the file
• This can help resolve Google server access issues

Modifying the Hosts file works by bypassing polluted DNS resolution and directly mapping domain names to the correct server IP addresses, thereby restoring normal access to Google servers.

Creating Your First Android Project

Building a Hello World Project

After completing the installation and configuration, create a test project to verify that your environment is working properly:

1. Select the "Empty View Activity" template
2. Name the project "Hello World"
3. Wait for Gradle sync to complete

Project Structure and View Switching

Android Studio provides two project views:

• Project view: Displays the complete file directory structure, including all real files on disk such as the .gradle cache directory, .idea configuration directory, and build output directory
• Android view: Displays files organized by module, logically grouping Java/Kotlin source code, resource files (res/), manifest files (AndroidManifest.xml), Gradle scripts, etc., while hiding irrelevant files like build caches

The Android view is recommended for daily development, as everything is clearly organized at a glance. This logical view design stems from the unique nature of Android projects — an Android app contains not only code but also layout XMLs, drawable resources, values configurations, and many other types of files. The logical view helps developers locate target files more quickly.

Running and Debugging

• View the run status via View → Tool Windows → Run
• Check the build status via the Build window
• Warning messages (such as fail-type warnings) that appear during compilation can usually be ignored — just wait for the build to complete

Modifying Code to Verify Your Environment

In the layout file, find the Hello World text and try changing the font size (e.g., set it to 40sp), then re-run to verify the change takes effect, confirming that your development environment is fully ready. Here, sp (Scale-independent Pixels) is a unit in Android specifically designed for text sizes. It adapts based on the font scaling preference the user selects in system settings. Similar to dp (Density-independent Pixels) but designed specifically for text accessibility, it ensures that when users with poor vision enlarge the system font, app text scales accordingly.

Summary

The core steps for installing Android Studio 2025.3.4 Panda 4 are: Plan directory structure → Install Studio → Configure SDK → Configure Gradle → Create emulator → Resolve network issues. For developers in China, preparing offline SDK and Gradle packages in advance, combined with network proxies or Hosts file modifications, can significantly reduce wait times and error rates during the installation process.

Key Takeaways