yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4692894]dezful[/MENTION] , its definitely good now , I don't know what happened but I re compiled again and it booted . its the same link in the op . download away ;)
[Samsung Galaxy Nexus] Shadow Death:
Nah, I'm waiting for an Omni FML f2fs before I jump to f2fs. This is the ext4 version.
[Samsung Galaxy Nexus] dezful:
wohoo.. Yes, it's working now. My gratitude for the kernel. :D
[Samsung Galaxy Nexus] Tribes11:
I wish I had the opportunity to have a 4.3 ROM like LiquidSmooth or some other with F2FS support.

I can't stand those random reboots with KitKat when watching whatsapp videos someone sent me, and that music playing stuttering when locking screen with power button... And that's nothing to do with Kernel or ROM version, because it always has occured with Kitkat ROMs on my GNEX
[Samsung Galaxy Nexus] Shadow Death:
Anyone seeing any noticable difference over Ext4 yet?
[Samsung Galaxy Nexus] chongns:
not yet, [emoji20] cause everyone is waiting and asking, so no one is testing, so you question has no answer yet[emoji12]
[Samsung Galaxy Nexus] Shadow Death:
I'll have an answer soon.. I hope :fingers-crossed:

There are other builds for f2fs but I'm mainly waiting on one in particular. :laugh:
[Samsung Galaxy Nexus] dezful:
Introduction Chapter of F2FS vs Ext 4 Thesis: :silly:

http://xdaforums.com/showthread.php?t=2697069
[Samsung Galaxy Nexus] osm0sis:
That was only 3 days ago. I've been busy. I'll try to look into it this week. :)

There were some decent storage benchmarks posted in this thread since we started playing with f2fs too, especially with the mount options metalspring came up with (which we currently use).
[Samsung Galaxy Nexus] calebv2:
For anyone who keep asking here is LS for f2fs it was a few pages back. Thanks to [MENTION=4015637]rkpeterson[/MENTION]. Here are the links you were asking for [MENTION=4596868]Tribes11[/MENTION].
[Samsung Galaxy Nexus] Tribes11:
Yes but this is the KitKat LS, I want a 4.3 ROM compatible with F2FS, is it possible?
[Samsung Galaxy Nexus] calebv2:
Not to be rude but WHY!!! 4.4.3 is way better.
[Samsung Galaxy Nexus] bsmitty83:
check the other thread you asked this in , I answered you there
[Samsung Galaxy Nexus] Tribes11:
Not rude at all, the reason is on previous post... As a matter of fact, I was going to reply you and my Omni 4.4.3 F2FS just rebooted again... :/
[Samsung Galaxy Nexus] calebv2:
I'm actually running version 2 with

pegasusq and custom turnabls thanks to [MENTION=2853378]Nephilim[/MENTION] and running latest LS with f2fs and have really good battery life and no random reboots or problems. [MENTION=4596868]Tribes11[/MENTION]
[Samsung Galaxy Nexus] hdoraemonk:
I think this kernel is fast, but not really smooth. I play game Clash of clans, and few apps, sometime it freeze about 1 second.

I'm using DirtyV-URSR 6-15 with PA 4.4 RC1 official. I think this not rom problem because i tried Franco kernel, it not happen.
[Samsung Galaxy Nexus] gautam_nexus:
I just flashed the latest build. i have always faced issue with Clash Of Clans on this kernel, rest everything is super smooth. I think the [MENTION=4608636]bsmitty83[/MENTION] needs to look at Franco's repos for GPU improvements.

I am also on PA rom RC1 clean flash. glad to see that I am not alone. I have been facing the lag issue on Clash of clans from while being on this kernel from a very long time, but somehow my posts were ignored.
[Samsung Galaxy Nexus] büscher:
I'm on f2fs since about two weeks now.

dirtyV was always smooth for me. The only big difference I really feel in daily usage (I dont play games or watch movies, nor do I copy a lot of files on my phone) is the play store lag that is gone.

I clean flashed CM-Remix and installed all my apps from play store and could set up my phone side by side without annoying lags.

also updates just install and don't make my phone unusable during this time.

I didn't benchmark, soemone else should do it because I cant rely on my phones storage anymore.

I cant tell if apps open faster, for me it "feels" the same like ext4.

But just the possibility to use f2fs gives me one reason more to not buy a new phone. I'm very happy about what our phone is capable. I really think if this one dies I'd buy another Gnex...
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4544860]osm0sis[/MENTION] will u please ask Andreilux if he is OK with fdroid submission, if not I'll take it down
[Samsung Galaxy Nexus] Oehr:
i wuv you :highfive:
[Samsung Galaxy Nexus] chongns:
Hi Everyone or someone :)

flashing the new TWRP is a necessary or it is a option for flashholic ?

i current on the TWRP-TUNA-F2FSALL, the first release of TWRP with F2FS support by ASOP or Bsmitty

thanks
[Samsung Galaxy Nexus] Hetalk:
This new one has some fixes (adb push and sideload issues). Plus it's a newer version. :good:

I know you're a flashoholic, so you need to flash this one. :D
[Samsung Galaxy Nexus] chongns:
that red word kinda confusing me :eek:
[Samsung Galaxy Nexus] bsmitty83:
I was in a hurry and reused the updater script that I used for cwm is all pay no attention
[Samsung Galaxy Nexus] chongns:
is allright, no harm done.. just post out to who didnt notice it. (including you) :laugh:

---------- Post added at 08:14 PM ---------- Previous post was at 08:06 PM ----------

Just flash the new TWRP 2.7.1.1 F2FS/EXT4.

in the recovery, you have to enable the f2fs function in the "Settings"

check the "Force data and cache wipe functions to use F2FS" and the "Include system partition" to turn on (not your mate, but) the F2FS wide function. :p

than you will see a line of "red word" on the TWRP banner.

ok for now, got to find my Gnex, it just slip alway after flash the newest kernel. :laugh:

---------- Post added at 09:01 PM ---------- Previous post was at 08:14 PM ----------

Before and After

it look like free space it not a speed cutter.
[Samsung Galaxy Nexus] gohamstergo:
Bring a charger
[Samsung Galaxy Nexus] chongns:
full charge the phone, and shutdown the phone.

this is the best way i know :p
[Samsung Galaxy Nexus] bsmitty83:
stop watching so much porn ? [emoji33]lol

really the only way is to not use the screen a lot , it drains the battery by far the most . or if your on LTE , kill the modem . or buy a bigger battery .

Hack the Tuna
[Samsung Galaxy Nexus] Wlld1:
Guys, is there any way to fix lockscreen background blur?
[Samsung Galaxy Nexus] Hetalk:
It's not a kernel/recovery thingy. You must post it in relevant ROM thread.
[Samsung Galaxy Nexus] jhonnyx:
Battery In B4 Porn
[Samsung Galaxy Nexus] ashclepdia:
or do what I did a long long time ago, buy the samsung oem external charger&stand. it comes with a battery ALSO. and when I bought it two years ago it was only $20, so I think for $20 NOW you could probably get two oem extended batteries AND the external charger that comes with an OEM battery. then just wear cargo shorts and carry your extra batteries when you go out lol. I used to have 4 batteries(2 oem extended, 2 oem regular) but dropped one of my extended in a puddle one day :(

there really isn't many tweaks you can do to improve gnex battery life, it's all main system settings stuff(like for me I use airplane mode ON with wifi toggled on, and get pretty good battery life since no longer have carrier anyways).

there IS something you can do to improve screen on time that I've done for a while, but is really only good if you are indoors or at night time, but can extend screen time pretty nicely.

go to color multipliers in trickster, save a profile where you turn all multipliers down to UNDER 100(lowest allowed in trick is 60, after that it gets REALLY low anyways and hard to see). then when the sun goes down, set that profile on, the screen will become MUCH darker, and will use WAY less battery.
[Samsung Galaxy Nexus] osm0sis:
Ask the guy yourself. I don't hold any special sway. Send him an email. :good:
[Samsung Galaxy Nexus] JuanG:
Can I flash DirtyV 6-15 with normal TWRP or I need change the recovery to the new versions of the first post? Thanks!!
[Samsung Galaxy Nexus] xxSAKISxx:
Sure you can. Go for it.
[Samsung Galaxy Nexus] Culex316:
Does undervolting the screen help? (The Vaux regulators)
[Samsung Galaxy Nexus] d0ge01:
yeah, but you forgotten 2 things

If you sell you phone, new owner can recovery all your delete data ( with encryption he can't )

for work's security rule, like my case
[Samsung Galaxy Nexus] Shadow Death:
Never use your personal phone for work purposes.
[Samsung Galaxy Nexus] alfiemenace:
where's the latest f2fs vanir?
[Samsung Galaxy Nexus] HONG86:
Well...I flashed 'TWRP-2.7.1.1-F2FS/EXT4-MAGURO'

I can't find f2fs-ext4 converting option...:crying:

anyway, I wipe dalvik and cache

and can't into rom.

google logo is ok, but rom loading screen keep going forever...

so I flashed rom again, but still boot fail...

I check whole setting... and find cache patition gonna ext4...:confused:

I changed whole partition to f2fs before... but after wipe, I gonna ext4 automatically.

so, I flash 'TWRP-F2FS/EXT4-TORO,TORO+,MAGURO'

change cache patition to f2fs, it works great.:victory:

It may become limited to the case of me,

But there could be a matter of recovery by any chance , please check. thx :highfive:

sorry for bad Eng :o
[Samsung Galaxy Nexus] israelian:
Here's the option on TWRP-2.7.1.1-F2FS/EXT4-MAGURO you're looking for:

http://xdaforums.com/showpost.php?p=53429492&postcount=10440

;)
[Samsung Galaxy Nexus] HONG86:
Thanks pal.

I didn't catch it :o
[Samsung Galaxy Nexus] jkleo:
I'm still getting Google logo boot loops with the latest DirtyV UR. CAB and FSync are both off, did not change anything and it still boot loops whenever I reboot from the ROM (SlimKat). Using EXT4. Is this no longer happening to majority of the DirtyV users?
[Samsung Galaxy Nexus] dezful:
No problem on F2FS :)
[Samsung Galaxy Nexus] jkleo:
But this has been happening since before F2FS. I was just waiting to see if it gets fixed but seeing how no one has said anything about it with the latest version I decided to mention it. The workaround I have been using is rebooting to recovery then reboot system there.
[Samsung Galaxy Nexus] qu4nd:
I'm using latest smittyV UR on ext4 Vanir 4.4.3 without any issues!
[Samsung Galaxy Nexus] Ziyan:
[MENTION=4608636]bsmitty83[/MENTION] how did you compile without this? lol, it instantly errored out for me without that equal sign.

Anyways, I'm going through Mpo's commits, to see if there's anything interesting left there :confused:
[Samsung Galaxy Nexus] gummie:
So how about considering chances of having S2W/S or DT2W and T2W get cooked in the Kernel?

Edit: Sorry for the nuisance, found it by changing keywords - Here, maybe [MENTION=3685904]ak[/MENTION] could help on DT2W since my Mako already has it (no slides still getting used to it).
[Samsung Galaxy Nexus] chongns:
in recovery, go in setting, select that 2 itmes, than only wide the phone.
[Samsung Galaxy Nexus] bsmitty83:
those flags are redundant , I've been meaning to remove them , except for the vectorize-with-quad , which I was going to move with the rest of the cflags . but it builds fine for me . what error was it throwing you ?

Hack the Tuna
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4608636]bsmitty83[/MENTION] my SwiftKey keyboard (secondary server) gets killed all the time with the newest DirtyV Version from the 15th of June. Did you change anything related to the Memory Management?

And the unified version you posted before (I think it was a SmittyV) is not in the OP. The last it from the 6th of June.
[Samsung Galaxy Nexus] bsmitty83:
I don't I have changed anything lmk related , that's odd

I'll add the version that's missing to the old versions

Hack the Tuna
[Samsung Galaxy Nexus] poo706:
I'm on 6/9 and I just had the issue yesterday. EXT4 and LiquidSmooth.

[poo]
[Samsung Galaxy Nexus] jkleo:
I had it on 6/9 as well. I wonder what is causing this [emoji45]
[Samsung Galaxy Nexus] dbh369:
[MENTION=1533050]bsmitty[/MENTION], [MENTION=4015637]rkpeterson[/MENTION]: So loaded this up as f2fs, working great, but lag fix tells me trim is not supported? Thought that was the point of f2fs build...
[Samsung Galaxy Nexus] NeverSeparate:
I thought lag fix was unnecessary Since 4.3. Doesn't the system do it on its on?
[Samsung Galaxy Nexus] AndreiLux:
A notice to everybody out there:

It is not OK to submit an application other than your own to a marketplace without asking the actual author of it for permission.

It is not OK to ask in some random third-party person if it is alright to do it after you have already done it.

It is not OK to submit an application that is licensed under MS-RSL to an open-source app repository like F-Droid, you are not only making fools out of the developer, but also of F-Droid and open-source apps.

People like you should be banned from the site.
[Samsung Galaxy Nexus] pvkiniyan95:
the thread in fdroid was closed and the app will not be added to the fdroid repo, i apologise for my foolishness
[Samsung Galaxy Nexus] pvkiniyan95:
of course the system does it but only after certain conditions, so lagfix always comes handy
[Samsung Galaxy Nexus] dbh369:
But if trim is not supported, it's not happening via the system or lag fix
[Samsung Galaxy Nexus] Charmacas:
So what are the changes? Because I did not have this issue before this version. Maybe it isn't kernels default but at least I want to ask.

Also I have a question: As the GNex does not have very much CPU power it's often unusable when some process wants 100 % power. Is it possible to give 100 % only to foreground processes. Background processes shouldn't get that much I think. I know something on that direction was done by [MENTION=4615478]boype[/MENTION] with the cgroups implementation but maybe we're able to push it a bit further!?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
the only changes between the 2 kernels were f2fs related

as for your 2nd question , I really don't know ...

Hack the Tuna
[Samsung Galaxy Nexus] creeve4:
[MENTION=4608636]bsmitty83[/MENTION]

Occasionally when I reboot, my phone gets stuck in a bootloop at the bootloader. Is there any log I can get at this point?
[Samsung Galaxy Nexus] Punkiderma:
For me is the same, which Rom are you running? I'm on slimkat, latest weekly

On my phone even this doesn't work anymore :l have to completely switch off my device from bootloader screen and then power it on again

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
LagFix includes their own binary which may or may not support f2fs, their app may also be restricting it to ext4. The point of f2fs is that it's fast as ****, and doesn't even actually need to be trimmed until the storage has completely been filled and it has to start overwriting old blocks of deleted data.

LS and Vanir have the f2fs vold patches which should allow the system to trim when uptime is >24h, idle for an hour and battery is above 80% unplugged or (something like) 40% plugged.

For those crack flashers who never reach 24h because they're mainlining nightlies, I altered suspend_trim for this purpose and it should work for both f2fs and ext4 (though I still need confirmation on f2fs). We've made LagFix obsolete. ;)
[Samsung Galaxy Nexus] Ziyan:
Makefile:363: *** missing separator. Stop.
Makefile:130: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2

I use Arch Linux btw, so my packages are always the latest, in this case, it may be Make 4.0, maybe your system uses an older Make, which accepts it...?

In the meantime, take a look, I think some of these commits could be cherry-picked to the "original" DirtyV too ;)
[Samsung Galaxy Nexus] osm0sis:
I've seen a few places that make 4.0 is ****ed. I think everyone likes 3.81. :)
[Samsung Galaxy Nexus] bsmitty83:
I'm OK on the mpokang commits . not my cup of tea .

Hack the Tuna
[Samsung Galaxy Nexus] Ziyan:
Ignore the ram speed commits, we've already decided that, I meant some of the other commits, they look fine to me :cowboy:
[Samsung Galaxy Nexus] BestBrd:
Sorry,i'm running commotio build+lastest dirtyv f2fs...i noticed that otg doesn't work,anyone can confirm that? Is it normal? Last time i used otg i was on the first builds of this kernel(i miss touch wake option

?) so i don't know if and when he stopped working...
[Samsung Galaxy Nexus] Droiderat:
Yes, I'm still getting Google logo bootloops, My workaround is to reboot via bootloader (faster than going via recovery).
[Samsung Galaxy Nexus] bsmitty83:
I just don't get it , I've been sitting here rebooting my phone for an hour straight , literally just reboot after reboot , have yet to have a bootloop . I'm beyond baffled at this . it has to be something conflicting with the boot.IMG . I've tried and tried to reproduce this on my end and can't . I never have been able to , this isn't the first time I've tried . so idk what to do about it . [emoji53]

Hack the Tuna
[Samsung Galaxy Nexus] Droiderat:
[MENTION=4544860]osm0sis[/MENTION]

It would be nice if you could fix the Synapse hooks on the recent kernels. I installed SmittyV-UR-6.15.14, and then tried to load my Synapse profile, and ended up with a crapload of error messages.

... and back to cwm-DirtyV-RSR-5.3.14-2-Synapsed we go.
[Samsung Galaxy Nexus] pattyboi:):
+1,downloaded and flashed and i dont get the reboot bug either,been doing it for 30 mins
[Samsung Galaxy Nexus] poo706:
Have we ever explored a correlation with xposed (assuming that's even possible) or ART? I can say I have the Google logo bootloop sometimes and I'm using xposed and of course dalvik.

[poo]
[Samsung Galaxy Nexus] pattyboi:):
i dont "think" xposed itself could cause the issue of course,i mean,a module from xposed exploiting something hardware wise on our gnex could do that,but i dont think there is any modules for xposed that do anything hardware wise for us,as for ART im un sure,i doubt it,as i know ART code is ONLY used when its chosen as the run time,good thoughts tho bro (ps,to anyone who knows more than me,correct anything i say that is wrong please)
[Samsung Galaxy Nexus] osm0sis:
Can you elaborate? I'm on 6-15 and it has the latest and greatest I've committed for Synapse. I don't see any errors at all. If you're using an old profile you might need to redo it since I fixed the config profile ownership on restore (should allow people to share profiles as well).

Edit: I take that back, [MENTION=4608636]bsmitty83[/MENTION] must have missed updating his local ramdisk with the commit for Dynamic Dirty Writeback control removal when he did 6-15. No biggie though, it's just 3 errors and backup/restore broken until the next build. :good:

I use Xposed and Dalvik and I went ages without the logo loop, then a month back I got it bad again. Clean flash fixed it. It's not ramdisk related since it's never happened on franco.Kernel and we've got the exact same base.

My theory is that it's either corruption of some kind, or, something left over from one of the attempts to inject a kernel bootsplash after the logo. The first makes more sense with the sporadic nature of it and wipes fixing it, and the second makes more sense with the timing during the boot.
[Samsung Galaxy Nexus] bsmitty83:
I think my phone got stuck in a bootloop once in the past few months , I cleaned the cache , rebooted and haven't seen it since .

Hack the Tuna
[Samsung Galaxy Nexus] jcooler:
Sorry to hear that man. That sucks.
[Samsung Galaxy Nexus] creeve4:
I'll do more experimenting in an attempt to narrow down the number of potential causes. [emoji106]
[Samsung Galaxy Nexus] DR3W5K1:
That sucks man!

If it helps at all i got robbed at gunpoint in my driveway one time.

Takes awhile but then you realise it could be worse. They didn't shoot and or kill you.

Goodluck bro!
[Samsung Galaxy Nexus] pvkiniyan95:
That totally sucks, sorry man....may be something good can happen out of it, hope for it
[Samsung Galaxy Nexus] demlv:
FYI - wiping your phone and reinstalling ROM does not always fix the Google logo boot loops with this kernel. I grew tired of them so I wiped everything and reinstalled. Everything was fine for a couple of days until I flashed DirtyV. The loops returned. I really like the kernel so I have just decided to deal with it. I actually did all of this twice, once with CM11 and another with Slim. Same results both times.
[Samsung Galaxy Nexus] bsmitty83:
have you tried just wiping the cache and dalvik in recovery ? I've never experienced bootloops that bad before but if I do get one that solved it . and i probably reboot my nexus twice as much as anybody here lol

Hack the Tuna
[Samsung Galaxy Nexus] osm0sis:
It also reminds me of a voltage thing, which would explain why it doesn't happen all the time and why some devices are more susceptible than others; not all silicon is made the same.
[Samsung Galaxy Nexus] midnightdevil66:
[MENTION=4608636]bsmitty83[/MENTION] do you have the SmittyV-UR-NoMeM 6.9.14? I deleted it by mistake and that one runs better than 6/15 on my phone. I don't see that one in OP.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
yup just change the date in the link address for the kernel to 6.9.14

Hack the Tuna
[Samsung Galaxy Nexus] creeve4:
Are custom voltages applied that early in the boot process?

I'm trying the trusty KK15 bootloader instead of MD04 to see if that makes a difference.
[Samsung Galaxy Nexus] Hetalk:
Request to anyone and everyone.

Can anyone build and maintain paranoidandroid with all the correct f2fs commits?

BTW I've been using paranoidandroid with my updater script changes and it works fine.
[Samsung Galaxy Nexus] gautam_nexus:
the one posted here is it not working fine?

http://xdaforums.com/showpost.php?p=53466740&postcount=40366
[Samsung Galaxy Nexus] Hetalk:
Lol I made the 1st f2fs PA build using this workaround.

I just want to see it done the right way.
[Samsung Galaxy Nexus] osm0sis:
No, if it were voltages it'd be the defaults, perhaps affected by some commit down the line. I seem to remember the logo loop was more prevalent when there were some OMAP 4430 timing patches involved.

I'm just guessing though. My main hunch is still that it's something leftover from a boot splash attempt like I mentioned above.
[Samsung Galaxy Nexus] misterk267:
This info was a lifesaver! Thank you
[Samsung Galaxy Nexus] gautam_nexus:
what is the navigation path to change the partition in the new 2.7.1.1 twrp ?

thanks!

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

maybe you can pick it up buddy with a little help from smitty. :D
[Samsung Galaxy Nexus] Hetalk:
There are couple of other threads (by [MENTION=5056454]sd3993[/MENTION] and [MENTION=4710962]-Jesco-[/MENTION] ) with unofficial PA builds. Hope one of those 2 threads can accommodate the correct f2fs commits in their builds.

I don't want to make another PA thread just for this.

Let's see how it goes.

Also, I'm not sure I'll be able to build ROMs on my windows pc (windows 7 at work and windows 8.1 at home). :D
[Samsung Galaxy Nexus] Droiderat:
I use ART (and I have the bootloop issue).
[Samsung Galaxy Nexus] sd3993:
I'll give it a shot. :)

Just waiting for my GNex to return from repairs. USB port got jacked :/
[Samsung Galaxy Nexus] Hetalk:
In case you wanna build latest PA it with f2fs commits (you can find more info on this thread), go ahead and build it. I(am few others on this thread as well) can test it for you. Then you can proceed and release it on your thread. JMO :good:

---------- Post added at 12:23 PM ---------- Previous post was at 12:17 PM ----------

I'm on Dalvik without xposed and have this bootloop issue as well.:confused:

I've been having it for some time. I stopped using the reboot option altogether.

I just tried this to see if it's still an issue for my device.
[Samsung Galaxy Nexus] sd3993:
I'll ping you on hangouts. I'm a noob regarding f2fs and will do a study later at night when i'll have lots of time. ATM i just need to know a few things. :)
[Samsung Galaxy Nexus] piterdemon:
Hahaha imposible :D

Wytapatano z Galaxy Nexus 4.4.3 PA