yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rajputrajat:
F2fs version... :D

---------- Post added at 10:02 AM ---------- Previous post was at 09:59 AM ----------

Brother... You guys are magicans... Another round of super-powers to old mighty galaxy nexus...

Device is running like never before...

Can't thanks enough :D:D:D:D:D
[Samsung Galaxy Nexus] rkpeterson:
May take a minute but, looking into adding f2fs to LiquidSmooth.
[Samsung Galaxy Nexus] my573r10us:
ask

I'm sorry, i cant get what u are talking about f2fs..

may i ask a question?

i'm on philz recovery touch, can i use f2fs? if yes, how? or i must change to twrp first?

can everyrom (4.4.2) can use f2fs?

i wanna try, but im scared my phone cant boot, because i always try to connect my phone to my computer, but it didnt recognize my phone.. try all way, always like that.

sorry for bad english and bad question :(
[Samsung Galaxy Nexus] michierusama:
Hi

First you have to know the only ROM (that I know of) that supports it by now its the one that's on the downloadable package posted on few pages back (it also includes the custom recovery they made to switch from one format to the other).

And no. Your phone won't get bricked as long as it is recognized in ADB. And you can pull zips and flash ROMs.

Also I recommend you use the search or read a few pages back because that's been discussed I think. But there you go. Your answers. Good.
[Samsung Galaxy Nexus] dezful:
MetalSpring DirtyV F2FS kernel without test: 32Mb/s Read and 5Mb/s Write.

MetalSpring DirtyV F2FS kernel with test: 32Mb/s Read and 10Mb/s Write.

sent from it-that-must-not-be-named
[Samsung Galaxy Nexus] my573r10us:
thank you for ur fast reply!

i've already search a few pages back, and i got Vanir ROM (aplha test), it that the right ROM u mean?

more thanks! :D
[Samsung Galaxy Nexus] _hz:
The 'test'-one doesn't boot on latest slimrom, stuck on google boot logo...

Wiping cache and dalvik didn't help, exposed framework disabled..

if someone can help me how so send a log i will post it here... just a link would be enough... ;)

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] pianistaPL:
Same here, i tried boot it with OmniMetal.
[Samsung Galaxy Nexus] redj12:
Wan't boot with Slim. Regular version.
[Samsung Galaxy Nexus] dbh369:
Nevermind
[Samsung Galaxy Nexus] osm0sis:
Doesn't sound like anyone's been able to get metal's ext4 test version to boot. Amiright?

[MENTION=4328678]metalspring[/MENTION] Stuck at the bootlogo sounds like a ramdisk issue.

Edit: Yup, it's the f2fs ramdisk still. Hold on, here it is with ext4.. ;)

DirtyV-R-5.3.14-metaltest-synapsed: http://d-h.st/zLL

Latest Synapse/ramdisk fixes from the official Git. :good:
[Samsung Galaxy Nexus] dezful:
This kernel appears to be very smooth, good score (11000) on antutu as well. However, it drains my battery faster than DirtyV Sypnased by osm0sis, only 1 hour 45 mins on screen time on. I also got random reboot once. :)

sent from that-must-not-be-named
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=4328678]metalspring[/MENTION]

Any idea if f2fs will interfere with the usual 24h uptime fstrim Android runs when idle? If not, then discard definitely still shouldn't be used as a mount option on data or cache to avoid slowing I/O down. We can likely still trust to the fstrim daemon for normal users and my updated suspend_trim script for the crack flashers. :)
[Samsung Galaxy Nexus] HONG86:
Yeah~ :cowboy: Here he comes !!!

Welcome to osm0sis world!!! :highfive:
[Samsung Galaxy Nexus] osm0sis:
Haha no no you've been in DirtyVille long enough to know that it's a Team Dirty effort. ;)
[Samsung Galaxy Nexus] aosp:
Not sure why [MENTION=4328678]metalspring[/MENTION] added discard or background_gc but no it will not interfere and the main reason I left it out was for suspend_trim can still be able to perform it's voodoo ?
[Samsung Galaxy Nexus] pvkiniyan95:
8hrs i missed this thread and got to read 10 pages...holy smokes things are coming together so well that this big bro GNEX is still in the race...

going to test [MENTION=4328678]metalspring[/MENTION] kernels :)

btw i listed about 20 apps to be installed over night and in the morning i found systemui fc which reappeared even after restart so did a factory reset, unfortunately couldn't find which app was the cause....any similar experiences
[Samsung Galaxy Nexus] Atento:
I can't disable suspend trim. Is it right? I'd like to disable it because it drains battery. I don't think it is necessary to run every 60 seconds.

Anyway, thank you guys for this amazing work.
[Samsung Galaxy Nexus] osm0sis:
a) It's disabled by default,

b) It doesn't drain battery,

c) It doesn't run every 60 second, that would be ****ing insane. ;)

My uptime/SOT are the best they've ever been on KitKat, so I suggest you check your wakelocks. It can run after every 20 minutes of screen-on time, but only after the screen has been off for 60 seconds. So, considering people get like 3 hours (tops) with KitKat, it can run (at most) 9 times per cycle, which is fine. It could also run 0 times if you never put your device down long enough. And it can be toggled easily within Synapse, or using the command lines I posted awhile back.
[Samsung Galaxy Nexus] Atento:
I tried to disable it in synapse before posting here. It didn't work.

I'll search for the command line then.

Thank you for your answer.
[Samsung Galaxy Nexus] osm0sis:
It works. You need to go into Synapse, disable it and apply the settings. Clearing Synapse app data won't do it because it's a persistent setting. I suggest you delete /data/trimhelper and reboot if you're having this much trouble.
[Samsung Galaxy Nexus] dezful:
So this kernel can be flashed on both f2fs and ext 4, eh? CMIIW. :p
[Samsung Galaxy Nexus] osm0sis:
No. ext4 only, since metal put the f2fs ramdisk in it by mistake. I've got work to do to unify things. Stay tuned for later this week though. ;)
[Samsung Galaxy Nexus] Ziyan:
Here's a quick antutu using Neph's settings with pegasusq & OmniMetal (ext4). Seems good, did we reach Mpo's RAM speeds now? :p
[Samsung Galaxy Nexus] Atento:
I don't know if [MENTION=4328678]metalspring[/MENTION] merged mpo's patches but there is a huge improvement in ram speed.
[Samsung Galaxy Nexus] metalspring:
That was the performance over time part. Discard is similar to fstrim, right? And the background_gc being on allows the garbage collection to run while I/O is idle to clean up useless and/or outdated caches I believe.
[Samsung Galaxy Nexus] osm0sis:
Discard trims as the I/O occurs, which keeps performance the same over time, but slows it down overall. Since Android and suspend_trim automatically handle trimming over time on /data and /cache, we might as well enjoy the improved I/O speed from having discard disabled on them. Leave discard on /system since it doesn't get a lot of writes and I left it out of suspend_trim to keep it quick. :)
[Samsung Galaxy Nexus] metalspring:
But does suspend trim use fstrim? F2fs does not support fstrim-

1|root@toro:/ # fstrim /system

fstrim: FITRIM: Not a typewriter

(no idea what the heck that means but fstrim does not work on f2fs)
[Samsung Galaxy Nexus] osm0sis:
It does use busybox's fstrim, yeah. And ah okay, I was just going by what aosp said here:

Since f2fs uses discard it must support trimming in general, I'd guess we just need fstrim to be updated in the busybox/kernel source to be aware of that.

---------- Post added at 12:43 PM ---------- Previous post was at 12:37 PM ----------

Discard may not be as detrimental in f2fs so it might not be a big deal, but it's hard to get a clear answer. Still looking but this is interesting: http://www.anandtech.com/show/7235/moto-x-review/9

He might be confusing the discard option with trim being "baked-in" for deletions though, since you could always do the same with discard on ext4 but it makes your I/O speed eat sh*t.

---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------

Here we go (#3.1): http://www.overclock.net/a/how-to-m...in-linux-with-some-general-extra-speed-tweaks

The overclock.net guys generally seem to know their sh*t, so they say fstrim works on f2fs on mainline Linux, so I guess I'm right and we need updated sources. :good:
[Samsung Galaxy Nexus] metalspring:
Yeah, I figured we needed an updated fstrim (which I believe [MENTION=2838735]aosp[/MENTION] is looking into), but until then discard doesnt seem to have too negative an effect to use until then.

Also, that first article showed just why background_gc (garbage collection) might be helpful-
[Samsung Galaxy Nexus] osm0sis:
Yup. I definitely agree with background_gc. :)

volume_id got f2fs support in busybox 1.22.0: http://www.busybox.net

CM has it in their 11.0 branch: https://github.com/CyanogenMod/android_external_busybox/commits/cm-11.0

So maybe fstrim gained awareness as well? What version is your built-in using?

Edit: Hmm the f2fs commotio build uses busybox 1.22.1 so you'd think it would work. :(

That AnandTech quote would also explain why discard isn't as detrimental on f2fs; it doesn't have to start trimming on overwrites until it's filled all the empty blocks. :good:
[Samsung Galaxy Nexus] Punkiderma:
SUCCESS! (well, it was a really stupid and easy thing, but since I just know how to flash something on android,it took me some time to understand what I needed to do)

I compared original slimkat updater script to vanir f2fs one and to grouper's f2fs slimkat, so I understood what lines needed to be replaced and how. Then, I replaced original boot.img with the one from vanir f2fs.

I've got some problem with zip (today life's lesson: just replace files inside zips, because if you extract/compress again it probably won't flash, making you mad), but now everything seems to work like it should!

If someone is a slimkat user and want to try, here's the link, try at YOUR OWN RISK, I'm not a dev I just tried sticking things togheter (weekly 5.4):

http://dropcanvas.com/4v1dy/1

NOTICE THAT I removed some apks that are useless for me from system (like faceunlock, email, exchange and others) so check and re-add them if you need them!
[Samsung Galaxy Nexus] metalspring:
Hmm, I'm still thinking that suspend_trim would be better than discard but since fstrim isn't working yet it would be pointless. I have noticed random pauses while running I/O tests, which may be due to discard? I'll have to make another test zip without discard to see

Edit: unless you want to make one and add in all the synapse stuff too [MENTION=4544860]osm0sis[/MENTION]? There aren't any kernel side changes that really need added at this point, just ramdisk. Btw, only remove the discard mount options, I tried adding in the rest of the mount options you had before and it just sits at the Google logo
[Samsung Galaxy Nexus] osm0sis:
Maybe. Theoretically it shouldn't matter until you've filled the storage with data and blocks to be trimmed.

But yeah, until we get busybox fstrim working there's no suspend_trim. The Android kernel's trim daemon might still work though, someone will have to get to 24h uptime and then leave their device alone for a couple hours with more than 80% battery and check the logcat.

---------- Post added at 01:37 PM ---------- Previous post was at 01:25 PM ----------

Nah, you go ahead. Most of those mount options were to cut down on ext4 journaling getting in the way of I/O performance, so I don't imagine they'd agree with f2fs. :)

Looks like Android's trim daemon is actually ROM-side in the vold: https://android.googlesource.com/platform/system/vold/+/master/fstrim.c

Not sure if changes are required yet, still reading it through.

Edit: Doesn't look fs specific, other than skipping vfat, so should be good, as long as the vold supports it.

Hopefully someone can confirm it's working like I outlined above. :good:
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=4328678]metalspring[/MENTION]

mkfs: add option to disable trim at format · fef98eb · CyanogenMod/android_external_f2fs-tools · GitHub - http://goo.gl/hR5eWq

f2fs-tools: discard is default but not set in config · d84ab2d · CyanogenMod/android_external_f2fs-tools · GitHub - http://goo.gl/EzRqXZ
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION]

Merge f2fs support by [MENTION=4308097]aeroevan[/MENTION] · 51881db · PhilZ-cwm6/android_system_vold · GitHub - http://goo.gl/PIh7FF
[Samsung Galaxy Nexus] drmxmyt:
working great! i was wondering who would do the slim's f2fs first. thanks alot.:good:
[Samsung Galaxy Nexus] osm0sis:
Good to know! Is that already in VanirF2FS? If not, we need it. :)

Here's busybox's: https://github.com/CyanogenMod/android_external_busybox/blob/cm-11.0/util-linux/fstrim.c

Looks good, but it all depends on your linux/fs.h include supporting f2fs, so that is probably the key.

---------- Post added at 02:16 PM ---------- Previous post was at 02:05 PM ----------

http://en.wikipedia.org/wiki/Not_a_typewriter#Occurrence

Must be f2fs missing in linux/fs.h causing the io error. :good:
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] has support and he will update f2fs like [MENTION=5380162]pattyboi:)[/MENTION] and [MENTION=4328678]metalspring[/MENTION] did with [MENTION=4898097]arter97[/MENTION] backports ;)

f2fs: support 3.0 · 4365e8a · HybridTeam/HybridMix · GitHub - http://goo.gl/T1mjc0

fs: import f2fs from git://git.kernel.org/pub/scm/linux/kernel/git/jaege... · 0711766 · metalspring/DirtyV_tuna · GitHub - http://goo.gl/kqDBuq
[Samsung Galaxy Nexus] bsmitty83:
My kernel is using those back ports , has been since f2fs worked

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Right.. The vold patch is ROM-side though, so you didn't really answer my question. ;)

To have the Android trim daemon running like it should VanirF2FS should add the PhilZ vold commit you posted above if they haven't already. :) :good:

---------- Post added at 02:58 PM ---------- Previous post was at 02:55 PM ----------

I think he just switched to using the squashed commit instead to keep it clean:

https://github.com/metalspring/DirtyV_tuna/compare/testing

Not sure if there are any newer changes included or not.
[Samsung Galaxy Nexus] bsmitty83:
Yes there is a lot of newer commits from DerTeufel's devilkernel (sgs3/note2) in my kernel .

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
But flush_merge mount option is broken/missing in your original source
[Samsung Galaxy Nexus] bsmitty83:
I'm still using the same initial source for f2fs as aosp keeps linking me . I just added commits to it , is flush_merge mount option broke in the kernels you posted ? I'm confused at what your talking about

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
In your kernel source, the option for flush_merge is somehow missing, so trying to use the mount option flush_merge causes it to not boot

I think somehow you missed it in this commit-

https://github.com/bsmitty83/DirtyV_tuna/commit/a862121cfe9543059206599b4e3a0945dc719a4f

Just search for flush_merge and you'll see its not there, whereas the commit I added does have it and flush_merge works-

https://github.com/metalspring/DirtyV_tuna/commit/0711766d3b2a3ce88fe099d571e920cd3dc9c487
[Samsung Galaxy Nexus] bsmitty83:
K I'll find it , working on some other things ATM

Hack The Tuna
[Samsung Galaxy Nexus] piterdemon:
New file system is awesome !! Rom is much snapier and smooth :good:

Wytapatano z Galaxy Nexus VanirF2FS
[Samsung Galaxy Nexus] AbhishekS:
Has a f2fs kernel been compiled with the 50% boost commits?

Pretty excited to test out that combo!
[Samsung Galaxy Nexus] osm0sis:
Yup. metal posted a f2fs-test2 a few pages back. Gogogo! :)
[Samsung Galaxy Nexus] redj12:
I can't see any difference between Dirty/50% boost and the regular Dirty version. Maybe I have to do something special to see the difference ? Hihi

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] drmxmyt:
i think other than benchmarks its hard to notice it.

here is bench results:

first is smitty's kernel what is shipped with vanir rom, second is metalspring's test kernel.
[Samsung Galaxy Nexus] metalspring:
A little off topic, but let the m8 f2fs experiment begin ;)

https://github.com/metalspring/android_kernel_htc_msm8974/commits/kk44

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8 (6.43.6 should have the format partition to f2fs/ext4 switch)

Plus some cherry-picks for the rom :P

Btw, someone should post in philz thread that toro, toroplus, and maguro should also get the recovery update to allow f2fs conversion, I would but I already requested that for the m8 earlier :(
[Samsung Galaxy Nexus] xzilem:
Wifi Tethering

Hi there, can anyone confirm that wifi tethering/hotspot doesn't work in commotio + smithyv f2fs?
[Samsung Galaxy Nexus] bsmitty83:
Its not gonna work its missing the hostapd binary from my ramdisk .

Hack The Tuna
[Samsung Galaxy Nexus] dezful:
Somehow, I always got google logo bootloop when attempting to boot to f2fs recovery. It happened in the past 48 hours. ROM: Vanir commotio; Kernel: Metal DirtyV f2fs with test. :)
[Samsung Galaxy Nexus] michierusama:
Same with me. So I flashed ROM again. And all good. Sometimes I got ramdom reboots.
[Samsung Galaxy Nexus] David 617:
Sooo glad I popped back in here to read this. This would be awesome for the m8. Thanks!!!
[Samsung Galaxy Nexus] metalspring:
Check out what /data /system and /cache say ;)

Edit: [MENTION=4090196]David 617[/MENTION]

https://plus.google.com/105124080515059221046/posts/YoiJKcgKTrE
[Samsung Galaxy Nexus] David 617:
Nice :D
[Samsung Galaxy Nexus] pvkiniyan95:
sioplus it is...the best consistent i/o scheduler for gnex, comotio f2fs + dirtyv metal f2fs test + sioplus at RAB 512

Read 33.27MB/s Write 23.04MB/s

i hit around these values consistently for almost 10 tests, try it

but ram speed never crosses 787MB/s for me
[Samsung Galaxy Nexus] paarthdesai:
touch control substitute :D :D

http://xdaforums.com/xposed/modules...rect)|utmcmd=(none)&__utmv=-&__utmk=190073768
[Samsung Galaxy Nexus] AbhishekS:
It does need support from the kernel too. Does Dirty_V have those stuff? I don't think so.

And above all its a Xposed module. Not of use for people using ART. :(
[Samsung Galaxy Nexus] sagara.sandaru:
Finally did it! I'm on f2fs now. Commotio build is smooth and battery life also seems great. Great work [MENTION=2838735]aosp[/MENTION] [MENTION=1533050]bsmitty[/MENTION] [MENTION=4544860]osm0sis[/MENTION] and [MENTION=4328678]metalspring[/MENTION] thanks for ur hard work! [emoji4]

Hope it will be available soon.. Can't wait to test it! Count me in if u want any pre release testers,,

---------- Post added at 05:39 PM ---------- Previous post was at 04:53 PM ----------

I'm on f2fs Commotio build and it says GPS was on all the time.. I had location tuned off all the time.

---------- Post added at 05:42 PM ---------- Previous post was at 05:39 PM ----------

And in Privacy guard it says location is running by Android System.

Am I the only one???
[Samsung Galaxy Nexus] Atento:
Guys, what do you think about make a new thread with the kernel and all "pat

ched/modified" roms?

I think it would organize all the information.
[Samsung Galaxy Nexus] calebv2:
This has been asked and answered a few times already. They said they will make another thread when they get a chance. Please if all possible read back a few pages before you say something. Thank you.
[Samsung Galaxy Nexus] bsmitty83:
Not really a point seeing as there is only one kernel , recovery and ROM ATM . its still pretty early in the development and a new thread will come . but for now , all the f2fs stuff is in one spot its just here instead of its own thread .

Hack The Tuna
[Samsung Galaxy Nexus] GilGameshn1:
I love you man . [emoji106]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
Slimkat f2fs works too
[Samsung Galaxy Nexus] Atento:
It's OK but, at least, you could update op with the links for the kernel and the rom. It would avoid posts asking for them.

Edit: There are 3 roms working with f2fs already.
[Samsung Galaxy Nexus] michierusama:
I think all that work will be done in the official thread. With detailed info. So there is not reason for rushing :P it will be when the time comes.
[Samsung Galaxy Nexus] bsmitty83:
The info is everywhere . I'm not going to be the solo f2fs thread here . anyone can start a thread . when I add one it will be mainly for the recovery / kernel . ROM threads can add their f2fs ROMs to their respective threads . I can't keep everyone's homemade ROMs straight and make links etc . sometimes I have to go to work , raise my kids , tend to the wife .......

Hack The Tuna
[Samsung Galaxy Nexus] Atento:
Sorry if I mean rude. Take your time.

I stopped right here asking for organization.
[Samsung Galaxy Nexus] dezful:
what are those three? :)
[Samsung Galaxy Nexus] Atento:
Vanir, carbon and slimkat
[Samsung Galaxy Nexus] michierusama:
Vanir nightlies? Im interested
[Samsung Galaxy Nexus] dezful:
wow carbon?! could you show me the link for carbon f2fs?
[Samsung Galaxy Nexus] pvkiniyan95:
wooow...that escalated quickly :p
[Samsung Galaxy Nexus] pattyboi:):
woahh woahhh..

i think everyone should lay off smitty a little..

he did just work his ass off for a long time guys..

im just as excited as everyone for f2fs to come to more roms,

but its still early,

and we are still basically beta testing

give it time..

good things will come

smitty and aosp cant do everything by themselves guys
[Samsung Galaxy Nexus] jhonnyx:
or you could start a thread to help, give a hand to the devs ;)

EDIT: wanted to say F2FS is a good advance for GNEX and wanted to thank Smitty and AOSP, for their effort and research on the matter.
[Samsung Galaxy Nexus] Royal King:
Ok, so after a lot of hassel, I was able to push the two files on my sd. Now while flashing via TWRP, it shows copying files since almost 5 mins. What should I do? It never takes so much time on CWM. Is it normal guys? :(
[Samsung Galaxy Nexus] jhonnyx:
if you're copying files, you're not "flashing". I assume you're talking about F2FS Kernel. Why don't you ask the question in the proper forum? The dev forum is regarding development or more technical questions

http://xdaforums.com/galaxy-nexus/help

Sorry to be rude, dude, but, you should ask there.

EDIT: Btw, say hello to the F2FS support thread
[Samsung Galaxy Nexus] _hz:
Have i missed a smitty_v version with f2fs support?

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] calebv2:
... Deleted
[Samsung Galaxy Nexus] Royal King:
Was definitely flashing. The recovery was deleting the files. God alone knows why. Anyways got it figured out. Working great now :)
[Samsung Galaxy Nexus] _hz:
Haha ;)
[Samsung Galaxy Nexus] bsmitty83:
No worries man , I didn't take it as rude , you have valid points and wouldnt mind adding a new thread , I just have some things to do first , like put a new kernel out since its been a month lol , I'll get something up soon .

I switched to philz cwm , it has f2fs/ext4 support , and its working nice . its also extremely easy to compile unlike twrp which I will still keep available.

As soon as I get a chance to write out the op which needs to be pretty specific for all to be able to follow . converting ROMs to full f2fs is also a very easy thing . actually now that we have the correct mount options , there is very little needed to actually convert to f2fs .

So again you guys know me by now . I'm never offended by anything and usually my answers are short cause I'm responding while at work or something lol .

Hack The Tuna
[Samsung Galaxy Nexus] shadowam:
Hey [MENTION=4608636]bsmitty83[/MENTION], sorry to disturb you but since you are working on a new kernel, could you please take a look at the new 'touch control' Xposed module? Thank you very much!

http://xdaforums.com/xposed/modules/app-wake-gestures-v1-0-t2768266
[Samsung Galaxy Nexus] redj12:
This is kernel is really nice but my battery is too bad, so back on regular DirtyV version.

I have a question. I am looking for some information about Synaspe but can't find noting.

Actually, what is Synapse and for example, what is the difference between this app and Trickster ?

Envoyé de mon Galaxy Nexus en utilisant Tapatalk