Related
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
Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II
Galaxy Note II said:
Hello, folks
Recently I upgraded to Android Kitkat 4.4.2 (Indian Version) on my Samsung Galaxy Note II, I have come across a serious BUG after upgrading to Android 4.4.2.
BUG Details: Memory card cannot be read internally
For Instance while connected to Winscp via SSHDroid new folder cannot be created in Memory Card but at the same time new folder can be created in Phone Memory
I guess writing has been restricted
It's not over..... While downloading videos via YouTube Downloader 4.2 (Dentex) when custom folder chosen to memory card downloading gets failed
Again I guess writing has been restricted
I tried 3-4 different memory cards guessing problem might be in memory card (formatted as well)
Flashed my Note II via Hard Reset
Tried all ways and I have come to conclusion the BUG is in Android 4.4.2 Kitkat (Indian Version)
Kindly share if you have encountered same BUG as well (Specially Indian Consumers)
Regards,
Note II
Click to expand...
Click to collapse
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.
anesterian said:
It's not a bug, it is included in the Kitkat update for security purposes.
There is a fix for that but you have to be rooted.
Click to expand...
Click to collapse
Bro What kind of security is it? I cannot copy my own files into my memory card
iQuran cannot read my memory card in which has supporting files
I cannot save/download videos from YouTube Downloader to my memory card
What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100
anesterian said:
What rom are you using?
You can simply transfer your files using a comupter...
Then paste it to your memory card..
That's what I did when I'm on Stock Kitkat ROM...
If you want to apply the SD Card fixed root your phone first.
Sent from my GT-N7100
Click to expand...
Click to collapse
Take a look at my signature
They did what. You can't copy from internal to external memory. Omg i see no 4.4 on my device.
Edit : ok i understand now.
Sent from my GT-N7100
you can copy or move anything with stock file manager My Files..only third party application has no permission to write.
xplore file manager can handle files in sd card too...
Google chose to block write access, for third party apps (those not pre-installed), to external storage; except in their own directories.
There is currently a loophole which some developers have updated their apps to use, but with future iterations of android this will likely be blocked.
This change has been primarily to keep the sdcard clean; un-installing third party apps had left orphaned files the sdcard and resulted in a poor user experience. Personally I'm not sure how viable an explanation this is when you weigh it up against the affect to the user experience of preventing 3rd.P apps from accessing anything outside of their own granted space, or the space granted to a partner app. I think this is either google being evil, trying to lower the value of an sdcard slot to drive OEMs to make devices without one (for various profitable purposes) OR because google goofed on their first time really deciding what access they should have (previously there was no formal access rights definition, it was a free-for-all.)
Hold this space
You can install my apks from play store to back up apk in external card and quick office for editing and saving dox in external card without rooting from play store..enjoy
Sent from my GT-N7100 using XDA Premium 4 mobile app
you are right,writing of sdcard has been restricted in android 4.4.2
Is it possible to revert back to 4.3?
wrena said:
Is it possible to revert back to 4.3?
Click to expand...
Click to collapse
The easiest solution is getting root access and using the sdfix app; reverting is overkill if you just want 3p rw access back.
Happened to me yesterday. I was goin to format my fone, so i took a backup of some apps on helium(Since im not rooted)on my sd card. I formatted my fone. After that wen i went in carbon folder, it was empty. No data.
So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.
No answers anyone?
Just do some searching mate. And use ROOT EXPLORER and give it access.
nsh121193 said:
So i was on g2 apps v5.5 rom for some time when all of a sudden my media stopped scanning, i wasnt sure why, rescan media apps werent working either, so i decided to flash a new rom and i chose candykat, since then all of my files that i used to have, pictures, videos, etc have completely vanished. i cant locate the files in 7 zipper, es file explorer, and media scan apps still bring me nothing. Yet my internal storage still has the same amount of space used that it did before, and also when i go into CWM and choose install a zip it shows all the folders and things that i am missing, but that is the only place i see the folders but i dont have access to my files from cwm. Also i have noticed that when i am on 7zipper looking through files my internal storage says storage/emoulated/0 and i have no idea what the emulated is about, if anyone has any info or knows what im talking about please to help, Im not too great with phone stuff but i am okay, so if anyone has any simplified steps to give me on how to fix this issue it would be appriciated, thank you.
Click to expand...
Click to collapse
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.
spexwood said:
The way Kitkat makes the "SDcard"/"Internal Storage" directory is different from how it was on Jelly bean. <--EDIT: By this, I mean that the directory path is different.
The card is reading that X amount of data is on the card, yet you can't see it because your files are technically still there, but under the old directory path.
There are a couple of ways to fix this, but the EASIEST (IMO) way is to first restore a JB Nandroid backup (you can backup your KK ROM first if desired). First thing you'll notice is that the files will be there again. Now, plug your phone into your computer and copy all the files to it.
Reboot into recovery and format the internal SD. It's best to do it from within recovery, because otherwise, JB will just recreate the JB file structure and immediately start saving stuff to it. So when you get to KK, there will once again be the old structure hidden and with some files taking up space.
Now either reflash your KK rom or restore your KK backup.
Boot it up and copy your files back to the phone.
*I ran into this same issue after flashing KK for the first time. This is the exact process I did to resolve it.
Another way is to use a root file browser and locate the old directory and copy everything over to the new one. However, I think this might take quite a long time since the phone can do this only so fast.
Click to expand...
Click to collapse
Okay, thank you, I will try that soon and see if it works.
Hope I'm not repeating a question here. I couldn't find anything in this forum. I just finished updating my international m8 to lollipop ota. After installing titanium backup from the market, I noticed my previous backup on ext_sd are reported as not writable by titanium. I was under the impression that the new android L would rectify this Kitkat issue. Is there any work around for this issue yet? Thanks.
So I found a test version of titanium backup for Lollipop http://bit.ly/1v0njNa. Unfortunately I'm getting Documents crashes when I selected the extsd after switching to documentprovider storage. So I'm still unable to assign the backup directory to my external sd. Any input would be appreciated. Thanks!
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thread link forum.xda-developers.com/showthread.php?t=2617921
Working ok.
Thanks for the reply. I did use that solution when I was on 4.4 but lollipop has a different documentprovider solution now. I finally figured out what was happening. The issue isn't with titanium backup up but with how documentprovider was accessing my ext_sd. For some reason the documents will crash if I left ext_sd unnamed. I ended resolving the issue by naming my sdcard and it's been working as expected. Weird little bug in lollipop... In addition to the DNS issue.
Thanks for that solution. I had the same issue.
After naming the SD card using my laptop, the HTC Documents application no longer crashed and I can allow write access to the application (ES fileexplorer in my case.).
I guess it is an HTC bug, the documentsprovider shows the label/name of the ext SD card on the button to be pressed to allow access, and apparently it can't handle an empty SD card name.
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Did you install the SD card fix app?
I think there is an option on lollipop to authorize other apps to access directories that are not there own. That might be the problem.
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thanks so much! I had to pick the option DocumentProvider storage and then select the directory through there. Working fine now.
Sorry. Meant Document provider not Directory provider. ?
Has anyone found a reason why TiBu now thinks the entire directory of dalvik cache is unnecessary when you run the clean up option?
Changing that to DocumentProvider storage solved my problem too sjancura, thanks!
Hi,
I spoke too soon... I am still having problem with using external SD card with titanium backup.
I changed the storage provider to DocumentProvider but I cannot 'save' that selection as it's grayed out - please see the screenshot.
I have tried changing name of ex SD card. At first I used SDFix apps which were able to help with similar problem in KitKat but haven't fixed the issue now in lollipop.
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
dajomas said:
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
Click to expand...
Click to collapse
Thanks...that worked for me too.
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Hours of frustration brought to an end by that advice ... thanks mate ... you're a legend!
Hi,
I tried running SDFix, having run it in tbe past, prior to finding out this morsel of info on changing DP. However I still can't get it to save that location. Same greyed out directory like previous user posted.
Yeah I found that as well, changed it but could not "save" to that folder location (greyed out). Tried SDFix app, no change. Tried creating a new folder in TB, AND then using ESFile Explorer & neither would allow me to write to the extSD card. Rooted, stock Sprint Lollipop ROM.
I had that issue, worked it out. When you're browsing for a folder with the DocumentProvider select the root of the SD card, then it should close and return to the browser in Titanium Backup. Browse to the sub folder you want, you should be able to click the save button now.
Hi Ghosthree3,
Thanks so much for this. I'm going to give it a shot. My extSD card was used in the past on an earlier version of Android OS, whereby I could write to the extSD card just fine. Consequently there are prior backups on there. As such, I'm wondering if i should mount the phone, copy that folder off, delete that folder on the extSD card and then via TB create a "new" Titanium Backup folder and see if it then allows me to write. Note: I tried mounting the phone to my PC in an effort to create a folder on the extSD card and that method too, prevented me from creating a folder, hence my thought on getting what I have off of the device, and attempting writing a new folder per your directions. I wonder if my PC will allow me to erase that folder.....
Dopamin3 said:
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Click to expand...
Click to collapse
Install xposed and then use xinternalsd then configure it as u wish. This will fix the problem
Sent from my iris_X8 using XDA Free mobile app
sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thank you!
Hi s j a n cu r a,
Thank you very much. Someone else posted that, but maybe i'm not selecting it properly. When I select Document Provider, I browse to "Open from SD card", scroll down to the "Titanium Backup" folder, hit "Select" the "Titanium Backups" that are there [at one time I had no issues writing to my EXT SD card], it then says, "Detect!" [External storage] and I select "Everywhere in External Storage". It finds 41 backups there, I select that "External Storage' radio button. That's where I seem to hit a wall. The "Use the current folder" appears to be greyed out. I'm left only with "Cancel". I think there is some deeper issue writing to ExtSD because with File Explorer I can't copy picture files from one folder to the other. That's what is giving me this feeling that something else is going on with write permission. Frustrating to say the least. My only recourse at this point is to use the internal SD, which does work.
Google lollipop external sdcard fix. There's an app in the play store.
Sent from my SM-N900T using Tapatalk