LegoKernel - With F2FS
NOTE This kernel version doesn't support "All-F2FS"
This is a Kernel for Android 4.4. I made this for SlimKat so i don't know if this will work with other roms.
Some users reported working also on:
Cyanogenmod (Reported by: buggatti)
Carbon (Reported by: Nosterius)
OmniROM (Reported by: SkOrPn)
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
The idea was of ss2man44. F2FS helps Nexus 7 2012 where he needs: IO Speed and slowdown after long period (months?) of use. This Filesystem is used in others phone too like Moto X where he shows good performance.
I tested this myself for some weeks without problems and i'm happy.
I started from the stock Slim kernel.
There are also others features by me:
Ported sl[aou]b from Linux 3.4
Ported timer and workqueue from Linux 3.4
Ported random from Linux 3.13-rc4
Ported rwsem from Linux 3.11
Kernel NEON Mode
Etc..Etc..
Added GPU OC (Franco way..)
Added Toggle for FSYNC
Revert CPU OC things (We don't need it and it was a bit dirty..)
Instructions:
I already said that i did this for SlimKat so my advice is to start this procedure with a working SlimKat rom or another rom that is reported to work good. (See the start of this post)
F2FS is a Filesystem so we have to Format our memory in this mode. How can we do this? We need a "special" TWRP and LegoKernel
Download LegoKernel LegoKernel-F2FS-140228
Download "special" TWRP recovery-F2FS-A.img
Copy LegoKernel on Tablet
Flash LegoKernel with your current Recovery
Flash "special" TWRP with Fastboot
I said "FORMAT" so it's obvious that you will lose all your data (even Movies..Music..all!). Backup them on PC to restore easily at the end.
Now..
Reboot in Recovery (To know that you are on "special" TWRP note that the BackKey is Red at the bottom-right)
Go to Wipe menu
Format Data (Not the simple Wipe!)
Reboot
Enjoy. (Now you may want to restore your backup)
Report back how do you feel your tablet now. I have a very positive opinion about this thing!!
Changelogs:
- 28/02/13: Add Kexec Support
Some thing you have to know:
After the switch to F2FS you can use only kernel with F2FS Support
Backup made with standard TWRP may not work with "special" TWRP and reverse.
How come back?
Flash a standard TWRP
Format Data
Flash your previous ROM/Kernel
Reboot
Github
It's great that someone else beside sgt.meow (Oxydo kernel) picked up ss2man44's idea. :good:
working great with cm 11
and Thank a lot for adding fsync off.. NOW THE NEXUS 7 FLIES
MultiROM v22a - With F2FS
I have adapted Tassadar MultiRom to work with F2FS. (All credits to him)
You need:
Its Multirom zip. Here
Kernel with F2FS Support and Kexec Support
(As now LegoKernel-F2FS-140228 is the only LegoKernel that work with MultiROM)
TWRP with F2FS Support and MultiROM. Here (For Grouper)
TWRP with F2FS Support and MultiROM. Here (For Tilapia)
If you already switched to F2FS:
Move Multirom zip and Kernel to your tablet
Flash TWRP with F2FS Support and MultiROM with Fastboot or Flashify
Reboot in Recovery
Flash Kernel
Flash MultiROM zip
Reboot
If you didn't switch to F2FS and want to do it now:
Copy Kernel to your tablet
Flash Kernel with your current Recovery
Flash TWRP with F2FS Support and MultiROM with Fastboot
Reboot in Recovery
Format Data in Wipe menu (you will lose all your files!!) Not the simple Wipe!
Reboot
Copy MultiROM zip to your tablet
Reboot in Recovery
Flash MultiROM zip
Reboot
Some things you have to know: (READ THEM)
All your ROMs must support F2FS so if you want to use "normal" ROMs you have to "share kernel"
I have tested this with SlimKat as Primary and CM11 as other ROM
I think i did some errors writing all the procedures. Hope they are right now.
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
EDIT:
CM11 2/28 is installed
Latest LegoKernel
Latest PA_Gapps
And I have not been able to flash the latest TWRP on it yet. But I do have the latest TWRP (MultiROM version) on it.
EDIT: #2, Ok I managed to use Fastboot on my laptop and I flashed the special TWRP. I went a head and re-wiped factory-reset and also re-flashed the CM11 rom and the latest LegoKernel, but after a reboot its still asking for some unknown password. Why would it need a password all of a sudden?
SkOrPn said:
Hmm, well I decided to try this as well, however after flashing the kernel I sat it down for a few minutes so I could fire up my laptop (it has Fastboot on it) and when I came back to the tablet it was turned off. I turned it on and now out of the blue its asking for a password to decrypt the storage?
I have ran CM11 for the past year on it and purchased it brand new from Google last January. However, after trying my Google email password it is still asking for a password.
Anyway, I decided to do a full wipe, installed CM11 2/28, LegoKernel and Gapps. And upon rebooting its still taking me to a screen asking for a password. Anyone know why it would spontaneously ask for a password? is there a default password I am supposed to use with this kernel by chance? lol, I am at a loss and I usually have everything under control grr haha
Click to expand...
Click to collapse
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
frantisek.nesveda said:
Did you format the /data partition with the modified recovery? This happens when Android can't access the /data partition, in this case very probably because there is a mismatch between the filesystem on /data (ext4) and the filesystem the kernel expects (f2fs). You have to first format the /data partition so it would have f2fs.
Click to expand...
Click to collapse
I cant remember now if I did or didn't format /data. I remember formatting everything except for OTG I think, lol.
Anyway, I used NRT and put the device back to stock, then I installed the modified F2FS TWRP recovery. Now I have the modified Recovery installed, and a fresh stock rom rooted with usb debug enabled. I just finished downloading the latest CM11 Rom and the LegoKernel and put it into my freshly formatted sdcard. I am sitting in TWRP at this moment but worried about flashing the kernel again. haha
Going to try again. Will report back. But first, let me make sure I have this right since I am trying to flash a ROM at the same time now.
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
I am almost certain I did this before, that's why I am asking.
SkOrPn said:
1st. Flash the CM11 ROM
2nd. Flash the LegoKernel
3rd. Format /data???
4th. Flash Gapps?
Click to expand...
Click to collapse
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
frantisek.nesveda said:
That should do it. Remember, you have to format /data, just wiping is not enough. And you'll have to flash gapps via sideload, because formatting /data also removes everything on /sdcard.
Personally, I'd format /data first, just to be sure you don't delete a part of the CM11 ROM after installing, but I think CM11 recovery zip doesn't flash anything into /data anyway, so it doesn't matter.
Click to expand...
Click to collapse
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
SkOrPn said:
Ok, that must be what I am doing wrong then. I somehow was not aware that wiping /data was not going to do it. I did the above but I wiped /data and now I am back to the password screen yet again. Not sure if I have to go all the way back to stock again or not now.
Click to expand...
Click to collapse
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
frantisek.nesveda said:
It will be enough if you now just format /data and flash gapps again. You probably never had to go back to stock anyway, I didn't and everything went well.
Click to expand...
Click to collapse
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
SkOrPn said:
Yeah everything seems OK now. Just waiting for Google to re-install all my apps. Wish I had realized there was a difference between wipe and format, and that the format data button is just staring you in the face too. lol
Thanks for your help bud. :good:
Click to expand...
Click to collapse
You're welcome. Glad I helped.
frantisek.nesveda said:
Hi,
this mod works well for me on my Nexus 7 3G running CyanogenMod 11. I've been running this just for a few hours, but the filesystem performance seems much better, my N7 no longer lags when installing apps, which it did before.
The only problem, or rather inconvenience, I had is that the recovery is not made for the N7 3G, so it won't install ROMs and stuff made for tilapia, as it expects them made for grouper. It would be cool to have a tilapia version of the recovery, or some instructions in the OP on how to use it there.
If you want to use this mod on tilapia, you have to:
Install the special recovery by legolas93 from the first post.
Format /data from within the recovery (format, not just wipe).
Install back a recovery made for tilapia and DO NOT FORMAT /DATA!
Install your ROM/gapps/hippo/etc.
Flash the modified kernel from the firts post.
Anyway, big thanks to legolas93 for doing this. Have you also considered making /system and /cache as f2fs? Do you think it would have any significant benefits?
Click to expand...
Click to collapse
Sorry. I dind't have time to do the tilapia recovery. But now i have just uploaded a TWRP Recovery with F2FS and MultiROM for Tilapia! Let me know if it is ok
I think that TWRP need some non-trivial edits from TWRP-guys to be able to use /system and /cache as f2fs. Anyway i don't think that we will gain some big benefits because..
- /cache is used very little..maybe only by recovery (i'm not 100% sure..)
- /system is used only by reading from it 99% of time so i dubt that we will gain some major benefits
Even Moto X use f2fs only for /data partition, maybe this is the best way to use it!
hows the battery life on this kernel, plus im running Kang-aroo kernel which mean ill lose all of the neat tweaks it supports, will you be adding tweaks and mods to this kernel or is this minimum version going to be how it stays moving forward.
Wtf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi Nexus 5 mediante Tapatalk
Why does it keep taking me back to the multirom menu when ever I boot it up ? You sure the kernel supports kexec-hardboot ?
Edit : Looks like flashing the kernel again after flashing the multirom fixed it.
Fransis88 said:
Wtf
Click to expand...
Click to collapse
Did you format /data with the modified TWRP? Remember, you have to FORMAT, not just wipe. And if you are really absolutely sure you did format, try flashing the kernel again.
Fransis88 said:
Wtf
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
You failed to use the format button. I did the exact same thing. All you have to do now is go back into the modified TWRP and use the "format data" button. It will work perfectly after that.
Sent from my Nexus 7 using Tapatalk
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Nexus One. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I've only tested it quickly on my Nexus One, and it seems to work.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-passion.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks for compiling and posting this update here. I hope it works better than 3.0.0.5
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
gwassef said:
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
Click to expand...
Click to collapse
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
I got it damaged 2 times, I thought it was my S2E app, but when i sent them they told me remove the 3.0.0.5 as it is known with this issue, install an older version. Since i installed the release before this one, i have no problems at all.
zyonee said:
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
zyonee said:
If you're testing it, let me know if it works.
Click to expand...
Click to collapse
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
Should work, but you'll need to try it.
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
joesatri said:
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
Click to expand...
Click to collapse
Is the recovery properly flashed? Works well on my NS
Sent from my Nexus S using Tapatalk
sorry, blonde moment :L
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Spakainz said:
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Click to expand...
Click to collapse
You'll have to ask koush or the other devs about that. I only compiled from source. I'm not that skilled at modding this kind of code...
Sent from my Nexus S using Tapatalk
This recovery works well for me. Flashed using fastboot.
I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).
Thanks for compiling and sharing this!
-D
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
This Corrupts EXT partition!
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
sir*mez said:
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
Click to expand...
Click to collapse
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
Sent from my Nexus S using Tapatalk
accuphase said:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
Click to expand...
Click to collapse
Yes, now having the same problem with sd-ext backups too.
zyonee said:
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Click to expand...
Click to collapse
Aww
But still, thanks for bringing it over to the N1.
Updated OP to version 4.0.0.0.
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
ll
minhgi said:
So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
Click to expand...
Click to collapse
where did you get 3.0.3-1 if you don't mind me asking?
And doesn't f2fs not play so well with supersu? And i heard, on the 6p, f2fs isn't any faster than ext4.
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Does it work with pure nexus?
minhgi said:
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Click to expand...
Click to collapse
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
TrainNanpaMaster said:
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
Click to expand...
Click to collapse
It's definitely there.
Sent from my Nexus 6P using Tapatalk
minhgi said:
It's definitely there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's not the official link. Might be an unofficial release.
The Frustrated Indian said:
It's not the official link. Might be an unofficial release.
Click to expand...
Click to collapse
Official TWRP does not support F2FS. You need this version made by The Flash (XDA moderator) in order to use F2FS, along with a ROM and kernel that support it. He's been supporting F2FS TWRP for some time now. That's his personal website.
So /system is useless since it's 'read-only' 99% of the time (this was Flashes findings he posted in his thread, feel free to search it yourself). He did note that he saw significant speed improvements in his testing for /data.
If you do decide to give it a try, you'll probably want to back up all of your data and decrypt your phone by formatting userdata. Older releases of Flashes F2FS TWRP do not support encryption. Even if your pattern/pin/pass is correct TWRP will say it's not and won't let you in. I haven't tried that newest release, but I did on the older ones. Maybe someone else could speak to encryption on 3.0.3-1. Aside from that, converting from F2FS will format your internal SD regardless, even if his TWRP works on encrypted devices. So back up and give it a shot.
Edit: if anyone stumbles upon this, Flashes 3.0.3-1 DOES work on encrypted devices now.
which rom are you on ?
As long as you use flash kernel, you can run any rom besides stock with f2fs. Ive used almost every rom for our phone with f2fs. There are quite a few unofficial versions of twrp that supports f2fs. The 3.0.3.. versions are really slow at restoring nandroid backups for some reason. I use multi rom twrp. I forget the version, its 3.0.2-2 i think.
Cache
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Ok, so I took the plunge into this F2FS thing. I followed this tutorial. Wiped everything including internal cache, converted to f2fs. Now, I'm trying to copy rom and gaaps from pc to phone by mounting system and data but having issues. My pc can see the phone in explorer but can't seem to copy. screenshots below.
Any help would be greatly appreciated.
EDIT: silly me, forgot to reboot the recovery lol.
TrainNanpaMaster said:
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Click to expand...
Click to collapse
Somehow my nandroid backup of lineage os wiped internal storage again (I restored after formatting /data and /cache to f2fs). Ended up doing clean install.
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
xSilas43 said:
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
Click to expand...
Click to collapse
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
yeah that's the kernel i normally use, however, i tried using r48 and r49 still get the same error, i even tried flash's kernel and I'm getting the same error, guess ill just stick with stock kernel for now. Very weird it worked fine for you but not me.
EDIT:
Somehow when i decided to try reflashing except not using SuperSU the kernel was able to flash.
Try a different twrp. The multirom twrp supports f2fs and a few more. Ive tried alot of them and never seen an error like yours.
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
i42o said:
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
Click to expand...
Click to collapse
It's fundamentally very similar to Uberstock ROM and kernel.
A lot of people on these forums think Purenexus is the best rom ever. (most likely because the developer really branches out with social media and branding).
They obviously haven't tried this or uberstock.
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.
When I try to format my Data partition to F2FS it shows:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda9 process ended with ERROR: 1
Unable to wipe Data.
Error changing file system.
And also when I format System to F2FS it succeeds but when I install a ROM (AOSiP) it won't install unless I reformat it back to ext4.
Hope anyone can help..
Thank you!
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
ThE_MarD said:
Heyyo, pretty much all ROMs will force system to default to ext4 for compatibility and stability reasons.
With that said? It is still possible to run any ROM that has f2fs support with your system as f2fs but you gotta work for it.
1. Install ROM (with gapps, etc)
2. Make a backup of system
3. Convert system to f2fs
4. In TWRP settings, enable the "instead of format use RM -rf"
5. Restore the backup of system
System should now be in f2fs... Albeit I can't remember if future ROM updates will revert to ext4 haven't tried system as f2fs in a long time...
As for data? Please flash the GalaticStryder build of TWRP found in my TWRP thread. It's a bug on TWRP for the make.f2fs not having the necessary updates for the encryption footer thus that encryption length error message.
Once you flash GS TWRP build? You should be good to go for converting data to f2fs.
Click to expand...
Click to collapse
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Jabbzz said:
Hi! I know it's been so long since I posted this but when I flashed AOSPExtended it shows an "Encryption unsuccessful " screen for me whenever I format Data partition as F2FS :/
Update: Dirty Flashed latest AOSPExtended and made a backup of it, did what you instructed and when I boot the phone it goes to fastboot mode.
Click to expand...
Click to collapse
Heyyo, hmm if that is the case I think AOSPExtended doesn't support quota for storage.. the only way to resolve this is to backup your data, copy it to USB OTG or to a PC and then going to wipe > format data > yes. After that you can copy back your data and restore the data backup.
drml said:
Hi friend, does Lineage run well with the system partition in f2fs?
I use only the data, do you think it's worth the test?
Rom is great at it, congratulations! :good::good:
Click to expand...
Click to collapse
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
ThE_MarD said:
Heyyo! To be honest I have not tested it much with f2fs. It feels smooth enough but then again ext4 still runs pretty darn good so any performance improvement is minor.
I only ever recommend converting the cache partition to f2fs as it constantly changes data and f2fs still doesn't handle file system fragmentation as well as others such as ext4 so f2fs on system and data still isn't as ideal as ext4 for long term performance retention.
Click to expand...
Click to collapse
f2fs ist superior to ext4 especially in write operations. That's way if you use f2fs you don't be affected to the slowness who comes with the time with the ext4. Otherwise ext4 exist longer and is more, lot of people assume this, stable. I use f2fs long enough to say that my last freezes with the f2fs filesystem are way back to 2014. Even then I would say that the troubles come with the custom roms than with the f2fs.
I use in my x2 the Lineage unofficial with f2fs without a single performance degradation and before that used Infrag nougat aicp with f2fs. F2fs is better but lot of people have trouble or they don't know how to convert the /data partition and before that that they must Backup the /internal Sdcard as the convert process wipe the whole /data + /internalsd
Here more Infos why f2fs is the better filesystem
https://www.google.com.cy/amp/s/www...ms-matter-interview-stan-dmitriev-tuxera/amp/
https://www.linux.org/threads/flash-friendly-file-system-f2fs.8931/