Develop Bugs

[MOD] MicroSD 2 Internal Memory Swap w/ICS support

***Warning Dragons Ahead!!***
Do this at your own risk, it will not void your warrantee but it may make your device unresponsive and cause other issues that I haven't discovered yet! Also, DO NOT at any point attempt to use the unmount sdcard found in your storage settings and DO NOT take your micro sdcard out while your tablet is on, doing these things will cause your apps to fc and potentially loose data. This has been tested only for the Iconia A100 and other devices will probably have different mount points.
It's working great for me but your results may vary, I am not responsible for any damage or problems you might encounter by using this mod (very unlikely that you'll have problems though).
What this mod does:
Since this particular tablet only has 5.4gb of internal storage, I thought it would be great to use my external sd (which is much larger) to install app data and everything else on. So this mod will dirty swap your External micro sd card with your internal memory and vice versa. By dirty swap I mean that the original mount points are untouched and I've just re-bound the mount points to different locations in the tablet. Not the ideal way of doing it, but it works and since we can't touch our init its just about our only option.
It will also speed up your sdcard's read and possibly write speeds by increasing the sdcard's cache.
Requirments: (things you'll need before doing this mod)
You'll need to be rooted, have root explorer installed and of course a micro sd card in your tab:
Instructions:
- Download and unzip the attached file and put it in the root of your internal sdcard (/mnt/sdcard)
- Open root explorer and navigate to /mnt/sdcard (if its not already there) tap and hold on the file install_recovery.sh and pick the copy option
- Now navigate to the /etc folder tap the Mount r/w button
- Find the install_recovery.sh file tap and hold it, then select the option rename. Change the name to install_recovery.bak and then tap paste to copy over the new file.
Now look just under the file, you'll see the date and permissions, it should say something like rwxrwxrwx if it does not you'll need to tap and hold the file tap permissions and check all three boxes for read and execute.
Once you've done the above steps reboot and wait about a minute after your tab comes up, goto settings and look at your storage space to see if the internal space size has changed.
To reverse just delete the install_recovery.sh file, rename the backed up one and reboot. If you decide to keep this mod, you'll want to copy the contents of /mnt/external_sd to /mnt/sdcard so you dont loose any of your app data. Also, you'll no longer need GL 2 SD or any other mod to fetch data from your micro sdcard.
Note: if you have problems deleting or writing to /mnt/external_sd after doing this mod, in root explorer goto /mnt press Mount R/W tap and hold on external_sd and choose permissions. Make sure that all boxes for read and write are checked.
You can use this in conjunction with ICS, its been tested and works great (actually improved my bench scores in antutu benchmark). You can merge the system r/w mod with this one to keep your system read /writable (in ICS) just add the system r/w commands to the end of this install-recovery.sh file.

Thank you! This Mod is greatly appreciated. I'll give it a go once my hangover settles down
Sent from my SPH-D700 using xda premium

Works like a champ. Awesome.

crossix,
...thanks a bunch for this mod, it works great, I've tested a number of apps and scenarios and so far so good.
I reviewed the original install_recovery.sh and noticed that it's there for some sort of firmware / recovery updates. ...so since we replaced the script I'm wondering if it will prevent future firmware upgrades, or more importantly could it prevent an emergency restore / recovery.
Perhaps merging your script with the original would be beneficial?
...any thoughts on this?
Thanks again for your effort on this, FredT

I don't forsee any issues, unless you get an ota update, then you'll need to redo this mod.
The system runs /system/etc/install-recovery.sh on boot and would normally check the recovery partition for files changed outside of an ota update (ie viruses or cwm). If a file gets changed this script would run at boot and restore it's origional recovery.
Normally in order to get cwm or any other custom recovery to "stick" you would need to delete this file (or delete it's contents) so that your modded recovery wouldn't be overwritten on the next boot.
An OTA update will overwrite the install-recovery.sh file and you may have to follow the above instructions again (or it may even break my mod). I'm still running the origional stock rom (3.2) and haven't tested this mod on the newer versions.
Sent from my MB860 using XDA App

cool thanks.... btw I am on the latest 3.2.1 ota update and this is working great for me so far....
Sent from my A100 using Tapatalk

thanks buddy

what format for the SDCARD
so I got a new large SDCard to use for this setup... I bought it off a buddy and it is formated as EXT4 already. I'm going to reformat it, what is the best format to use with HC ? EXT4 or something else?
Thanks FredT

Unfortunatly only fat32 will work, I've tried formatting & mounting the sdcard as ext2, 3 and 4, but couldnt get the tab to mount it automatically.

Thank you a million times can finally put all my gameloft games on the sd card without having to delete others.

I don't have install_recovery.sh I have a init_goldfish.sh
And the etc folder you are talking about, is it the one in system or the one just under the main root of the device (/etc or /system/etc)? I only bring that up because I thought it odd I had two "almost" identical etc folders!?! One in /system and one under /.
Either way, I don't have a install_recovery.sh file. only the init_goldfish.sh file. Any thoughts on this?

/etc is actually a symlink to /system/etc so they are one in the same.
What Build is your tab running? (find out by tapping the time in the bottom right corner of the screen and then push the little lines on the right and tap system, scroll down to about tablet and look for build number.
Sent from my MB860 using XDA App

It worked like a charm!!!!
I just have one question, what happens to the files/apps on internal memory? So basically it just swapped it witb external sd?
Sent from my A100 using xda premium

Yup, you can just copy all of the contents from /mnt/external_sd back to /mnt/sdcard and everything should be good.

Awesome mod, this is a life saver. Just the other day found myself having to delete apps to dload GTAIII now I can use my 32GB Sd Card.
Thanks a ton!

crossix said:
/etc is actually a symlink to /system/etc so they are one in the same.
What Build is your tab running? (find out by tapping the time in the bottom right corner of the screen and then push the little lines on the right and tap system, scroll down to about tablet and look for build number.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't have the file under /etc or /system/etc either
Kernel version 2.6.36.3
Build number Acer_A100_1.018.05_COM_GEN2
Edit: I followed the instructions and it WORKED!!!!
Sent from my HTC EVO 3D using xda premium

apparently they are having some success getting this to work with the a500 so assuming you can find a working root method for the a101, this should work with it as well.
Sent from my MB860 using XDA App

Thank you for this
One problem - I needed to move to a larger drive due to Audible - but now that I'm moved over, Audible is complaining "Please insert SD Card" and then exiting!
Looks to be more of a Audible thing vs. storage, but if anyone has any thoughts on working around this, that'd be great

OK... Weird thing. I have about 3gb free space in my micro SD card, 2.5gb of real internal memory, but only 880mb free for application space. Is it just me?

This did not work for me, I follow all your instruction but still nothing, can it be because I have the build.prop mod act, any help.
Sent from my A500 using xda premium

Android 4.2.1 and Multiuser Thingy

Sorry to create a new although they have alot of thread regarding this Recovery+0 Folder+Multiuser because none of them solve my problem.
I already flashed the latest CWM(6.0.1.9)
When I tried to flash AOKP 4.2.1 on my Gnex which is currently running on CNA 3.8,It is showing 4 different types of Storage in Astro file manager?
Even I tried to wipe the whole sdcard and Installed Custom rom on top of Factory Image,It is still showing like
Local Storage 1 (/mnt/shell/emulated)
Local Storage 2 (/storage/emulated)
Local Storage 3 (/storage/emulated/0)
Local Storage 4 (/storage/emulated/legacy)
IS there any way to avoid it?
Is there any way to remove it?
I heard that Latest PA doesn't have this multiuser thing,Is that true?

use the guide linked in my sig

IntelBashy said:
Sorry to create a new [...] because none of them solve my problem.
[...]
IS there any way to avoid it?
Is there any way to remove it?
Click to expand...
Click to collapse
I don't think so since there is no problem or better that's Astros problem. There is nothing wrong with these mounts, I have the same on my Nexus with stock ROM (flashed the factory image via fastboot).

I'm not sure why everyone is so hellbent on "fixing" the new data structure. I'm pretty sure Google's engineers know what they're doing with file system layouts. Here's some information I posted in another thread:
Specifically, the physical internal storage is found at /data/media.
/data/media is fuse mounted as /mnt/shell/emulated.
/mnt/shell/emulated/0 is then symlinked to /storage/emulated/legacy.
/storage/emulated/legacy is then symlinked to /sdcard, /mnt/sdcard, and /storage/sdcard0.
So the files seen in /sdcard are files physically located at /data/media/0. As such, files in /data/media can use space, but not be seen when looking in /sdcard.
Click to expand...
Click to collapse
That was a thread about missing space, but it shows the basic file structure. Everything is necessary for forward and backward compatibility. The only problem with the new structure was for early adopters who were flashing multiple 4.2 ROMs without an updated recovery and ended up with multiple nested /0 folders. Other than this issue, the new file structure is working as intended. The "multiple copies" are symlinks and fuse mounts, which don't use any extra space.

I'm not sure why everyone is so hellbent on "fixing" the new data structure.
Click to expand...
Click to collapse
People are always looking for something to complain about and noobs don't search. Combine the two and you've got dozens of threads about sdcard/0.

noobs...
063_XOBX said:
People are always looking for something to complain about and noobs don't search. Combine the two and you've got dozens of threads about sdcard/0.
Click to expand...
Click to collapse
I kinda agree with you for the most part, but being a well-worn noob, sometimes you get overwhelmed and a lot of the search utilities on many forums are for crap. Sometimes what the search comes up with doesn't always fit the situation. For noobs, a hand-holding goes a long way. Some of the current noobs will be helping someone in the future (me for example). The "search damnit!" mentality doesn't work on someone who is panicking b/c their phone is jakked.

prostang said:
The "search damnit!" mentality doesn't work on someone who is panicking b/c their phone is jakked.
Click to expand...
Click to collapse
Pre-research would prevent 75% or more of the "I screwed my phone up" situations that happen.

I even had this same kinda problem today. To remove it I tried top delete emulator folder but I didn't know it's a sdcard menu... So I got into trouble by removing it... :'( SD CARD FORMATTED..
Sent from my Galaxy Nexus using Tapatalk 2

prostang said:
The "search damnit!" mentality doesn't work on someone who is panicking b/c their phone is jakked.
Click to expand...
Click to collapse
I have to disagree, do you go cross a minefield without the mines being marked?
Well it's not about your life on this one, but you get the analogy.
You research on unlocking and rooting before you go all jack sh*t and f*ck your phone up..

prostang said:
I kinda agree with you for the most part, but being a well-worn noob, sometimes you get overwhelmed and a lot of the search utilities on many forums are for crap. Sometimes what the search comes up with doesn't always fit the situation. For noobs, a hand-holding goes a long way. Some of the current noobs will be helping someone in the future (me for example). The "search damnit!" mentality doesn't work on someone who is panicking b/c their phone is jakked.
Click to expand...
Click to collapse
Just because somebody makes a mistake and ****s up their phone doesn't suddenly make them special. If 90% of users can manage to use their phone without messing it up then the 10% who can't should learn to follow instructions, the most basic of which is to use the search function.

sam razzy said:
I even had this same kinda problem today. To remove it I tried top delete emulator folder but I didn't know it's a sdcard menu... So I got into trouble by removing it... :'( SD CARD FORMATTED..
Click to expand...
Click to collapse
Perfect example of why people shouldn't mess with their file system structure without understanding it.

Thanks so much for the clear explanation of the 4.2 file system. My problem is making 4.1.2 and 4.2 coexist. If I move data from /data/media to /data/media/0, my Books directory, for instance, so I can access it from 4.2, then it disappears from 4.1.2... I'm going to try symlinking a /data/media dir to /data/media/0 in 4.1.2, and see if it shows up in 4.2.... Nope, at least not simply... I'll keep playing w/it. If anybody has any suggestions for keeping data from 4.1's /sdcard on 4.2's /sdcard, and vice versa, I'd appreciate the hints
Cilraaz said:
I'm not sure why everyone is so hellbent on "fixing" the new data structure. I'm pretty sure Google's engineers know what they're doing with file system layouts. Here's some information I posted in another thread....
Click to expand...
Click to collapse

Cilraaz said:
I'm not sure why everyone is so hellbent on "fixing" the new data structure. I'm pretty sure Google's engineers know what they're doing with file system layouts. Here's some information I posted in another thread:
That was a thread about missing space, but it shows the basic file structure. Everything is necessary for forward and backward compatibility. The only problem with the new structure was for early adopters who were flashing multiple 4.2 ROMs without an updated recovery and ended up with multiple nested /0 folders. Other than this issue, the new file structure is working as intended. The "multiple copies" are symlinks and fuse mounts, which don't use any extra space.
Click to expand...
Click to collapse
Thank you for that description! I've searched before but couldn't find that information for some reason. It explains a problem I had a while back and couldn't figure out. :thumbsup:

dbrickg said:
Thanks so much for the clear explanation of the 4.2 file system. My problem is making 4.1.2 and 4.2 coexist. If I move data from /data/media to /data/media/0, my Books directory, for instance, so I can access it from 4.2, then it disappears from 4.1.2... I'm going to try symlinking a /data/media dir to /data/media/0 in 4.1.2, and see if it shows up in 4.2.... Nope, at least not simply... I'll keep playing w/it. If anybody has any suggestions for keeping data from 4.1's /sdcard on 4.2's /sdcard, and vice versa, I'd appreciate the hints
Click to expand...
Click to collapse
You can't symlink /data/media to /data/media/0, since both are existing directories.
Are you dual booting or something? If so, don't, since the different file structures aren't compatible. If not, then why do you need 4.1.2 and 4.2 to co-exist? If you're looking at it from a developer standpoint, use the endpoint (/sdcard), as that will be the same regardless of the file structure.

Sorry if I wasn't clear: not symlinking /data/media to /data/media/0 (though I have seen that done... makes interesting infinite loop , but, for instance, ln -s /data/media/Books /data/media/0/Books.
As for the other question, not dual booting, per se, but moving back and forth between one backup and another. Since I'm still not sure about all the features of 4.2, I'd like to be able to return to 4.1. And, /sdcard is NOT the same regardless of file structure. In 4.1, /sdcard has all my data, but when I install 4.2, /sdcard has lost it all. If I move the data from /data/media to /data/media/0, then /sdcard has the data for 4.2, but loses it if I return to 4.1. As you say, the file structures aren't compatible. I was just hoping someone had come up with a simple way to make them appear to be compatible. I thought symlinking would make sense, but it just doesn't work. I could copy everything from /data/media to /data/media/0, but then I'd double my data, and have all the problems of keeping 2 sets of data in sync. Eventually 4.2 will get its bugs worked out, and I'll feel confident about moving to it permanently, but for now, I'd like to keep both, and it's frustrating that I haven't been able to figure out a way to make that work.
Cilraaz said:
You can't symlink /data/media to /data/media/0, since both are existing directories.
Are you dual booting or something? If so, don't, since the different file structures aren't compatible. If not, then why do you need 4.1.2 and 4.2 to co-exist? If you're looking at it from a developer standpoint, use the endpoint (/sdcard), as that will be the same regardless of the file structure.
Click to expand...
Click to collapse

The thread linked below "should" fix the issue you're talking about. My apologies if you've tried it already, I didn't look back through the thread to see if anybody else linked it.
http://forum.xda-developers.com/showthread.php?t=1999214

dbrickg said:
Sorry if I wasn't clear: not symlinking /data/media to /data/media/0 (though I have seen that done... makes interesting infinite loop , but, for instance, ln -s /data/media/Books /data/media/0/Books.
As for the other question, not dual booting, per se, but moving back and forth between one backup and another. Since I'm still not sure about all the features of 4.2, I'd like to be able to return to 4.1. And, /sdcard is NOT the same regardless of file structure. In 4.1, /sdcard has all my data, but when I install 4.2, /sdcard has lost it all. If I move the data from /data/media to /data/media/0, then /sdcard has the data for 4.2, but loses it if I return to 4.1. As you say, the file structures aren't compatible. I was just hoping someone had come up with a simple way to make them appear to be compatible. I thought symlinking would make sense, but it just doesn't work. I could copy everything from /data/media to /data/media/0, but then I'd double my data, and have all the problems of keeping 2 sets of data in sync. Eventually 4.2 will get its bugs worked out, and I'll feel confident about moving to it permanently, but for now, I'd like to keep both, and it's frustrating that I haven't been able to figure out a way to make that work.
Click to expand...
Click to collapse
Why would you bounce between 4.1 and 4.2? Either 4.2 works for you or it doesn't. Also, yes, /sdcard is the same endpoint when you're not screwing with your data structure. /sdcard is configured to point to your internal data, regardless of Android version. In 4.1, everything is in /data/media. After fuse mounts and symlinks, /sdcard is the endpoint for developers. When 4.2 is installed, everything in /data/media is moved to /data/media/0. After fuse mounts and symlinks, /sdcard is again the endpoint for developers. Android isn't designed (especially versions with file structure updates) for bouncing back and forth between two versions, and your backups don't move your internal storage around when they're restored.
If you insist on bouncing between 4.1 and 4.2, you'll be spending a lot of time moving your data around manually.
02ranger said:
The thread linked below "should" fix the issue you're talking about. My apologies if you've tried it already, I didn't look back through the thread to see if anybody else linked it.
http://forum.xda-developers.com/showthread.php?t=1999214
Click to expand...
Click to collapse
That thread has posts to help fix multiple nested /0 directories or fix your data structure if you're downgrading from 4.2 to 4.1. I don't think either helps in this situation.

Cilraaz said:
Why would you bounce between 4.1 and 4.2? Either 4.2 works for you or it doesn't. Also, yes, /sdcard is the same endpoint when you're not screwing with your data structure. /sdcard is configured to point to your internal data, regardless of Android version. In 4.1, everything is in /data/media. After fuse mounts and symlinks, /sdcard is the endpoint for developers. When 4.2 is installed, everything in /data/media is moved to /data/media/0. After fuse mounts and symlinks, /sdcard is again the endpoint for developers. Android isn't designed (especially versions with file structure updates) for bouncing back and forth between two versions, and your backups don't move your internal storage around when they're restored.
If you insist on bouncing between 4.1 and 4.2, you'll be spending a lot of time moving your data around manually.
That thread has posts to help fix multiple nested /0 directories or fix your data structure if you're downgrading from 4.2 to 4.1. I don't think either helps in this situation.
Click to expand...
Click to collapse
No, that thread is a guide to keep the same sdcard file structure on 4.2 as on 4.1.2 so that you can flash between both. If it was just to get rid of nested /0 directories it would be pointless because all you have to do is flash an updated recovery to keep from getting multiple /0 folders. It should help with the OP's issue if he can get it to work correctly. I never could cause I kinda skipped a step unintentionally, but it seems to get rid of the /0 directories for anybody else that does it correctly.
---------- Post added at 03:07 PM ---------- Previous post was at 03:02 PM ----------
Haha, the op of the thread I linked was the second poster in this thread. lol. I didn't see that at first.

[SOLVED] Where did all my storage go? CM10.1

[Q] Where did all my storage go? CM10.1
Hi all, I'm currently have a problem finding out where all my storage space has gone and what is safe to delete.
I'm on CM10.1 and the storage indicator in settings is attached. It says I only have 888MB available but the graphic shows around 2/3 of the internal storage is unused
I found 3 folders (storage/sdcard0, storage/emulated/0, and storage/emulated/legacy) that are both 2.62GB large. They look to be identical copies of /sdcard.
are any of these folders safe to delete? I am running out of memory and I believe these folders are the reason why.
Thanks!

Only yesterday someone mentioned something similar somehow. So I don't think that thread is really far away if you checked the first few pages in this Q & A section.
By typing in the searchbox "4.2 storage", I got this thread as the first result. So please try searching harder next time
Feel free to explain further if your issue is not resolved using the above link

Do not delete those folders. They are merely symlinks and not taking up any extra space.
Sent from my Nexus 7 using Tapatalk 2

Thanks for the reminder to search more, I will remember to do so in the future.
I thought they were symlinks because changes i made in sdcard were reflected in the other folders however when i check the size of the storage folder I can see that the total size is 7.87GB. If they were symlinks wouldn't that be 2.62 gb? I will continue to search for how to fix this issue.
I don't think the problem is an app because that would show up in the storage graph under settings would it not?
thanks!

found this thread that seems like a very similar issue
http://forum.xda-developers.com/showthread.php?t=1906449&highlight=storage
however again I see a discrepancy in the used storage vs per app usage. The SD card Analysis is attached.

On my GNex, the storage/sdcard0 is of size X, and it is the same X size for each of storage/emulated/0 and storage/emulated/legacy. This is very similar to what you originaly mentioned in your first post. I was just checking mine as well.
Hmmm, is this only happening with CM 10.1 ? Any other ROM you tried ? A reboot could help?

ahmadallica said:
On my GNex, the storage/sdcard0 is of size X, and it is the same X size for each of storage/emulated/0 and storage/emulated/legacy. This is very similar to what you originaly mentioned in your first post. I was just checking mine as well.
Hmmm, is this only happening with CM 10.1 ? Any other ROM you tried ? A reboot could help?
Click to expand...
Click to collapse
Check how much storage is used by your nandroid backups. I know that those aren't reported on the Storage space screen.

ahmadallica said:
On my GNex, the storage/sdcard0 is of size X, and it is the same X size for each of storage/emulated/0 and storage/emulated/legacy. This is very similar to what you originaly mentioned in your first post. I was just checking mine as well.
Click to expand...
Click to collapse
This is true for mine as well. The size of the /storage is 3*X. Good to know this isn't problem I am having.
AOKP gave me the same problem earlier. I have rebooted and wiped data... Is there any other folder i can check?
I've attached another screenshot of the sdcard analyst in es file manager. This is very confusing to me that the directory size is 2.48GB but out of a total 13.33GB space only 1.01GB is free?!

Reedbo said:
Check how much storage is used by your nandroid backups. I know that those aren't reported on the Storage space screen.
Click to expand...
Click to collapse
I am not complaining of any problem. I was trying to help the OP
Anyway, the ES File Explorer "SD Card Analyst" seems to include the nandroids as well
---------- Post added at 12:58 AM ---------- Previous post was at 12:55 AM ----------
extraGuac said:
This is true for mine as well. The size of the /storage is 3*X. Good to know this isn't problem I am having.
AOKP gave me the same problem earlier. I have rebooted and wiped data... Is there any other folder i can check?
I've attached another screenshot of the sdcard analyst in es file manager. This is very confusing to me that the directory size is 2.48GB but out of a total 13.33GB space only 1.01GB is free?!
Click to expand...
Click to collapse
Just to confirm, do you remember making any "hidden" folders on your sd card?
Actually SD Card Analyst should by default show hidden folders as well but I thought it is bettER to ask you and be sure

ahmadallica said:
Just to confirm, do you remember making any "hidden" folders on your sd card?
Actually SD Card Analyst should by default show hidden folders as well but I thought it is bettER to ask you and be sure
Click to expand...
Click to collapse
No, i don't recall intentionally making hidden folders.
and if the nandroid comment was directed at me, I checked the CWM folder where I believe they are saved. I only have one nandroid backup currently and the size is 1.25GB,

What do you have in /data/media/ ???
I have 3 folders there: 0, legacy, obb
the "0" folder seems to be another symlink as well.
I am trying to find anything on your sdcard different than mine. That's why I'm asking

ahmadallica said:
What do you have in /data/media/ ???
I have 3 folders there: 0, legacy, obb
the "0" folder seems to be another symlink as well.
I am trying to find anything on your sdcard different than mine. That's why I'm asking
Click to expand...
Click to collapse
This is very strange, my /data/media/ is very different from yours.
I have the same 3 folders you have: 0, legacy, and obb however I also have what seems to be an older /sdcard backup. There are folders in there that seem to be from before I wiped data.
The 0 folder also appears to be a symlink but unlike the other symlinks this one takes up no space. In fact none of the folders in /data/media take up any space. When I check the size of /data/media es file explorer says it contains 0 files and 0 folders???
Thanks for all your help so far! I will keep searching

Yes it does not show any size with me as well but I can see the same contents of /sdcard/ in /data/media/0/ .
Would you please explain further about that "older" /sdcard/ backup you mentioned?
I am starting to think that maybe the first few times you went to 4.2, you did NOT have the latest TWRP or CWM installed. So the sdcard files were moved inside a "0" folder each time, then maybe you transferred your backup from PC to /sdcard/ so it became duplicated. Sorry I am not sure I am clear enough in explaining this but it is just an assumption because something similar happened with me before this "0" folder issue was fixed in TWRP actually.
Maybe I can help you bettER if you explain to me more about that "older" /sdcard/ backup you found

ahmadallica said:
Yes it does not show any size with me as well but I can see the same contents of /sdcard/ in /data/media/0/ .
Would you please explain further about that "older" /sdcard/ backup you mentioned?
I am starting to think that maybe the first few times you went to 4.2, you did NOT have the latest TWRP or CWM installed. So the sdcard files were moved inside a "0" folder each time, then maybe you transferred your backup from PC to /sdcard/ so it became duplicated. Sorry I am not sure I am clear enough in explaining this but it is just an assumption because something similar happened with me before this "0" folder issue was fixed in TWRP actually.
Maybe I can help you bettER if you explain to me more about that "older" /sdcard/ backup you found
Click to expand...
Click to collapse
This was immensely helpful. You are correct, I had stock 4.2 on my GNex before I got CWM. This will get confusing but I will try to explain what I see in /data/media
/data/media/0/ seems to be a symlink for sure. however the other folder in there are from before wiped data earlier today. /data/media/download/ has a file I downloaded last week however /data/media/clockworkmod/backup has backups as recent as yesterday. I believe these are app data backups because I recall 3 of them. I do not see the nandroid I recently created in this folder. Is there anything you need to know?

extraGuac said:
This was immensely helpful. You are correct, I had stock 4.2 on my GNex before I got CWM. This will get confusing but I will try to explain what I see in /data/media
/data/media/0/ seems to be a symlink for sure. however the other folder in there are from before wiped data earlier today. /data/media/download/ has a file I downloaded last week however /data/media/clockworkmod/backup has backups as recent as yesterday. I believe these are app data backups because I recall 3 of them. I do not see the nandroid I recently created in this folder. Is there anything you need to know?
Click to expand...
Click to collapse
Well, I think that "everything" you already have on your /sdcard/ including "clockworkmod" backups, blobs, and so on, should be duplicated (as symlinks) in the /data/media/0/ not in /data/media/. At least this is what I have in my sdcard. This should be the same for /data/media/download/ because the "download" folder of your /sdcard/ should be duplicated (again, as a symlink) in the /data/media/0/. Therefore, you said there are "backups" for clockworkmod in /data/media/clockworkmod/, so assuming the backup would be around 1.5 to 2 GB, then 3 backups of these would be about 4.5 to 6 GB of storage.
Please take note that I have "never" messed with these files and my above thoughts may be incorrect, so maybe first you may try to check whether these clockworkmod backups are really consuming a lot of storage. If they are really consuming that much storage, then it is bettER to play it safe by taking them out to your PC first just in case deleting them would cause something wrong. I hope some other more experienced member can "confidently" tell you to proceed in either deleting this /data/media/clockworkmod/ or suggest another solution. Sorry but I would not tell you to do something unless I am very confident and sure of it. I hope you understand
I will try searching for an exact answer on whether this /data/media/clockworkmod/ is safe to delete, and if I found something then I will let you know for sure

I made a nandroid backup and deleted all files in that folder except for 0, legacy, and obb. checked my storage and now I see 9.65GB available which is fantastic! I still have 1.18GB unaccounted for but I now that I know what seems to be the issue I can go through the rest of my data and try to weed out the problems.
Thank you so much for your help!

WOW! Glad to hear so
That was a brave thing to do. I would have done it if it is my phone but would not suggest for others unless I am sure it won't cause any trouble
It would be great if you mark/edit the thread's title as "[SOLVED]"
Well Done! :highfive:

In hindsight it was not my smartest move Thanks again for all your help!

Fixed
*************
SOLUTION:
*************
Here's what worked for me.
1. Make sure your phone is rooted
2. Open ES File Explorer
3. Press the Menu key > Tools > Root Explorer (grant it super user premission)
4. Some dialog pops up. I didn't understand the options, chose R/W permission and then pressed back at the next screen
5. Go to the root directory "/" and then "/data/logs"
6. Delete all the files in there
7. Thats it! :good:
There was about 1.6 GB of log files in there for me. 1440 files about ~1.5 mb each.
(Strangely, a huge number were from the 26th of last month, then 1 on the 27th, 30th and then all the rest from the 14th of this month?)
cya
R

Where did my storage go?
A huge thank you R !!!
been breaking teeth & puling whatever little hair got left for ages trying to solve this, mostly with complicated & futile suggestions. But yours worked right off the bat ! God bless you.
although i already had to go back twice within hours and wipe all files again its probably because i restocked on all those apps i had to delete before due to lack of space. At this point i'll take any solution over none.
if anybody ever rights a code that will prevent the dumpstate from accumulating he'll have a serious karma !
Rehaan said:
*************
SOLUTION:
*************
Here's what worked for me.
1. Make sure your phone is rooted
2. Open ES File Explorer
3. Press the Menu key > Tools > Root Explorer (grant it super user premission)
4. Some dialog pops up. I didn't understand the options, chose R/W permission and then pressed back at the next screen
5. Go to the root directory "/" and then "/data/logs"
6. Delete all the files in there
7. Thats it! :good:
There was about 1.6 GB of log files in there for me. 1440 files about ~1.5 mb each.
(Strangely, a huge number were from the 26th of last month, then 1 on the 27th, 30th and then all the rest from the 14th of this month?)
cya
R
Click to expand...
Click to collapse

[Guide]Functional ext4 for external microSD with just a few bumps left

Y.G. said:
I formated my sd card to Ext4 and when insert it in to my phone, it says that's it's blank and has unsupported files. Any reasons for that?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
The SPH-L710 Samsung Stock LJ7 TW 4.1.1 Android doesn't understand/support the change to ext4 external SD card (microSD) without a few things being done.
I'm working this out right now. So far I have manually been able to mount the newly created ext4 partition on the microSD card through adb, and after some chown/chmod I was able to go back to "Settings and Storage" and the "Mount SD Card" picked it up, and I was up and running ext4. But this didn't persist after a restart. So I'm looking into: /etc/vold.fstab MODS to keep it after restart right Now !!
If Some one else already has this perfected please chime in. I'm wanting to do most of the devices in the house this way when I get time because better performance, having a file system with a journal, and getting rid of thins like 4 Gig per file limitations is pretty Sweet in my humble opinion *Grin*
0) Assuming you already have your microSD card formatted ext4. I also happened to label mine extSdCard for the volume label within gparted
1) Can mount with:
mount -w -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard/
2) To get the correct owner and permissions run:
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
3) Should make the extSdCard owner/permissons match the regular internal sdcard you can verify this like so:
cd /storage/ && ls -l
drwxrwxr-x root sdcard_rw 2013-01-12 18:16 extSdCard
drwxrwxr-x root sdcard_rw 2013-01-12 17:05 sdcard0
4) After that you can go to the "Settings and Storage" to run "Mount SD" and you will have ext4 extSdCard Show up and it bring up the File System Status !! --> Until you reboot and it goes to crap because I don't have the vold.fstab edit/MOD complete _yet_ ... So, for now a boot script has been put in place to bring our external SD card back online during restart, so the system will acknowledges it, making the world a better place.
Example of how things look file system wise: mount | grep extSdCard
/dev/block/mmcblk1p1 /storage/extSdCard ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
5) Have not been able to resolve the vold.fstab to make this ext4 extSdCard matter fully Legit (in my opinion), but I did manage to make it remount the card on boot, so its online when the system comes up instead of having to manually mount it. Did this by -->
Added the following lines to the very bottom of: /etc/init.qcom.post_fs.sh
## sponix MOD to match with ktoonz kernel for better power management
stop mpdecision
## sponix MOD to mount extSdCard prior to GUI work around to make ext4 function
## read and write extSdCard mount
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
mount -w -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
## if you want read only extSdCard mount
## mount -r -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard
Still attempting to automate the process so the Stock+root LJ7 can pick up the extSdCard _normally_ without having to do the mount command manually, but so far its kicking my butt. Also this is more a "General, or Question and Answer type Topic" the Kernel(s) obviously support ext4 the system fs uses/requires it *Grin*.. So we might get Our Friendly Neighborhood Moderator to Migrate it to the proper place to help others. Just hoping to get the last few bumps smoothed out, or find someone that already documented the process that I've overlooked *Grin*..
Current Known Issues: If you unmount the card through the "Settings | Storage | Umount SD" or by hand with umount, you will either need to reboot for it to reattach through the /etc/init.qcom.post_fs.sh boot script script addition, or will have to mount it manually if you want to keep the system up and running. Guess you could also probably just run the /etc/init.qcom.post_fs.sh as root from a terminal emulator (or adb).
Still searching for vold.fstab bits of wisdom but that will have to continue next weekend -->
Sexy and You Know it,
Keep on Flashing,
sponix2ipfw (sponix
:fingers-crossed:

Ha! Sorry. Deleted: Didn't understand that you had it running on boot (can't read properly )

Great idea
Am I really the only one who also thinks this idea is the nuts?
Am I the only one who longs to transform the mess that passes for a filing system on the internal sd using symbolic links into a beautifully organized, encrypted and cloud synced system on my external sd?
Is it just me and a few others that want to be able to achieve the above so that we can move from one ROM to another or recover from a lost phone with the minimum of fuss?
Are we freaks? :cyclops:
Say it isn't so XDA!! :crying:
I'm gonna try this on my international S3 running Null_ Rom 25 JB 4.1.2
PS do you have any idea how the entire ExtSD or just a folder can be enrypted using Cryptonite and automatically mounted at boot time?

emp111 said:
PS do you have any idea how the entire ExtSD or just a folder can be enrypted using Cryptonite and automatically mounted at boot time?
Click to expand...
Click to collapse
Is this along the lines of what you're looking for?
http://forum.xda-developers.com/showthread.php?t=1141467
Also your idea is pretty insane, but also genius
If you get that to work please do come back and share

Insane ideas are the best lol
CNexus said:
Is this along the lines of what you're looking for?
http://forum.xda-developers.com/showthread.php?t=1141467
Also your idea is pretty insane, but also genius
If you get that to work please do come back and share
Click to expand...
Click to collapse
Thank you for your prompt reply, yes it is asking a lot I know but I think that it can be done.
Now if you really thought that idea was insane......check this out:
Imagine that we asked every Android app developer to submit the various paths used for their config (and config backup) files to a central database and had the ability to add or own custom paths (which could be added to the central database once approved).
We could build an script/app that would retrieve a list of currently installed apps on your phone then automatically build a symbolically linked file system (and/or backup file system) in the location of your choice that you could either encrypt and/or sync using your current tools or even incorporate this functionality into the app itself along with the ability to choose what was encrypted/backed up and how i.e. either synced to the Cloud or (S)FTP or SMB as either a dd copy or even a cwm flashable zip.
Could I dare hope for a Tasker module or the ability to add custom scripts?
I wish I could do this myself but my coding skills are non existent
Anyway the LUKS manager app won't automatically mount a file system, but I really like it anyways, thank you for pointing me to it!
And on the Ext4 front, the mount command (yes the 1st one ) failed, maybe the op could offer a suggestion. :angel:
BTW is there a place for people to suggest ideas for apps here?

Wait really it wont? I couldve sworn I remembering that it did
But dude....
You need to learn yourself some java and start whipping stuff up
Idk about the whole central database thing, but the rest could definitely be done with root access
I think the main problem with that is the proprietary aspects...i mean even here on XDA where binaries released are supposed to be GPL compliant, many of them arent and its sad because it deteriorates the overall quality of work thats released afterward

This whole thing is just hard work!
CNexus said:
Wait really it wont? I couldve sworn I remembering that it did
Click to expand...
Click to collapse
Doesn't seem to unfortunately
But dude....
You need to learn yourself some java and start whipping stuff up :D :D[/QUOTE said:
You make it sound soooo easy lol, and at another point in my life maybe it would have been but right now I'm operating at a reduced level due to some unforeseen circumstances that have left me lacking focus, motivation etc
You know all the things you need to be creative, learn etc lol
Anyway back to the matter at hand, I have got my ext4 SD card to the stage where I have to manually mount it from within the Settings/Storage as I'm using the international S3 and don't have the init.qcom.post_fs.sh, I think the qcom refers to Qualcomm chipset in US S3's.
As for modifying vold.fstab so we can avoid the above workaround it would seem that maybe thats a dead end as according to a German guy on android-hilfe. de, Vold may have been modified by Samsung to only deadl with exFAT on External SD's.
Looks like I'm not gonna be in Android nirvana for a while :crying:
Unless anyone else on XDA fancies getting in on this !!!!
Click to expand...
Click to collapse

Got it working ..... kinda
Got an app called ezymount (by ezynow) that automounts my ext4 64GB microSD at boot time.
I have to wait a few seconds for the boot process to complete but it's automatic, am pretty happy!!
Now gotta get symlinks, encryption and cloud synchronization sorted :/

[Q] Storage explanation needed

Hi all, I just wanted someone to help me with some confusion I have about the internal memory of the galaxy nexus
I'm aware there's obviously no SD card however inside the storage section there seems to be a folder called sdcard0 which has all my usual sub folders in it. However, when I tried to restore with TB after flashing a ROM earlier I couldn't and when I checked it was because the TB folder on sdcard0 was completely empty, as well as all the others. What I also found was that there is a sub folder like all the others, except it's called "0" and has exactly the same folders as sdcard0! This is where I'm confused, the TB folder inside 0 has all my backup data but in the app it doesn't recognise there's anything to restore and some help on this would also be appreciated if anyone could help me with this issue and maybe explain how this 0 folder has been created I'd be very grateful, thanks again
Sent from my rooted time travelling slice of cheese

Use the search function next time.
Sdcard0 is related to 4.2+ multi user feature. 0 is essentially admin. Having multiple 0 folders means you flashed a 4.2 rom on an outdated recovery that didn't handle it correctly. Move the folders into the main 0 and delete the extra. Then update your recovery.

4.2 have multiuser support and the 0 is for the first user.
Though it is only on tablets you can actually create other users, at least on stock
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

what the other guys said!
path forward: either update your recovery and then manually move over all the data from sdcard0/0 to sdcard0/ or if you dont want to do that you can simply open TiBackup and change the location of the folder of the backups. Option is available in TiBackup Preferences.

DZYR said:
what the other guys said!
path forward: either update your recovery and then manually move over all the data from sdcard0/0 to sdcard0/ or if you dont want to do that you can simply open TiBackup and change the location of the folder of the backups. Option is available in TiBackup Preferences.
Click to expand...
Click to collapse
That's terrible advice. The extra 0 folder will only cause issues down the road and should be gotten rid of asap.

063_XOBX said:
That's terrible advice. The extra 0 folder will only cause issues down the road and should be gotten rid of asap.
Click to expand...
Click to collapse
In addition to this, it was bad advice as it was suggesting the file structure change be done at the sdcard0 level. The entire SDCard file structure is based out of /data/media. This is where the manual changes should be made (for instance, moving everything from /data/media/0/0/0 to /data/media/0). After making the change, reboot. The fuse mount points and symlinks will then properly reflect the change. It's always safest to make this drastic of a change at the base, physical data location, rather than on a fuse mount point or a symlink of a fuse mount point.
Also, as previously suggested, update your recovery. The current versions of CWR and TWRP have this issue resolved.