yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
Those look promising to improve I/O performance but would they effect ram speed performance? That's the one thing mpokang outshines every other kernel on

For example, here are a couple antutu ram benchmarks from mpokang kernel

And I'll post a couple from dirtyv in a minute to compare
[Samsung Galaxy Nexus] metalspring:
And this is what dirtyv scores are for ram in an tutu

(Notice how ram operation is about the same as mpokang but the ram speed is nowhere close)

This is why I'm curious if mpokang has some type of ram over clock or something like it

Would it be possible to tell what clock speed the ram is running at?
[Samsung Galaxy Nexus] ak:
have you merged arm omap cache commits?
[Samsung Galaxy Nexus] demlv:
I'm interested -- what do you use to set governors or cpu frequencies on a per app basis?
[Samsung Galaxy Nexus] namtombout:
Franco kernel updater or you can Google "per app modes"
[Samsung Galaxy Nexus] iluvamk:
If that was directed at me I ment no offense by it. Was just asking.
[Samsung Galaxy Nexus] osm0sis:
It helps a bit, but it totally f*cks up the way your screen looks when it does its thing; grainy looking, some striping if your screen is prone to that defect. Most people disable it because they'd rather have a screen that doesn't look like sh*t than 10min more screen on time. :p

In your case though, since you also mentioned you had voltage changes, I'd troubleshoot by clearing tweaking app settings. REALLY make sure it's clean by uninstalling and reinstalling the app (...Trickster... *fist-shake*). Then only set CAB on at boot (ie. don't touch ANYTHING else). See if you have the issue on f2fs then ext4 again. I have a feeling it might be voltages for you and once you switched to ext4 your voltages weren't set? OR maybe voltages were slightly touchier for you on f2fs for some reason.

If you can do that I'd greatly appreciate it, to help us understand the problem better. If it does end up being CAB and only on f2fs for you, then we'll just have to add that to the list of weird caveats for that issue. As for ondemand, is it not in [MENTION=4608636]bsmitty83[/MENTION]'s 6-9 builds? If not, I'm sure he can comment on the reasoning. I think his upcoming recovery builds should fix sideloading issues too. :good:
[Samsung Galaxy Nexus] pattyboi:):
bout time
[Samsung Galaxy Nexus] Nephilim:
When are we gonna get an ext3 Android 2.3.2 compatible DirtyV? I mean seriously.....
[Samsung Galaxy Nexus] bsmitty83:
Shhh , I'm working on it , lmao . you want a donut ROM too ? It sure would go great with some "random" tunables [emoji39]

What's up [MENTION=2853378]Nephilim[/MENTION] ? Good to see you still around

Hack The Tuna
[Samsung Galaxy Nexus] Nephilim:
Word, I'm still here, I'm always here. Just gotta lurk sometimes since I've been working a lot lately. ;)
[Samsung Galaxy Nexus] osm0sis:
Okay, weird, I can't reproduce this at all on metaltest2-Unified, even on a clean install of Synapse with no /sdcard/Synapse directory present. I'll try out the build you're on and see if I can reproduce it there, and try to figure out what the difference could be.

Edit: AH! Dynamic Dirty Writeback is removed. I'll update Synapse to reflect that. Good thing, in my opinion, since that feature generally seemed kinda useless. :good:

https://github.com/bsmitty83/DirtyV_tuna/commit/3072db8cb0bd1a564d62b3efc1fbca50f8223014
[Samsung Galaxy Nexus] DHO:
*waves hi*

Thanks for the @ mentions :D
[Samsung Galaxy Nexus] bsmitty83:
Welcome to the party . [emoji106][emoji6]

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Bad news... not even the Busybox v1.22.1 included in TWRP 2.7.1.0 maguro has a blkid applet that successfully reports f2fs. :eek:

Good news... TWRP-TUNA-F2FSALL does (too bad it's dynamically linked..) ;)

Best news... [MENTION=4015637]rkpeterson[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=2838735]aosp[/MENTION]

LS-KK-v3.1-2014-06-08-maguro-f2fs.zip/META-INF/com/google/android/updater-script (for example):

Replace:

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");
ui_print("Mounting f2fs System...");

With:

ifelse(run_program("/sbin/sh", "-c", "test `blkid /dev/block/platform/omap/omap_hsmmc.0/by-name/system | cut -d\\\" -f4` == 'ext4'") == 0,
( format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");
ui_print("Mounting ext4 System...");
),
( run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");
ui_print("Mounting f2fs System...");
)
);

BOOM!

Unified ROM install zip. :cool:

And with my Unified kernel ramdisk files on board that = no more special build f*ckery to support f2fs on tuna for ROM devs.

Same type of workaround as fscheck for now; if it's ext4 it's ext4, if it's not it's f2fs. Once all the busybox binaries finally catch up to having proper f2fs support I've got another version that's even better (supports any filesystem ever), but this'll handle it until then.

Edit: Some people seemed confused by the mount command that would come next. It should be the following to remove the need for specifying filesystem type:

run_program("/sbin/busybox", "mount", "/system");
[Samsung Galaxy Nexus] aosp:
You forgot [MENTION=2765426]styr[/MENTION] ?
[Samsung Galaxy Nexus] aosp:
[MENTION=2838735]aosp[/MENTION]

Stop quoting yourself ?
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION]

I might need you to help test a maguro commotio build with a open source ril you game?
[Samsung Galaxy Nexus] osm0sis:
Sure as long as I don't have to format data. Managed to do all the above stuff without, just tested on /cache instead. ;)

By the way, where do you guys have the source for TWRP-TUNA-F2FSALL ? I want to grab the busybox from it and try to compile it statically.
[Samsung Galaxy Nexus] aosp:
[MENTION=2765426]styr[/MENTION] Pass the awesome sauce to our Canadian bad arse please ?
[Samsung Galaxy Nexus] bsmitty83:
Its the twrp forked on my github

BTW I just got the kernel to compile with lz4 , but its too big to flash lol .

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Hahaha what? Weird! There must be some way.. I know [MENTION=3292224]franciscofranco[/MENTION] is using lz4 on his flo/deb zImage now, and [MENTION=2687601]Metallice[/MENTION] used to use lz4 for both zImage and ramdisk on grouper for awhile. The latter is what I'm hoping we can try here. :D
[Samsung Galaxy Nexus] bsmitty83:
The zimage was 7mb lol , normally its ~3mb , so idk I'll have to explore more , its probably in the way I have the makefile.lib , im trying some things ......

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
That's totally okay. As long as it runs and the boot.img is less than 12mb we're laughing bro. :cowboy:

Info for everyone: For awhile people wanted better zImage compression because they thought smaller might mean faster, but it's the other way; big is faster to decompress so it boots much more quickly. lz4 is the fastest decompression around.
[Samsung Galaxy Nexus] bsmitty83:
Well its too big to fastboot as is ...

Edit : I fixed it by using high compression ( c1 instead of c ) but it doesn't boot so i think the ramdisk needs work to support it

I pushed the changes to dirtyV-f2fs-exp anyways

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Really.. Huh, could have sworn the partition limit was 12mb. Maybe I'm mistaken and it's 8?

Recovery and Radio are definitely 12. Lemme dump the kernel partition real quick..

Edit: Yup. Damn. Boot is 8mb. It's 12 on flo, that's why I was confused. :good:

[MENTION=4608636]bsmitty83[/MENTION] Hmm, ramdisk shouldn't matter unless you enabled lz4 for ramdisk and also disabled gzip for ramdisk in the defconfig.
[Samsung Galaxy Nexus] bsmitty83:
I think the updater script and any mention of lz4 needs to be changed to lz4c , that's the issue , the new lz4tools for Linux are named as such .

Hack The Tuna
[Samsung Galaxy Nexus] KiD3991:
CAB issue. After I commented the last post I finalized my phone and rebooted to install V4A. Then it happens again. I turned CAB off, then all fine. I use -75 across board and an extra -25 for all the frequencies above 1200. Now all is fine and my phone is cool and awesome. CAB off makes stuff looks nice too. :angel:
[Samsung Galaxy Nexus] osm0sis:
Cool, good to know. So ext4 and f2fs?

updater-script like the flashable zip? There's no gzip stuff in there. :confused:

P.S. TWRP's Android.mk just makes reference to external_busybox so no luck there. I'm just going to try with PhilZ's GitHub source, it looks up to date. :good:
[Samsung Galaxy Nexus] KiD3991:
I'll retry F2FS after grabbing lunch. :P

I'll still need to worry how to put stuff into my phone using Sideload
[Samsung Galaxy Nexus] Charmacas:
After formatting with smittys recovery just flash PhilZ recovery and adb push everything to your device. ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] styr:
It was built from Omni source with busybox and f2fs-tools branches from CM merged over, multirom twrp merged over and a modified device tree. I think that was all of them. I`ll try to build you a static busybox if you remind me to power on the vm.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Did you say LZ4 voodoo?

https://github.com/cod2xnp/android_kernel_samsung_tuna/commits/test
[Samsung Galaxy Nexus] osm0sis:
**** yes! Man you're one amazing Git miner! :)

[MENTION=4608636]bsmitty83[/MENTION] lz4 r116 (not lz4c, so it should match that guy's commits) I compiled for Linux here: http://v.ht/AIK-

r117 is the latest and didn't have any significant changes so I'm skipping it. :good:
[Samsung Galaxy Nexus] aosp:
No tuna left behind ;)

And forgot these

Add uevent switch for event logs

http://goo.gl/QU6d6u

Re-integrating Broadcom wireless driver v1.141.44 with fixes.

The same driver was submitted and reverted because of some regressions.

http://goo.gl/TK2Uos

Google hack too? ?

android.googlesource.com/kernel/omap/+log/glass-omap-xrv70d
[Samsung Galaxy Nexus] DR3W5K1:
Thanks for your sd card permissions fix zip.

Just realized my sd card was screwed up after adb pushing my sd card back in the f2fs twrp.

Easy as pie ;)

THANK YOU!
[Samsung Galaxy Nexus] mangusZen:
Is there a version with mpok commits still floating around somewhere? The [MENTION=1143630]osmosis[/MENTION] ones?
[Samsung Galaxy Nexus] bsmitty83:
I've been using his git as reference all along , why do you think I thought the updater script set perms for lz4 ?

All I know is that lz4 doesn't get recognized by Ubuntu . if you apt-get install lz4lib-tool , you gotta use lz4c , which is the the most current according to everything I've seen . ive tried every way with just using lz4 , always get a bin/sh : lz4 unknown error . so idk .

Hack The Tuna
[Samsung Galaxy Nexus] xzilem:
How to get a log of bootloop?

I'm having a problem with a bootloop when using reboot command from power menu with the latest dirtyv.
[Samsung Galaxy Nexus] Hetalk:
Check post#2 for your log options.
[Samsung Galaxy Nexus] rajputrajat:
Posting it here again (after vanir thread):

With 06-10 dho nightly, i do not have mobile network on my phone.

Any ideas.

Getting this SMS

"Samsung-RIL: The modem just crashed, please reboot your device if you can't get service back."

Do not want to try anything else right now, because phone was never running this smooth.

I did not flash original rom, but modified version for f2fs (changes in update script). Could this be the reason?

Kernel is latest dirty SR.

Edit:

Problem solved. Thanks to [MENTION=2838735]aosp[/MENTION].
[Samsung Galaxy Nexus] gautam_nexus:
i am planning to shift to f2fs but the copy of recovery is 2.7.0.0, can anyone share the latest twrp with f2fs support.

do i need f2fs compatible gapps as well or i can flash the ussual PA gapps copy.?

Thanks
[Samsung Galaxy Nexus] Hetalk:
Post#1 has got a twrp and philz cwm that [MENTION=4608636]bsmitty83[/MENTION] built for us. Both support f2fs. :good:

I've used banks gapps and aospa gapps and both work well with f2fs.
[Samsung Galaxy Nexus] gautam_nexus:
Thanks buddy! :cowboy:
[Samsung Galaxy Nexus] bsmitty83:
Used to ....... Lol I took the philz down due to it not reading ext properly , as for the twrp , its somewhere in this thread , I haven't linked it in the op

Hopefully soon I'll have a new philz up

Hack The Tuna
[Samsung Galaxy Nexus] Hetalk:
In that case, here's the link [MENTION=2838735]aosp[/MENTION] provided. It's got f2fs twrp

https://drive.google.com/folderview?id=0B60Mii9V3x83aW5PSUVBX2RobDQ
[Samsung Galaxy Nexus] midnightdevil66:
Instead of reboot do a power off instead and power on via button. That works for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dezful:
After about 3 days using DirtyV SR 6/9 with CarbonROM 4.4.3 F2FS mode. I can say that everything is working flawlessy on either Dalvik or ART. No freezes, random reboots, etc. Well done developers! :good: ;)
[Samsung Galaxy Nexus] osm0sis:
Last night you said you thought the updater script might need to be fixed for lz4. *Shrug* Anyway, use the lz4 I compiled. apt-get doesn't get the right thing. Extract lz4 and put it in /bin/ on your machine. It's static so should be good to go. :)

Definitely works in my AIK-Linux script for building a working lz4 ramdisk. Maybe take a look at the command line I used in repackimg.sh to make sure your zImage one is up to date as well?
[Samsung Galaxy Nexus] rkpeterson:
By all means go ahead....
[Samsung Galaxy Nexus] hasnol143:
Has anyone tried this kernel with resurection ROM?
[Samsung Galaxy Nexus] osm0sis:
Already done sir :)

http://xdaforums.com/showpost.php?p=53312320&postcount=10192
[Samsung Galaxy Nexus] MWisBest:
...what? I don't remember ever talking about CAB. :eek: Fill me in on what's going on!
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION] , I can't find that lz4 binary , I see the Google link for the source but I'm missing the prebuilt . since I'm slow can you possibly link it for me lol , otherwise I'll compile it some other time , or I'm gonna search the internet

Disregard I found it [emoji6]

Hack The Tuna
[Samsung Galaxy Nexus] Oehr:
new kernel doesnt seem to work with resurrection remix... cant even get to the boot animation.

anyway, any chance you can upload your older kernels again? the ones listed in the first post are pretty old and the mentioned devhost has pretty much nothing to offer...
[Samsung Galaxy Nexus] jhonnyx:
1 - Which version are you using?

2 - Old versions are downloading OK for me. Which one are you trying to download?
[Samsung Galaxy Nexus] bsmitty83:
I'll try to update the old kernels as soon as I can . if you remember the date of the kernel your looking for , you can simply copy the link address of the current version and change the date to match what you want , they are all on my host , I just haven't added the old links to the op .

I haven't used dev-host in a while but ill try to get it together

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Really? Haha I'm crazy maybe. I thought someone reported in your thread about the spontaneous reboot at the lockscreen which happens when CAB is changed by a tweaking app before you unlock and the screen turns off. I told them it was CAB and to set it with init.d instead and then you said you'd look into the reason that'd happen in the source. Again, I might be crazy. :p

:laugh:
[Samsung Galaxy Nexus] bsmitty83:
Yea I found it threw it in /bin and lz4 compiles normal again gotta wait to test it tho . for some reason adb and fast boot hang on my machine sometimes until I reboot , but I got a ROM building so .....

Thanks again tho

Hack The Tuna
[Samsung Galaxy Nexus] rkpeterson:
Built this morning for Toro worked beautifully.

Currently building ext4 for Official builds; planning on building f2fs for all three gnex when I get home in the morning.

Should I continue posting f2fs builds here?
[Samsung Galaxy Nexus] bsmitty83:
I got no problems with that

Hack The Tuna
[Samsung Galaxy Nexus] gautam_nexus:
i flashed this img file from adb...went into advanced settings...checked the f2fs radio button and checked all the partitions. hit the format button...adb pushed the PA rc1 f2fs ROM and gapps..now when i am flashing the ROM getting error!

am i missing anything?
[Samsung Galaxy Nexus] bsmitty83:
Reboot recovery after partitioning to f2fs

Hack The Tuna
[Samsung Galaxy Nexus] gautam_nexus:
Thanks a lot buddy..it worked. now when i am flashing the lastest pa gapps it gives error updater binary has failed.:confused:

Its because the gapps size...but when i was on ext4 i was able to flash the same gapps file? i am confused now
[Samsung Galaxy Nexus] bsmitty83:
Think you need a different gapps package , try banks gapps or some of the other ones people have been using . some are compatible , others are not

Hack The Tuna
[Samsung Galaxy Nexus] gautam_nexus:
when i shifted to ext4 i am able to flash the same gapps file...does f2fs reduce the system partition size?
[Samsung Galaxy Nexus] osm0sis:
There is something weird about the free space/reporting after formatting to f2fs. Someone reported that flashing the same ROM you have less free space on f2fs than when flashed on ext4.
[Samsung Galaxy Nexus] bsmitty83:
Yes , by about 100 MB apparently . I haven't been switching back and forth so I didn't notice , but others have commented on it and it does .

Hack The Tuna
[Samsung Galaxy Nexus] gautam_nexus:
is this a bug or expected from f2fs?:confused:

---------- Post added at 03:15 AM ---------- Previous post was at 03:06 AM ----------

That sucks!...hope there is a way to fix this...you guys are awesome devs can do anything:good:
[Samsung Galaxy Nexus] aosp:
Normal and expected ?
[Samsung Galaxy Nexus] osm0sis:
Why? Log vs journal?

Good news is with the upcoming PA GApps I've been helping a little with you'll be able to select which apps you don't want prior to install so we can slim down Stock to fit. :good:
[Samsung Galaxy Nexus] gautam_nexus:
I have always been using stock gapps by aospa...what gapps shall I use?:crying:

---------- Post added at 03:22 AM ---------- Previous post was at 03:21 AM ----------

that is one awesome news....;) btw what is the permissible size for gapps in f2fs?
[Samsung Galaxy Nexus] aosp:
Yeah you can say logs but a few hundred megs for the awesome ain't nothing to write home about ?
[Samsung Galaxy Nexus] osm0sis:
You can switch to a smaller PA GApps in the mean time; full modular or something. It's however much space the ROM leaves behind, minus maybe 10mb buffer for ROM growth. Our system partition isn't that large to begin with.

Less bloated ROMs will be a must for f2fs because of the differences. :good:

Edit: I guess our other option would be to have system remain ext4.. I dunno. All or nothing is obviously much easier to support. :p
[Samsung Galaxy Nexus] Oehr:
ah thanks! i tried it before but i forgot about the namechange (extra U), so no wonder I couldnt grab it :D
[Samsung Galaxy Nexus] Atento:
Unfortunately, smittyV 05-31 is way faster than last version in my case. Even though ram speed seems only affect benchmarks, in my case this is not true.
[Samsung Galaxy Nexus] michierusama:
Kernel is now a MegaCharizard.
[Samsung Galaxy Nexus] Shadow Death:
Is this with all f2fs roms or just a select few? I was told once that the boot.img is responsible for the block size of the partitions.
[Samsung Galaxy Nexus] amd_h4x0r:
[MENTION=4697422]gautam_nexus[/MENTION]

http://xdaforums.com/showpost.php?p=53287840&postcount=10135

I had to switch from the mini PA GApps to the micro PA GApps due to the space issue with f2fs. I just got the missing apps (Hangouts, Maps, YouTube, etc.) from the play store.
[Samsung Galaxy Nexus] dezful:
There is inconsistency in f2fs /system free space. Titanium backup says that there is 156mb free space. However, Diskinfo apps shows only 134mb of free space.

Day 4 of using the latest DirtyV kernel. Random lags occurred somehow. Interestingly, pulling down the status bar fixes the lags. Weird! I don't know this is kernel or ROM related issues.
[Samsung Galaxy Nexus] Hetalk:
I've been using latest paranoid with paranoid mini gapps package and had no issues with space. Just a FYI
[Samsung Galaxy Nexus] KiD3991:
Its the CAB issue for the reboot after reboot issue. F2FS working fine here. Anyone ported the 4.4.3 SlimKat to F2FS? :P
[Samsung Galaxy Nexus] Punkiderma:
I think I'll do it as soon as I can, by the way I and [MENTION=4278473]Hetalk[/MENTION] tried to explain the simple steps behind "converting" a rom (even if, like [MENTION=4328678]metalspring[/MENTION] said, is not a full f2fs support), you can find them here

By the way, for me kernel is fast, but I stil have some problem:

1. If I reboot via power menu, I still get infinite bootloop at google logo. I have to push the three buttons and now that I've installed TWRP f2fs recovery boot into recovery doesn't work anymore, I have to power off and then power on the phone in order to make it boot properly.

2. I still have some random reboots, but less than before.

3. Sometimes, after some hours of use, my phone still become sluggish

I'm on f2fs, and I know I wrote very generic things, but is just to understand if these have been fixed and remain only on my phone or if it's normal.

Thanks!
[Samsung Galaxy Nexus] molimo:
hi guys,

what is the difference between SuperRam and BigMem versions?
[Samsung Galaxy Nexus] KiD3991:
Thanks for you effort converting. IMO those are compatibility issues rather than kernel. Most of the kernels I used here doesn't give me any issues other than the CAB and inability to go below 230Mhz(could be me undervolting too much).

---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------

SuperRam have the highest amount of RAM available while bigmem is just larger than stock.

If you can sacrifice(or dont use at all) Full HD video recording, by all means go for SuperRam. Although I can assure you if you have low usage both wont matter too much, empty RAM in Android OS barely means anything as long as you have 10% remaining.
[Samsung Galaxy Nexus] büscher:
you are not alone. I have exactly the same issues (CM-Remix 2.9.6 & DirtyV BigMEM 6/9)
[Samsung Galaxy Nexus] gautam_nexus:
cant we just increase the size of the system partition to balance the 100 mb loss? :fingers-crossed:
[Samsung Galaxy Nexus] DR3W5K1:
In theory yes.

I suspect it might be an even bigger ordeal than the filesystem change we just had.
[Samsung Galaxy Nexus] Atento:
You guys are not alone. Exactly the same issues here. The third one is very annoying.
[Samsung Galaxy Nexus] Reinvented:
#ThrowbackThursday (???)​
[Samsung Galaxy Nexus] KiD3991:
I hope you don't mean insult. Because I am still using that. =w=

Its my MP3 player.

---------- Post added at 10:03 PM ---------- Previous post was at 09:54 PM ----------

First time I get to sideload on F2FS, then this time sideload don't work? What kind of black magic do you guys use to make sideload work?
[Samsung Galaxy Nexus] Reinvented:
As long as it's an Android in your hand, we're cool. :cool:
[Samsung Galaxy Nexus] DR3W5K1:
Adb doesn't start up for a minute or two for some reason.

Keep typing adb devices until it returns with your phone.

Now try side load.

*pro tip*

adb push and pull works also
[Samsung Galaxy Nexus] aditya.jazzmaster:
Does anyone have try latest official TWRP v2.7.1.0?

I heard it support f2fs

Thanks
[Samsung Galaxy Nexus] osm0sis:
Definitely an ordeal haha. The only recovery that supports repartitioning as an enduser feature is Safestrap, and nobody has built it for the GN.

It does, but it still hasn't been enabled for the GN yet. Dees_Troy asked people to PM him if 2.7.1.0 still didn't support f2fs for a device that needs it. I assume someone's done that by now, so hopefully we'll get it in the next version. :good:
[Samsung Galaxy Nexus] aliesz:
Yes I have tested it and this version supports f2fs.[emoji106]
[Samsung Galaxy Nexus] osm0sis:
It supports reformatting to other filesystems, but you'll notice f2fs isn't in the list. ;)
[Samsung Galaxy Nexus] aditya.jazzmaster:
So which TWRP I must use for f2fs?

bsmitty one or original one?

Thanks
[Samsung Galaxy Nexus] osm0sis:
I've seen people recommend using Smitty's for the initial format, then switching to the official from that point on for adb sideload fixes, etc.