This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Android Virtual Device | |
|---|---|
| Name | Android Virtual Device |
| Developer | |
| Released | 2008 |
| Latest release version | Varies with Android SDK |
| Programming language | C++, Java |
| Operating system | Microsoft Windows, macOS, Linux |
| Genre | Software emulator, Virtual device |
| License | Apache License 2.0 |
Android Virtual Device Android Virtual Device (AVD) is a configurable emulator target used with the Android (operating system) Software Development Kit to run and test Android Studio applications on desktop platforms such as Microsoft Windows, macOS, and Linux. It enables developers working for organizations like Google, Samsung Electronics, Sony, Huawei, and Xiaomi to simulate hardware configurations, screen sizes, and OS versions for compatibility testing, continuous integration pipelines, and debugging across releases like Android 4.4 KitKat, Android 6.0 Marshmallow, Android 9 Pie, Android 10, and Android 12.
AVD acts as a virtual device definition within the Android SDK and Android Emulator ecosystem, pairing a device profile with a system image to emulate mobile hardware for app validation on targets such as Pixel (smartphone), Nexus (tablet), and generic device profiles derived from industry standards like ARM architecture and x86 (architecture). Maintained by Google and used by companies including Intel, Qualcomm, Motorola, and LG Electronics, AVDs are essential in workflows that incorporate tools such as Gradle (software), Jenkins (software), Travis CI, and GitHub Actions.
AVD supports multiple features: emulation of CPU architectures (e.g., ARMv8-A, x86_64), virtual sensors reflecting location and accelerometer inputs, network condition simulation including proxies and packet loss, and configurable display parameters matching devices like Samsung Galaxy S series, Google Pixel, and tablets like Nexus 7. It integrates with debugging tools such as Android Debug Bridge and profiling suites like Android Profiler, and supports advanced capabilities including Google Play services emulation, virtual camera mapping to host cameras, and snapshot states for rapid startup.
AVD definitions are created and managed via graphical tools in Android Studio and command-line utilities such as avdmanager and sdkmanager. Profiles specify screen density (DPI) and resolution mappings consistent with devices like Pixel C and Samsung Galaxy Tab S, memory and storage allocations, and emulated hardware features like Wi‑Fi and Bluetooth. Device configurations are stored in the user profile and can be shared across teams using version control alongside tools like Android Emulator Container Scripts and virtualization frameworks from Docker and CI integrations with CircleCI.
System images paired with AVDs derive from API levels (for example, API level 30, API level 29) and come in flavors such as Google APIs, Google Play, and AOSP builds. Images are provided for architectures supported by vendors like Intel (HAXM), ARM Holdings (ARM), and Android Open Source Project distributions. Device images emulate firmware components, SELinux policies, and services used by apps integrating SDKs from Firebase, AdMob, Facebook (company), and Twitter (service).
AVD performance depends on hardware acceleration technologies such as Intel HAXM, KVM (kernel-based virtual machine), and vendor-specific drivers from NVIDIA and AMD. Graphics acceleration uses APIs and drivers influenced by Vulkan (API), OpenGL ES, and host GPU virtualization methods. Performance tuning often references CPU pinning, host memory allocation, and nested virtualization strategies used in enterprise datacenters run by Amazon Web Services, Google Cloud Platform, and Microsoft Azure for scalable emulator farms.
Common use cases include functional testing for apps published on Google Play Store, automated UI testing with frameworks like Espresso (testing) and UIAutomator, regression testing in continuous integration pipelines managed by Jenkins (software), and educational labs at institutions such as Massachusetts Institute of Technology, Stanford University, and University of Cambridge. Teams building apps for ecosystems like Android Auto, Wear OS, and Android TV rely on AVDs to validate interactions with platform services, accessory emulation, and certification processes connected to vendors like Sony Corporation and LG Electronics.
AVD troubleshooting often addresses issues with acceleration layers (e.g., Intel HAXM conflicts), incompatible host GPU drivers from NVIDIA Corporation or AMD cards, and discrepancies between emulator behavior and physical devices produced by manufacturers like Samsung and OnePlus. Limitations include imperfect emulation of radio stacks found in devices by Qualcomm and MediaTek, differences in thermal throttling and battery models, and restricted support for some proprietary sensors used by vendors such as Huawei Technologies Co., Ltd. and Xiaomi Corporation. Community guidance is available through channels like Stack Overflow, GitHub, and official issue trackers maintained by Google.