Owners of smartphones with limited internal memory often face a critical lack of free space, especially after updating to Android 11. The system began to take up more space, and modern applications require more and more resources, which forces users to look for ways to expand the storage. Transferring data to an external drive seems like an ideal solution, but Google has made this process much more difficult in the latest versions of the operating system.
Starting with Android 6.0, the Adoptable Storage function allowed you to combine internal memory and a microSD card into a single pool, but by the release of the eleventh version, most smartphone manufacturers completely abandoned this option in their shells. Now, using standard settings menu tools, it is almost impossible to move app executable files to external media, unless the manufacturer has explicitly left such a button. This is done for the security and stability of the device, since external memory cards often have low read and write speeds.
However, there are workarounds to solve the problem of not having enough gigabytes without buying a new phone. In this article, we will look at all the available methods: from checking hidden settings to using advanced ADB debugging tools. You will learn why the system writes “Cannot move” and how to bypass this prohibition by turning your microSD card into a full-fledged extension of the internal memory.
Why Android 11 limits the transfer of applications
The main reason for blocking the transfer of applications lies in the security architecture Android Runtime and the requirements for the speed of drives. Unlike older versions of the system, where applications could easily run from slow class 4 or 6 cards, modern apps require high response speeds, which only built-in eMMC or UFS chips can provide. If the application starts from a slow card, it will lead to UI freezes and data loss, which degrades the user experience.
Additionally, Google has implemented strict data encryption rules. When you install an application, its data is encrypted and tied to a specific device and memory section. Moving this data onto removable media that can be easily removed and inserted into another phone creates a security hole. The Android 11 system prohibits such operations by default to prevent data theft or malicious code running from an external source.
It is also worth considering the policies of smartphone manufacturers. Companies like Samsung, Xiaomi or Huawei often modify the Android source code to remove support for the Adoptable Storage feature at the system kernel level. This is done not only for the sake of safety, but also to stimulate sales of models with a large amount of built-in memory. Even if your memory card has a speed class of U3 or V30, the system may ignore it as potential storage for apps.
⚠️ Warning: Using third-party transfer methods may lead to unstable operation of applications. If the memory card is removed or damaged, all transferred apps will no longer run and their data may be lost.
Understanding these limitations is important before starting any manipulations. You should be aware that bypassing system restrictions is always a risk that requires a backup copy of important data. However, if you are ready to experiment, the following sections will help you free up precious megabytes of internal memory.
Checking transferability using standard means
Before resorting to complex methods with a computer and the command line, you need to make sure that your specific smartphone does not support the transfer natively. Some manufacturers, especially in the budget segment, still leave this option, but hide it in the depths of the menu. To begin, insert a high-quality memory card and wait for it to be fully initialized by the system.
Go to the settings section of your device. The path may differ depending on the shell, but most often it looks like this: Settings → Applications → Manage apps. Select the app you want to move and click on "Memory" or "Storage". If the "Edit" or "Move to SD card" button is active and not greyed out, you're in luck - you can transfer data in one click.
In most cases on Android 11, you will see a "Can't move" message or a ghost button. This means that the application developer has disabled the transfer in their manifest, or the system is blocking the operation globally. It is important to note that system applications and widgets cannot be transferred under any circumstances, since they are critical for loading the operating system.
If the standard method doesn’t work, don’t despair. There is a more powerful tool built into Android itself that allows you to bypass these restrictions. It is called Android Debug Bridge (ADB) and gives the user rights to change the file system configuration, hidden from the normal interface.
Preparing a smartphone and computer to work with ADB
To complete further instructions, you will need a personal computer (Windows, macOS or Linux) and a USB cable. The first step is to activate developer mode on your smartphone. Find the "Build number" item in the "About phone" section and quickly click on it 7 times in a row until a notification appears indicating that you have become a developer.
Next you need to enable USB debugging. Go to the "For Developers" menu that appears (usually in the "System" or "Advanced" section) and activate the switch USB debugging. When you connect your phone to the computer for the first time, a request to confirm debugging will appear on the smartphone screen - be sure to click “Allow” and select “Always allow from this computer.”
Now you need to prepare the software on the PC. Download the official platform SDK Platform Tools from the Android developers website. This is a set of legitimate tools that does not require installation and works through the command line. Unpack the archive into a convenient folder, for example, the root of drive C, so that the path to the files is short and does not contain Cyrillic characters.
☑️ Checking readiness for transfer
Make sure that the computer sees your device. Open a command prompt in your tools folder and enter the command adb devices. If the serial number of your smartphone with status deviceappears in the list, then the connection has been established successfully. If the device is not displayed, ADB drivers may not be installed or a cable that only supports charging is used.
Instructions for transferring via the ADB command line
The transfer process itself consists of sending a special command to the PackageManager server. This command forcibly changes the installation flag of the application, allowing it to be placed on external media. First you need to know the exact package name of the application you want to move. This can be done through the command adb shell pm list packages, which will display a long list of all installed apps.
To simplify the search, use a filter. For example, to find the Telegram messenger package, enter: adb shell pm list packages | findstr telegram (for Windows) or adb shell pm list packages | grep telegram (for macOS/Linux). In response, you will receive a string like package:org.telegram.messenger. We need the part after the colon - org.telegram.messenger.
Now run the command to wrap. The syntax is as follows:
adb shell pm set-install-location 2However, this command changes the global setting for all future installations. To move an already installed application, use the command:
adb shell pm move-package org.telegram.messenger externalReplace org.telegram.messenger with the name of your package. After executing the command, the system will try to move the files. Successful completion of the process is not always accompanied by a visual notification, so check the result through the app settings menu or with the command adb shell pm get-install-location, which should return the value 2 (external memory).
⚠️ Attention: The command
move-packagemay not work for system applications or apps that are hard-coded in the internal memory by the developer. In this case, you will receive a "Package not movable" error.
What should you do if the command returns an error?
If you see an error message, try uninstalling the application first and installing it again with the install-location 2 setting active. Also make sure that the memory card has free space and is formatted as internal storage (if such an option was used previously).
Using the Adoptable Storage function (for advanced)
There is a more radical method that forces Android 11 to perceive the memory card as part of the internal memory. This process is called formatting the card as internal storage. It completely encrypts the card and links it to a specific phone. After this procedure, it will be impossible to remove the card without losing data and move it to another phone.
To activate this function, if it is hidden by the manufacturer, it is often necessary to use ADB commands to change the system configuration. The command adb shell sm list-disks will show your card ID (for example, disk:179,64). Next comes the formatting command: adb shell sm partition disk:179,64 private.
After successful completion, the phone will offer to transfer data. This method is the most effective, since the system itself will decide where to download new applications. However, the interface speed may decrease if you use a cheap memory card. It is recommended to use standard cards A2 (Application Performance Class), which are optimized for running applications.
| Parameter | Standard SD card | A2 class card | Internal memory (UFS) |
|---|---|---|---|
| Read speed | Up to 100 MB/s | Up to 160 MB/s | Up to 2000 MB/s |
| Write speed | Up to 30 MB/s | Up to 90 MB/s | Up to 1500 MB/s |
| IOPS (operations per second) | Low | High (4000+) | Very high |
| Suitability for apps | Photo/video only | Good | Ideal |
Buy memory cards only from trusted brands (SanDisk, Samsung, Kingston). Cheap cards from marketplaces often have underrated characteristics and quickly fail when recording is active.
Possible problems and their solutions
During the transfer process, users often encounter various errors. One of the most common is that the application stops updating on Google Play. This happens because the app store cannot access the files on the external storage device with write permissions. The solution is to temporarily return the application to the internal memory before updating.
Another problem is the appearance of the “SD card is damaged” notification or constant interface lags. This indicates that the card is not fast enough to run modern applications, or the file system is corrupt. In this case, you need to format the card again or replace it with a more powerful model.
It is also worth mentioning the problem with WhatsApp and Telegram. These messengers store huge amounts of media files. In Android 11, folder paths have changed to Android/mediaand some files may become invisible to the gallery after transfer. Use file managers with access to system folders to find your media.
If after the transfer the phone starts to work slower, return the heaviest applications (social networks, navigators) back to the internal memory. It is better to use a memory card for photos, videos and music.
Don't forget to back up your data regularly. External drives are less reliable than the built-in flash memory of a smartphone. A sudden failure of the card can lead to the loss of progress in games or important documents stored in transferred applications.
Frequently asked questions (FAQ)
Is it possible to transfer an application back to internal memory?
Yes, it is possible. Use the command adb shell pm move-package package_name internal or select the "Move to device" option in the application settings if it becomes active after the transfer.
Will migrated applications eat up more battery?
Theoretically, yes, Reading data from an SD card may use a little more power than reading from internal memory, but in practice the difference is not noticeable. The main impact on the battery is the activity of the application itself, and not where it is stored.
What will happen to the application data if you remove the memory card?
The application will no longer launch, and its icon may disappear from the desktop or become gray. All data on the card will not be available until it is reinstalled on the same smartphone.
Does this method work on Android 12 and 13?
The principle of operation of ADB commands remains similar, but the folder structure and access rights in Android 12/13 have become even stricter. The command move-package may be blocked at the kernel level in new firmware versions of some manufacturers.
Do I need to format the card before transferring?
It is advisable to format the card to the exFAT or FAT32 file system through the phone settings to ensure maximum compatibility. Formatting will delete all data from the card, so make a backup copy in advance.