Database Users

SD Card File Disappearing

My application has a backup/restore feature that writes a csv file to a directory named after the app, in the root of the sd card. I have a user trying to move from one tablet to another. The backup feature appears to properly be creating the backup file on her SD card. When she places the SD card in her new tablet, the backup file and the directory it's stored in do not appear to be on the SD card at all. Apparently she was successful in having other data from other apps move over.
I've walked her through everything I can think, including writing a test app to verify the issue. Without a doubt, the files exist on the old device, but don't exist when installed in the new device.
I'm unsure what the original device is, but the new device is a Dell Streak 7.
Anyone seen this before? I'm leaning towards corrupt SD card, but it seems it's my burden to prove as my app is the only app she's having issues with.

The root of /sdcard is not necesarrily the SDCARD you can remove and take out.
/sdcard is usually part of the build in memory which can be accessed and used by the user.
The SDCARD you can remove is usually found at /sdcard/external_sd on Android 2.2 devices and /sdcard/sd on Android 2.1 devices.
Yes the naming is a bit confusing .

Dark3n said:
The root of /sdcard is not necesarrily the SDCARD you can remove and take out.
/sdcard is usually part of the build in memory which can be accessed and used by the user.
The SDCARD you can remove is usually found at /sdcard/external_sd on Android 2.2 devices and /sdcard/sd on Android 2.1 devices.
Yes the naming is a bit confusing .
Click to expand...
Click to collapse
That would certainly explain some things, especially if a user is moving a SD card from one device to the next.
My app creates a folder under the path returned by the Environment.getExternalStorageDirectory() function, where it creates and reads a backup file.
My documentation asks users to connect their device to a computer, mount as USB, and copy the backup file into that directory. This user is simply moving the SD card between devices. I'm wondering if there is a better method than using the getExternalStorageDirectory that I can use, so that I can have a common location on all SD cards to facilitate users moving cards between devices.

wct097 said:
My documentation asks users to connect their device to a computer, mount as USB, and copy the backup file into that directory. This user is simply moving the SD card between devices. I'm wondering if there is a better method than using the getExternalStorageDirectory that I can use, so that I can have a common location on all SD cards to facilitate users moving cards between devices.
Click to expand...
Click to collapse
Well it depends on the device what happens if they mount as usb,
if they get the internal sdcard or the external sdcard or both.
On my galaxy i9000, both the internal(/sdcard/) and external (/sdcard/external_sd) are shown when pluging it into my computer and mounting it as usb.
Environment.getExternalStorageDirectory() will always return the path of the users storage enviroment which is in usually /sdcard . Thats fine so far.
The problem is there is no function to get the external storage (/sdcard/external_sd or /sdcard/sd).
The only option i know atm, would be to probe manually if such a directory exists. You can use Build.VERSION.SDK_INT to see which android the user has and check the right directory.
Build.VERSION.SDK_INT <= 7 would mean if he has plugged in an external sdcard it would be mounted under
Environment.getExternalStorageDirectory().getAbsolutePath() + "/sd/"
Build.VERSION.SDK_INT >=8 would be
Environment.getExternalStorageDirectory().getAbsolutePath() + "/external_sd/"
You could use that and maybe a "import backup" function to check for the file on an external sdcard?

External SD card

Hey guys I am new just got the tablet yesterday. My question is how can I save things like kernels and things to my SD card? It saves yo internal storage and then from there I try n use astro file manager to move it to external from the mnt section but it lets my see the external card it just wont allow me paste it there I had to put SD in my Atrix and then do it and then have to out it back in the a500. Thank u I am rooted using the minimalist rom
Sent from my Motorola Atrix 4G MB860 using XDA Premium App

I have same issue.
i Just re-bought my Iconia last night. I rooted this unit for the first time soon after (MinimalistRom). I see the same thing your seeing. Internal memory is seen as sdcard and my added MicroSD is read as external1. External2 I have to assume would be storage connected to usb connection. Yes i cant copy files over to microsd (external1) from internal (so called SDCard). I'm going to try giving permissions to that xternal1 mnt folder using es explorer like i read in other earlier topic. Ill try to post what i find out.

make sure your tab is rooted then either use es file explorer or root explorer and it will work just fine. I don't think astro can manage it.

I couldnt figure it out. Got to the point of instaling superuser, busybox, super manager and ghost commander. Got every thing, i guess, somewhat hooked up. But in super manager's file explorer, i could get it to chmod rwe on owner --- and other r-e. Group had everything checked rwe. I guess there is something else i'm missing here to change this directories permission. So I'm stumped at the moment and re-image with another rom to see if it correct the mounting of this microsd card external1. Sure would like to figure this out to have app manager send app2sd to my microsd class 10 card on external1.

Sauyai1 said:
I couldnt figure it out. Got to the point of instaling superuser, busybox, super manager and ghost commander. Got every thing, i guess, somewhat hooked up. But in super manager's file explorer, i could get it to chmod rwe on owner --- and other r-e. Group had everything checked rwe. I guess there is something else i'm missing here to change this directories permission. So I'm stumped at the moment and re-image with another rom to see if it correct the mounting of this microsd card external1. Sure would like to figure this out to have app manager send app2sd to my microsd class 10 card on external1.
Click to expand...
Click to collapse
"I could get it to chmod rwe on owner.." ....couldn't get it to chmod rwe...

That's why we need the DEVs to tear this script apart and make it works with custom roms
http://forum.xda-developers.com/showthread.php?t=1175342
so far, no taker
bump it to the top once in awhile if you can
~~~

[Q] First impressions & SD card issue?

Hi,
Just Got the 7.7 3g - so far so good. Screen is as good as they say
The extra resolution defn. helps with web browsing.
Not finding any lag really.
7.7 is just about the limit for my two handed use but i would say the original 7" was a wee bit easier to handle but something with time should become more intuitive.
Just a few issues - external sd card is somewhat limited. Might be deliberate by Samsung but does not make sense.
Normal user apps cant access to the external sdcard. Using connect bot, i checked permissions and it seems that it is mounted by the os with system permissions, where as the internal sdcard is mounted as sd_rw.
This can't be correct? The only way to copy stuff to it is to use the samsung system file explorer as it has system permissions So copy to internal first then to external - this sounds like a bug?
I have not rooted this yet - might then chown to sd_rw get rid of this ?? There is a lot of entries in the vold.fstab to make sense of. Not a hacker so just looking around. A bit too early to start soft-bricking
But I take these don't have protected bootloaders so thats why we can root ?
Video playback is v.good but I am not able to throw on a bluray m2ts file (obviously with the sd card issue) and play smoothly. I found Dice player can handle m2ts by renaming it to a ts file. It then can use hardware decoding. Still drops frames but still watchable to a certain degree. For all other files mx player is still best. I have lossy transcoded some "native" blurays clips and seems that it handle high profile h264 1080p at high bitrates very well. Hoping, formatting sd card ext3/ext4 will improve things.
On the whole very impressive device - plus more ics goodies to come soon hopefully.

I've noticed some issues with the external SD card as well. Only the stock file manager can copy files from the internal storage to the external storage. I was able to transfer files to the ext. SD via Dooblou's Wifi Explorer, though. Although that would crap out a few times.
I'm hoping that we see some new ROMs with a different file system at any rate. The 4GB limit is so 1998.

Fix for external sd write issue
I've already posted a fix for this in our original thread?
davp said:
There is a fix for the write to external storage in this thread:
Samsung Galaxy Tab Plus->Galaxy Tab Plus General->unable to write files to external sd card
post #7
Requires root to apply fix.
There is a new permission that older file managers aren't asking for yet. The stock file manager knows to ask for it.
Fix worked for my P6810 wifi.
Click to expand...
Click to collapse
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse

Rooted and then applied this change.
Can write to ext sdcard !!!!
Cheers

Will apply as soon as i get tad, should be getting it today, cant wait
Sent from my GT-P1000 using XDA App

I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium

will6316 said:
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Using downloaded apps or the stock File Manager app? Because I formatted the SD card in the Tab and nothing else can write to it. Now, I can drag and drop stuff from my computer via MTP, but that's not the same issue.

Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.

burhanistan said:
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
Click to expand...
Click to collapse
Thanks Burhanistan. I had this problem too and did what you did to get around it. Now I can read/write to the external SD with any file explorer.

Hello,
I can access the external SD with no problem, only issue is Titanium backup showing 440Mb capacity on the external SD (32Gb card).
Anyone with the same issue? Any fix?
Thanks.

No problem for me
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Things must have changed as i got my P6800 recently did the upgrade from samsung and tried to copy to external sd and no problem for me. I never tried to do it pre upgrade but maybe the upgrade fixed that. Re i can copy and paste to device from my pc when its connected - to both device and sd. I can also copy using the the stock file manager from device to sd card.

No Issues here also
I recieved the tap a week ago. Now my 32GB Sandisk SD is here.
The Tap did at the first startup and using the described 12 MB Android update via internet conn.
Until now there is no issue between writing from/to SD over PC/MTP, copying between internal and external SD. Used preinstalled Filemanager and ES File Ex.
I tried it unrooted and rooted but not before the Android update.

davp said:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Some people are reporting the above procedure is no more needed, however, with several apps (like Titanium backup, and a SAMBA explorer), writing to the sdcard (extstorage/.../sdcard) is still impossible (GT6800 updated to latest samsung firmware).
I have used this procedure and can state that Titanium backup works now with the SD card.
Thanks to many reading within the XDA forum, I have found this simpler procedure :
- download / install the "Root Browser Lite" app from the android market
- add write access to group and other to the following directory: /system, /system/etc, /system/etc/permissions (with root browser Lite, press on the directory name during 3 seconds to get a contextual menu allowing to change the permissions)
- add write access to group and other to the file platform.xml in /system/etc/permissions
- use the editor of "Root Browser Lite" to modify the file platform.xml as described above (you should have two <group gid= ...> lines within the WRITE_EXTERNAL_STORAGE xml block.)
- save the file. Verify that a .bak file has been created and that the date of platform.xml changed.
- remove the write access.
- Turn off the GTAB, then turn it ON.
NB: Titanium backup still reports a erronous free size on the SD card (401MB), but backups on the sdcard work.

can't save the xlm doc
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Hi, I edit the file but when I try to save it I fail because it says original saved as .....xlm.bak, but I can't find that file and the one I find is unchanged, any ideas?

There is an automated installer for the fix here:
http://forum.xda-developers.com/showthread.php?p=21670802
Is for the plus but worked fine for me
Sent from my SCH-I815 using Tapatalk

damm, must forget something, just followed exacty all the steps
still no writing on sd card
the automatic installer failed also

IS there a way to go into the (forgive the incorrect term) "registry" or similar, and have Android re-interpret/understand that instead of looking in "/sdcard"... it should instead look/point programs to "/mnt/sdcard/extstorages/sdcard"...
i heard that it might be called something like a "simlink" or "symbolic link"... maybe this could resolve the application installation issue to the sdcard as well as backups, transfers, etc... right now, not only do i run out of space too fast, can't install apps to the sd card, but as well, if i should run a hard reset... all my data erases! (yes, the internal "SD card" is erased in a hard reset)...
so, for all practical senses, when it says it will erase data, unless you KNOW you have copied ALL you user data to your "Real" SD Card, you will kill your data without even knowing it when you do a hard reset, even if you "thought" you were protected because "I saved my info to the SD card!"
(and yes, this was my experience today, so it's a fact.)
backup programs won't point to the sd card, (app manager, titanium, app list backup, etc)...
so unless you actively move files individually to the card (and know where to look)...
Bottom line... is there a hack/workaround on this that's not just "open up for file transfers" or is someone working on a ROM that might kill the partitioning and allow the /sdcard to actually point to a real external card?

Edited: Nevermind...

acess-rights-hell
hi forum
i would like to use the EzyKernel v1 - 23/02/2012 as in post http://forum.xda-developers.com/showthread.php?t=1513413&highlight=ezykernel
one of the prerequisites is a stock ZSKL firmware.
on the tab is/was XXKL4 AUT/CH
i successfully flashed the ZSKL2 - but that's where the nightmare started: i could not write to sdcard, busybox/superuser don't work properly, as i can't get root via su - which means to me, that there are messed up accessrights also in other places, not just the SD. the funny thing is, that i finally got the overclocking EzyKernel working, but not busybox + superuser.
does that sound familiar to anyone ?
i would really appreciate any ideas about this.
thank you
with best regards from switzerland
roland

could you please explain what "make sure you have mounted the file system r/w" means. And sorry for my noob question, but does this fix allow to install apps on the external sd card or I'm missing something.

[Q] 4.4.2 microSD card problems (N9005 rooot)

Hi,
I opened a new thread because my problem seems different from this one:
http://forum.xda-developers.com/showthread.php?t=2607215 as I experience the same microSD card problems but that thread's fix won't work.
Brand new, out of the box, N9005. Before using it I immediately rooted it and then I immediately flsahed 4.4.2 (polish) and then re-roooted. Root is confirmed as Titanium, ROM Manager etc all work.
Evrything is fine except the microSD card:
- Android OS can see the card, mount/unmount and format.
- File Expert PRO cannot even read the card.
- Astro File mngr can read (let me edit with editors) and save but cannot rename.
- Dropsync cannot download anything onto the card.
- Dropsync can download same files on internal memory.
- Can see, edit, save, rename, delete - everything ok - if I operate via PC w/ USB.
- Apps can see the content but cannot write on it.
- Apps which rely on microSD card (but not move to ExtSD) are greyed out and don't work.
I tried 3 cards, 8GB, 32GB (class 4) and this 64GB Sandisk (class 10).
All exibit the same problem.
I formatted all the cards with rapid format in PC.
The 64GB card I also did a full, 1 hour, format in PC.
I utried both NTFS and FAT in PC.
Help! Please!

Same problem here, i hope you found a solution for it
Sent from my SM-N9005 using Tapatalk

Nope! Sorry. Still searching...
Sent from my SM-N9005 using Tapatalk

Try to use FX file explorer

i did instruction from link above, it works, i am using es explorer, enable root tools, check / and /system, replace platform.xml, set properties rw-r--r-- reboot, done
Sent from my SM-N900 using XDA Premium 4 mobile app

hillzx said:
i did instruction from link above, it works, i am using es explorer, enable root tools, check / and /system, replace platform.xml, set properties rw-r--r-- reboot, done
Sent from my SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where is the "above link" , how can I find it
Thanks

From the Note 2 thread. Unsure if this is exactly the same resolution as the above
External SD card mount point fix for kitkat roms
Im unrooted so I'm just having to wait for the 3rd party updates.

this is bull*
i don't want to root my phone in order to solve their problem .. JESUS!
it seems it's a Kikat problem, google also wants to f*ck us now.
http://android.stackexchange.com/questions/58592/using-an-external-sdcard-with-kitkat

Agree... For once, I left my phone unrooted (after owning Galaxy S, S2 and Note2), and now this... I can modify the external SD with the built in file explorer, but ES File Explorer, Solid Explorer, SMS Backup & Restore and Sygic have problems writing or modifying content on the SD.
As the builtin file manager CAN access the SD, I hope it can be solved by the app devs, however, I find it strange that it is still not fixed for a lot of apps (actually none I could find in my app list), and that this is not one of the top discussions here...
I already contacted some of the support teams of the apps, but some of them indicate they are working on a fix themselves, whereas others say it can not be fixed in 3rd party apps...

I have the Sprint Note 3 running 4.4.2, and could access the SdCard from Titanium Backup. I used this link http://forum.xda-developers.com/show....php?t=2607215 from above. I downloaded the platform.xml and used root explorer to place it in the right folder, set permission and rebooted. It worked perfectly and now I can run Titanium Backup and save it on the ExtSdCard.
Thanks

its the new kitkat ext. sdcard rules.. !
now developers have to update their apps to work with the new rules..
ES file explorer is updated,, it does work to some extent..
btw,, everythings ok with the Samsung's own file manager..

Set external SD card to default install location [HELP]

Hi, my problem is with the phone of my girlfriend. Now have external 64GB SD, because internal storage is full. I used Android SDK and all the instructions for set default storage for install APP the new SD Card, you know, with the command adb shell pm set-install-location 2. And no error, i try get-install-location and report 2. But googe play only try to install in the internal storage.
I think the problem is with the system of the emulated storaged or something, but i tried many APP, many solutions, and i cant fix this, i search in google and others locations, have 30 tabs in firefox open with information, but i cant found the solution for this
Samsung Galaxy NOTE 4 (910F)
Android 5.1.1 (Of samsung of course)
Rooted
The vold.stab is:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
PLEASE, help me! thanks

I tried dismounting and mounting the SD, touching the vold.stab file, but do not get any results.
Can anybody help me?

Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).

ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
Thanks, for the moment 6.0.1 is not released in Orange (confirmation date has passed and still not have it, I assume that is in the offing). When have 6.0.1 i try you solution, thanks.

ph03n!x said:
Go back to stock, upgrade to 6.0.1. Then see if this helps-
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
The article is for S7, but see if you can have that working in the N4 - just have a backup of everything (int SD, ext SD, full backup in recovery).
Click to expand...
Click to collapse
I tried this in my phone. While the command itself worked after a bit of a tweak, the storage situation was pathetic - the phone showed the External SD as a part of the overall storage, but did not save files to it. Instead, it started saving files to the actual internal SD Card, resulting in space running out pretty soon. The External SD card was just there, and there was no way to migrate the files from the internal storage to the adoptable storage.

I just got a new Note 4 (this is the 3rd one I'm using since the first release in 2014) and I also want to adopt external memory card as my internal space bcos the 16Gg duos version is just too small and app to SD comes with a lot of hassles. After a lot of search for different solutions (which I tried out by the way but didn't work) I came across this thread for another phone entirely but it resolved my issue: https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478.
The only downside is that I can't pop out my card (128Gg Samsung) and plug into my PC but I can still explore it directly from the phone itself.
I've been using the phone for 3 days and it runs smoothly, I hope that solves your problem too.

So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.

Will Rickards said:
So there are two parts to the adoptable storage. The first part is the partitioned SD card and mounting the partition. Simple to be done via root essentials or the command line.
The other part is the actual menu entry on an app in application manager for moving it to the second partition. IIRC samsung does not have this support built in. So you need to flash something to replace that manager bit. In my experience with an on5 (like less than 1GB free on internal storage out of the box), adoptable wasn't really worth it, too much stuff still on internal storage. As not every app will allow you to move it to that second partition. It requires both system support and app support.
What I did there was to use the app apps2sd. Same idea, second partition on SD card. But it doesn't show up in settings -> storage. You manage where the apps go via that app. I use the link feature which places a symbolic link in the internal storage and moves all the actual files to that sd card partition.
Click to expand...
Click to collapse
I've been using apps2sd fot about a year and it comes with it headache too, sometimes the apps wouldn't find the external data (usually games with a lot of data) and it'll start downloading it again into the internal memory, so I usually find myself having to force stop the app, delink and relink the data on the memory card to fix the bind. I also didn't bother to partition my SD card since I can explore it on the PC with my phone connected. What this solution ( https://forum.xda-developers.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478 ) does is to flash back the option to use the SD card as internal memory that Samsung removed from the phones and it works seamlessly on all Samsung phones with rooted stock OS.