The situation when applications refuse to move to the memory card in the Android operating system is one of the most common problems faced by users of budget and mid-budget smartphones. The device's internal memory often fills up faster than expected, and the standard solution seems to be to transfer data to an external drive. However, when you try to activate the corresponding option in the settings or application menu, the button may be inactive, absent altogether, or the system displays a runtime error.
The root of the problem lies in the deep changes in security policy and file system architecture that Google has been implementing since Android 6.0 Marshmallow and continuing in more recent releases. Operating system developers are gradually limiting random access of applications to external drives to protect user data from theft and ensure system stability. Understanding the technical reasons for this ban will allow you not to waste time on useless attempts, but to find a truly working solution to free up space.
In this article we will analyze in detail the transfer blocking mechanisms, explain the difference between adaptive storage and portable mode, and also consider the available methods for bypassing the restrictions. You will learn why some apps physically cannot be moved, even if technically there is free space on the card, and what risks are hidden behind attempts to force a transfer through third-party utilities.
Android architectural limitations and security policy
The main reason for the impossibility of transfer is a change in the data storage structure. Modern versions of Android use a system of access rights that strictly isolates the data of each application. By default, external drive is considered by the system as an untrusted zone, to which critical software should not have access. This is done so that if the memory card is removed or damaged, the application does not lose its configuration files and stop working.
In addition, Google has introduced the concept of on-the-fly data encryption. The internal memory of a smartphone is encrypted with a key tied to a specific device. If an app is moved to an SD card that has not been formatted as internal storage, it will lose access to its encrypted data. The system simply does not allow you to perform an operation that is guaranteed to lead to a failure of the app.
⚠️ Attention: Attempts to forcibly change the attributes of application files through root access can lead to a violation of the integrity of digital signatures. In this case, banking applications and highly secure services may stop launching.
It is important to understand that the absence of a transfer button is not a bug, but a feature implemented at the system kernel level. Android developers have deliberately limited functionality to prevent data fragmentation and performance degradation, since the reading speed of external cards is often lower than the speed of internal eMMC or UFS memory.
Requirements of application developers and manifest files
Another critical factor is the position of the software developers themselves. When creating an application, the programmer sets in its manifest (file AndroidManifest.xml) a parameter that determines the possibility of installation on external drives. If the code contains a value android:installLocation="internalOnly"then the operating system will physically prevent the user from moving this software to the SD card, regardless of the phone settings.
Why do developers choose this path? Applications that need to run in the background (messengers, alarm clocks, health trackers) require instant access to resources. External memory cards, especially budget models, may have a high response lag or go into sleep mode to save power. If an important application ends up on such a carrier, notifications may arrive late, and the alarm may not work.
In addition, there are applications that are tightly integrated with the system or require high data exchange rates. These include launchers, widgets, live wallpapers and some graphics-heavy games. Transferring such apps to a card with a low reading speed will cause lags and freezes, which will negatively affect the user experience and the reputation of the developer.
How to check whether the transfer is allowed by the developer?
To do this, you can use utilities like App2SD or the ADB command "adb shell pm get-install-location". However, the easiest way is to try moving the application through the standard settings. If there is no option, it means that the developer has prohibited this action at the code level.
It is worth noting that large companies such as Facebook or Instagram often update their applications, and the data placement policy may change in new versions. What could be transferred a year ago can today be blocked by the developer in order to increase stability.
SD card operating modes: Portable storage vs. Internal
The key point in understanding the problem is the difference between the two operating modes of the external drive in Android. By default, the card operates in Portable Storage (Portable storage) mode. In this mode, it behaves like a flash drive: you can put photos, music and documents there, but system restrictions prohibit installing full-fledged applications there.
There is a second mode - Adoptable Storage (Adaptive storage). When this mode is activated, the memory card is formatted, encrypted and becomes a logical extension of the smartphone’s internal memory. The system begins to consider it an integral part of the phone. Only in this mode does it become possible to transfer most applications that were previously blocked.
However, activating adaptive storage has its own nuances. The memory card must have high write and read speeds (class not lower than UHS-I, preferably U3). If you use a slow card as internal memory, the entire smartphone interface will begin to slow down, since the system will constantly access the slow media for system files.
Use memory cards marked A1 or A2. These standards are specifically designed for running applications from a memory card and guarantee a minimum number of I/O operations per second.
When switching to internal storage mode, all data on the card will be destroyed. Also, this card cannot be simply removed and inserted into a computer or other phone without losing access to the data, since they will be encrypted with the key of a specific device.
Technical characteristics of the memory card and compatibility
Even if you have configured the card as internal storage, problems may arise with transferring specific applications due to the technical limitations of the drive itself. The file system of the card also plays a role: modern versions of Android require formatting in ext4 or f2fs to work in internal storage mode, while standard cards come with a file system exFAT or FAT32.
The following table shows the impact of card characteristics on the ability to transfer applications:
| Characteristic | Impact on application migration | Recommended value |
|---|---|---|
| Speed class | Low speed causes timeouts during installation | Class 10, UHS-I (U3) |
| File type systems | Incompatible formats block transfer | ext4 (when formatted by the system) |
| Memory capacity | Cards older than 128 GB may not be supported | Up to 256 GB (depending on model) |
| Health status | Sector errors make transfer impossible | Lack of bad sectors |
If the memory card has bad sectors or low writing speed, the Android system can automatically block attempts to write application data there to prevent damage. In this case, I/O errors will appear in the system logs.
It is also worth considering the age of the card. Over time, the resource for rewriting memory cells is depleted, and the drive goes into read-only mode or begins to operate unstable. In this case, transferring applications becomes technically impossible, and it is recommended to replace the card.
Methods for bypassing restrictions through ADB and the engineering menu
For advanced users, there is a way to force the system to ignore the ban of the application developer. This is done through USB debugging and the use of tools Android Debug Bridge (ADB). This method allows you to force a change in the installation location for all new applications or move a specific application, even if the button in the interface is inactive.
First, you need to activate the developer mode by quickly clicking 7 times on the build number in the menu About the phone. Then the menu for developers includes USB debugging. After connecting to the computer, a command is executed to change the global installation parameter.
adb shell pm set-install-location 2This command tells the system that by default all applications should be installed on external storage (value 2). A value of 0 returns the auto setting, and 1 forces everything to internal memory. However, it is worth remembering that this is not a panacea: if the application is hard-coded to work only internally, it may simply not start after transfer.
☑️ Preparing to use ADB
⚠️ Attention: Using ADB commands to change system parameters can lead to unstable operation of the device. If after the command
set-install-locationthe phone begins to behave strangely, return the value to 0 (automatically) by rebooting or repeating the command.
Alternative solutions: transferring media and cache
If you cannot transfer the applications themselves, free up the internal memory by transferring user content. Most heavy applications (Telegram, WhatsApp, Instagram, Spotify) store the bulk of data not in the body of the app, but in their folders with cache and media files.
Many modern applications allow you to independently choose the path for saving downloaded files. For example, in instant messengers you can configure saving received photos and videos directly to an SD card. In navigators (Yandex.Navigator, Google Maps), you can manually move offline maps to an external drive through the settings of the application itself.
To manage the cache of social networks and browsers, you can use built-in cleaning tools or third-party file managers with a disk analysis function. Moving folders Android/media and Android/data (with caution) can free up gigabytes of space, making the issue of moving the application itself less pressing.
Moving media files and caches often frees up more space than moving the body of the application itself, and does not require complex manipulations with access rights.
It is also worth considering the possibility of using cloud storage. Services like Google Photos or Yandex.Disk can automatically upload photos and videos to the cloud, deleting their local copy from the device, thereby freeing up precious internal space.
Frequently asked questions (FAQ)
Why did the ability to transfer disappear after updating Android?
In new versions of Android (11, 12, 13 and higher) Google is tightening its security policy, completely blocking application access to the file system of external cards in portable storage mode. This is a system limitation that cannot be circumvented without formatting the card as internal storage.
Is it safe to format the card as internal storage?
It is safe for data if the card is of high quality. However, the card will be encrypted and linked to this phone. You won’t be able to insert it into another phone or PC without formatting (and losing data). Also, the card should not be removed while moving.
Is it possible to transfer system applications to an SD card?
It is strictly not recommended. Transferring system components can lead to a cyclic reboot (bootloop) or complete inoperability of the smartphone. The system blocks this action to protect the integrity of the OS.
Why is a 64 GB card detected as 32 GB or does not allow files to be transferred?
Perhaps the card is fake or has a FAT32 file system, which does not support files larger than 4 GB and has capacity restrictions. To work with Android, it is better to reformat it to exFAT through standard system tools.
Will the application be deleted from the phone if you remove the SD card?
If the application is installed on the card (or transferred there), then when the drive is removed, it will stop working, and its icon may disappear from the desktop or become gray. These applications will not be available until the card is returned to its place.