In order to allow symlinking I want to format the internal 11GB /mnt/sdcard to ext3.
One way is backupping everything to a laptop over USB, then reformatting it from Linux by gparted (or Disk Utility from Mac OS with Macfusion ext3 plugin) . So far so good.
But then remounting it on the SGS2 will probably issue an error as Android does probably not automount it.
Is the only way rooting it and then edit /etc/fstab if that exists on the device ?
Who knows ?
Hi,
how did you manage to partition the internal memory?
I too am trying to reformat it, but gparted shows the partiton as "unallocated". The external SD card also appears as "unallocated" in gparted when the phone is connected through the USB cable.
I can access all the files from the internal/external "cards" though.
PS: I'm using a Galaxy W, sorry for posting here but I couldn't find a specific section for my phone.
PS2: I found /etc/vold.fstab (there is no /etc/fstab), and the partitons are mounted like this:
-------------------------------------
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
------------------------------
So no references to the file systems used, maybe the mount should work after reformatting?
I do not like how the internal sdcard is the default data storage instead of the external sdcard. I've had to factory reset a couple times now and all app data, downloads, etc.. were erased. That and if something happens to the phone the data would be lost. I remembered it was like this on one of the tabs I had so dug around a bit and found a mod to the vold.fstab file.
This file is in etc/ and also system/etc/
(not sure why it says HTC Passion???)
Code:
## Vold 2.0 fstab for HTC Passion
#
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard 37 /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount sdcard2 /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
If I read the mod correctly you would have to change the sdcard to sdcard2 and vice versa like this:
Code:
dev_mount sdcard2 /mnt/sdcard 37 /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount sdcard /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
What I'm not sure on is if it is the same for phones as it is for tablets and is this the correct way to change the sdcard mounts? I am thinking the mod needs to be done on both files and if this is the correct way it may be hit or miss if the mod sticks after a temp root reboot.
i'm really curious about this too. i want to figure it out so as soon as i get s-off i can change the mounts. this has already bit me in the a$$ once with this phone and i lost some stuff.
Do u mean like if ur downloading files and how data is stored that way? Just curious, because it is annoying to me as well.
"BEATin" through "REZOUNDingly"
youngpettyboi said:
Do u mean like if ur downloading files and how data is stored that way? Just curious, because it is annoying to me as well.
"BEATin" through "REZOUNDingly"
Click to expand...
Click to collapse
Some applications are correctly downloading files to the external SD card where storage is supposed to go. But other applications (usually older not updated) have the tendency to use the internal SD card. This becomes an issue when you factory reset and the internal SD is wiped. Some people have lost their data unexpectedly.
I guess I'm the only one who likes the way this is set up, I hated it when apps would crap up my sdcard with all their data. As for changing the mount points you would need to be rooted to accomplish that.
I got hit hard when all my downloaded pics from mms where wiped
I'll try it this weekend and see what happens and if it sticks after reboot. I wonder if it does work, would a factory reset wipe the external card if it is not removed. Well I won't test that theory but I would like to at least see if the mounts are able to be changed with only temp root.
You should be able to remount if Android supports the "-o remount" flag in mount. I believe it does. I don't think this will persist beyond a reboot but if it does, then I'd like to do something a little more intricate. Mount 10GB(of external SD) to /sdcard/music and 2GB to /sdcard/DCIM and 4 GB to /sdcard/Download or something like that. Might cause hell connecting to a PC though..
you need to be root to mount devices, also just issuing the command won't persist beyond reboots, you need to place it in the equivalent of fstab.
That's what I'd thought too.
/system/etc/vold.fstab would need to repoint /sdcard to the real external
card. And something to the /sdcard fuse re-director for the internal memory.
Right now, I sync /sdcard/Kindle and /sdcard/Nook to their corresponding
/sdcard2 directories so my user data (side loaded books) can be found
since those apps are written to Froyo's SDK level. I've written to both vendors
and they say their developer's are working on updates in support of the
ICS level of SDK. They both thought the simple solution of a configurable
option to use as an 'app root' for where to look for its data made sense.
That would workaround future directory moves in the OS.
A full scan of user space, like Titanium Backup, does for its
data directory works too.
Would the hboot wipe / write rom functions be using the
/dev/<devicename> or their mount points to do its writing?
I'm guessing the built in recovery's fstab would be pointing all
at the internal memory directories and partitions, be cause it would
not be aware of customization in the running OS's /system/etc.
I'd guess whatever custom recovery get put together, would be
aware of int_flash vs ext_flash memory locations.
As far as downloading stuff, you can change that thru your browser. It gives you the option to download stuff to your internal SD or external in the options. Not sure if any of you knew that. For pics, GOSMS always saves my pics on the Ext SD card by default. I actually like it like this better. I hated the Dinc since it would always run out of space and had to use my Ext SD Card for apps.
/sdcard is part of the internal flash erased by a hard reset
So since by default, there isn't a way to save user data programatically,
or by virtue of being a physically separate partition, it gets wiped too.
I manually mount the /sdcard and /sdcard2 directories to windows
and sync them with desktop directories for backup, daily.
I wonder if anyone has (or knows of) an android app to sync
between /sdcard and /sdcard2 sub-directories? I mean,
to use /sdcard2/Kindle and /sdcard2/Nook for example as
backups of the e-book databases on /sdcard (which is subject
to erasure by accident).
Does Titanium's sync app do that?
Thanks
Therev29 said:
I do not like how the internal sdcard is the default data storage instead of the external sdcard. I've had to factory reset a couple times now and all app data, downloads, etc.. were erased. That and if something happens to the phone the data would be lost. I remembered it was like this on one of the tabs I had so dug around a bit and found a mod to the vold.fstab file.
This file is in etc/ and also system/etc/
(not sure why it says HTC Passion???)
Code:
## Vold 2.0 fstab for HTC Passion
#
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard 37 /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount sdcard2 /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
If I read the mod correctly you would have to change the sdcard to sdcard2 and vice versa like this:
Code:
dev_mount sdcard2 /mnt/sdcard 37 /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount sdcard /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
What I'm not sure on is if it is the same for phones as it is for tablets and is this the correct way to change the sdcard mounts? I am thinking the mod needs to be done on both files and if this is the correct way it may be hit or miss if the mod sticks after a temp root reboot.
Click to expand...
Click to collapse
Just made this change on my ReZound, and its stuck in a boot loop. So I suggest doing a nandroid backup before trying it!
Let me know if anybody does this mod successfully...
lennysh said:
Just made this change on my ReZound, and its stuck in a boot loop. So I suggest doing a nandroid backup before trying it!
Let me know if anybody does this mod successfully...
Click to expand...
Click to collapse
Code:
dev_mount sdcard /mnt/sdcard 37 /devices/platform/msm_sdcc.3/mmc_host/mmc2
dev_mount sdcard2 /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
I think that is how it should be, but I haven't tested it.
con247 said:
Code:
dev_mount sdcard /mnt/sdcard 37 /devices/platform/msm_sdcc.3/mmc_host/mmc2
dev_mount sdcard2 /mnt/sdcard/ext_sd auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
I think that is how it should be, but I haven't tested it.
Click to expand...
Click to collapse
Yeah, as soon as i get this rom back restored, I'll try that method...
lennysh said:
Yeah, as soon as i get this rom back restored, I'll try that method...
Click to expand...
Click to collapse
My change should work because it swaps the hardware addresses for each mount point. The OP's swap had the names and mount points contradicting eachother.
con247 said:
My change should work because it swaps the hardware addresses for each mount point. The OP's swap had the names and mount points contradicting eachother.
Click to expand...
Click to collapse
Trying now...
---------- Post added at 02:17 PM ---------- Previous post was at 02:11 PM ----------
con247 said:
My change should work because it swaps the hardware addresses for each mount point. The OP's swap had the names and mount points contradicting eachother.
Click to expand...
Click to collapse
Nope, neither card would load the file list, and one was reporting as damaged. Reverting back...
lennysh said:
Trying now...
---------- Post added at 02:17 PM ---------- Previous post was at 02:11 PM ----------
Nope, neither card would load the file list, and one was reporting as damaged. Reverting back...
Click to expand...
Click to collapse
Wanna try one more? I have one last idea.
im interested... what would i need to do to test your idea?
im curious to a fix as well....as google music seems to save all music to the internal sd card....very annoying due to lack of space.
Code:
dev_mount sdcard2 /mnt/sdcard/ext_sd 37 /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
That should do it. If not, then it can't be done this way.
Are you using a CM7 boot disk and another OS? By default the B&N stock will mount the first partition of the SD card. This is not what we want, as the 4th partition is the one where we are going to be storing data.
In order to change the mount point you need to edit the vold.fstab file located in /system/etc
You will find a line that points to the sd card for mounting:
Code:
dev_mount sdcard /mnt/sdcard auto auto /devices/platform/usb_mass_storage/lun1/devices/platform/mmci-omap-hs.1/mmc_host/mmc0
Change the first "auto" to 4. This defines the 4th partition for mounting. As seen in the following:
Code:
dev_mount sdcard /mnt/sdcard 4 auto /devices/platform/usb_mass_storage/lun1/devices/platform/mmci-omap-hs.1/mmc_host/mmc0
Now reboot your device and you should now have access to the 4th partition in the stock android OS.
I've partitioned my sdcard with minitool and now I'm trying to edit vold.fstab to mount the second partition but I'm getting nowhere.
This is the line that mounts the first partition:
Code:
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/mtk-sd.1/mmc_host
This works unless I change auto to 1 which then tells me my sdcard is damaged.
The line for the second partition is based on this:
Code:
dev_mount sdcard /mnt/sdcard/sdcard auto /devices/platform/mtk-sd.1/mmc_host
I created a mount point on the internal storage for now. I've changing the mtk-sd.? number and auto but nothing's working.
Any ideas? Where can I find the correct device pathname? And why don't explicit partition numbers work for me?
I have a cheapo DragonTouch Y88X. I'm not looking for a custom ROM or anything - its for the kids and honestly it does everything they need, with one exception: Disney Movies Anywhere can't download videos to the external SD card.
As near as I can tell, this is an application problem - hardwired looking for /mnt/sdcard instead of using the Google API to find where the SD card is mounted, and DragonTouch was brain dead and mounted part of the internal storage to /mnt/sdcard (the actual SD card gets mounted to /mnt/extsd).
OK, so I'm not going to get Disney to change the app (and there's no setting to change where it downloads to other than "Save To/Play From SD Card"), so I started poking around how to change the mount points. I'm reasonably familiar with linux, sys admin duties and the like. But the format and options on the fstab file are a bit unfamiliar to me... All I really want to do is make the external SD card be mounted at /mnt/sdcard (and maybe mount the internal partition to something useful - maybe app cache space or something?)
I managed to get root and installed ES File Explorer, and the fstab file (/fstab.sun8i to be specific) has the following lines that I think are relevant...:
Code:
...
/devices/virtual/block/nandk auto vfat defaults wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host auto vfat defaults wait,check,noemulatedsd,voldmanagedsd=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
...
I don't know quite enough about either fstab or Android/DragonTouch's variant of it to know why both sdcard and extsd have two entries each... Or exactly how to swap them. I could try to change the voldmanaged=[name] entry on each - would that be safe?
Is what I'm trying to do crazy, or should this work?
Thanks