Related
As the title, is it normal if we get those folders after update to 4.2 ? Because as far as I read the problem when updating to 4.2 is only 0 folder.
I was using PA 2.54 that based on 4.1.2. I have installed latest TWRP. Then made a factory reset, after that I flashed PA 2.99. And it created those folders. Please help. Thanks.
Sent from my Galaxy Nexus with Paranoid Android powered by Trinity kernel
Ridho1 said:
As the title, is it normal if we get those folders after update to 4.2 ? Because as far as I read the problem when updating to 4.2 is only 0 folder.
I was using PA 2.54 that based on 4.1.2. I have installed latest TWRP. Then made a factory reset, after that I flashed PA 2.99. And it created those folders. Please help. Thanks.
Sent from my Galaxy Nexus with Paranoid Android powered by Trinity kernel
Click to expand...
Click to collapse
After reluctantly accepting the 4.2 ota, i also gained legacy and obb folders in data/media. I do have emulated showing, but im still confused at this point. Google made some waves.
bodh said:
After reluctantly accepting the 4.2 ota, i also gained legacy and obb folders in data/media. I do have emulated showing, but im still confused at this point. Google made some waves.
Click to expand...
Click to collapse
and this is why I want a physical SD card in my phone... this emulated BS is driving me crazy today... over already accidentally deleted files thinking this so called linked directory was not a real directory ... it is in fact a fake directory with real actions... come on google... 1 directory to call home... not the multi linked mess of fake folders ....
/rant (GNexToro(HWv9)-TapTalk2)
Does anyone know what directories/folders are safe to delete? I have an entire duplicate of everything across two folders.
They reside here.
/storage/emulated/legacy/0/
/storage/emulated/0/0/
They are exact duplicates. Same size, etc.
Which is safe to remove? I searched for like a day on this forum, and many others. I have been trying to figure out which is safe to remove, but I am more confused now then ever. :silly:
I feel like just picking one to delete to free up space and if I muck up, I'll restore from a Nandroid.
The 0 folder is the new directory.
located at data/media/0
Created when you upgrade from 4.1.x to 4.2.1
The other folders you see are links to these folders, not duplicates of what you have stored in these folders.
Installing the latest recoverys will take care of the extra 0 folders ie 0/0/0
If you delete the folders from one of the link folders, you may delete the actual folders. They don't take up space.
gpfnzl said:
The 0 folder is the new directory.
located at data/media/0
Created when you upgrade from 4.1.x to 4.2.1
The other folders you see are links to these folders, not duplicates of what you have stored in these folders.
Installing the latest recoverys will take care of the extra 0 folders ie 0/0/0
Click to expand...
Click to collapse
Hey, thanks for the reply.
I do have the latest recovery, but apparently if you updated to the latest CWM after moving to JB 4.2 you are still gonna get the folders. Updating before going to 4.2 would have prevented this. Well, this is what I get from reading other messages and forums.
So I am wondering if there is another way to sort these so it's not so confusing.
If not, I'll accept it and may roll back to 4.1, update my recovery, then flash the 4.2 rom.
and this is why I want a physical SD card in my phone... this emulated BS is driving me crazy today... over already accidentally deleted files thinking this so called linked directory was not a real directory ... it is in fact a fake directory with real actions... come on google... 1 directory to call home... not the multi linked mess of fake folders ....
Click to expand...
Click to collapse
i'm still not sure what the actual presentation of the data loss that i heard about was, it wasnt people simply not finding the right path to the data was it? but i also dont get why so many people are so keen to remove a link to their internal memory. Why is it so bad for it to be there? just dont go into the folder
a lot of people seem to get that it is an exact mirror (it's just like a shortcut in windows), so just use one, and whats the bother?
d0wns3t said:
i'm still not sure what the actual presentation of the data loss that i heard about was, it wasnt people simply not finding the right path to the data was it? but i also dont get why so many people are so keen to remove a link to their internal memory. Why is it so bad for it to be there? just dont go into the folder
a lot of people seem to get that it is an exact mirror (it's just like a shortcut in windows), so just use one, and whats the bother?
Click to expand...
Click to collapse
They arent exact mirrors. The fact that I have to go through four virtual SD cards to find something I downloaded that's buried in one of them. Its a total pain. Which one is the real one?
DelphinusMinor said:
Hey, thanks for the reply.
I do have the latest recovery, but apparently if you updated to the latest CWM after moving to JB 4.2 you are still gonna get the folders. Updating before going to 4.2 would have prevented this. Well, this is what I get from reading other messages and forums.
So I am wondering if there is another way to sort these so it's not so confusing.
If not, I'll accept it and may roll back to 4.1, update my recovery, then flash the 4.2 rom.
Click to expand...
Click to collapse
From what i see, reverting back to 4.1 won't do it.
You have to go back to a particular stock 4.1 then install latest CWM recovery. untested by me. There is a guide around but i've lost the link.
For me I did a full manual wipe of everything (including SD card), then a manual reinstall of cwm and a 4.2 rom.
I have a 0 folder, but i don't have a 0/0/0 folder created when switching between roms.
Need someone clever to write a clear guide and have it stickied
I too would be interested to know if a solution has been found yet. My legacy folder is taking up more than half of my internal storage. Is it safe to delete?
Sent from my GT-N7100 using Tapatalk 2
I didn't think my dirs were duplicated at first, and the other day I investigated more. One directory structure looks exactly the same, but when I went thru the diff folders and compared between the two, alot of the folders didn't have the same contents. Some folders were even empty and it's clone had data in it, settings and whatnot.
I may post a screenshot once my phone is charged.
/emulated/legacy/0/0/
Is completely different from
/emulated/legacy/0/
The data is diff sizes if you compare both of those folders.
Why Android went this way by setting user accounts/profiles is beyond me.
Here is an example pic. I am not going to take screenshots of everything tho, obviously.
On the left all the folders and data is older then the data in the directory on the right, so I am thinking it is probably safe to delete the older data.
Any ideas?
Here is another example.
What is in the legacy folder on right, is totally diff from what is on the left, but in this case, the data on the left is now the newest data, where the right has no data at all.
Just noticed /emulated/legacy/0/0/0/ also has totally diff contents then the first two I mentioned and the folders vary in size dramatically.
It's a bit frustrating.
EDIT: Added another pic.
DelphinusMinor said:
Here is another example.
What is in the legacy folder on right, is totally diff from what is on the left, but in this case, the data on the left is now the newest data, where the right has no data at all.
Just noticed /emulated/legacy/0/0/0/ also has totally diff contents then the first two I mentioned and the folders vary in size dramatically.
It's a bit frustrating.
EDIT: Added another pic.
Click to expand...
Click to collapse
Please correct me if im wrong in my thinking. Its normal if I flash from 4.2 (for a day or to) then flash back using a nandroid to 4.1 to have a left over 0folder sitting in my main storage SDcard0?
So when im back on 4.1 I have Sdcard0/0 thats where it ends for me as of now. I flash back and forth all the time. I also get legacy folders but as of yet there always emty. The 0folders left over (mind you im on 4.1) im only testing 4.2 but the left over folder 0 does contain a lot of folders though only data is located in the duplicate android folder.
Questions so being that im on 4.1.2 again what do I do with the left over folders? Up till now I just use windows copy them over and let all the folders merge. Seems to work most the time but It can cause issues.... there gotta be better way? How come I get left over crap in a 0 folder every dang time I flash back from 4.2 to 4.1
Thats normal? Oh BTW im on newest TWRP installed from GOO. I am running Jellybam 4.1.2 I don't delete folders just merge them back into my other folders but maybe I shouldn't do this?
I dunno when im on 4.2 I don't have any issues except that I think this concept is some stupid guys idea of trying way way to hard to be smart. Smoked a little ot much weed before he came to work ya know?
Please
1. What do we do about 0 doler / legacy folder when we flash back to 4.1
2. Whats normal... what should we except when flashing from 4.1 to 4.2 assuming we have newest TWRP or CWM
3. Anything else you think you should add
4. whats your home launcher
peace
xxsicknessxx said:
Please correct me if im wrong in my thinking. Its normal if I flash from 4.2 (for a day or to) then flash back using a nandroid to 4.1 to have a left over 0folder sitting in my main storage SDcard0?
So when im back on 4.1 I have Sdcard0/0 thats where it ends for me as of now. I flash back and forth all the time. I also get legacy folders but as of yet there always emty. The 0folders left over (mind you im on 4.1) im only testing 4.2 but the left over folder 0 does contain a lot of folders though only data is located in the duplicate android folder.
Questions so being that im on 4.1.2 again what do I do with the left over folders? Up till now I just use windows copy them over and let all the folders merge. Seems to work most the time but It can cause issues.... there gotta be better way? How come I get left over crap in a 0 folder every dang time I flash back from 4.2 to 4.1
Thats normal? Oh BTW im on newest TWRP installed from GOO. I am running Jellybam 4.1.2 I don't delete folders just merge them back into my other folders but maybe I shouldn't do this?
I dunno when im on 4.2 I don't have any issues except that I think this concept is some stupid guys idea of trying way way to hard to be smart. Smoked a little ot much weed before he came to work ya know?
Please
1. What do we do about 0 doler / legacy folder when we flash back to 4.1
2. Whats normal... what should we except when flashing from 4.1 to 4.2 assuming we have newest TWRP or CWM
3. Anything else you think you should add
4. whats your home launcher
peace
Click to expand...
Click to collapse
I use Apex Launcher but you don't see it in the images. I think you are referring to FlashFXP which is a file manager I use to move files and folders between my PC and my phone, and to move files and folders between diff folders on the device itself by connecting to my phone in two instances.
It's my understanding the "0" folders are designated for the different user accounts.
If you go to JB 4.2. and then go back to 4.1 I believe the files from your 4.2 install remain intact(Or at least the file structure). No data is actually wiped unless you intentionally do so.
Now, I am just someone who flashes casually and I wouldn't consider myself an expert. I am confident in my skills, just not at a point where I can say anything with serious conviction. So your mileage may vary.
I actually found out which set of folders were the ones in use, and I ended up doing a nandroid, and then deleting everything else on my phone to be safe. I have rebooted several times and haven't had any issues. This was a few days ago.
Remember too, if you restore from an older nandroid from a prior firmware version it will roll back whatever kernal you currently have, etc. It basically brings your phone to the exact state it was in when you did the backup.
Good luck with whatever you do! :cyclops:
AHHHHHHH All my precious data on internal sdcard GONE. All because of the stupid linked legacy folder! I was just trying to delete 1 duplicated (or so I thought) mp3 file, then Google had to come into the action and screw everything over!
I'm done! I'm done with all this BS. I can't even sleep properly! Just let me enjoy my summer
Peteragent5 said:
AHHHHHHH All my precious data on internal sdcard GONE. All because of the stupid linked legacy folder! I was just trying to delete 1 duplicated (or so I thought) mp3 file, then Google had to come into the action and screw everything over!
I'm done! I'm done with all this BS. I can't even sleep properly! Just let me enjoy my summer
Click to expand...
Click to collapse
If you just deleted one file... how did literally all of your data get erased?
I... what
tritonesub said:
If you just deleted one file... how did literally all of your data get erased?
I... what
Click to expand...
Click to collapse
I deleted the undetectable, sneaky, linked legacy/emulated folder because it was in /sdcard. So it portrayed itself as another folder, but in it's entirety was the /sdcard itself masquerading as emulated/legacy causing ones mind to think it is an expendable piece of foolery. Linked folder(/sdcard->emulated) contains emulated folder which links sdcard, but it was placed in sdcard so it's entire existence is invalid. Inception eh.
gpfnzl said:
The 0 folder is the new directory.
located at data/media/0
Created when you upgrade from 4.1.x to 4.2.1
The other folders you see are links to these folders, not duplicates of what you have stored in these folders.
Installing the latest recoverys will take care of the extra 0 folders ie 0/0/0
If you delete the folders from one of the link folders, you may delete the actual folders. They don't take up space.
Click to expand...
Click to collapse
thank you for this, finally i found where to hunt down the folders taking up space on the storage and delete that ****, now i have more room on the internal memory.:good:
tomh1979 said:
thank you for this, finally i found where to hunt down the folders taking up space on the storage and delete that ****, now i have more room on the internal memory.:good:
Click to expand...
Click to collapse
Could you give us all a pointer as to which folders you found safe to delete--I'm sure that we could all do with getting that bit of extra storage??
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.
[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
I have been having a bit of a problem with my Galaxy Nexus and its driving me nuts because of the storage situation..
Up until a couple weeks ago, I had the latest (at that time) version of AOKP on the phone (4.1.?, JB build 2 possibly). Then, around the first of the year, they updated to their 4.2 version JB-MR1 Build 1. The first time I installed the ROM, I installed it with the wrong GAPPS, ICS vs JB, and the phone went all haywire. I tried to get into the SD card to check which GAPPS was installed, but there were SO many force closes, I couldn't do anything. I rebooted into recovery, tried to go to my SD card, but ALL my info was gone. Basically a clean SD card.
So, I within minutes, I restored back to what I was on and everything was happy. No problems. I then downloaded the right GAPPS, installed the new ROM and GAPPS and everything worked great. Happy happy joy joy..
Today, I went to do a restore and remove some old backups and again, there is a second SD card. There is the normal one, and one labeled under /0/ in the directory.
I can access that directory while in recovery, but cannot with root explorer (or via my computers explorer) to erase it. The problem is, I think it is doubled up my photos and media, and now the card is full..
So, long story just to ask, how can I get rid of this other SD card directory? When talking with a co-worker, he mentioned it creates another directory when a second profile gets created..something I never did.
Any thoughts on how to get this removed so I can have my space back?
MikeDaub said:
I have been having a bit of a problem with my Galaxy Nexus and its driving me nuts because of the storage situation..
Up until a couple weeks ago, I had the latest (at that time) version of AOKP on the phone (4.1.?, JB build 2 possibly). Then, around the first of the year, they updated to their 4.2 version JB-MR1 Build 1. The first time I installed the ROM, I installed it with the wrong GAPPS, ICS vs JB, and the phone went all haywire. I tried to get into the SD card to check which GAPPS was installed, but there were SO many force closes, I couldn't do anything. I rebooted into recovery, tried to go to my SD card, but ALL my info was gone. Basically a clean SD card.
So, I within minutes, I restored back to what I was on and everything was happy. No problems. I then downloaded the right GAPPS, installed the new ROM and GAPPS and everything worked great. Happy happy joy joy..
Today, I went to do a restore and remove some old backups and again, there is a second SD card. There is the normal one, and one labeled under /0/ in the directory.
I can access that directory while in recovery, but cannot with root explorer (or via my computers explorer) to erase it. The problem is, I think it is doubled up my photos and media, and now the card is full..
So, long story just to ask, how can I get rid of this other SD card directory? When talking with a co-worker, he mentioned it creates another directory when a second profile gets created..something I never did.
Any thoughts on how to get this removed so I can have my space back?
Click to expand...
Click to collapse
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Lord Yurij said:
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Am I crazy saying that it could be taking up a couple gbs of space on my card? It seems that since this started up, my SD is almost full.
Any idea how to merge, or remove that? I can only access the 0 folder while in recovery, and no other time.
They put in symlinks to the folder so you can access it from different directories. The information shouldn't be doubled unless you personally did it.
Reading this might help you understand:
http://forum.xda-developers.com/showthread.php?t=2107194
Lord Yurij said:
Android 4.2 has a multiuser framework.
The "0" folder you are seeing is the first user.
Although it's only possible to create more users on tablets without tweaks
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
eqjunkie829 said:
They put in symlinks to the folder so you can access it from different directories. The information shouldn't be doubled unless you personally did it.
Click to expand...
Click to collapse
Thanks for the everything and helping me understand...
I did not copy over anything to that directory, and in fact cannot even access it outside of Recovery. It just looked to me that things were copied over by the file structure, which is why I thought it duplicated things. It just seemed odd to me that when all this happened, my SD card seemed to get much fuller..
Thanks again..
MikeDaub said:
Thanks for the everything and helping me understand...
I did not copy over anything to that directory, and in fact cannot even access it outside of Recovery. It just looked to me that things were copied over by the file structure, which is why I thought it duplicated things. It just seemed odd to me that when all this happened, my SD card seemed to get much fuller..
Thanks again..
Click to expand...
Click to collapse
Late but useful info for "the next guy". When you install 4.2 its creates a multi-user environment, correct. And you do loose half your space (assuming it was full when you upgraded). Here's why. In 4.2 there is only /data/media which is where your internal SD card (sdcard) is symlinked to (ie: the actual location of your files). When you install 4.2, all of /data/media is copied to /data/media/0 for the first user, then /data/media/11 for the second user, then /data/media/12 for the third user and so forth. Each user gets their own /data/media directory which has all the files that the single user had in 4.1 For each user you add, say its only yourself, you just lost half your space because /data/media still exists but now so does /data/media/0 (a duplicate copy). So you sdcard's space is divided by the number of user accounts your system has installed in 4.2. Hope this clarifies things.
elfaure said:
Late but useful info for "the next guy". When you install 4.2 its creates a multi-user environment, correct. And you do loose half your space (assuming it was full when you upgraded). Here's why. In 4.2 there is only /data/media which is where your internal SD card (sdcard) is symlinked to (ie: the actual location of your files). When you install 4.2, all of /data/media is copied to /data/media/0 for the first user, then /data/media/11 for the second user, then /data/media/12 for the third user and so forth. Each user gets their own /data/media directory which has all the files that the single user had in 4.1 For each user you add, say its only yourself, you just lost half your space because /data/media still exists but now so does /data/media/0 (a duplicate copy). So you sdcard's space is divided by the number of user accounts your system has installed in 4.2. Hope this clarifies things.
Click to expand...
Click to collapse
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..
MikeDaub said:
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..
Click to expand...
Click to collapse
you do. its what you see when you plug your phone in.
if you have a old recovery and are flashing roms, it will create multiple /0 folders.
Zepius said:
you do. its what you see when you plug your phone in.
if you have a old recovery and are flashing roms, it will create multiple /0 folders.
Click to expand...
Click to collapse
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..
MikeDaub said:
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..
Click to expand...
Click to collapse
then you need root to explore /data/media/
Zepius said:
then you need root to explore /data/media/
Click to expand...
Click to collapse
Right. I would just find it handy to do via my desktop...
MikeDaub said:
If that is the case, I would like to access the standard folder, the copy, or original, or whatever the none /0 folder is..
Click to expand...
Click to collapse
"/data/media/" and "/storage/sdcard0/" or even just "/sdcard/" are the same thing. You dont have copies of files on your phone. If you delete it in one location, it deletes in the other because they are the same. You have the "0" folders on "storage/sdcard0" as well. If you do happen to have copies of files, you can organize it all on your computer if you plug in your phone.
MikeDaub said:
Thanks. After a bunch of research, that is what is happening, and why my phone is always full of "stuff" now.
Now, if I could only access the /0 folders from my desktop...then I would be set..
Click to expand...
Click to collapse
Please thank me by hitting the "thanks" button
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
louiscar said:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
Click to expand...
Click to collapse
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
ashyx said:
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
Click to expand...
Click to collapse
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
louiscar said:
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
Click to expand...
Click to collapse
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
ashyx said:
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
Click to expand...
Click to collapse
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
louiscar said:
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
Click to expand...
Click to collapse
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
ashyx said:
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
Click to expand...
Click to collapse
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
ashyx said:
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
Click to expand...
Click to collapse
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
ashyx said:
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
Click to expand...
Click to collapse
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
louiscar said:
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
Click to expand...
Click to collapse
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
ashyx said:
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
Click to expand...
Click to collapse
This was the method I used as soon as I updated to MM and didn't notice the "this folder is not writable" message.
However, the option to choose mnt/media_rw isn't available. If I use Detect > whole device I'll be offered :
/storage/F91E-D472/Titaniumbackup
perhaps I'd see the other option under normal circumstances but Tba is not able to access that path so wouldn't find it in a search ... I guess
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
https://www.youtube.com/watch?v=GATqU1_xzqA
louiscar said:
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
Click to expand...
Click to collapse
ExFAT. Anything above 4gb should be ExFAT.
ashyx said:
ExFAT. Anything above 4gb should be ExFAT.
Click to expand...
Click to collapse
curiously I set permissions to 777 for the mnt/media_rw and titanium can go there but any further (even though I've done the same for the sdcard folder - nada!
and sadly after converting to exfat - mnt/media_rw .... "this folder cannot be accessed"
Not sure what else I can do.