Hey!
I want to sync the DCIM folder with my Dropbox/Photos folder.
Problem: FAT doesn't support symlinks.
Is it possible to set up one ext2/ext4 partition for the Data & APP2SD and one fat32 for media exchange?
As there's no /etc/fstab in Android the filesystems have to be listed somewhere else. Does anyone know where? Or is there a fixed pattern which partitions are used?
Is there a solution for moving the journalling of ext4 to the internal memory? Afaik this would increase speed.
I'm curious about what the Xoom is using to make apps think there is an "external" storage on the device. It is my understanding that with Honeycomb, there is no longer a partition on the internal storage formatted as FAT that is mounted as /mnt/sdcard. Rather the majority of the internal storage is now part of the /data partition. But then, what is mounted at /mnt/sdcard? Surely not the entire data partition? Since doing that would expose app's private data which other apps aren't supposed to access. So I'm guessing that it's probably a subdirectory on the /data partition that is mounted at /mnt/sdcard so that apps that hardcode that directory to use for external storage can still work. Is this correct? If so, what is the exact directory that is mounted there? Thanks.
Chirality said:
I'm curious about what the Xoom is using to make apps think there is an "external" storage on the device. It is my understanding that with Honeycomb, there is no longer a partition on the internal storage formatted as FAT that is mounted as /mnt/sdcard. Rather the majority of the internal storage is now part of the /data partition. But then, what is mounted at /mnt/sdcard? Surely not the entire data partition? Since doing that would expose app's private data which other apps aren't supposed to access. So I'm guessing that it's probably a subdirectory on the /data partition that is mounted at /mnt/sdcard so that apps that hardcode that directory to use for external storage can still work. Is this correct? If so, what is the exact directory that is mounted there? Thanks.
Click to expand...
Click to collapse
Consider /mnt/sdcard to be just a name for a portion/partition of the Xoom's internal flash memory that does not get touched when you flash a new kernel or ROM or get an OTA update. This has certain implied meanings to where android looks for certain files or multimedia. The external micro-sd card gets mounted at /mnt/external1 which on my Xoom also has a link to /MicroSD. I hope this helps clear up some of the confusion.
davidsos said:
Consider /mnt/sdcard to be just a name for a portion/partition of the Xoom's internal flash memory that does not get touched when you flash a new kernel or ROM or get an OTA update. This has certain implied meanings to where android looks for certain files or multimedia. The external micro-sd card gets mounted at /mnt/external1 which on my Xoom also has a link to /MicroSD. I hope this helps clear up some of the confusion.
Click to expand...
Click to collapse
Yes, I assume it is a part of the /data partition, which is unaffected when you flash a new ROM, because that is on the /system partition. The problem is that I don't think it's the entire /data partition, since that partition contain private app data that other apps should not be allowed to read. I'm just wondering which subset of the /data partition is mounted at that location.
If im not mistaken the /mnt partition is written in Fat32 so that when you connect your phone to a windows pc the pc will recognize it. so the sdcard in /mnt is what you see when you plug your xoom into the pc, and the /sdcard partition automatically writes changes you make to its files to the /mnt/sdcard version to reflect the changes that were made when you plug into windows pc. the true sdcard, the one you manually put into the top of the xoom is /mnt/external1, or /microsd in the main filesystem "/" Atleast thats what I believe, Im no dev
Use "mount" command in Terminal Emulator or ADB shell
All mounted devices and mountpoints will be listed there.
_TB_TB_ said:
Use "mount" command in Terminal Emulator or ADB shell
All mounted devices and mountpoints will be listed there.
Click to expand...
Click to collapse
That's what I'm hoping somebody would do, I don't own this device.
/data/media is underlying directory for the Android sdcard fuse file system that is mounted at /mnt/sdcard/
solarnz said:
/data/media is underlying directory for the Android sdcard fuse file system that is mounted at /mnt/sdcard/
Click to expand...
Click to collapse
Thanks! That's in line with what I was thinking.
very usefull this to me
so I guess it means that if my /mnt/sdcart space has become way too small in proportion to the available space on the card after a flash recovery so I can fix this by enlarging my /data partition, which thus is not really a partition, but merely an imbedded file system -an image file. Which can be enlargend with dd.
Thank for this discussion
Mikkel
Since I'm using a custom ROM that make the External (bigger: 14GB) SD mount as the default /sdcard, and internal (smaller) as /sdcard2 or something I don't really need it and would much rather like to mount it entirely as /data
.. something similar to this script : http://forum.xda-developers.com/showthread.php?t=1716124 except that it "Mounts **/sd-ext** to /data" but I want to mount /mnt/sdcard2 to /data
. How do I do that?
Problems: I've found that Android would neither let that internal partition be ext3 (it switches it back to FAT even if I somehow manage to format it as ext3). Nor would it mount /data to a FAT partition. What can/should I do?
iBrickYouNot said:
Since I'm using a custom ROM that make the External (bigger: 14GB) SD mount as the default /sdcard, and internal (smaller) as /sdcard2 or something I don't really need it and would much rather like to mount it entirely as /data
.. something similar to this script : http://forum.xda-developers.com/showthread.php?t=1716124 except that it "Mounts **/sd-ext** to /data" but I want to mount /mnt/sdcard2 to /data
. How do I do that?
Problems: I've found that Android would neither let that internal partition be ext3 (it switches it back to FAT even if I somehow manage to format it as ext3). Nor would it mount /data to a FAT partition. What can/should I do?
Click to expand...
Click to collapse
you can't
How to open / modify "vold" and "sdcard" file, Android KitKat 4.4.4
I have a Zopo zp999 and zp920.
On both devices the external sdcard is sdcard0 and the internal card is sdcard1, so all of the apps are installed on the slow external sdcard and the external card is recognized as the internal card..
I looked after for a way to swap these cards and on most smartphones there is a vold.fstab where i could change this - but not on my zopo phones.
on an earlier FW of the zp999 the cards have been in the (for me) correct order (internal sdcard0, external sdcard1) and when i took the two files from /system/bin "vold" and "sdcard" of the old FW to the new one, the order of the sdcards was correct.
for the zp920 is workaround is not possible, now i am searching for a way to open and modify these two files.
can anyone help me with this - please?
i tried to change the fstab / fstab.nand / fstab.fat.nand from the boot.img from:
Code:
...
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
...
to
Code:
...
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard1:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard0:auto
...
with the "Android Kitchen" and cygwin
but after repacking the boot.img and flashing it back to the phone, the phone is stock in a bootloop.
maybe the unpacking / packing is wrong with my boot.img and Android Kitchen / cygwin (there are no errors)
i tried with both, the original boot.img and a boot.img from a marsapa custom rom.
i have same problem like yours..hope someone can help..
i want the internal storage be the sdcard0..
Any progress on this? From what I figured out so far it seems that MSDC0 is the internal sd card. So from the fstab you would expect the internal sd card to always be mounted to SDCARD0. But once you insert the external sd card the internal sd card becomes SDCARD1 and the external sd card becomes SDCARD0. This cannot be the intended behaviour as it breaks file paths for apps
So I bought a new Samsung sdcard. The sdcard automatically formats into f2fs if I try to use it as adoptable(Internal) storage. I don't have any problem with f2fs bit seems like my device or ROM doesn't support it (Random reboots and bootloops). I used the sdcard as portable as fat and ext4 and there Werner any issue. I previously had another sdcard which would convert into ext4 while using as internal and it didn't have any problems.
So can I change the sdcard's default file system so that it would convert into ext4 instead of f2fs if used as internal ? Any help is appreciated.