Related
This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.
If you are like me and bought the 16GB version of our beloved SG3, thinking you could always move apps to the external sd card, then this mod is for you. It swaps the internal and external sd cards so apps install on your external card, because your phone is fooled into thinking the external card is the internal card.
I suggest that if you are going to do this, you should probably do it right after installing a new ROM, and before you install any apps. That way everything will get installed onto the external SD card.
I didn't invent this, Zedomax adapted in from mattiadj. But most people haven't been able to get it fully working, probably due to variations in the init.d function of various ROMS. They'd be able to see the External SD card as the internal SD, but the internal SD would disappear. This method avoids using init.d, and instead uses the app Script Manager to load the script on boot.
After much fooling around, I figured out how to do it so the External SD card and the internal cards are swapped, but you can see both with any file Explorer. I got it working on CleanROM 2.0, but it should work on Beans 10 as well.
Here's how to do it: Warning, if you do not understand the following instructions, or don’t have experience doing these things, you probably don’t want to do this hack. I am not responsible if you a) brick your phone, b) delete your data, or c) get very frustrated. That being said, the most likely failure will be that you only see the one card (the External card).
Back everything up that you care about first!!!!
1. First, I'd recommend making a Nandroid backup of your phone.
2. Next, just to be extra safe, I would backup your internal SD card to your PC. While you are doing that, if you have data on the external SD card, back that up too.
3. Next, I would format your external SD card to fat 32. (You could probably use Ext format too, but I didn’t test that.)If you already have it in that format, and have content on it, this won't affect the content, but back it up just to be safe. It’s probably better to have the Ext SD blank to begin with, you can always copy back its content from your pc.
4. Next copy the contents of the internal SD to the External SD card. This is to avoid confusion about apps and such.
5. Next install script manager free from the play store:
https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd
It will show up on your phone as S manager ads.
6. Download the mod from here: http://downloadandroidrom.com/file/...ternalsd_gs3_fat32orextfat_US_ZEDOMAXv0.2.zip
7. You’ll see a folder called: 11extsd2internalsd_gs3_fat32orextfat_US_ZEDOMAXv0.2.zip
You need to unzip the folder, then go to System/etc/init.d and copy the 11extsd2internalsd file from there to your phone. Put it into the /data directory. Use Root Explorer, and your phone will need to be rooted.
(https://dl.dropbox.com/u/6305/SD Card Hack SG3/11ext file in data directory.png)
Or you can get just the 11extsd2internalsd file here: https://dl.dropbox.com/u/6305/SD Card Hack SG3/11extsd2internalsd
8. Using Root Explorer, navigate to that file in the /data directory. Press and hold the file name until the menu pops up, and click on permissions.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Permissions.png
(Unix geeks set them to 777, and everyone else copy the picture below. Click OK.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Permission settings 777.png
9. Open the script manager app, and select Browse as Root in the config screen. Tell it to remember this setting.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Script manager browse as root and save.png
10. Navigate to the /data directory and choose the 11extsd2internalsd file that is located in /data and click on it. Click on the “Is script” button.
11. Now tap on the buttons that say Su, Boot, and Save. The file name will come up in yellow after the save.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Script manager setting after save.png
12. Reboot your phone and you should see the swap working and be able to access both internal and external SD cards. The external card will show up as sdcard, and the internal card will show up as extSDCard. Your apps should now install to the external card, since your phone will think it's the internal card. Is that confusing? It was to me too!
Good luck and please share your experiences specifying which ROM you used, so that others can avoid frustration.
Thank you’s always appreciated.
Wonder if this works on asop roms as well.
Please excuse my Galaxy S III, it's a bit Paranoid.
On my X2, this same mod was done via a flashable zip...not sure how it worked, but it was worked perfectly. At some point the roms incorporated the flip flop as part of the Rom. I like the feature because I wouldnt need to move certain app data to my external sd card. Also, I wouldn't have to show tibu where to look for my backups.
Sent from my SCH-I535 using Tapatalk
Clienterror said:
Wonder if this works on asop roms as well.
Please excuse my Galaxy S III, it's a bit Paranoid.
Click to expand...
Click to collapse
What's the consensus on this? Can this mod as posted above be applied to AOSP/CM9/CM10?
Just flashed this on aokp and both sdcard and external_sd are my physical sd card. The internal card is not showing.
Op, can we get an cm10 ver?
Did a little playing around. Below seems to work on cm10 aokp. Can op confirm this is good?
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
maniac2k said:
Just flashed this on aokp and both sdcard and external_sd are my physical sd card. The internal card is not showing.
Op, can we get an cm10 ver?
Click to expand...
Click to collapse
Are you actually flashing it, or using the Script Manager? As far as I know, only the Script Manager approach works.
maniac2k said:
Did a little playing around. Below seems to work on cm10 aokp. Can op confirm this is good?
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Click to expand...
Click to collapse
Not sure, but take a look at the code from 11ext2internalsd file. If it works, and you can see both sd cards, then you've nailed it.
Yeah sorry, im running the script apk. It seems to work. I just dont understand the exacts of the vold/179:97 or if it should be vold/197:96?
When i go into settings/storage, should my physical sdcard stats be showing under internal memory?
Thanks I got mines to work now. Thanks to your suggestions.
Sent from my SCH-R530U using Xparent SkyBlue Tapatalk 2
Update: ive been using the script below for a littlw while and it is working great on cm10. It is best to enable it after a fresh rom install.
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
I need to do this.
MODERATOR.
This is not a Q&A Thread. Needs to be moved to appropriate location.
Apps Did Not Move After Internal / External SD Swap for GS3
Well I thought everything went perfectly because as mentioned, when I go to storage my internal shows my 64g card and internal of 12g now shows as external. However the apps are still on my internal which is now called my external and when I go to app manager it shows remaining space 5.9g. So I am not sure what I did wrong because I have reviewed this several times and started right after I installed a fresh rom . I am hoping someone can help me correct this because basically all it did was change the name of the two drives but apps are still getting installed to original location. Thanks in advance for any help you can give me
Swapping internal>external did not work
i followed all steps as stated above but when I go to File Manager (default), long pressing Internal SD>Details show 1.2 MB and External SD shows 1.8 GB which is not true. I have external SD of 8 GB and internal is 2 GB in my micromax a110 phone.
The steps above did not work to swap the memory but it now shows even incorrect size. I installed Root Browser lite but got no way to chck the size of the SD cards.. Please help
Does this work with the new Verizon Jelly Bean which they are now sending out via OTA? Are there other Verizon S3 Jelly Bean Roms that are known to work with this method? Thanks
Its works on the leak so i dont see why it wouldnt work on the actual vz rom
not working
This is not working with my samsung s duos please help
Any cm 10.1 updates for this?
I am unable to change the file permissions to -rwx-rwx-rwx- whenever I try to change it I get an error that the phone is unable to change permissions.
EDIT:
Successfully changed permissions and followed the instructions as given. Still not working on the international S3, my internal memory is still 16 GB and external 32GB
Hi
I have a Galaxy Note 10.1 which is rooted.
I installed Titanium hoping that I could move apps to my SD card but the option is not available.
I initially tried re-partitioning my card so I not have a fat32 partition and an Ext4 partition - still no joy.
I put an app folder on the Ext4 partition - still no joy.
I've tried App2SD and Link2SD - still no joy.
What is the easiest way to move an app onto the external sd card when using a rooted Note 10.1?
Many thanks
Note101Beginner said:
Hi
I have a Galaxy Note 10.1 which is rooted.
I installed Titanium hoping that I could move apps to my SD card but the option is not available.
I initially tried re-partitioning my card so I not have a fat32 partition and an Ext4 partition - still no joy.
I put an app folder on the Ext4 partition - still no joy.
I've tried App2SD and Link2SD - still no joy.
What is the easiest way to move an app onto the external sd card when using a rooted Note 10.1?
Many thanks
Click to expand...
Click to collapse
Might this do the trick for you?
http://forum.xda-developers.com/showthread.php?t=1888986
schnurrbidurr said:
Might this do the trick for you?
http://forum.xda-developers.com/showthread.php?t=1888986
Click to expand...
Click to collapse
It looks interesting but the main downside is that you have to move everything from internal to external storage.
In an ideal world, I only want to move 4 or 5 of the big apps/games as most are really tiny.
Note101Beginner said:
It looks interesting but the main downside is that you have to move everything from internal to external storage.
In an ideal world, I only want to move 4 or 5 of the big apps/games as most are really tiny.
Click to expand...
Click to collapse
Just use: http://forum.xda-developers.com/showthread.php?t=1410262
I'm currently using it myself, pretty easy. The only thing is:
You basically got 3 partitions on your note (i.e. 16GB version). 1. system (~4GB) 2. sdcard (internal) (~11,5GB) 3. sdcard (exernal)
If you look at an app in (I hope the following are the correct translations, I only got german) systemsettings/storage and tap on apps and then on a specific app, you'll have the sizes "total", "app", "USB-Storage for App", "Data" and "SD-Card". Everything in "App" is in the 2. partition,but you can't locate the data under /storage/sdcard0/, nevertheless it's on the internal sdcard partition, cause it can't be in the system partition. I have no clue where the data is, my guess is, that sdcard (internal) is just a part of the second partition. Anyway, the data under "App" can't be moved with DirectoryBind, cause you (or let's say I) don't know where exactly it is. The data under "USB-Storage for App" should be in /storage/sdcard0/Android/obb/<package name>, and that's the data you can move. Most of the big games, have their data in these directories (ie. GTA Vice City). So what you want to do with DirectoryBind is: Set target to the above mentioned path, and the location to a exact replica of folders on your sd card and select "move data". What directory bind does is the following: It sets up a pseudo file in the original location, which is just a reference to where the file really is.
I hope that wasn't to confusing.
Have fun.
Hello,
I've been trying for around 3-4 days now, playing around with custom ROMs and such, trying to switch my internal (8GB) memory with my external (64GB).
I'm currently using the Taktik ROM, and there is no vold.fstab under the system/etc folder.
I've also tried things like scripts that are executed, mounting the int_storage versus the sdcard1. However, upon looking, the internal storage on my tablet is called sdcard, and the external is called sdcard1, so I tried modifying the script, replacing int_storage with sdcard. This still claims that there is no file or folder found.
Is there app or script that will do this?
Thanks
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
thesavo said:
Has any one else lost the ability to write to their socketed sdcard since the 4.4.2?
Click to expand...
Click to collapse
Thats a "feature" of kitkat. Can't be changed unless you have root.
Seriously?
Yes, see here for fix(if your rooted):
https://play.google.com/store/apps/details?id=nextapp.sdfix
thesavo said:
Seriously?
Click to expand...
Click to collapse
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Time to move the podcasts. So my older shows that I worked hard to keep to keep the ext sdcard1 as a target, will have to be copied to sdcard0.too bad.thanks @iBolski
No wonder BeyondPod kept 'accidently' putting shows on SDcard0 for the last year. Even though I "pinned" it to SDcard1 in the advanced settings.
Even with the application that patches the /etc/permissions/platform.xml, I have found certain apps still do not work correctly. Dolphin Browser, for example, cannot switch to /storage/sdcard1. It keeps saying it can't find it and I need to ensure I don't have "USB Mode" enabled, which I don't even have as an option when connected to a PC.
I also have init.d installed on my machine and I had startup scripts that mounted various directories from my external to the internal SD card to "fool" the device so that apps that wouldn't save to the external but the internal would save across a mount. Well, that no longer works. For example, Amazon MP3 will not save downloaded music anywhere except to the internal sd card. I had my startup scripts mount an amazonmp3 directory on my external SD card to the internal amazonmp3 directory on the internal memory card. When I proceeded to download music, it didn't show up in the external directory. However, I noticed that the internal sd card's memory did decrease. I then unmounted the directory and saw that the Amazon MP3 app was ignoring the mount under KitKat and directory saved the files into the /storage/sdcard0/amazonmp3 directory, even though it was mounted to the directory on the external SD card. It did work under JB and ICS, but apparently, with KitKat, some apps will still write directly to the native directory on the internal SD card, ignoring the fact that I've mounted a different directory to it.
The stock Moto camera will write to the external SD card if you go and change the setting for it. However, the Google Camera does not give you any option to store your pictures anywhere except on the internal SD card memory. :crying:
Remember, apps can write to the external card, if you don't apply the "patch", but only to what is considered a protected are (the /storage/sdcard1/Android directory structure) and then, they can only write to a directory that the app created. They can read other directories, but they cannot modify them.
iBolski said:
It's a security issue. Before KK, the SD card was wide open to any other process to be able to request read/write to any directory and file, regardless of whether or not they created that file or directory.
Now, under KK, a program can create a file or folder in a "protected" area and only that program has the ability to modify the contents in that folder. It cannot modify other folders or files that it didn't create.
Click to expand...
Click to collapse
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Zeljko1234 said:
That's official explanation (bull****) as you described above with non stock camera. Basically KK made external storage almost useless. I found this nice description quite long time ago.
https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
Click to expand...
Click to collapse
I know at this point, Root Explorer still works with it, after setting the correct permissions into the /etc/permissions/platform.xml file. That works for a lot of apps. The only one that I know that is currently broken is Dolphin browser. I cannot navigate to the /storage/sdcard1/ area anymore. It keeps telling me it can't find the file or directrory and that I should make sure the SD card is ready and USB Mass Storage (haven't seen this option since my Droid X2) is not on.
So definitely, Dolphin Browser is doing something differently that even the patch isn't working for it.
Problem is that without root user cannot edit platform.xml and even after that some applications refuse to write to sd card. Another example is OfficeSuite 7 Pro which I bought and now cannot edit file if it's needed. Workaround is to save to internal then overwrite to sd card.
Basically stock Android becoming more and more limited, harder and harder to get root... That's so bad that I wouldn't update to official kk in the case that my phone has locked bootloader.
Read this article http://www.xda-developers.com/andro...use-even-more-issues-for-root-app-developers/