Owners of smartphones that have been updated to Android 11are often faced with a paradoxical situation: the device’s memory is full, and standard search tools for “heavy” files do not provide a complete answer. Google's operating system has undergone significant changes in its security architecture, which directly affects access to system directories. The question of where exactly the cache is stored is no longer trivial, since the usual paths have become partially or completely hidden from direct viewing.
Caching is a mechanism designed to speed up applications by storing temporary data for quick access. However, over time, these files grow, taking up gigabytes of usable space. Understanding the file system structure in the new OS version is necessary for proper device maintenance. In this article, we will analyze in detail the physical and logical ways of storing temporary data, as well as methods for safely managing them.
The need for manual cleaning is rare, but in cases of critical memory shortage or software failures, it becomes mandatory. Standard methods of “wiping everything” can lead to the loss of important settings or authorizations in applications. Therefore, it is important to know exactly which folders are responsible for temporary storage, and which absolutely cannot be touched.
Android 11 file system architecture and access changes
Introduction Scoped Storage (limited storage) was the main change that affected access to files. In previous versions of the operating system, applications could request access to the entire contents of the internal memory. Now each app is isolated and only has access to its own files and media content.
This means that the standard file manager you used to use no longer shows the full picture. Folders that were previously viewable are now hidden or only accessible through special permissions. The system protects user data and other applications from unauthorized intervention.
The system partition, where the main OS files reside, remains closed without being retrieved root access. However, the user section, where application data is stored, is now structured more strictly. This increases security, but makes manual garbage cleaning more difficult for advanced users.
⚠️ Attention: Attempts to get root access on Android 11 may lead to loss of warranty and disruption of banking applications due to security integrity checks (SafetyNet/Play Integrity).
The changes affected not only visibility, but also paths. Some system logs and caches have now been moved to hidden sections, accessible only via USB debugging (ADB). This is done to prevent accidental deletion of critical files necessary for stable operation of the interface.
The user must be aware that access restriction is not a bug, but a feature. The operating system takes over memory management more aggressively than before. However, automatic cleaning algorithms are not always effective when working with “heavy” instant messengers or navigators.
The main application cache storage directories
Despite the limitations, the main paths remained the same, only the mechanism for accessing them has changed. Physically, the application cache is stored in the internal memory of the device. To access this data through the file manager, you will need to provide special rights or use built-in analysis tools.
The key directory is located along the path /Android/data/. This is where the folders of all applications installed by the user are located. Inside each folder named by the batch name (for example, com.whatsapp), there is a subfolder cache, where temporary files are located.
The second important directory is /Android/obb/. This is where cached data is stored for games and heavy applications that require loading additional resources. Clearing this folder may result in the need to re-download gigabyte data packages the next time you start the game.
- 📂 /Android/data/ — the main storage for the cache of user applications, including photos from messengers and temporary browser files.
- 🎮 /Android/obb/ — directory for the cache of games and heavy apps, deleting the contents of which requires re-downloading the data.
- 📱 /Android/media/ —new folder in Android 11, where some applications transfer media files that were previously located in the root of memory.
It is worth noting that direct access to the folder /Android/data/ through the standard Explorer in Android 11 is limited. When you try to log in, the system may report that the folder is empty, even if there are files there. This is part of the Scoped Storage security policy.
☑️ Checking memory full
System cache and hidden sections
In addition to user data, there is a system cache, which takes up a significant amount of space. It is located in sections that are inaccessible for normal viewing without special tools. System logs, Google Play Services update cache, and temporary files of the operating system itself are stored here.
Clearing the system cache is often required after major firmware updates. In Android 11, recovery mode is designed for this (Recovery Mode). You can enter it using a combination of buttons when booting the device, which allows you to clear the partition cache partition without losing personal data.
The cache of Google services also takes up a significant amount of space. It accumulates in the background, synchronizing contacts, mail and card data. Excessive growth of this cache can lead to rapid battery drain and heating of the smartphone case.
| Cache type | Location | Cleaning safety | Impact on operation |
|---|---|---|---|
| Application cache | /Android/data/[package]/cache | High | Startup acceleration, loss of autosaves |
| Media cache | /Android/media/ | Medium | Freeing up space, loss of thumbnails |
| System cache | Recovery partition | Low (requires skills) | System stabilization after updates |
| Dalvik Cache | System partition | Critical | Slowdown of the first launch after cleaning |
It is important to distinguish between application cache and application data. The cache can be safely deleted - these are temporary files. The data is your logins, game saves and settings. In the memory management menu, these items are separated, and it is difficult to confuse them when cleaning them through system settings.
What is Dalvik Cache?
Dalvik Cache is an optimized application code that Android creates for quick launch. Clearing it does not remove applications, but forces the system to rebuild this code the next time you turn it on, which may take several minutes.
Methods of access and cleaning through file managers
To work with the file system in Android 11, the standard Explorer may not be enough due to access restrictions. It is recommended to use specialized managers, such as Files by Google, Total Commander or FX File Explorer, which can request the necessary permissions to access system folders.
When you first launch such a manager in a new OS, you will be asked to give permission to access files. In Android 11, this process looks different: the system will take you to a special settings menu, where you need to manually confirm access to the folder Android. Without this step, the folders will be displayed empty.
The algorithm for obtaining full access usually looks like this: you go to the root of the internal memory, try to open the Android folder, the system displays a warning, you click “Use this folder” and confirm the action. Only after this the file manager will have full access to the cache.
The use of third-party Cleaner apps in Android 11 has become less effective. Due to security restrictions, they cannot automatically clear the cache of other apps in the background. Cleaning now requires user interaction or the use of built-in system tools.
Use the built-in Cleanup feature in the Files by Google app - it safely deletes temporary files without disrupting applications and has access to hidden sections.
Using ADB for deep cleaning
For technically advanced users knowledge, the toolkit Android Debug Bridge (ADB) remains the most powerful tool for managing the file system. Connecting to a computer allows you to bypass many visual limitations of the interface and gain access to hidden directories.
To work, you must enable USB debugging mode in the “For Developers” menu. Once connected to a PC, you can execute commands to delete the cache of specific packages or entire directories. This is especially useful if the application has bloated to a gigantic size and does not have an internal cleanup function.
adb shell pm clear com.package.nameThis command completely clears the data and cache of the specified application. Be careful: it resets the application to the state immediately after installation, removing all logins and settings. To clear the cache only (without data), the commands may vary depending on the ADB version and access rights.
You can also access the partition through ADB /data/local/tmp