Is there any way to convert these two filesystems to ext2 or above?
I'm looking for an I/O boost in quadrant as well as looking forward to seeing how this will affect daily usage performance and speed.
Didn't find any threads on the matter.
Would appreciate if someone helped me out here
Thanks.
Well, apps2sdext hard links the data and dalvik cache folders to an ext partition on your sdcard
But if I am not mistaken the internal NAND flash is faster than my SD card.
I've observed that such a thing is possible on phones like the Samsung Galaxy Spica, where the filesystem on the /data and /system partitions can be converted to EXT to get a huge boost in speed and stability.
Sent from my Nexus One using Tapatalk
Related
I am a noob. So, please can anyone explain what is the difference between ext2, ext3 and ext4 partition??? and which partition and application is best suitable for x8 as it has low internal memory and y???
too_cool_4_all said:
I am a noob. So, please can anyone explain what is the difference between ext2, ext3 and ext4 partition??? and which partition and application is best suitable for x8 as it has low internal memory and y???
Click to expand...
Click to collapse
Well, If I´m not wrong, ext2 is the primitive file system used on linux based system. ext3 and 4 are evolution of it. I´m using ext4 on my X8 without any problem, but it depends on kernel support.
You could get more information about file system here.
I´m using link2SD, besides the rom have App2SD native, but it wasn´t installing apps on sd-ext partition.
I've been playing around with the CM-mod/S7 and can sucessfully make it boot with all ext4 partitions.
Backround information:
Parititions and formatting
Partitions are the basic unit of storage on my devices with storage (think C: D: E: if you use windows)
The standard layout of android devices:
A /cache partition
A /data partition
A /system partition
Other hidden partitions (this part isnt relevent to us)
The common filesystem formats for recent android devices are EXT 3 and 4 (4 being the newer obviously)
The S7's default partitions:
stock 3xx: (ie froyo)
/cache: ext3(?)
/data: ext3(?)
/system: ext2
stock 5xx: (ie honeycomb)
/cache: ext3
/data: ext3
/system: ext4
my ext4 mod:
/cache: ext4
/data: ext4
/system: ext4
All other devices that launched with HC installed use all ext4 partitions.
But the S7 didnt launch with HC, it launched with froyo.
Dell couldnt upgrade /data to ext4 without wiping user data.
They could upgrade system, since they wipe it on install anyway.
Cache they didnt for the outside chance a user had actual important data in it.
My proposal
What I propose is a modified version of CM9-mod with /cache and /data formatted as ext4 partitions.
I've already got a working version, the main issue is that:
I dont know what the difference is. I've ran quadrant with ext4 and again with ext4, and there's very little difference.
Since quadrant has an I/O and database benchmark (and they run on /data), at least it shows that there's only 1% change in scores.
Would anyone actually be interested in using an ext4 mod?
There are some downsides (depending on how you view it):
ext3 and ext4 nandroids arnt compatable
You will need to do a fac reset on first install (as it reformats)
You will need seperate versions of CM9-mod and CWM
This space for rent
A simple modification of the boot.img to change init.streak7.rc mount points to ext4, easy as pie.
Yea that's what I did, along with a CWM recovery.fstab mod.
But like I said I havnt really noticed any changes in quad, and it's using /data for it's tests
As soon as I get wifi up and working on cm10, going to see if there is any benefit to switching
Sent from my Nexus 7 using Tapatalk 2
I can test it tomorrow.
Sent from my PG86100 using xda app-developers app
On the stock GB ROM, Link2SD requires a FAT32 partition to move the App and DalvikCache to the SD.
EDIT: Actually requires FAT32 OR EXT2 for stock...
Titanium backup requires an ext2/3/4 partition to use the Data2SD feature.
Is it possible to do both of these on a stock rom? Or use some other method to get the App, DalvikCache and app data to the SD without flashing another ROM?
I will be doing this for 3 of my family's phones and would much prefer to not have to flash ROMS and them have to put in extra effort afterwards.
I promise I've searched so apologies if this has been answered elsewhere, the closest I could find was http://forum.xda-developers.com/showthread.php?t=1605006 which didn't answer the question...
Thanks in advance!
Tim
I have created two partitions, one FAT32 and one EXT2 using MiniTool Partition Wizard
Link2SD is correctly setup and working.
Titanium Backup has this to say:
The supported mount points for the ext2/3/4 partition are:
/system/sd/ (“classic” sd-ext)
/sd-ext/ (“Cyanogen” sd-ext)
/data/sd/ (“MIUI” sd-ext)
However none of these mount points are present (it appears to mount under /data/sdext2/) so I'm unable to use the Data2SD functionality as yet.
So the question now becomes, can I create multiple mount points for a single EXT2 partition on a Stock ROM (ideally easily!).
Install a custom kernel with init.d support.
Cf-root is the most common since it's based on stock, and preserves baseband.
After that, there's many choices:
-link2sd as you've beeb using
-cronmod or amarullz scripts (int2ext+) which mount sd partition as extention to internal memory (every app on internal gets installed to the partition).
-s2e has the option to also move data to the partition.
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.
dxppxd said:
Install a custom kernel with init.d support.
...
...
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.
Click to expand...
Click to collapse
Thanks for the advice.
I have a class 10 card that I was hoping would help mitigate the problem, am I just being naive?
I was hoping I'd be able to avoid a custom Kernel (haven't researched them enough yet)
I will try and find an S5830 Stock + init.d kernel tomorrow and see how that goes, I'm still planning on Titanium Backup to do the Data2SD.
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?
KingTimus said:
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?
Click to expand...
Click to collapse
I really can't say about titanium backups' data2sd function since i've never used it before.
The init.d script (i found cronmods' int2ext to be the most convenient) mounts the sd partition as part of /data. When making backups of apps+data titanium backup had 0 problems finding and backing up all apps. The problem might arise if the data2sd function tries to move /data (in which the partition is already mounted) to the partition.
Someone in the forum might know more details. You can always make a nandroid backup and see what happens. Good luk.
I'm looking for the best way to move /cache partition which is at 210mb to micro sd card. I'm having freezes when apps access that cache partition. While some apps are working fine, i could gain a bit of stability if i pull this out.
Looked on google for link2sd, and formating the sd card to a specific file type. So there could be a work around for cache, too.
It'd help me a lot to find a solution for this problem.
someone try this:https://play.google.com/store/apps/details?id=com.spazedog.mounts2sd
That's not it, that moves the APP (all of it) to a 2nd EXT4 partition on the SDcard and creates a symlink.
To move the /cache partition, would require a little tweaking. You're still needing the 2nd partition, /cache cannot be on FAT32.
neier24 said:
I'm looking for the best way to move /cache partition which is at 210mb to micro sd card. I'm having freezes when apps access that cache partition. While some apps are working fine, i could gain a bit of stability if i pull this out.
Looked on google for link2sd, and formating the sd card to a specific file type. So there could be a work around for cache, too.
It'd help me a lot to find a solution for this problem.
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda app-developers app
I got sick of trying to fix. I'll see what i can do in a couple of months when i get back to this... after a "short" break.
I finally decided to take the risk of converting to the F2FS file system. I'm a little confused on just how far I should go with it. The readily available guides only mention changing the cache and data partitions. I have made this jump, and I absolutely notice a difference. My question is that there is also an option to format the system partition to F2FS, but I can't find anything concrete on its benefits. Honestly I can't find much of anything about it. Does anyone have any experience with F2FS system partition conversion?
You don't write anything to system partition as it's pure read-only. F2FS would make zero difference. It's just a hassle making ROMs work with /system under F2FS.
Lawstorant said:
You don't write anything to system partition as it's pure read-only. F2FS would make zero difference. It's just a hassle making ROMs work with /system under F2FS.
Click to expand...
Click to collapse
Thanks, that makes complete sense to me. So I'm done then? Just go with what I have?
donkeypunch1257 said:
Thanks, that makes complete sense to me. So I'm done then? Just go with what I have?
Click to expand...
Click to collapse
Don't format the system partition to F2FS. There is zero benefit from this since, as stated above, it is mounted as R/O at boot time, diminishing any positive effect F2FS may have the phone's performance (slower reads, faster writes, theoretically.) Anyways, most ROMs format /system to ext4 when being flashed, so there's that too. Just go with what you have, which is ext4.