yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Technecium:
Updated Bonnie++ Results

A little explanation first...

I completed some tests a few hours ago, the results are the ones you see in the previous post. Those are ext4 vs f2fs.

However, a little while ago, I checked to see if there were any new commits by Jaegeuk Kim, and there was, a very nice one in fact.

So attached to this post are the results of the previous f2fs test vs f2fs with the latest commit. :D So from top to bottom, you are looking at 10 iterations of f2fs vs 10 iterations of f2fs with flush_merge.

NOTE TO DEVs.... The newest commit requires flush_merge to be added to the mount options of the fstab
[Nexus 5 Original Android Development] dennes544:
Kernels and recovery updated. Added Purity kernel

Changelog:

Added flush merge

Added kexec-hardboot patch

Soon wait multirom :victory::victory:
[Nexus 5 Original Android Development] Batfink33:
So will the new recovery need a full wipe and format again?
[Nexus 5 Original Android Development] dennes544:
recovery maybe. format no.
[Nexus 5 Original Android Development] Batfink33:
OK, thanks.
[Nexus 5 Original Android Development] pikachukaki:
after flashing this recovery....every time i flash a new rom and i wipe /data, /cache, /dalvik and /system../data will always wiped as f2fs??
[Nexus 5 Original Android Development] Batfink33:
You have flash the recovery in this thread then do a full format of the phone in recovery. Then everytime you flash it'll be f2fs.
[Nexus 5 Original Android Development] pikachukaki:
Yeah..i did that thanks...but i couldn't boot slim latest with faux latest...i boot with franco's from OT so its faux kernel fault...
[Nexus 5 Original Android Development] hicks12:
Thanks for your hard work , appreciate being given the opportunity to try a new filesystem.

Tried Purity with UBER kernel (based off a post here) unfortunately it seems both UBER kernels arent working with f2fs and give the unlock storage message, I have gone back to trying your purity kernel to try things out, was looking forward to the UBER one though lol! Is there anything special you have modified on the purity one?

Again thanks for the work, hopefully I can try other kernels later!
[Nexus 5 Original Android Development] Batfink33:
I'm using Uber with f2fs at the moment. You have to flash the AOSP f2fs kernel from the first post here then flash Uber.
[Nexus 5 Original Android Development] hicks12:
hmm strange I tried that first and it didnt work for me and then the dennes544 updated the OP with a new purity kernel which worked for me.

Which version of the UBER kernel are you using and what compiler? sabermod or linerao?

Cheers
[Nexus 5 Original Android Development] Batfink33:
Sorry, just tried with the new recovery image and uber seems to be causing the password problems now(it didn't previously) I guess the new commits need to be added to ubers kernel for it to work.
[Nexus 5 Original Android Development] phishfi:
So it's not possible to format the /system to f2fs? Just data?
[Nexus 5 Original Android Development] xtrymind:
It's possible, i'm using f2fs on /system /cache and /data
[Nexus 5 Original Android Development] phishfi:
How?
[Nexus 5 Original Android Development] xtrymind:
Edit fstab on kernel ramdisk and on modified twrp

Format /system /cache using adb shell on recovery

Edit updater script in rom to mount f2fs
[Nexus 5 Original Android Development] phishfi:
Do you have any more detailed instructions than that? If not, I'll try tomorrow
[Nexus 5 Original Android Development] xtrymind:
Uh well that's a hint, try so search on xda ;)
[Nexus 5 Original Android Development] dennes544:
[MENTION=5518280]Enddo[/MENTION], skulldreamz is just trying to help people safely and intelligently use these wonderful mods
[Nexus 5 Original Android Development] skulldreamz:
Thank you for maturely rectifying the previous post. Thanks again for continuing to pound away at your wonderful port! :)
[Nexus 5 Original Android Development] daftlush:
FYI... I can t get this new CM kernel to boot with the 4/9 CM nightly.
[Nexus 5 Original Android Development] phishfi:
See, I never understand these completely unproductive comments. I've search for f2fs and f2fs all partitions and nothing of value came up. You comment saying to simply search on XDA, yet you have already figured out how, which leads me to believe you would be a good resource, not to mention the fact that there are surely plenty of others who want to know about this too.

So you take the time to leave a useless nasty comment instead of providing me with a useful link or giving me quick instructions...

For those wanting to switch their whole fs to f2fs, I'll keep looking and I'll post here if I figure it out!
[Nexus 5 Original Android Development] lbroksle:
Hey go look in the 2012, Nexus 7 forum. I have all three partitions formatted to f2fs. He should be able to explain to you how to do it on the n5 too.
[Nexus 5 Original Android Development] phishfi:
Thank you very much!!! Hopefully I can do all of this from my phone (I'll have time at work but I can't plug my phone into work computers). I appreciate the thorough response! Where did you find this info? I searched all over...
[Nexus 5 Original Android Development] Enddo:
someone needs a spoon
[Nexus 5 Original Android Development] mchj:
+1

new CM Kernel is broken:

6.1.Flash kernel(FOR CM) http://d-h.st/Bqa
[Nexus 5 Original Android Development] GSLEON3:
SmartA$$! :p

That was funny as hell though!
[Nexus 5 Original Android Development] dennes544:
Thx for test. I'll fix it so soon as possible

Everything works. I just tested it, and it works
[Nexus 5 Original Android Development] tarroyo:
[MENTION=636360]koe1974[/MENTION] will you be updating Franco kernel to r44?
[Nexus 5 Original Android Development] Technecium:
There's been a lot going on with the kernel recently but I'll build the most recent this weekend.
[Nexus 5 Original Android Development] Sc4ryB3ar:
OK, I've been curious for a while now, and following this thread for over a month, reading, rereading, so on.... I have moved to OmniRom, and Faux Kernel, which both support f2fs. I think I'm ready to format and move forward.

I have 2 questions that I have not found the answer to yet.

Once the data partition is moved over to this format, are we able to Odin/Heimdall back to full stock?

Is it possible to fully complete this process, just on the phone? Flash new recovery from recovery, clean flash a new Rom, gapps, kernel, etc.? It seems like it is, since all you are formatting is the data partition, which doesn't touch SD storage, but I want to make sure. Also does it have to be done in fastboot, or is there a flashable available? Maybe one that flashes the recovery image and formats data partition in the same flashable. I know there are update script gurus out there that can combine all this stuff, I'm just not one of them....
[Nexus 5 Original Android Development] dennes544:
1) Yes, of course u can back to ctock

2) it format data including SD storage
[Nexus 5 Original Android Development] killer23d:
You probably come from Samsung device when you say Odin. Nexus uses Factbook and all you need to return to stock is download the recovery image from Google, extract it, run the batch file and it will re partition the phone and restore everything to factory.

There is no SD card in Nexus, it is called media in the data partition. You must back up all storage content before format to F2FS

I tried to do Omni and Faux combo and it will stuck at boot screen. I think there is something in Faux or Omni causing this so don't try it just yet.

I would love to wait for a dev to make a F2FS all guide so that we can benefit completely.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Technecium:
Some have been asking about f2fs for system, data and cache partitions. I was curious, so I did it.

EDIT: And now after running it for about a day I have to say, I don't see any real advantage for this device. You may have a better experience than I did.

I don't want to have to explain how this works and I'm not going to but I will put a few notes that you really should read.

If you're lost after reading this post, then it's probably a road you shouldn't travel.

The tar.gz file contains a recovery image based on twrp 2.7. It should only be used while doing f2fs-all.

The tar.gz file contains a boot image based on franco kernel r35. It should only be used while doing f2fs-all.

Format data via recovery (Wipe - Format Data)

You must also format system and cache to f2fs

+++++Download koe1974-n5-f2fs-all.tar.gz+++++

Unavoidable Questions:

How do I format cache and system?

$ mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/system
$ mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/cache

Can you build a kernel for the latest franco release?

No, I use kernel source code based on r35 for a very specific reason.

Is it better than [_____]?

It's better than bad [____] but not nearly as good as fantastic [_____].

Can you make a flashable zip?

Nope, but with time and energy you or anyone else can.

Will I lose all my data?

Yes.

Does it work with [____] rom?

Try it, and let others know.
[Nexus 5 Original Android Development] Malnilion:
[MENTION=636360]koe1974[/MENTION],

Assuming we're already using f2fs on /data, switching to your recovery and kernel would only require reformatting /system and /cache, right?
[Nexus 5 Original Android Development] Technecium:
Correct. Just flash the recovery, format cache and system and flash system and kernel.
[Nexus 5 Original Android Development] firegate22:
Can anyone explain step by step how to get ElementalX (or other kernels with F2FS support running)? I'm using F2FS with the AOSP Kernel at the moment. But every other kernel (except koe1974's franco img) is not working (showing decrypt message). Thank you in advance!
[Nexus 5 Original Android Development] notthesun:
i'm using Furnace kernel and i'm very happy with it...if you want to try just flash the boot.img https://drive.google.com/file/d/0B7Y0fZvN7UuvRjNDbnRWYVd5R00/edit?usp=sharing and then flash in recovery the kernel http://xdaforums.com/google-nexus-5/orig-development/kernel-furnace-1-0-0-lg-nexus-5-t2679826
[Nexus 5 Original Android Development] firegate22:
Thanks for your answer but I want ElementalX, I just tried others. So far I understand your post I need a specific boot.img for the specific kernel (then I go to the kernel thread and ask for it)?
[Nexus 5 Original Android Development] Technecium:
Yes. You will have to request f2fs be added.
[Nexus 5 Original Android Development] Pretoriano80:
AFAIK elemental-x already have f2fs support, but first you need to install an f2fs kernel from this OP. Then boot your rom at least one time, after that reboot to recovery and flash elemental-x (aosp or cm version, depends on your rom), reboot and your rom should work just fine.

Before you ask, you need to do this procedure because elemental-x doesn't have f2fs enabled in ramdisk so it will modify your current one on the fly.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] firegate22:
This is definitely not working. I flashed the asop kernel from op again, started the phone, flash elementalx, reboot -> decrypt message. Was the procedure correct?
[Nexus 5 Original Android Development] killer23d:
If you see decrypt message, it means the data partitions cannot be mounted. I think there was a few posts about this, search this thread for "password"
[Nexus 5 Original Android Development] Technecium:
adb reboot recovery

adb shell

mount

what do you get for output?
[Nexus 5 Original Android Development] firegate22:
Here you go! I mean if those two "features" are not supported together it's okay, so I have to sort out which is more important for me.
[Nexus 5 Original Android Development] Technecium:
Assuming you are only trying to use f2fs on data, then your partitions are fine.

I would double check you have flashed an appropriate kernel. Try the stock kernel from the OP.
[Nexus 5 Original Android Development] firegate22:
[MENTION=636360]koe1974[/MENTION]: the stock kernel as well as your franco "img" kernel is working. I'm only asking because ElementalX as well as Linaro as another example are showing f2fs support in their changelog but every "zip" flashable kernel is at the moment not working for me. A couple of pages earlier in this thread a user is mentioning that some recent recovery changes made custom kernels incompatible, is that possible?
[Nexus 5 Original Android Development] dakore:
What would happen if you use older recovery+f2fs kernel from OP and try ElementalX? I assume at some point Elemental and f2fs things from OP were compatible... This is just my opinion, haven't tried f2fs (yet).
[Nexus 5 Original Android Development] Nickamina:
Anyone tried this with bricked?

I flash slimkat, the aosp kernel - up until that point it's all fine, I can boot normally. If I then try to flash bricked kernel I get the password block when I reboot. I'm using the latest stable bricked. Is there a special version I need or something? Can somebody tell me the steps they went through to get it to work? Not sure what the issue is.

Cheers
[Nexus 5 Original Android Development] firegate22:
We both have the same issue. In my case it is not related to any kernel at all, every custom kernel (tested linaro, ElementalX, bricked) is not working at the moment by flashing them via recovery. The custom version of franco's kernel from koe (img flash) is working.

[MENTION=2692781]dakore[/MENTION]

As far as I know some time ago all this was working but somehow it is not working anymore ;) A appreciate all the work here, but the usage of my preferred kernel is more important for me than F2FS and I don't have the coder / linux / android knowledge to fix sth like this by myself.
[Nexus 5 Original Android Development] Nickamina:
I've been recommended this by someone who managed to get it to "work" but I'm not sure how good an idea it is...

http://xdaforums.com/showpost.php?p=51922707&postcount=1706
[Nexus 5 Original Android Development] Technecium:
Anything is possible. I just try to keep the f2fs code up to date. How others use it or even if they use the code I have in my repo is on the dev.

There are so many variables; source code, ramdisk, recovery, etc. It could be one thing or a combination of many.
[Nexus 5 Original Android Development] firegate22:
Yes, that's working! Thank you!
[Nexus 5 Original Android Development] magnamentis:
cannot be pointed out enough

i confirm that, same on my n7100, even worse because the kernel dev switched without telling that, even without reformatting,

one gets stuck with the kernel, means it was not possible to flash "ANY" other rom without that kernel, had to reformat "EVERYTHING"

with special tools and go from scratch via ODIN and even then i had to reformat the sdcard a second time via TWRP while CWM still did not

work before that.

36 hours of pure reconfiguring ( lot's of apps and data ) to get the same rom i had back but with the possibility to flash others and or the same

without custom kernel so to make my device open and freely configurable again and at no point i had a visible and thus a significantly faster device,

so practice, like so often cannot keep up with the theory, albeit true, because something already very fast compared to something let's say 5% faster

cannot be distinguished with our senses, by pure eyesight for example.

SO BE WARNED, DON'T GO THERE, IMO THE POSSIBLE NEGATIVE EFFECTS ARE HIGHER THAN THE EVENTUAL BENEFITS.

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11, AGNI Kernel 2.7.5_r3, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )

Please Click The Thanks Button If I Helped You Out
[Nexus 5 Original Android Development] dennes544:
Soon kernel updates + add f2fs-full
[Nexus 5 Original Android Development] AJM-hackers:
Currently if any other kernels are flashed it results in the error to decrypt the storage. Could you fix this also in the next update> I tried using zetachromium and uber kernels
[Nexus 5 Original Android Development] AJM-hackers:
[MENTION=5499742]dennes544[/MENTION] I saw that you edited the post and posted an update but on dev host it is still the old kernel from april 9
[Nexus 5 Original Android Development] dennes544:
I added links to github only. I didn't update kernels. Wait few days, until I restore my PC fully
[Nexus 5 Original Android Development] AJM-hackers:
Thanks for the heads up. There's a bug which causes me to lose root after flashing, it would be much appreciated if you could fix this as well.
[Nexus 5 Original Android Development] Technecium:
Regarding the too few, too many arguments, go to the mentioned file, and line number of the error. You'll be able to see what it is asking for. You'll have to determine what arguments are extra or missing. You'll have to poke around.
[Nexus 5 Original Android Development] sir mordred:
Thanx for your answer bro

But im not experienced on debugging for compilation errors

What do you mean?

Also if i detect error and line, then what will i do?

Thanx again

With my best regards
[Nexus 5 Original Android Development] Technecium:
fs/generic_acl.c:161:3: error: too many arguments to function ‘posix_acl_chmod’

In file included from fs/generic_acl.c:13:0:

look at line number 161 of fs/generic_acl.c

look also at line 13. it should point to another file.

something doesn't match between these two files regarding posix_acl_chmod

look through the referenced file for posix_acl_chmod

I'm using my phone to write this so I can't really off to debug the code for you. you should take some time to read through the errors one by one. try searching github and Google for examples that might help you out to better understand the error.
[Nexus 5 Original Android Development] dennes544:
Thx for that. Just some line missed in headers. I'll fix it when can
[Nexus 5 Original Android Development] sir mordred:
thanx again for helping me bro

But as i said i just know the pushing and reverting commit into kernel

İf you find some free time, can you help me sir?

İm using github also. Maybe you can make a pull request and i can merge the fix into my kernel sir

Huge thanx

With my best regards

---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------

Wooww thanx sir

And also can your fix solve my compile error?

İ'll be waiting for you sir thanx again

Regards
[Nexus 5 Original Android Development] dennes544:
To pm please
[Nexus 5 Original Android Development] Nickamina:
[MENTION=636360]koe1974[/MENTION] Is your F2FS Franco kernel still being updated?
[Nexus 5 Original Android Development] Technecium:
I just uploaded r47. FYI: I usually take a day or two to test just to make sure things are in order.
[Nexus 5 Original Android Development] daftlush:
Any chance we can get a new cm kernel? I can only get furnace to work with the latest one and I would love to get elemental to work and bricked to work also.
[Nexus 5 Original Android Development] dennes544:
Of course cm kernel will soon. Maybe even today
[Nexus 5 Original Android Development] phishfi:
[MENTION=5499742]dennes544[/MENTION] did you say that you're working on building f2fs-all? Instead of just data? That would be frikkin awesome! I tried the methods a lot of people referred me to but nothing seemed to work well enough. Probably just my limited "skills" reading/editing code...
[Nexus 5 Original Android Development] ilia1985:
Hi... Using your f2fs Franco r47 kernel... For some reason can't see or mount internal memory in recovery? Did I miss something? Thanks in advance
[Nexus 5 Original Android Development] Technecium:
I'm not certain what you mean by internal memory? Can you go into recovery, select the Mount button. Choose system, data and cache. The issue mount via adb. Please post the output and tell me which mount point you expect to see but don't.

Thx
[Nexus 5 Original Android Development] ilia1985:
System and cache mount fine but data refuses to mount....
[Nexus 5 Original Android Development] Technecium:
Can you post the link to the same recovery you are using so I can test on my device?
[Nexus 5 Original Android Development] ilia1985:
I used the recovery found in OP
[Nexus 5 Original Android Development] Technecium:
There are 5 links to different versions, again, can you post the link to the one you are using?

Thx
[Nexus 5 Original Android Development] daftlush:
I'm watching them turn popes into saints and all I can't think of is... I wonder if they finally released a new caf f2fs kernel.
[Nexus 5 Original Android Development] ilia1985:
Here you go http://d-h.st/vFQ this the one I used
[Nexus 5 Original Android Development] Technecium:
[MENTION=3053815]ishaqs60[/MENTION]

I haven't forgotten about your problem and thanks for bringing it to my attention. However, I'm not going to have much time to do anything about it. My device is currently not formated for f2fs so I can't even do any tests.

My build of Franco uses f2fs code from 3.4 and Dennes544 is using a backport of 3.15. If you want, as a possible temporary solution, try using an earlier version of the recovery. That may allow it to mount.
[Nexus 5 Original Android Development] gharrrrrr:
So on the N4 thread there is a way to format all /system /cache and /data to f2fs but I can't seem to find one in the N5 section. Am I missing it?

Sent from my Hammerhead using my T.A.R.D.I.S.
[Nexus 5 Original Android Development] kevdliu:
I observed something very interesting today. I had my /data formatted to f2fs, installed ROM and f2fs kernel and everything works great. Today in a rush I forgot to flash the f2fs kernel after reflashing the ROM. However instead of failing to boot, the ROM actually booted with the stock ext4 kernel. Naturally the setup wizard was displayed as the ROM was in its factory state. I thought I had lost all my data but when I flashed the f2fs kernel, everything went back to normal and no data was lost. I'm not a computer scientist so bear with me here. Are there now 2 filesystems written over each other on the flash drive?
[Nexus 5 Original Android Development] sir mordred:
[MENTION=636360]koe1974[/MENTION]

May i ask a question master?

İ compiled succesfully twrp recovery which support f2fs for my device and it is working

But making recovery didnt create zimage or boot.img(for f2fs kernel)

İ dont know why but i tried another method

İ builded a kernel by adding following patchset for f2fs support

Here is the patchset(look the latest commits):https://github.com/jfbs/samsung-kernel-msm7x30/commits/w-f2fs

Kernel compiled succesfully but im not sure because while compiling kernel i didnt use modified ramdisk for kernel

İs this necessary for kernel which support f2fs sir?

Thanx

Regards
[Nexus 5 Original Android Development] corey749:
Any eta for multiboot?
[Nexus 5 Original Android Development] dennes544:
Sorry, but I'm passing exams that's few weeks, so will not updates soon
[Nexus 5 Original Android Development] corey749:
Thanks for the response. Good luck in your exams!
[Nexus 5 Original Android Development] GR0S:
Does faux kernel boot stock Rom?

I wanna backup /system to usb drive , then format everything and restore /system after all.

Update: I flashed recovery, formatted /data, rebooted to recovery, and flashed faux f2fs kernel. It does not boot.

Tried to format everything, then install omnirom with gapps and faux123, still doesn't boot. Probably because of faux kernel.

Update 2: faux kernel and omnirom dont have proper fstab patches, so they can't boot. Flashing factory image for now.