yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] panni:
I've just installed SlimKat 4.9 weekly using your method. How exactly would I install an update of SlimKat without losing my data? Via sideloading, or doesn't that affect my current installation at all when using the default TWRP flashing method? How to update the kernel I've installed?
[Nexus 5 Original Android Development] drawde40599:
Any1 wanna give me a truly honest opinion on this mod? Is there that big of a performance/speed increase , I'm not looking for ' try it yourself and c' because if wiping your whole phone wasn't involved I would ;) I'm on stock ROM i use flar2's kernel I don't use any dalvik/bionic hacks or GPU " updates" . so if someone with some time and same set up can tell me there experience with it would be much appreciated
[Nexus 5 Original Android Development] bray424:
Actually I'd say you've got the ideal set up for this mod. As far as I can tell, the biggest drawback is getting pigeonholed into always needing to use an f2fs compatible rom and kernel, but if you're not the kind of person who wants to try out every new rom that comes out, that's not going to be an issue.

As for actual performance gains, yes, it is "faster", but I'm willing to bet if you handed your phone to anyone here they wouldn't be able to tell if you had gone f2fs or not without using an app to tell them what file system you're running.
[Nexus 5 Original Android Development] snives:
For this device regardless of specific setup F2FS will almost definitely give a performance boost, however with how fast this already is most people would be unable to perceive in everyday use beyond possibly apps installing faster. Don't get me wrong, F2FS is a great development project, but lower end devices are more likely to make the benefit obvious. It's like overclocking this CPU while most games only need 1-1.2ghz dual core.

Essentially, if you have to ask or hesitate to try it for risk of having to rebuild your setup , don't worry about it for now. If you are a crackflasher or extreme min/maxer you'll enjoy it and maybe learn something. :)
[Nexus 5 Original Android Development] dennes544:
Soon updates!
[Nexus 5 Original Android Development] aosp:
Thanks for being the only truly open dev with all this f2fs converting the community truly appreciates it dude ?
[Nexus 5 Original Android Development] dennes544:
Thank you too?
[Nexus 5 Original Android Development] aosp:
Add settings to enable/disable f2fs forcing mode so we can switch on …

…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it

http://goo.gl/NTamfl

Add code to analyze the fstab to determine whether we are in f2fs mod…

…e or ext4 mode

http://goo.gl/MJXQpE
[Nexus 5 Original Android Development] snives:
F2FS support was added to MultiRom recovery for anyone interested. ;)
[Nexus 5 Original Android Development] Dodgexander:
I can't seem to use any kernel with f2fs apart from the ones in the OP. The modified franco..bricked or any kernel with f2fs support doesn't work.

I am using Multirom and have only data formatted as f2fs
[Nexus 5 Original Android Development] dennes544:
In second ROM u too should use f2fs-ed kernel
[Nexus 5 Original Android Development] Dodgexander:
I haven't even tried a second ROM yet. Only the primary. All these kernels list f2fs support yet none seem to work.

Edit* Never mind I got bricked kernel to work. No idea why the others with f2fs support aren't though.
[Nexus 5 Original Android Development] Dodgexander:
Been using this for a while with the latest PA and I thought I'd report my findings.

1. No noticeable performance gain myself. Perhaps slightly faster when installing an app but that's it.

2. Few force closes of background processes, but nothing making the phone unusable.

3. Force closes and slow-downs when running Simpsons Tapped Out. Probably because a lot of small data is loaded at once.

4. Some kernels claim f2fs support but don't work. Sometimes you can't boot, sometimes decrypted storage comes up. This can be fixed sometimes by installing modified kernel here first and then the said kernel, but sometimes that doesn't work. - I suspect this is more to do with the kernels than f2fs itself and has been explained earlier in this thread.

5. Sometimes wifi was turning itself off. Not sure why was this happening though.

It probably could be used daily if you wanted too, but for me I'll revert back to ext4. You have to remember that everything gets tested using ext4, so if you get problems in games or apps which read a lot of data you know what's to blame.

thanks for giving me the chance to test :)
[Nexus 5 Original Android Development] rachanta:
I have implemented this in racer nexus 5 kernel which you can Google and get. I used [MENTION=5499742]dennes544[/MENTION] github commits for kernel, device and fs-tools and also built f2fs ROM based on AICP. I am very happy with using my builds and have shared at the thread.
[Nexus 5 Original Android Development] rachanta:
In which folders should these cherry-picks be applied eg., is it in packages/apps/settings?
[Nexus 5 Original Android Development] dennes544:
In bootable/recovery I guess
[Nexus 5 Original Android Development] kakabobo:
any link to franco r49 kernel that support f2fs ?

Thanks in advance.

Regards
[Nexus 5 Original Android Development] Technecium:
No, my Franco + F2FS is on hold for now.
[Nexus 5 Original Android Development] rachanta:
[MENTION=2838735]aosp[/MENTION], I have added these commits to my f2fs kernel and have noticed the change in partition identification. (f2fs) is visible against data partition in TWRP/Advanced/switch to f2fs. Any thing else that should be visible?

The second commit creates some conflicts in files that get added in first commit. A time consuming resolution is required. Can the right files be added in first commit itself?
[Nexus 5 Original Android Development] aosp:
These patches are for TWRP

Add settings to enable/disable f2fs forcing mode so we can switch on the... · e71ab1e · ktoonsez/KT-TWRP · GitHub - http://goo.gl/UT1gbd
[Nexus 5 Original Android Development] rachanta:
So I guess I need to do it only if TWRP is part of the ROM I build and offer to users, right?
[Nexus 5 Original Android Development] aosp:
Yes for f2fs and if building TWRP
[Nexus 5 Original Android Development] tarroyo:
Anyone tested this? https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs
[Nexus 5 Original Android Development] androiduser44:
[MENTION=457736]tarroyo[/MENTION] i ll give it a shot tonight or tomorrow

i ll report
[Nexus 5 Original Android Development] Malnilion:
Non-CAF only for Nexus 5 is kind of a non starter for me.
[Nexus 5 Original Android Development] danarama:
This kernel, only F2FS support added?

I'm looking to replace the prebuilt zimage for KOT49H with a prebuilt F2FS kernel (no gimmicks) for compiling recovery. Would this be suitable and would you mind if I start conducting tests please?
[Nexus 5 Original Android Development] dennes544:
Yeah it's stock kernel with added f2fs driver
[Nexus 5 Original Android Development] danarama:
Great thanks, I'll run some tests and hopefully it will work for us. If I use it in the recovery, I'll credit in OP :)
[Nexus 5 Original Android Development] dennes544:
Oh thanks :)
[Nexus 5 Original Android Development] Citizen_Snips:
Very nice. So I won't have to be on CM or ROM based on it? Also in the OP it says you need Omni recovery, can this not be used with multirom then?
[Nexus 5 Original Android Development] dennes544:
Sorry, but no. You can't use multirom, because multirom use ext4 on data. Maybe in future I will create recovery with f2fs for multirom.

And yes soon you will be shouldn't have on phone CM or CM-Based rom. Aosp kernel will be available today or tomorrow
[Nexus 5 Original Android Development] djelement1:
I followed instructions exactly. Using the older kernel the phone would reboot straight to twrp. Using the new kernel it would not get past the Google splash screen, although it did appear to get further in the boot process because I had adb functionality.

Steps I took.

1. Fresh install of CM11 M3.

2. Installed recovery from OP.

3. Wiped data as instructed.

4. Rebooted to bootloader and flashed kernel (tried both from OP)

5. Rebooted phone.
[Nexus 5 Original Android Development] DREWHAMM974:
So basically if I flash this and then decide I don't like it there is no option to go back?
[Nexus 5 Original Android Development] dennes544:
Change steps.

2

3

1

4

5
[Nexus 5 Original Android Development] dennes544:
Why not? Just flash twrp without f2fs and reflash your firmware(without my kernel of course)
[Nexus 5 Original Android Development] dennes544:
Aosp kernel will be based on purity's kernel
[Nexus 5 Original Android Development] djelement1:
Same outcome. Won't get past Google splash screen. Still have adb functionality though
[Nexus 5 Original Android Development] quadomatic:
Will it be possible for other developers to patch their kernels with this? (like, Franco Kernel?)

Also, has anyone done any benchmark testing?
[Nexus 5 Original Android Development] dennes544:
Tell to my hangouts dennes544 @ gmail(dot)com
[Nexus 5 Original Android Development] dennes544:
Yes, of course other developers can patch their kernels.

I don't do any benchmarks
[Nexus 5 Original Android Development] DREWHAMM974:
This post from the first page is why I believed so. Like the third or fourth post first page.

Be very careful when using f2fs... Basically it's very very fast, BUT you are stuck with it. You can't flash other kernels, and you can flash only certain roms that support f2fs, otherwise the rom reformats the system partition to ext4. I had this on my galaxy s3, and it got me in tons of trouble when I tried to flash anything to it. I had to go back to stock twice and restore my efs partition... It's a lot of work basically.
[Nexus 5 Original Android Development] dennes544:
Rom never can reformat partition to ext4. It can only recovery!!!

P.S. in one or two hours wait AOSP kernel

P.P.S

Wrong! You can flash any rom, but you also should flash modifed kernel
[Nexus 5 Original Android Development] willybarca:
so can I use ur aosp kernel on omnirom
[Nexus 5 Original Android Development] Citizen_Snips:
Can't wait to try out AOSP version :)
[Nexus 5 Original Android Development] ed2975:
revert

I flashed it successfully using CM 03/02 nightly and its working extremely smoothly

Surely guys all you need to do to revert is fastboot erase system -w then flash normal TWRP and reinstall favourite rom
[Nexus 5 Original Android Development] dennes544:
Wrong too! You should flash normal TWRP , format data and "reinstall favourite rom"
[Nexus 5 Original Android Development] Luigi_2:
BTW, all the partitions are converted to F2FS or just the storage partition? And can you do a read/write benchmark then compare it to the ext4 benchmark?
[Nexus 5 Original Android Development] dennes544:
Only /data partition(includes internal sdcard)

Can't now do benchmark. Testing OmniROM with f2fs ;)
[Nexus 5 Original Android Development] Luigi_2:
Thank you :), spare my noob but i want to confirm it. If i want to use this file system, first I need a recovery that uses a F2FS compatible kernel to format the data, then flash the ROM, lastly a F2FS compatible kernel?
[Nexus 5 Original Android Development] danarama:
So, does anyone know how to confirm f2fs is working?

I assume you can titanium backup / restore fine however, what about nandroid? Essentially it's copying the files so FS shouldn't bee an issue should it?
[Nexus 5 Original Android Development] dennes544:
Type 'mount' command in terminal and look for f2fs in output

About nandroid, twrp (as I know) backuping to the images of partitions. So I think ext4 nandroid isn't compatible with f2fs nandroid
[Nexus 5 Original Android Development] danarama:
Ah ok. Thanks (Sorry ran out of thanks buttons today )
[Nexus 5 Original Android Development] :
If this wipes all data, how can I enable usb debugging? Will the current rom still be in tact? Can this be done through a custom recovery and no l without compute access? Sorry for my lack of know how
[Nexus 5 Original Android Development] kdh2834:
U don't have to enable USB debugging. ROM will not be intact as you wipe the whole phone. This can only be done through a custom recovery where you need your computer to flash the custom recovery and also convert ROMs and kernel to support f2fs. You would also need computer to flash rom and kernel via adb as everything inside your phone will be formatted.
[Nexus 5 Original Android Development] :
Thanks for the response.:good:

I think my learning curve is as steep as a wall.

Wouldn't I have to enable usb debugging in order to have my device recognize by the pc/adb?
[Nexus 5 Original Android Development] kdh2834:
U just need to go to recovery and select adb sideload. That's it. No USB debugging need to flash via adb.

U just need proper adb drivers :thumbup:
[Nexus 5 Original Android Development] :
Thanks for the help! I was able to do it.
[Nexus 5 Original Android Development] :
Will the latest android update have any effect on this?
[Nexus 5 Original Android Development] danarama:
If you OTA, yes. We don't know if there are any kernel changes yet either so if there are, you'll need custom kernels to be updated too
[Nexus 5 Original Android Development] :
I've been using an app (Convert to F2FS) to convert roms/kernels with good success thus far. Hopefully it continues working without any issues.

Thanks for the quick reply again. I appreciate it.
[Nexus 5 Original Android Development] danarama:
No problem. One thing to bear in mind though, if any of us could accurately tell the future, we probably would be too busy for xda ;)

Edit > I take that back, 4.4.3 tags released https://source.android.com/source/build-numbers.html
[Nexus 5 Original Android Development] :
Great! Thanks for the info
[Nexus 5 Original Android Development] :
Can confirm everything is good to go.:good:
[Nexus 5 Original Android Development] tyea:
With the latest 4.4.3 Roms with f2fs support included and he latest TWRP and a new/us device, is switching to f2fs as simple as using the recovery advance wipe feature to change file system? Just back up user data off the device,correct? I'd like to try this on Manta and Hammerhead devices.
[Nexus 5 Original Android Development] Somairotevoli:
Having issues with ROM mounting data. I've tried many of ROMs with many of kernels. Same issues every time. ROM boots up, but no radio, no SD card mounted. I've used both twrp and phil's recovery. Used format script, formatted data with f2fs, reboot to recovery afterwards, etc. Followed instructions to the tee. Have had no issues with my nexus 7 and f2fs. Just can't get this working on nexus 5:(

Sent from my Nexus 7 using Xparent Skyblue Tapatalk 2
[Nexus 5 Original Android Development] danarama:
Are you sure you haven't formatted /cache? "No Radio" is a result of bad Cache formatting usually
[Nexus 5 Original Android Development] Somairotevoli:
I've formatted cache as f2fs. Should it stay ext4?

Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
[Nexus 5 Original Android Development] danarama:
Yes, this kernel only seems to support /data
[Nexus 5 Original Android Development] Somairotevoli:
Which kernel? This happens with any f2fs kernel I tried. Don't think the ROM would even boot if kernel didn't support f2fs on system. Even with racers ROM. Again I've had no issues on my nexus 7.

Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
[Nexus 5 Original Android Development] danarama:
It's down to the kernel to add /system or /cache as supported partitions and since having them as f2fs is pretty much pointless, they won't. Just partition /data. That's all that's needed
[Nexus 5 Original Android Development] Somairotevoli:
I will try that now and report back.

But thing is I've got all three partitions formatted f2fs on my nexus 7. Working great! I'm still confused on this one. Following the instructions in twrp f2fs it states to convert all to f2fs. This is exactly how I did it on my 7.

Edit: got it working on all partitions using a f2fs-all kernel.

Work this time just formatting data. Thanks! Still confuses my brain.

Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
[Nexus 5 Original Android Development] hawktalon:
Hi, sorry to sound like a noob but I have a few things I want to confirm.

1. We can and should only get /data to f2fs?

2. To get f2fs, we need a recovery which can format to f2fs and mounts it? In my case, I've got TWRP 2.7.1.1

3. Next we need a kernel that supports f2fs. Which is to say kernels that has the f2fs driver, e.g. franco?

4. ROM has nothing to do with the ability to run f2fs?

5. After getting f2fs-ed, the only way to go back is to format back to ext4 though TWRP(i think), flash normal kernel and ROMs?

Again, sorry for being a noob if this has already been answered.
[Nexus 5 Original Android Development] danarama:
1) Depends which kernel you use, but /system and /cache are not much use

2) Yes

3) Yes

4) Correct

5) Yes

I think with TWRP there is one rversion that does F2FS and one that does EXT4 and you have to change recovery? Correct me if I am wrong
[Nexus 5 Original Android Development] hawktalon:
Thanks for clearing that up, much appreciated!

Well according to TWRP changelogs, versions after 2.7.0.0 has the ability to format to f2fs. As for ext4, I've poked around TWRP just now and found options to format to ext4 so no, I don't think we need to change recovery to format to either filesystems.

One question though, I'm now at 4.4.3 so obviously the modded kernels in the OP aren't suitable. Is there a way to flash a zip file of some sort to patch the 4.4.3 kernel to include f2fs driver? Otherwise I can't go any further until someone makes a 4.4.3 f2fs kernel.
[Nexus 5 Original Android Development] danarama:
There are some updates coming from dennes but the RAMDISK from the kernel in this thread with elementalx is certainly working fine on .3 for me
[Nexus 5 Original Android Development] adrman:
The latest TWRP 2.7.1.1. supports F2FS. I'm using it on my grouper since Philz isn't up to date on that device yet. I prefer Philz interface/implementation and plan on switching back once it's updated. On grouper, there is a huge performance difference using F2FS.
[Nexus 5 Original Android Development] hawktalon:
Can I have your build of elementalx to try? Also, is there a way to add f2fs to just about any kernel? Thanks in advance.
[Nexus 5 Original Android Development] danarama:
Using elementalx 0.43 which is in the thread here.

You still have to flaah the aosp kernel in post 1 first.

Yes I suppose there is but I've never done it. Various tutorials about.
[Nexus 5 Original Android Development] hawktalon:
[MENTION=2872010]rootSU[/MENTION] Tried your method. I always thought that those kernels that claimed to have f2fs support was lying, I was wrong. Here's the steps I took:

1. Reflashed my ROM, in this case, CarbonROM. Along with gapps.

2. Flash the AOSP moddified kernel in the first post.

3. Clear dalvik and cache.

4. Format /DATA to f2fs.

5. Reboot to system. Let it sit for a while.

6. Go back to TWRP, flash ElementalX 0.43 from [MENTION=298610]Flar[/MENTION] thread directly. No moddifications.

7. Wipe dalvik and cache again, reboot.

8. Profit.

The first boot when formatted to f2fs, everything was so laggy and slow. But after a while, it became super snappy. Then after flashing elementalX, everything was still snappy. The response was fluid and quick, app installations are blazing fast too. Overall very happy to have made the switch but I will have to observe for a while more to see if there are any problems. Will update when I do find some.
[Nexus 5 Original Android Development] Koopa777:
Wait, CarbonROM works? It broke like hell when I tried with F2FS on the 6/03 nightly. Hm.....You using the 6/10 nightly?
[Nexus 5 Original Android Development] hawktalon:
Yea, 6/1 nightly. But now after a restart I get no cellular network as if I'm on flight mode. Going into settings>about phone I see the baseband version as unknown. Selecting mobile networks gets me "Unfortunately, Settings has stopped." then FC. Tried redoing from scratch but to no avail. Even tried clean flashing. When was the last known working nightly?
[Nexus 5 Original Android Development] Koopa777:
That's what I thought, F2FS doesn't work. That's what I got with F2FS enabled, ext4 on all nightlies works fine.
[Nexus 5 Original Android Development] Somairotevoli:
Just converted latest nightly to f2fsall. Will upload and post rom and link kernel used. Since y'all already have data converted it makes it much easier to move to all f2fs.

Using Phil's recovery made things much easier for me as I was able to back up current system and return anytime without flashing ext4 recovery.

Just toggle f2fs/ext4 conversion under Mount

Format system and cache f2fs flash ROM, gapps, then kernel.

Converted ROM here: carbon nightly 6/10 0037 4.4.3 https://drive.google.com/file/d/0B9d2CAFi7MLPVFo2VjdxTldpMkE/edit?usp=sharing Kernel used here http://xdaforums.com/google-nexus-5/development/kernel-f2fs-supported-kernels-t2746951

r53 test2 F2FS-ALL

Tested myself and decided to stick with it. Was using stockish 4.4.3 also f2fsall. Carbon is much more fluid. Same kernel and even restored data.
[Nexus 5 Original Android Development] kyleco:
Let me first say thank you. I am on Carbon now and am very interested in trying this patch. I'm glad to see you managed to convert Carbon to F2FS! I want to make sure I understand correctly, this is a modified version of the 6/10 nightly and this in no way means that the official Carbon builds are F2FS compatible correct? So we will be stuck on 6/10 nightly until Carbon fixes this or you are kind enough to update another nightly, correct?

Thanks to everyone involved in this!
[Nexus 5 Original Android Development] Somairotevoli:
Yes this is a modified version done with https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs

Now for the kernel, it's still 4.4.2., but I'm sure there will be kernel updates soon.

Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
[Nexus 5 Original Android Development] kyleco:
I just wanted to come back to say that Carbon is working well after using the above mentioned app. Running with Elemental kernel on ART. Carbon delta also works, you just need to use the converter app on the zip in the Carbon delta folder, then overwrite the old zip with the converted zip.
[Nexus 5 Original Android Development] les02jen17:
I'd like to know if the latest PA RC works with F2FS...? Does anyone know if it works without any hitches? Thanks.
[Nexus 5 Original Android Development] hawktalon:
Tried the converted Carbon nightly with disasterous results. Stuck at google logo. Since I formatted /DATA to f2fs to make the swap, I now have nowhere to flash normal ROM from. My bad for not making nandroid backup beforehand and adb is not working bcs windoze doesn't recognize my phone. Gonna try mounting USB drive via otg later..
[Nexus 5 Original Android Development] Koopa777:
Try it. Backup everything if you haven't converted already. Worst case, it doesn't boot, and you can adb push a ROM or flash a known working ROM.

That Carbon is f2fs-all. You need /cache and /system f2fs as well. Windows is a hoe when it comes to Android drivers. Try Naked Drivers or Koush Universal drivers.
[Nexus 5 Original Android Development] hawktalon:
Both didn't work. Now with TWRP2.7.1.1 I thought I could mount usb-otg but it seems that I can't for some reason. Is there any other way to get files into the phone?
[Nexus 5 Original Android Development] :
[MENTION=5499742]dennes544[/MENTION] Any news on these updates?
[Nexus 5 Original Android Development] Волк:
Try using Philz touch recovery, it has F2FS support and auto-mounts USB OTG.

Edit: link http://xdaforums.com/showthread.php?t=2565174
[Nexus 5 Original Android Development] dennes544:
Sorry, now i haven't fast internet connection and cant upload them :(
[Nexus 5 Original Android Development] robertostorm:
Ok, so i have pa rc2, linaro kernel with f2fs support...Now what?