On Ice Cream Sandwich, I used to use an app called DS Super App2SD but it doesn't work on Android 4.3 Jelly Bean. I'm using Samsung Galaxy Tab 2 running on Cyanogenmod 10.2 nightly (Android 4.3.1) I already tried the adb shell pm set-install-location to SD card location. It made everything worst by thinking my empty 32GB micro SD was full. So I set it back to 0.

I am using Android 4.2.2 Jelly Bean on TI OMAP 5 platform. I want to install applications on an external SD card, but even if a lot of space is free (more than 25MB), I am getting an error "Insufficient storage". 1. Is it possible to install applications on an external SD card in Jelly Bean? 2. How can I move an application installed on internal memory to an external SD card?

Recently I have purchased Micromax A121 Canvas Elanza 2. I have used a 16GB External SD card. I want to change the default storage Internal SD card to External SD Card without installing any apps. I googled and read some blogs. They are saying go to Settings -> Storage -> Change your default storage. But I saw on my mobile there are no options for set default storage.

I want to extend my storage using an SD card. To ensure the data is secure even if the phone is lost or stolen, the SD Card should be encrypted. So formatting the card as portable storage is out. Requirements: - Encrypted - Ability to decrypt and access data using a PC (Linux machine is fine) - SD card should be usable by common apps. - Even when formatting the SD card as adoptable storage, some apps cannot be moved and don't give the option to use said adoptable storage. They do give the option to store their data on a card formatted as portable storage. - Read/write speeds should not be significantly lower than when using SD card normally. - Nice to have: I can still restrict which apps have access where to keep separation and avoid a shared storage space accessible to all apps. I found a couple of other threads on this topic, however, it seems with newer Android versions and scoped storage, these previous methods have some limitations. Considered options: - Format as adoptable storage and move apps there. - Issue 1: not all apps can be moved, some data, like photos/videos are still stored internally. - Issue 2: Decryption isn't easily possible, guides such as [this one](https://android.stackexchange.com/questions/145443/how-to-decrypt-adopted-storage/145446#145446) appear to be outdated. I believe the encryption mode has changed. (If someone has pointers to adapt this to current versions of Android, I'd be thankful). - Set up a LUKS encrypted partition. Various instructions exist on how to set this up in principle, including this [handy script](https://github.com/pegelf/Android-LUKS-mount/blob/e05de18a770cc63a04b86922d12e5af27f449666/01-mount-luks-sd.sh) . - Seems to work in principle, in that I can mount and access the encrypted file system somewhere in /storage/emulated/0/. However, I've not been able to figure out how to get apps to actually be able to write to that mount, given the scoped storage concepts in Android -> permissions error. - Also, some apps don't provide the option to alter the location where they store data, as long as they don't believe an SD card is inserted (e.g. camera storing photos). - **EDIT:** Actually, my main issue here seems to be SELinux. If I setenforce 0, I can use this mount. I haven't found a way around this without significantly weakening security. The perfect solution would be if I could get the phone to think it sees a SD card in "portable storage" mode, which is actually a LUKS-encrypted partition on the card under the hood. Any ideas/pointers on how to set up something like this or similar? Environment: rooted LineageOS 22.1

My Android device no longer recognizes its **encrypted SD card** (formatted as Adoptable Storage), **even though it was originally encrypted by this same phone**. The card is inaccessible in file managers, and standard fixes (rebooting, reinserting) fail. I need to recover data without formatting if possible.

Is there any way to back up directly to my SD card in KitKat without an internet connection? I am currently forced to back up to the internal storage (after clearing space), then copy to the SD card, then delete the copy on my internal storage. This wastes *much* time and effort. My phone storage is only 2.8GB free, but my SD card has 28.0GB free.

I'm using Moto G 2nd Gen with Android version 6.0. I was using an external SD Card as Internal storage, and I guess it has encrypted the card. Recently, my phone started to work abnormally. It randomly fails to recognize the storage. After a device reboot, it would work for some time and fail again. In the "Storage & USB" settings menu, I clicked "Forget" on the external SD card. Then I realized I cannot access the data from my computer using the SD card reader. How can I re-plug the SD card back as Internal Storage without formatting it again?

**System**: rooted Samsung Galaxy S10 with Android 10 I have replaced my old external sdcard (128GB) with a new and bigger one (512GB). The old card was automatically mounted to /storage/6639-3031. The new card is mounted to: /storage/9C33-6BBD. Since I have a lot of configured appz that use custom paths pointed to /storage/6639-3031/somesubfolder I would like to change the new id: 9C33-6BBD back to the old one 6639-3031 system wide. Since there is no fstab in Android responsible for this and I cannot find **where this id's are stored in Android**, maybe some experts here can help me? It seems like a simple problem but I did not find the solution yet. Some clues I already found: 1. Android equivalent of /etc/fstab? 2. Remount FUSE partition Once I have found where this external sdcard id is stored, **can I just change the id** (I have **root**)? **Will it be stay changed after reboot**?

The phone is a Xiaomi Redmi 9 running Android 10 and MIUI 12.0.1. After a reboot, my phone refuses to mount my SD card. From what I have searched, this seems to be a common problem with MIUI, but no one seems to have tried to do anything except reformatting, which probably makes the phone just not scan. - I have checked, the SD card is alright. It never had any problems until the reboot and Android weirdness, and still does not have any problems on any other device. - I have tried putting another SD card from the same brand, and it passed the check, however, that card has way fewer files, which I think might be part of the reason. - I ran adb logcat vold, and I have noticed that every time it tries to mount the card, it runs fsck.exfat, After 50 seconds, the check times out. After a while, the check finishes with no errors, but since it times out, it does not mount. This seems like a pretty bad design choice. - adb shell sm list-volumes returns the card as unmountable. There is a slight chance some corruption occurred after the restart, as it was not present earlier. And yes, I am absolutely sure there are no problems with the card. Now the question is, is there any way to change the check timeout? Or just do anything else to fix this instead of having to move files or format the card? Maybe a way to force the mount? I have tried pretty much everything, nothing works except for the command to mount the card

I'm using Samsung Galaxy S10e on Android 12. I took several screen recordings using the native function. Moved many to SD card using "Files by Google" app. Moved them separately in groups of 1-3. Some of them are playable, some are not. As pictured, the ones with blank thumbnails are unplayable. They are unplayable with both the native video player and EX File Manager. The files still show the full sizes (1+GB). With EX File Manager, I could see that they were 0 mins long in the file info. Worth noting that the SD card is 99% full now. Also, worth noting that a couple of the files wouldn't transfer due to limited space, so I had to make more space, then they transferred, and I remember at least one of the specific files that I had to reattempt is definitely playable after transfer. What can be done?

I have a Samsung Galaxy A7 Lite tablet with updated Android and a 32GB Adata SD card I bought a few months ago. I was trying to move apps from internal storage to an SD card and the tablet suddenly crashed. Now, the apps on the SD card are greyed out and not usable. I tried to move SD card files to a PC and it cannot copy one file with the **asec** extension. The error indicates it's corrupt or broken. Could that be the problem? I don't want to lose data as much as possible. How can I solve it?

I've been having trouble getting my Android devices to recognize my SD card. Despite formatting it to FAT32, none of my Android devices can detect it. However, when I plug it into my Windows or Linux machine, it's recognized without any issues. I've tried reformatting, checking for errors, and using different SD card readers, but nothing seems to work. Has anyone else experienced this problem? Any suggestions or solutions would be greatly appreciated!"

I have a similar goal as discussed here 5,5 years ago: But I'd prefer to use a file-based approach on-top of a "removable storage" setup managed by Android, so I can dynamically choose how much of it I want to use to store my private encrypted files only readable by this phone and other devices where I enter the key - and how much for unencrypted files I can share with other people by removing the microSD-card from my phone. I managed to easily setup a gocryptfs volume using the DroidFS app installed via F-Droid and also mount it via a Termux root shell with gocryptfs /storage/67DF-FCFD/DroidFS /mnt/crypt -nosyslog -allow_other The remaining obstacle is how to make that decrypted view = mount of my gocryptfs volume available for any app to read from and write to? I thought I could use a bind mount, see also: and But so far everything I tried failed:

# mount | grep /crypt
/storage/67DF-FCFD/DroidFS on /mnt/crypt type fuse.gocryptfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=1048576)
tmpfs on /mnt/crypt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=3900340k,nr_inodes=975085,mode=755,gid=1000)

# ls -alih /mnt/crypt/1/
total 5.2M
1048987 -rwxrwx---. 1 root media_rw 773K Mar 11 22:06 IMG_20250311_220628_348196.jpg
1048988 -rwxrwx---. 1 root media_rw 2.1M Mar 11 22:06 IMG_20250311_220639_873732.jpg
1048989 -rwxrwx---. 1 root media_rw 2.1M Mar 11 22:06 IMG_20250311_220644_933558.jpg

# nsenter -m -t pgrep rs.media.module -- mount -o bind /mnt/crypt/1 /storage/emulated/0/crypt
CANNOT LINK EXECUTABLE "mount": library "/data/data/com.termux/files/usr/lib/libtermux-exec.so" not found: needed by main executable

$ su -Mc mount -o bind /mnt/crypt/1 /storage/emulated/0/crypt
mount: '/mnt/crypt/1'->'/storage/emulated/0/crypt': No such file or directory

Please help! Thank you :)

Just in case what I'm seeing is OS specific: I am running the latest OxygenOS on a OnePlus 10 Pro 5G (GLO NE2213_15.0.0.401(EX01)).The phone is rooted via Magisk but I doubt that matters (except for how i can use the phone to format the disk; but the behavior is identical when I format with a PC) I format a USB flash-disk with exFAT, via mkfs.exFAT /dev/sxx1, either from a root termux shell on the phone, or from a root terminal on my (arch) linux PC. Either way, the format succeeds, and I can immediately mount the flash-disk via mount /dev/sxx1 /mnt/. The disk is empty, and I can write and read files on it. But if I then unmount it, unplug it (from the PC or the phone), and then insert it into the phone (which might mean "insert it back into the phone), then the phone automagically both mounts the flash-disk AND writes the following 13 directories/folders onto it:

Alarms   Audiobooks  Documents  LOST.DIR  Music          Pictures  Recordings   
Android  DCIM        Download   Movies    Notifications  Podcasts  Ringtones

I would be grateful to read the explanation of: 1. Just what process/system/thingie in Android is noticing the insertion and reacting in this way? I put "Android udev?" into title of the question as a way of asking how whatever is doing that mount+write compares with udev.... 2. Is there some profound (or even just necessary) reason for or benefit from providing all this structure on EVERY disk one might insert? The fact is that I inserted the flash disk so that I could do a TWRP backup to it. And although there are more annoying things about my phone than just needing to erase some folders whenever i want to use a USB flashdisk, perhaps something "bad" will happen if I do? And in any case, I might well want to retrain it to do something else, once I know what's going on. thanks PS: I note that SE points me to [this and this ; but neither explains what system service is doing this udev-like functionality, nor why it is now MORE invasive than it used to be (in the sense that it now writes 13 directories, and not 2. Perhaps it's a OnePlus/OPPO "improvement" ...)

My photos were encrypted on my phone, a Samsung Galaxy S20 FE with an SD card, but I had a problem with the fingerprint sensor which forced me to factory reset my phone. After that, I can't access any photos. It thinks that the phone has changed. Is there a solution to make the photos known on mobile?

After a factory reset of my Galaxy S5(same accounts and sim etc), some apps did not restore. I suspect it was the large ones I had moved to the SD card a while back for space reasons (I took my SD card out during the reset and restore process). Looking in my files>SD card>android>data, there are plenty of apps that did get restored that have files on SD card, but it helped me pinpoint a few that didn't reappear. For example Excel. I then checked the app manager and there aren't there under SD card (though I might be confusing the inbuilt and external SD card). On Play store>my apps & games, they obviously aren't under 'installed', nor even under 'Library', nor when i search for them individually do the paid versions show as already paid... I synced my backups on google and Samsung accounts directly before the factory reset My questions are: - Where can I find out what I've lost? ie a list of apps as of yesterday - Is there any way of restoring apps moved to SD card? - If not, I might as well wipe the pre-reset data folder on SD-card, right? - What is likely to have happened? - Before any future factory resets, should I move everything important back to phone before syncing and resetting

I recently acquired a replacement phone and as soon as I mounted my existing SD card, the files disappeared while the SD card is showing the storage is in fact used. When I looked at it further, it seemed that Android recognized the files as 'system'. Now, even mounting it on Windows through an SD card reader doesn't work. However, if I use the MTP USB storage mode, it does show but without the files (just shows an empty SD card). Is there a way to undo or recover these files?

I have a textbook Android tablet and an SD card, but when I try to download apps like Viber and other apps, they say I have insufficient space and my tablet is saying "Storage space is running out. Some system functions may not work".

I've tried different file managers on this Android TV 10, but none of them is able to write on the external memory. In the past and other Android TVs, I have written on external storage without this hassle. On Settings, I've granted "Storage" permissions to all the file managers. For example, CX Explorer showed an overlay window with information about the process to grant access to SD in a supposed next window, but no window was open to do these actions. Has Google imposed restrictions on writing on Android TV 10? What can I do?

Nowadays, phones don't have SD cards anymore, but some have a ton of storage. So, I was thinking of creating a fake external SD card using an extra partition to be able to store all of your zip flashable files, pictures, and music and have it stay when you inevitably format user data when flashing a ROM or whatever. My question is: **How to properly mount a partition as an SD card so that Android thinks you have an external SD?** (you see it in a file manager, can store pictures on it directly, etc.) What I've done already : - I have created an extra partition on my OnePlus 6 with parted, it's sda17 - I have successfully mounted this partition to be able to use it normally (mount -t ext4 -o rw /dev/block/sda17 /external_sd) This command allows you to navigate to /external_sd and see your files, but Android doesn't think that you have an external SD card. I'm thinking of using a Magisk module to mount everything properly at every boot (if this is even possible)