Related
Hello,
Perhaps a strange question, but suppose I have 2 microSD cards, and I install an application on a microSD card. If I want it to run regardless of what card is inserted, does it suffice to copy the folder in which it was installed from one card to the other card (reconstructing the directory structure)? Or do I have to go through the install procedure and install the application on the second card as well?
Can anything be said about the settings of this program: are they dependent on which of the 2 cards the application is running from, or are they independent of it? Or does this depend on the application at hand?
Thanks!
Jörg
when i got my 8525, i initially had a 2gb micro sd. when i got the 4gb micro sdhc, all i did was copy everything from the 2gb micro sd to the 4gb micro sdhc. then i was set to go.
no problems whatsoever.
V J said:
Hello,
Perhaps a strange question, but suppose I have 2 microSD cards, and I install an application on a microSD card. If I want it to run regardless of what card is inserted, does it suffice to copy the folder in which it was installed from one card to the other card (reconstructing the directory structure)? Or do I have to go through the install procedure and install the application on the second card as well?
Can anything be said about the settings of this program: are they dependent on which of the 2 cards the application is running from, or are they independent of it? Or does this depend on the application at hand?
Thanks!
Jörg
Click to expand...
Click to collapse
That would work fine.
Thanks...
(good to know there are no hidden things)
I assume that settings will be depend on whether they are stored in registry or in configuration files.
Shortcuts to non-existing targets (e.g. to a program that is on a card that was removed) are still shown in the program list... Is there a way around this? My Psion 5mx had a dynamic "programs folder", showing only the available programs.
Perhaps there is a possibility to trigger a script upon card removal that simply copies the shortcuts to some other folder, and similarly copies them back upon insertion (after checking e.g. the volume label); but I don't know if/how this can be done... I can see myself making a script (MortScript) allowing me to remove/set shortcuts, but I don't see how I could automate this... (perhaps this ought to be in development and hacking).
Thanks!
Jörg
am really confused as to what you are up to..
seems like you are making an occupation out of something very simple to do.
Yes...
Simpler would be to execute a script on the card upon insertion... (thought of this after posting)
Bottom line is: I tend to forget to execute the scripts, leaving me with non-functional shortcuts. If this were automated, only the valid shortcuts would remain...
Jörg
To save some people time in searching and asking the same question I had (and for 4.4.2 I think there will be plenty...):
I had severe issues using a brand new SD card in a brand new unrooted Galaxy S5. However, I now found through test that it was not the card.
I tried many things, formatting on my computer, formatting on another phone, etc etc. Nothing worked. I then tried to use the card on other devices, which worked fine! I then tried other cards, none of them seemed to work.
So I thought the S5 was defective. I did some searching online, and found that it actually is not defective. This is a feature of kitkat 4.4.2!
The card is perfectly usable, but under very restrict situations.
For example, reading is perfectly possible, but writing is controlled by kitkat. I found through some websites that Samsung decided to beef up security and at the same time make the use of external storage more clean.
Previously you could use any file browser to manage any file son any external storage, like an SD card. Although this gave great freedom, Samsung also seemed to believe that it is a source of security risk where rogue apps could read/write to folders they didn't create. They also seemed to believe this made management of files on external storage messy. To control this Samsung now allows properly installed apps to generate folders only in internal memory, and those same apps can only access folders they themselves created. The exception to this are factory standard default apps that come preinstalled on the device.
So my mistake was to use ASTRO file manager to move around a file. Once I read the issue online, I tried the same action with Samsung's pre-installed file manager, and to my surprise the file did transfer to the SD card!
To further clarify, I suspect this "feature" is limited to write activities. For example, backup to SD apps will fail to write apps to SD. Similarly, Airdroid cannot copy files from your desktop to the SD card, only to their own folder (and thus you need Samsungs file manager to move those files to the SD card).
What's interesting about this however, is that READ access seems to still be possible. ASTRO file manager can still read files from directories other apps made. Adobe reader can still read files on all kinds of folders.
The criminal spy app can still read and copy your banking files from your bank directory to its own directory for transfer to the criminal mind who will then plunder your account. So no, the security issue Samsung wanted to address has not been addressed.
What is my opinion about this? Well, I think Samsung made a nice attempt to improve security. However, they completely failed to address the biggest security risk, which isn't write access, but read access. And at the same time made it very painful and difficult to store large numbers of music, video and document files to the SD card. Because now you will either need to plug in your memory card into your computer, or move all those files via internal memory to the external SD card using Samsungs file manager, which of course takes much more time.
More info on the feature can be found here:
http://gs4.wonderhowto.com/how-to/b...ns-android-4-4-kitkat-your-galaxy-s4-0152036/
here:
http://support.solidexplorer.pl/responses/kit-kat-442-issue
And here:
http://developer.samsung.com/forum/...Lines=15&startId=zzzzz~&startPage=2&curPage=4
We could all ask Samsung to revert this "feature", but chances that they will, are remote since there are ways around this problem.
Of course, people who use many many apps/games will be out of luck, as they will be restricted to 16/32 GB.
Note to moderators: Can we make this a sticky for kitkat 4.4.2?
Root and you'll be able to R/W on the ext-SD card and try this app SDFix
Samsung has nothing to do with it... It's an Google's android policy.
So, the links I provided make that same statement. I.e. I'm aware of possible fixes. However, I bought my phone in Singapore so I could have a reliable unhacked, unrooted, unmodified phone. Others might also want original phones and not root their phone until their warranty runs out.
This was not my point though. My point was to provide some info that could be turned into a sticky so it is easier for people to find what could cause their memory card issues.
I still hope the original post will help others troubleshoot their memory card issues with their s5.
I did search and with the google searches I've done, can't really figure it out so thought might ask here.
When I moved applications to external sd card, i didn't realize it didn't move the application data itself (inside obb folder), which is in the android device's internal memory. So basically, I have the application (i guess equivalent to .exe for windows) on the external sd card, but the beef of it (the applicatin's data) is still on the internal memory and using up the device's memory....how can I move the data (obb folder) to external, remove it from interernal to free up space, and have it boot up / work on the android device?
i'm not advance geek so need a dummy explination
You didn't provide details of how you moved the app or even what app we are talking about. So it's impossible to give targeted advice. Which is unfortunate since you want a dumbed down, simple answer. Which can't be done without knowing those crucial details.
You can use one of the Play store apps to move the app. I'm sure that some of them would move the app data as well. Or change the app data path (folder) in the app's settings. Or reinstall the app. Or alias the current internal data location to the external card with a symbolic link. Or any number of other ways.
The simplest options there would be trying some of the Play store apps that assist in moving programs to the external data card. And if that doesn't work for some reason, then reinstall your app.
Good luck.
.
fffft said:
You didn't provide details of how you moved the app or even what app we are talking about. So it's impossible to give targeted advice. Which is unfortunate since you want a dumbed down, simple answer. Which can't be done without knowing those crucial details.
You can use one of the Play store apps to move the app. I'm sure that some of them would move the app data as well. Or change the app data path (folder) in the app's settings. Or reinstall the app. Or alias the current internal data location to the external card with a symbolic link. Or any number of other ways.
The simplest options there would be trying some of the Play store apps that assist in moving programs to the external data card. And if that doesn't work for some reason, then reinstall your app.
Good luck.
.
Click to expand...
Click to collapse
Only thing I've done was root it then moved the application (move to sd card) via settings >> Application Manager. i want to do it for all apps but it's mainly due to games taking up lots of space. Reinstallng won't help cause everything that's obb just direct itsself to the internal storage, nothing i installed even gives me the option to install data into external, just only has a install button and it installs to internal memory
I'm not going to sort all of that out. It can be done if you look into the details.
The best advice that I can offer is to consider installing a custom S5 ROM like Phoenix. It has a setup option to swap the SD cards. That would mean that all of your apps that automatically install and live on the internal memory.. would actually end up on the external card. And it works perfectly.. because the apps think that they are on the internal card even though they aren't.
The source script could also be applied to your existing configuration, but doing so would not fit inside your stipulation for a simple answer.
.
by the way...
fffft said:
I'm not going to sort all of that out. It can be done if you look into the details.
The best advice that I can offer is to consider installing a custom S5 ROM like Phoenix. It has a setup option to swap the SD cards. That would mean that all of your apps that automatically install and live on the internal memory.. would actually end up on the external card. And it works perfectly.. because the apps think that they are on the internal card even though they aren't.
The source script could also be applied to your existing configuration, but doing so would not fit inside your stipulation for a simple answer.
.
Click to expand...
Click to collapse
fffft, one question here: Would it be possible to format the whole external SD card with ext4? So it would be quite simple to copy such files manually within a shell and set a softlink to the moved files? I don't understand why android stays with that fat drived file systems were softlinks are not working. Is there any reason for? So all data2SD apps have to work with specific *mounts*. I can't believe that this is fast and stable.
brachypelma said:
fffft, one question here: Would it be possible to format the whole external SD card with ext4? So it would be quite simple to copy such files manually within a shell and set a softlink to the moved files?
Click to expand...
Click to collapse
That won't work unless you do a lot more prep work. The file system isn't invisible, the OS would have to interact differently with ext4 than ExFAT. The OS would balk the first time it tried to follow a symbolic link and didn't find the ExFAT structure it expects.
To make that work, you'd need to mount the card yourself, manage permissions and hide the file attributes i.e. permissions from the void manager and other housekeeping tasks. Android expects to find a case insensitive and permissionless FS. Otherwise, void will report errors to the volume manager and the OS won't recognize your card. All of which is to say that this is a more distant outlier to the requirement for a simple solution. So you'd be generating fatal errors the first time the OS tried to follow a symbolic link to your ext4 files.
So yeah you can shoehorn an ext4 card into the system with enough work. But it isn't as simple as you believe. So back to my suggestions that the OP either install a custom ROM that does what he wants or that he looks at the script that I linked him to. Or perhaps migrate to CM 11, where native support for ext4 and NTFS have been added.
.
I slowly look there no longer. I have rooted my S3 Neo initially quite normal and provided with CWM as it has been explained in various tutorials. Then I fixed the Android 4.4 write access issue with the "NextApp SDFix" from Android market. With the "ES File Explorer" and "Total Commander" I could normally rename files on the SD card, copy and move.
However, to me the practical effect is associated with all apps, which store data automatically on the SD card very mysterious, because instead of the SD card, they will continue stored internally namely in "/storage/Emulated/0". I tested this with "Dead Trigger 2", which is usually stores the game data in "Android/OBB". In Application Manager I have the opportunity the app to move itself to the correct SD card (.android_secure directory), but just the app itself and not the game data wich stay in the internal, emulated SD-Card.
For my previous smartphone, an Ace 2 NFC (I8160P) there was a fix for it to fit the "vold.fstab" to file: http://forum.xda-developers.com/showthread.php?p=28419837#post28419837
I could find only a tutorial changing the internal memory with the real SD-Card for the normal S3, which, however, is probably not compatible with the S3 Neo: http://android-hilfe.digidip.net/visit?url=http://forum.xda-developers.com/showthread.php?t=2036796 - Or should I try it so anyway?
At first the question: Why the Kitkat-Fix is at all useful, if it does not help in practice and the data continues to be stored internally? The only thing that has been directly accessed files to the correct SD card was the photo app but that's about it.
Update: I just see that it also provides an Android folder on the right SD card as well as in the emulated and actually reside in folders and the installed apps, including "Dead Trigger 2". However, the folder unlike emulated SD card are completely empty. What does that have to mean again?
I hope somebody can help me ans find a solution as I can't use my external SD-Card for most game datas or apps as planned or I will send back my S3 Neo tomorrow.
PLEASE!!! Can somebody help me???
do you use xposed? there are a couple of modules that allows you to use obb files from sdcard. Personally i use "xinternal". those ps apps never worked for me also.
Use Folder Mount
I use a xposed module called "HandleExternalStorage" and it works like a charm! Try it yourself!
Good luck
Hi Everyone,
Back with an android phone after quite a while.
Just added a sd card to my SGS7E and realised I can't do anything with it.
All I want is to be able to use the sd card as you would normally, create and move files, folders etc.
Is this possible without rooting?
If so could someone provide any advice or point me to a relevant resource.
If i need to root what would you good people recommend? I don't want to do anything fancy at the moment (I'm sure that'll change) just use the card as normal storage.
Thank you for your help, advice and time.
The SD issues are my biggest let down. My camera won't save to it... people tell me to factory reset but I don't feel like loosing all my work I put into it.
Other apps see it as having storage in mb I think instead of GB. issues and nobody talks about it
Hi,
The sdcard is working okay for me. If system apps can't read or modify the content inside the sdcard, then reinsert the card or reformat it because it's very likely that the phone isn't seeing it.
If you want user installed apps to access the sdcard, it's a bit more annoying. Open the app that you want to access the card, then try to make a modification in it (like creating a new file if a file manager, saving a picture if a camera, downloading a file if a torrent client, etc), it will say it can't access the sdcard and will ask you to point where to root of the sdcard is, just select your sdcard folder on the prompt and it will work fine.
Keep in mind some stuff like app data can't be moved to the sdcard, so try to keep all media on your sdcard and all apps in your internal memory, that's what I found to be a pretty easy and good memory management. If you want however to install apps on your sdcard, you can enable adoptable storage using a terminal window (formatting your card), or root your device to use some third party app that will do that for you.
All the best,
~Lord
Sent from my Samsung Galaxy S7 Edge using XDA Labs