So, I am using Folder Mount on 4.4.2 Kitkat on the touchwiz ROM.. The issue I am havingis that, after it transfers the obb file to the sd card, it still leaves the obb file in the device storage for some reason, and when I delete that file in Device storage, it seems to delete the sd card obb file at the same time. How do I fix that if its possible?
Related
Whenever I use a TW based ROM, I am able to use the file explorer to view both directories. Upon opening file explorer, it would default to the directory for internal storage. A folder in this directory labeled external_sd would then lead to the directory for the external SD card as advertised.
I realize however that CM9 and AOKP rename internal sd to emmc and external to sd card. The issue is, when using a file browser such as estrongs, the root directory defaults to sd card (aka the external storage) and it is impossible find the emmc. When downloading zips from the browser, the files are automatically saved to the emmc (internal) under the download folder, but on CM9/AOKP I can't figure out how to move files from emmc to sd card because I set TWRP to look at external only. Help?
Sent from my SGH-T989 using xda app-developers app
If you enable root explorer in the settings of esfile explorer (free app) u can go to the internal like on tw roms
Sent from my SGH-T989 using XDA
Try Astro File Manager, it comes up for me just fine.
I don't understand
Hello everyone.
I'm really sorry if I am repeating some other thread or if I am asking questions at the wrong forum. If so, please point me to the right direction.
I searched a lot on the internet about my issue but I can't find any solution for it.
I have a Moto Razr XT910 GSM and just installed AOKP based on Android 4.2.2.
I followed the instructions I found over the internet. They are the same, almost everywhere. So it worked just fine.
I wiped out delvik, cache and internal storage, then created a slot-2 partition with 1GB, where I flashed the ROM. It booted perfectly, and everything was working just fine until I started receiving an error message when I tried to install apps from Google Play. It said I had no space left on my internal storage.
The device I have comes with 8GB internal sdcard. I use my 32GB external sdcard to store music and it was not mounted when I flashed the ROM.
Now, when I go to system settings / storage, I can see I have two entries of internal storage: one with 0,98 GB of space, 150 MB available; and another with 8GB, 5,89GB available, which I can't access and neither can the OS. All the apps are being installed on the 0,98GB internal storage.
When I connect to my PC, it shows two mass storages: one, the external sdcard with 32GB; and the other, the internal sdcard with 8GB, but the Android OS does not recognize almost 6GB of it.
It is not an excess of files or trash, or rest of old OS files, nor anything like that. And all of the sudden I have this icon telling me my "storage space is running out". How can it be if I still have Almost 6GB of free memory? I don't understand,
Can anyone explain to me what is happening? Is there anything I can do to solve this problem?
Thank you very much.
--
Edit:
When I mounted my external sdcard, the OS started to install the app files on it, and not on my internal sdcard.
Also, my root explorer shows something wrong with the sdcard, and sdcard-ext. The files inside the sdcard folder are those from my external sdcard, and vice-versa.
Maybe that is the problem, but I am don't know how to solve it.
I'm in liquid rom when I delete a folder in internal sd by usb I continue seen it in internal sdcard even if I reboot, but because the folder is deleted I get an error when I try to deleted by file explorer, the problem began when I try to blind the folder to external sd
Hi, I recently installed beanstalk 4.3 on my S3 and noted that my internal memory is almost full but I can't figure out what is taking up all the space. I'm including a screenshot, are there any scripts or hacks to swap the internal and SD memory for this ROM?
thanks
Use a file explorer and look at the internal storage and see if there is a folder called 0. If this here than it is most likely the issue and you will need to update your recovery and clean out the 0 folder.
nsmith4 said:
Use a file explorer and look at the internal storage and see if there is a folder called 0. If this here than it is most likely the issue and you will need to update your recovery and clean out the 0 folder.
Click to expand...
Click to collapse
I cleaned up the 0 folder but noticed that on my internal memory root folder I have an external_sd and extsdcard folders (which have everything I have on my actual external sd card) in addition to the storage folder which contains my actual sd card (sdcard1) as well as the sdcard0 and emulated folder. I think this is what's using up all the memory (maybe?) any idea why all these folders were created? can I just erase the external_sd and extsdcard folders since all that data is in my actual sd card or are they bound?
sorry for all the questions but I dont want to mess anything up
nesssy said:
I cleaned up the 0 folder but noticed that on my internal memory root folder I have an external_sd and extsdcard folders (which have everything I have on my actual external sd card) in addition to the storage folder which contains my actual sd card (sdcard1) as well as the sdcard0 and emulated folder. I think this is what's using up all the memory (maybe?) any idea why all these folders were created? can I just erase the external_sd and extsdcard folders since all that data is in my actual sd card or are they bound?
sorry for all the questions but I dont want to mess anything up
Click to expand...
Click to collapse
No don't delete those folders. Those are linked to your SD card should have nothing to do with your internal memory. Nor sure what's going on with your internal memory though. You may want to try saving your 0 folder to a pc then deleting it entirely(the 0 folder). If that doesn't work then maybe go back to stock.
When you check out an app's info, there is an option to "Move to SD card". When I do this, I see that the available internal storage space really does free up. I tried finding the app data in the external sd, but no new directories are made and the size of the "Android" folder in the external sd remains at 32 bytes. So, where is the app data in the external sd?
I don't mean to resurrect an old thread, but I felt compelled to answer this, since this issue bugged me for hours. I'll just leave it here in case anyone else stumbles on to this.
If you are able to move apps to the SD card in G3, android v.4.4 Kitkat, whether by default, or by applying the SD Fix ("media_rw"...), then doing so will only move certain files to your SD (the .apk, I think), but not inside the /external_SD/Android/data folder. The files will instead be moved to the /.android_secure folder, which is hidden and cannot be viewed using a file browser in Android, even with root (tried ES Explorer). You can view this folder if you insert the SD directly to your PC via a card slot. The files moved will have the .asec extension.
In order to move the actual files from the data or obb folder, and save space, one would have to use an app such as FolderMount, although I haven't tried this myself.
My phone is detecting my external san disk memory card but the contents of the card are not visible. It says there are no files but it is actually full of files. If I move a file from internal t o the external sdcard that file only is visible in the gallery but it is not visible in the file manager. I am using root explorer. I am not rooted. Please help.
thadoukuki said:
My phone is detecting my external san disk memory card but the contents of the card are not visible. It says there are no files but it is actually full of files. If I move a file from internal t o the external sdcard that file only is visible in the gallery but it is not visible in the file manager. I am using root explorer. I am not rooted. Please help.
Click to expand...
Click to collapse
Try the stock android browser. It might be the KK sd card problem popping its head up.
The only way to fix that is to root and run KK sd car fix from playstore...