Related
Hi, just reporting my findings on F2FS,
To use system partition in F2FS you need to convert rom, adjust scripts, etc.. so i was trying to find if it worth the hassle
Let's take in consideration two things:
1. F2FS have consistently better write speeds than EXT4 , but the same cant be said for read speeds.
2. EXT4 can become laggy when not trimmed, F2FS is always trimmed,
F2FS makes sense for /data and /cache partition but not for /system... /system partition have almost no changes so its 99% trimmed and usually read only
i used this app https://play.google.com/store/apps/details?id=vog.com.aiv to benchmark bootup time in seconds
CM11 2305 nightly, /data and /cache in F2FS , only change is /system partition format (less is better)
ext4
32,06
28,55
28,01
28,13
27,08
27,77
f2fs
27,44
28,65
40,91
36,95
28,29
27,46
28,41
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
DZeros said:
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
Click to expand...
Click to collapse
F2fs is good, I'm using it, but Just for partitions with lots of writing operations only, simple as that.
And the big plus is that i don't need to worry with compatible roms and updates, just flash any rom updates, without any conversion, and flash kernel after..
Enviado de meu Nexus 4 usando Tapatalk
opssemnik said:
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Click to expand...
Click to collapse
Read times for /system are not faster in f2fs, but it's up to you
Enviado de meu Nexus 4 usando Tapatalk
Thank you for pin pointing this out. A lot of people still believe F2FS will make their phones fly for some reason. I've tested a phone with F2FS next to another running EXT4 and there was no real world performance boost or anything of that sort. F2FS got higher benchmark scores. That's it. Its no a placebo effect but in real world performance it makes no difference.
Sent from my Nexus 4 using XDA Premium 4 mobile app
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
This would explain why there is now a longer than normal delay every single time when I hit the home button that is not noticeable when system is ext4. When on ext4 system this delay was hardly noticeable and with f2fs it seems like there is lag but as soon as it does go home I can then open the app drawer immediately with no lag whatsoever. If it was normally slow or laggy to go home then it took an equal amount of time to open app drawer as the lag existed everywhere, here it is only on the home button.
okanb3 said:
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
Click to expand...
Click to collapse
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
diogo.sena said:
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
Click to expand...
Click to collapse
There must be another way, with this method,the rom doesnt boot.
ashishv said:
There must be another way, with this method,the rom doesnt boot.
Click to expand...
Click to collapse
What rom and what kernel exactly did you use?
diogo.sena said:
What rom and what kernel exactly did you use?
Click to expand...
Click to collapse
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
ashishv said:
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
Click to expand...
Click to collapse
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
diogo.sena said:
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
Click to expand...
Click to collapse
Twrp with ext4/f2fs format option for mako
http://d-h.st/g59
Multirom app, which will install the recovery without fastboot.
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Does anyone have encountered this issue?? It's really damn annoying... Thanks for any help
I did have it and it is very annoying, I installed TWRP Blue Spark and it solved the issue. I will look for it and if I find it I will share it with you.
What version of TWRP are you using? 3.0.3-1, 3.0.4 and 3.0.4-1 have all been working well so far.
Anova's Origin said:
What version of TWRP are you using? 3.0.3-1, 3.0.4 and 3.0.4-1 have all been working well so far.
Click to expand...
Click to collapse
This happens if yu are f2fs formatted and swipe in allow for modifications when booting in §TWRP. If you don't swipe, you can still flash roms. Not sure what's changing anyway...I formatted ext4 and have no issues right now.
iam using f2fs with latest twrp (3.0.4.x) and no such issues.
but i was losing apps randomly after booting into recovery, on older TWRP versions.
Installed TWRP 3.0.4 and everything seems back to normal. Thanks for ur help guys.
Now my next problem is 4g reception in France..
Cheers thanks a lot
PS: how do I know if I'm using f2fs or ext4?
I believe there was an option somewhere in TWRP to view all your partitions and their file formats. By default, only the data partition is formatted in f2fs, everything else should be ext4 (and maybe fat?)
Edit: If you select Wipe in TWRP, then advanced wipe, and select the Data partition, you can click partition options to see what the file format is (don't swipe right if you don't want to wipe it). Aside from data, every other partition should be ext4 by default.
There's also apps like disk info that can tell you the file system used as well.
piffa_ said:
Installed TWRP 3.0.4 and everything seems back to normal. Thanks for ur help guys.
Now my next problem is 4g reception in France..
Cheers thanks a lot
PS: how do I know if I'm using f2fs or ext4?
Click to expand...
Click to collapse
there is a app on playstore disk info
and there is new twrp avaliable 3.0.4.1
I hope I'm on the right channel to ask this..
I successfully booted MIUI 8 stable with F2FS partition (data and cache) but root fails to install..I've heard it's much faster (or better) than ext4..in LOS, with F2FS, you can easily gain root using su add-in..been searching answers for almost a week now..any inputs would be appreciated.. TIA!
viking_kong16 said:
I hope I'm on the right channel to ask this..
I successfully booted MIUI 8 stable with F2FS partition (data and cache) but root fails to install..I've heard it's much faster (or better) than ext4..in LOS, with F2FS, you can easily gain root using su add-in..been searching answers for almost a week now..any inputs would be appreciated.. TIA!
Click to expand...
Click to collapse
and how did you do it i mean miui f2fs partition
gowtham300 said:
and how did you do it i mean miui f2fs partition
Click to expand...
Click to collapse
I format both data and cache through twrp then flash global stableb rom from xiaomi's download page..that's it..
viking_kong16 said:
I format both data and cache through twrp then flash global stableb rom from xiaomi's download page..that's it..
Click to expand...
Click to collapse
thats impossible miui doesnt support f2fs
viking_kong16 said:
I hope I'm on the right channel to ask this..
I successfully booted MIUI 8 stable with F2FS partition (data and cache) but root fails to install..I've heard it's much faster (or better) than ext4..in LOS, with F2FS, you can easily gain root using su add-in..been searching answers for almost a week now..any inputs would be appreciated.. TIA!
Click to expand...
Click to collapse
Check whether your partitions have been reformatted to ex4. Regardless, try PHH superuser, it worked great for me.
viking_kong16 said:
I hope I'm on the right channel to ask this..
I successfully booted MIUI 8 stable with F2FS partition (data and cache) but root fails to install..I've heard it's much faster (or better) than ext4..in LOS, with F2FS, you can easily gain root using su add-in..been searching answers for almost a week now..any inputs would be appreciated.. TIA!
Click to expand...
Click to collapse
Are you using a custom kernel, or is f2fs supported in the stock kernel?
SuperSu is not working because of chainfire is using mount -t ext4 to mount data and cache. With a f2fs formatted partition that is failing for sure.
Gesendet von meinem Xiaomi Mi MIX
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.
Hi,
I made this guideline for those who want to convert filesystem from EXT3 / EXT4 to F2FS on lavendar, for amazing speed & performance.
I already had MIUI EU beta working on my phone.
Note: Internal data storage will be wiped. Make sure to have a backup.
Steps:
1. Install Orange Fox Recovery (latest one)
2. Reboot to recovery
3. Go to Manage Partition
4. Select "Cache" and click orange tick button, then choose F2FS as the file
system and proceed.
5. Again, select "Data" and click orange tick button, then choose F2FS as the file
system and proceed.
6. Reboot to Recovery again.
7. Install a custom kernel which support F2FS (i.e Evira)
8. Install Universal F2FS support patch file. (otherwise causing boot loop)
9. Reboot
Enjoy the speed.>>>>>>>>>>>
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Click to expand...
Click to collapse
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
jalzate94 said:
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
Click to expand...
Click to collapse
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Plast0000 said:
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Click to expand...
Click to collapse
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Plast0000 said:
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Click to expand...
Click to collapse
... Well, my info is wrong then... In this case it would be useful
Sent from my Note 5 / 5 Plus using XDA Labs
White_Lion said:
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Click to expand...
Click to collapse
No, the data partition will be converted back to ext4 everytime you do "format data".
Not formatting your data could keep the f2fs status, but it's risky to not formatting data when changing ROM in lavender due to it's strict encryption issue.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
Click to expand...
Click to collapse
Miui.eu ROMs doesn't fully support F2FS. The rom does, but the kernel doesn't.
You need to make sure both the ROM and kernel has F2FS support.
if one of them don't, you'll get bootloop.
Plast0000 said:
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Click to expand...
Click to collapse
I've been on F2FS since.. April I think, and I've installed and tried so many roms without any problem.
here's what I normally do and it works all the time:
- Make sure data & cache are ext4
- format data
- reboot recovery,
- wipe cache, dalvik, system, data, internal,
- flash firmware
- flash ROM
- flash gapps (optional)
- flash magisk
- flash kernel that has f2fs support (optional, if the rom's kernel doesn't support F2FS)
- reboot system
————————————————————————
it's necessary to install the rom in EXT4 because automatic encryption doesn't work in f2fs partition (I think... based on my experience). granted, you can do the encryption manually from settings, but it's require to have 80%++ battery and the more stuff you have in your internal, the longer it'd take to manually encrypt the device. automatic encryption is just easier to do. You can leave your internal decrypted as well, but you won't be able to use your fingerprint or any screen lock methods. That's just how redmi 7 family works.
————————————————————————
- once you get into system, reboot to recovery once again
- convert cache & data to f2fs
- flash magisk
- flash universal f2fs patch
- reboot
now your /data and /cache are in f2fs.
If you're already on a rom and kernel that support f2fs, you can just do the later half of this tutorial without the need to reinstall rom and everything, but you'd lose all your data. good luck!
What's the benefit of changing cache into F2FS?
begging
Seeking flash tutorial videos
Thanks
thx for guide.
Which custom rom that support f2fs?