Users often come across a mysterious number 21 in technical specifications or error logs, wondering: “21 SDK which Android?” This is not just a build number, but a fundamental marker that separates eras in the development of a mobile operating system. Understanding which version is behind this identifier is critical both for owners of old devices and for developers trying to run specific software.
Behind this number is Android 5.0 Lollipop a revolutionary update that brought Material Design and the transition to the new ART runtime environment. If your device or application requires this particular API level, then we are talking about a system released in late 2014. Although today it is considered an outdated standard, many specialized tablets, set-top boxes and ATMs still operate on this basis.
Knowing the exact version is necessary to correctly install security updates or specialized utilities. Incorrect interpretation of the SDK number may lead to an attempt to install incompatible software, which will cause installation errors or unstable operation of the gadget. Let's look in detail at what this API level is and how to work with it in modern realities.
Version identification and technical characteristics
When you see a mention API Level 21, this is a clear correspondence to the version Android 5.0. It was the first release in the Lollipop line, which was later updated to 5.1 (API 22). The key feature of this version was the complete abandonment of the Dalvik virtual machine in favor of ART (Android Runtime), which significantly changed the process of installing applications and working with memory.
The system requirements for working at this API level were quite high for its time. The processor architecture had to support ARMv7 instructions or higher, and the amount of RAM was often required at least 1 GB for comfortable operation of the interface. The graphics engine switched to OpenGL ES 3.0/3.1, which opened up new possibilities for games, but imposed limitations on older chipsets.
For the average user, the difference between SDK 19 (KitKat) and SDK 21 was felt visually and tactilely. Animations have become smoother, but the CPU load has increased. If you are trying to determine the version on a device without accessing the menu, you can use debug commands.
adb shell getprop ro.build.version.sdkThis command in the debug console will return a number 21if the device is running the base version of Lollipop.
Before attempting to flash a device with SDK 21, be sure to take a full backup of your data via ADB, as rolling back to older versions is often impossible due to changes in the partition structure.
Device compatibility and list of models
The Android 5.0 era covered a huge range of devices, from budget smartphones to the flagships of that time. However, today support for this version from most popular applications has been discontinued. Developers set the minimum entry threshold at Android 8.0 or higher, leaving SDK 21 users outside of digital services.
However, in the corporate sector and the IoT (Internet of Things) sphere, these devices live a second life. Data collection terminals, cash registers and media players often get stuck at this API level due to the high cost of replacing the equipment. Understanding compatibility helps to find alternative versions of software.
- 📱 Google Nexus: Nexus 4, 5, 6, 7 (2013), 9, 10 models officially received this version and worked stably on it.
- 📱 Samsung Galaxy: S4, S5, Note 3, Note 4 lines, as well as the Alpha series and the first A-series models (A3, A5, A7 2015).
- 📱 Sony Xperia: Models Z, Z1, Z2, Z3 and compact versions Z1 Compact, Z2 Tablet.
- 📱 LG: Flagships G2, G3, G4 and Optimus L9 II series.
It is worth noting that the availability of updated firmware did not guarantee perfect job. Many devices with 512 MB or 1 GB of RAM began to work slowly after updating to SDK 21 due to the increased requirements of the ART environment.
⚠️ Attention: When purchasing a used device to work with specific software, check not only the Android version, but also the security patch date. Devices running SDK 21 have not received security updates since 2016-2017, which makes them vulnerable on open Wi-Fi networks.
Development features and API limitations
For developers, the transition to API 21 has become one of the most difficult in the history of the platform. The changes affected not only the visual part, but also the deep mechanisms of working with code. The introduction of new permissions and changes in the behavior of background processes required a complete recheck of application logic.
One of the main innovations was the appearance of Material Design. This meant that apps targeting SDK 21 had to use new themes and widgets. Old interface elements (Holo) looked alien and could cause rendering failures on new versions of the system.
The model for working with notifications and access to equipment has also changed. The concept of "Headless notifications" and stricter control over access to the camera and microphone in the background have appeared. These changes laid the foundation for the modern Android permissions system.
- 🔒 SELinux: The SELinux operating mode was changed to "Enforcing" by default, which significantly increased security, but complicated the work of system utilities that require root access.
- 🔋 Battery Optimization: The first rudiments of energy optimization appeared, limiting the operation of applications in the background when the screen is off.
- 📡 Network: IPv6 support has been improved and changes have been made to Wi-Fi scanning to save battery.
If you support legacy code, you will have to take into account that many modern libraries simply do not compile for targetSdkVersion 21. You have to look for older versions of dependencies or write your own wrappers.
Problems with 64-bit architectures
Although Android 5.0 theoretically supported 64-bit processors (ART), many applications of that time were written only for 32-bit (armeabi-v7a). On devices with pure 64-bit chips (for example, some versions of the Nexus 9), such applications could not launch without emulating instructions, which greatly slowed down the system.
Problems with launching modern applications
Users of devices based on SDK 21 often encounter the message “Your device is not supported” in Google Play. This is due to the fact that modern developers raise the minimum API level (minSdkVersion) to 23 (Marshmallow) and higher. The reason lies in the use of new security features and APIs that are not physically present in Lollipop.
Breaking changes to cryptographic libraries in newer versions of Android make it impossible for end-to-end encrypted banking apps and instant messengers to work on older systems. Security protocols are outdated, and servers simply reject connections from clients on Android 5.0.
Even if the application can be installed bypassing the store (via an APK file), there is a high probability of a crash at launch. Errors like java.lang.NoSuchMethodError or ClassNotFoundException indicate that the code is trying to call a function that appeared only in Android 6.0 or 7.0.
| Software category | Status on SDK 21 | Cause blocking |
|---|---|---|
| Banking applications | ❌ Do not work | Outdated encryption protocols and OS security requirements |
| Messengers (WhatsApp, TG) | ⚠️ Partially / No | Refusal of support for older versions of TLS and notification API |
| Social networks | ❌ Does not work | Use of modern web widgets and rendering libraries |
| Office packages | ✅ Work (old versions) | Basic functions do not require new APIs, but no synchronization |
| Games | ⚠️ Depends on the engine | New versions of Unity and Unreal Engine do not support API 21 |
The only way out for such devices is to use web versions of services through a browser or search for modified old versions of applications (which carries security risks).
⚠️ Attention: Interfaces of banking services and security rules change every year. What worked a year ago on Android 5.0 may today be blocked at the server level. Always check the current requirements with the support service of a particular bank.
☑️ Preparing the device for operation
Debugging and emulating the environment
To test applications or work with specific software, an emulator with an API 21 system image is often required. In Android Studio, this is done through AVD Manager. It is important to choose the correct system image, since simply choosing the Android 5.0 version can pull up a newer patch (API 22), which will distort the test results.
When debugging real devices via ADB, you should take into account that the debugging protocol in Lollipop was different from modern versions. Memory and CPU monitoring commands may produce formatted output that differs from what Android 10-14 users are used to.
Particular attention should be paid to access rights. As of SDK 21, the permission model was all or nothing. The application requested all rights upon installation, and the user could not revoke access to the microphone or contacts individually in the settings, as was possible in Android 6.0 (API 23).
adb shell pm list packages -fThis command will show all installed packages and their APK file paths, which is useful for analyzing used space or finding system applications that can be safely disabled to speed things up.
Emulation of Android 5.0 on a modern PC requires the allocation of at least 2 GB of RAM for the virtual machine, otherwise the interface will work with critical delays.
Safety and risks of operation
Operation of a device based on Android 5.0 in 2026-2026 involves serious risks. The lack of security updates means that all vulnerabilities discovered over the past 7-8 years (including critical holes in the Linux kernel and SSL libraries) remain unpatched.
Attackers can use outdated protocol stacks to intercept traffic. Even when using HTTPS, older versions of the OpenSSL or BoringSSL libraries firmware in SDK 21 may be susceptible to "Man-in-the-Middle" attacks.
It is not recommended to use such devices to enter sensitive data: passwords, card numbers, passport data. The best use for them is offline tasks, playing local media content, or using them as a digital photo frame.
- 🚫 Public Wi-Fi: It is strictly not recommended to connect to open networks, since WPA2/WPA3 security mechanisms at the system level may not work correctly.
- 🚫 root access: Obtaining superuser rights on older versions often opens access to kernel vulnerabilities (for example, Dirty COW), which have long been fixed in new OSes.
- 🚫 Third-party stores: Installing APKs from unknown sources on an unprotected system almost guarantees infection by miners or Trojans.
If using the device is unavoidable, try to isolate it from the main network. Set up a guest Wi-Fi network with limited access to local resources for such a gadget.
Is it possible to update Android 5.0 to a newer version?
Officially - no, if the manufacturer has stopped supporting it. Unofficially - it is possible through the installation of custom firmware (LineageOS), but this requires unlocking the bootloader, having TWRP and technical skills. For many devices with SDK 21, there are no longer active builds of modern versions of Android due to drivers.
Why does the application write "Android 6.0 required" even though I have 5.0?
The developer set the minSdkVersion=23 parameter in the application code. This means that the app uses features (such as new permissions or camera APIs) that are not physically available in Android 5.0 (SDK 21). The only way to get around this is to find an old version of the application (v1.x - v2.x) released before 2016.
Which browser is better to use on Android 5.0?
The standard browser and older versions of Chrome no longer receive security certificate updates. It is recommended to use Firefox Focus or special browsers with their own rendering engine (not the system WebView), which continue to receive security updates even for older OSes.
Does SDK 21 affect the speed of games?
Yes, it does indirectly. Games built for the new SDK may not launch. Games built under SDK 21 will work, but the ART environment in Android 5.0 is less optimized for heavy computing than in subsequent versions. In addition, the lack of support for new versions of Vulkan or OpenGL may limit graphics settings.
How to find the exact SDK build through the menu?
Go to Settings → About phone. Find "Build Number" or "Kernel Version". The security version may be indicated there. To accurately determine the API level, it is best to use a free application from the store (if available), for example, "Device Info HW" or "AIDA64", which show the exact API Level.