View source for Restoring Android Studio 3 AVD Manager

'''Summary:''' Android Studio 3.0 was designed around a 2017-era Android SDK. Attempting to use Android Studio 3.0 with modern SDK components can result in missing AVD Manager functionality, Gradle synchronization failures, emulator incompatibilities, and a generally unstable development environment. This article documents the investigation, diagnosis, reconstruction, and validation of a fully functional Android Studio 3.0 environment capable of running Android 8.0 Oreo (API 26) virtual devices. == Symptoms == * Android Virtual Device (AVD) Manager missing or unavailable. * Android-specific tooling partially disabled. * Emulator installed but not fully integrated into Android Studio. * Gradle project synchronization failures. * Dependency resolution failures. * Modern SDK components installed alongside Android Studio 3.0. == Environment == === IDE === <pre> Android Studio 3.0.0 Build 171.4408382 </pre> === Operating System === <pre> Windows 10 </pre> === SDK Location === <pre> S:\Android\Sdk </pre> == Initial Observations == Although Android Studio appeared to function, the installed Android SDK contained components from wildly different generations. == Root Cause == The underlying issue was a version mismatch. Android Studio 3.0 expects components contemporary with its release period: <pre> 2017 </pre> The SDK, however, had accumulated components from approximately: <pre> 2017 - 2026 </pre> == Reconstructing a Period-Correct SDK == === Android Studio === <pre> Android Studio 3.0.0 </pre> === Java === <pre> OpenJDK 1.8.0_152 </pre> === SDK Tools === <pre> 26.1.1 </pre> === Platform Tools === <pre> 26.0.0 </pre> Direct download: <pre> https://dl.google.com/android/repository/platform-tools_r26.0.0-windows.zip </pre> === Build Tools === <pre> 26.0.2 </pre> === Android Platform === <pre> Android 8.0 (API 26) </pre> === Emulator === Recommended: <pre> Android Emulator 27.2.9.0 Build ID 4773671 </pre> === HAXM === <pre> Intel HAXM 7.8.0 </pre> == Verifying SDK Functionality == === List Targets === <syntaxhighlight lang="dos"> avdmanager.bat list target </syntaxhighlight> === List Devices === <syntaxhighlight lang="dos"> avdmanager.bat list device </syntaxhighlight> == Creating a Test Device == <syntaxhighlight lang="dos"> avdmanager create avd ^ -n Test26 ^ -k "system-images;android-26;default;x86" </syntaxhighlight> == Launching the Emulator == <syntaxhighlight lang="dos"> emulator.exe -avd Test26 </syntaxhighlight> == Verifying ADB Connectivity == <syntaxhighlight lang="dos"> adb devices </syntaxhighlight> Expected: <pre> emulator-5554 device </pre> == Restoring AVD Manager == After rebuilding the SDK using period-correct components and configuring Java correctly, Android Studio regained full AVD functionality. == Final Working Configuration == <pre> Android Studio 3.0.0 Java 1.8.0_152 SDK Tools 26.1.1 Platform Tools 26.0.0 Build Tools 26.0.2 Platform Android API 26 System Images Oreo x86 / x86_64 Emulator 27.2.9.0 HAXM 7.8.0 </pre> == Lessons Learned == * Validate components individually. * Avoid mixing SDK generations. * Keep legacy SDKs isolated. * Archive known-good components. == Related Topics == * Android Studio Legacy Environment Preservation * Android SDK Version Compatibility * Intel HAXM Configuration * Android Emulator Troubleshooting * Gradle Dependency Resolution * Software Archaeology and Environment Reconstruction