yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Shadow Death:
From what I undertand Philz has gone down hill since Phil himself stopped maintaining it.
[Samsung Galaxy Nexus] bsmitty83:
I updated the op with TWRP recovery . I can't seem to get philz to read ext on the /data partition . so I removed them until it fully works .

Hack The Tuna
[Samsung Galaxy Nexus] cujo6801:
Well you know what that means bro...

You just went from a god to a demigod.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
look at the thanks number...:eek:

666 = # of the beast

6666 = # of the Smitty
[Samsung Galaxy Nexus] bsmitty83:
lmao [emoji83]. you got me , I was sent to cause chaos and trouble .

patty , what troubles you having with your kernel ? is it f2fs ? if so let me know , I'm sure I can help .

Hack The Tuna
[Samsung Galaxy Nexus] pattyboi:):
its for askp,i use the same exact backports for f2fs from arter,but it wont build,ive included every commit i can think of but i still get trace errors when it builds,thing thats driving me nuts is that i build my personal kernel just fine,but askp refuses to build :/ if i dont get it build today,ill hit you up on a pm with the exact error (if your cool with that)
[Samsung Galaxy Nexus] bsmitty83:
yea no problems , I can always clone it and see what I get as well [emoji6]

Hack The Tuna
[Samsung Galaxy Nexus] pattyboi:):
if you want to bro :P thanks :3
[Samsung Galaxy Nexus] bsmitty83:
kernels I don't mind building , they take like 15 min , I'm sooo sick of ROMs and recoveries lol they take a lot longer

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
Kernels are sexier
[Samsung Galaxy Nexus] pattyboi:):
i couldnt even wait enough for rom source to download,i have no patience
[Samsung Galaxy Nexus] Bosio91:
Where can I find the latest synapsed version of DirtyV? Could someone please post a link to it? Thank you :)
[Samsung Galaxy Nexus] sagara.sandaru:
on OP! all the three versions are Synapsed. :)
[Samsung Galaxy Nexus] ashclepdia:
settings>storage>partition info shows it as FAT(i always wondered why FAT was used, I don't know all specifics on fs types lol)...I cant even say if that's fully accurate or not, just what I've always seen lol
[Samsung Galaxy Nexus] Nephilim:
rkpeterson is going to be building f2fs versions of the latest LiquidSmooth so hold tight for a short bit, I'm sure he'll have them out in no time. ;)

Sent from my Android 4.4.3 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
He still makes commits all the time to both CWM and PhilZ. What are you talking about? :confused:

Is that on ext4 or f2fs? I think it's okay for everyone booted though right? Which means it isn't FUSE or sdcard daemon at fault. Recovery is a whole other method.. Maybe vold, or a recovery.fstab problem?
[Samsung Galaxy Nexus] Sik-1:
No links to 6-13-14???? The op links don't match up
[Samsung Galaxy Nexus] bsmitty83:
that was for the recovery that was updated yesterday
[Samsung Galaxy Nexus] Shadow Death:
Someone told me that he's backed off while other guys have taken over the development. The person who told me is on a One m7 though so more than likely it's the maintainer for that phone. I could very easily be wrong, that's why I didn't claim to be right. :P
[Samsung Galaxy Nexus] rkpeterson:
Latest and greatest LiquidSmooth F2FS

http://www.mediafire.com/download/9p87q8324ir8br4/LS-KK-v3.1-F2FS-2014-06-14-maguro.zip

http://www.mediafire.com/download/momu6487m646aoj/LS-KK-v3.1-F2FS-2014-06-14-toroplus.zip

http://www.mediafire.com/download/j03odtjnu80fajk/LS-KK-v3.1-F2FS-2014-06-14-toro.zip[COLOR="Silver"

---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------

[/COLOR]Smitty over the next week I plan on trying to build LiquidSmooth f2fs with your kernel inline, any tips?
[Samsung Galaxy Nexus] bsmitty83:
I just grabbed koushs anykernel from github , but thanks for that . I'll check your out for sure ..
[Samsung Galaxy Nexus] nickdc986:
Does it work on cm11?
[Samsung Galaxy Nexus] bsmitty83:
no but now its on the todo list
[Samsung Galaxy Nexus] osm0sis:
Yeah Koush's is broken and kinda awkwardly scripted. Definitely give mine a read through. :)
[Samsung Galaxy Nexus] fracama87:
ehehe I known vaux3 from some months but I didn't know a lot of other :)
[Samsung Galaxy Nexus] Firewalker1980:
I've had it too this morning on DirtyV2-SR-Linaro (using Nephilim's settings). Candy Crush Saga crashed all of a sudden and the phone was pretty hot and crashed too.

I lowered the GPU to standard setting. Also on Interactive sometimes I needed to press the power button 3 times to get it to turn on the screen.

I don't have a logcat though. Should look into how that's taken, never done it before. But I thought it would be worth mentioning the issue anyways.

Other than that... very snappy and stable.
[Samsung Galaxy Nexus] cartman333:
Can someone please give me a simple explanation about the differences between Sabermod and Linaro? :D i can't find anything on google, and i really want to know what im flashing :D
[Samsung Galaxy Nexus] Firewalker1980:
Different set of optimizations of the Linaro Toolchain, if I'm correct ;)
[Samsung Galaxy Nexus] juju2011:
My maguro seems to hate sm builds had sod last night on charger with nephs settings tried every governor an got a sod so switched back to linaro 4.7 and not a single problem :/ would've tried to get a log but happened before I had to go meet the gf and needed a working phone .will try again today n see if I can get it to happen again
[Samsung Galaxy Nexus] poo706:
Quick question, little off topic. I've been playing around with building my own ROM to pair DirtyV with. How do I make sure that I'm using Linaro 4.8 with O3 and fstrict-aliasing?

[poo]
[Samsung Galaxy Nexus] metalspring:
You mean building the rom with linaro 4.8, O3 and fstrict-aliasing?

That requires a ton of commits to fix all the aliasing errors in all different repos

What rom are you trying to build anyway, vanir and liquid are already built with everything needed but other roms will need the fixes
[Samsung Galaxy Nexus] juju2011:
I'll try your rom when its conpleted :)
[Samsung Galaxy Nexus] erghetto:
differences between dirty v, superram and your personal build? and superram means no 720p? there is a version with more ram, but still with 720p?
[Samsung Galaxy Nexus] poo706:
It's Vanir I'm building. I've been using openpdroid for a long time and have always relied on [MENTION=4342828]mateorod[/MENTION]'s auto-patcher. The auto-patcher Vanir patches need reworked quite often, which mateor is always cool with. But he gave me instructions on how integrate OPD in the source since I mentioned that I had built Vanir in the past. The 1/26 Vanir broke auto-patcher yet again after we just spent a few days getting it fixed for the 1/25 nightly. So now I'm playing with building my own Vanir with OPD built in, but I'm not positive that my build environment is as ideal as it could be.

[poo]

---------- Post added at 12:26 PM ---------- Previous post was at 12:21 PM ----------

I'm just trying to build Vanir with openpdroid built-in for toroplus. If you have no interest in OPD or are on toro/maguro, just stick with Vanir.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
DirtyV is big mem , my personal build is superram . no 1080p with superram . dirtyV, everything should work .
[Samsung Galaxy Nexus] juju2011:
[MENTION=3927368]poo706[/MENTION] Oh ok I use carbon rom again....had horrible sods on liquid yesterday thank god for my backup :/
[Samsung Galaxy Nexus] Nephilim:
720p works on all of the builds.

Guys, this is getting a little ridiculous now. Please read the thread before asking about the differences in kernel versions. Its been explained multiple times now, just like the linaro vs sabermod question. (Which also does not need to be asked again.)

Reading and using the search tools are part of XDA guidlines.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Unless you change any C/C++ code (which I dont think adding openpdroid will do) or changing the clfags vanir uses (in build/core/combo) you should be fine

if you want to improve optimization any more I think the only thing you could do with vanir is trying to build with c++11, I know they have some patches for it but whether they have all that is needed, i dont know

Try adding this to build/core/combo/TARGET_linux-arm.mk under TARGET_GLOBAL_CPPFLAGS += -fvisibility-inlines-hidden

ifneq ($(DEBUG_NO_STDCXX11),yes)

TARGET_GLOBAL_CPPFLAGS += $(call cc-option,-std=gnu++11)

endif

Or you could try adding any of the clfags I use on my omni builds here- https://github.com/metalspring/android_build/commit/4cf5ecf03cea601428f486df55a042869ca6df45
[Samsung Galaxy Nexus] erghetto:
sorry i meant 1080p.

however theese defferences should stay in first page IMO.

if i see 3 type of the same kernel, the first thing i want to know it's what change from one to one.
[Samsung Galaxy Nexus] poo706:
Ok sweet. I was under the impression that I needed to do something with GCC on my end. I'm not looking to reinvent the wheel, so I'll just leave well enough alone. What about java? On the first build environment I set up, I didn't know what I was doing and ended up using openjdk. When building Vanir, it chastised me for using openjdk instead of oracle jdk, but built and installed just fine. When I set up another build environment on a faster PC, I made sure to follow Vanir's instructions to get oracle jdk. Something wasn't right though and it failed halfway through building, so I said to hell with it and went back to openjdk. If I'm getting successful builds with openjdk, does it even matter? Thanks for your prompt replies, by the way. I knew this would be a good place to ask. And smitty, sorry about getting off topic.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
nice , I've never done that , but you might want to check out [MENTION=4328678]metalspring[/MENTION] 's omni-metal , his dev tree also has the ramdisk in it . my github should be good , I just have to update the defconfigs , so I'll make sure its good for you to use . the ext4 branch should be OK as is , but the f2fs I havent updated the configs in a while and it won't build with it set as is .
[Samsung Galaxy Nexus] bsmitty83:
I just built a new twrp recovery . this one is gonna be a keeper . it's twrp version 2.7.1 , I added ktoonsez f2fs options .

To use , the f2fs options is under settings , check "force data and cache wipe functions to use f2fs" , then another box will appear to also include /system . then use like any other twrp . I'll add it to the op in a few min
[Samsung Galaxy Nexus] demlv:
The new twrp....will it work for all variants or is it device specific?
[Samsung Galaxy Nexus] bsmitty83:
should be OK for all , but if not let me know and I will build all 3 variants .
[Samsung Galaxy Nexus] dezful:
Is this the same version of ext4 with updated f2fs updater script or any other changes?
[Samsung Galaxy Nexus] bsmitty83:
I updated the OP with all the old versions of the kernels for those who wanted them ......:eek:
[Samsung Galaxy Nexus] rkpeterson:
Added vold patch for fstrim support and vanir's commits to build rom with f2fs support, included boot.img is osmOsis Unified dirtyV. Other than that it is straight LiquidSmooth.
[Samsung Galaxy Nexus] bsmitty83:
I updated the configs for the kernel , should be good to use straight from git now
[Samsung Galaxy Nexus] KiD3991:
As of now what's DirtyV and SmittyV's difference? Dirty = Stable, Smitty = Experimental? I'm a long term fan of DirtyV because smittyV dont have onDemand. :P
[Samsung Galaxy Nexus] bsmitty83:
SmittyV is just the way I run my kernel . my personal preferences , both use the same code , just different governors and schedulers , no memory reclaim , different smartreflex .
[Samsung Galaxy Nexus] michierusama:
SmittyV is very Stable :)
[Samsung Galaxy Nexus] dezful:
Everything seems to be smooth. One bug so far on this build: settings > interface > hover always gives me error message. ;)
[Samsung Galaxy Nexus] pvkiniyan95:
ohh yeeeaaaaahhhhh!!!!! its so gud to be back, gues what, my GNEX is back with the bang....managed to save some money and ordered the port and now got my gnex repaired.....right on time to flash the latest DirtyV....the past 10 days were like a husband expecting a child ;)...btw got 30 pages to read on this thread
[Samsung Galaxy Nexus] mrgnex:
Yeah!! Welcome back buddy!
[Samsung Galaxy Nexus] saprer:
bought my phone yesterday evening because my S3 fell down and is dead :/

i have to say great job with this kernel i use AOKP together with this kernel and its uber-fast.

its even smoother than my S3 running cm10.1

got an idea:

Can u make ur own kernel setting app? or support for STWEAKS?

this would rock :)

thx for everything

but got 1 prob with recovery:

it cant mount sdcard all the time so icant flash anything

ps: im not using F2FS (is it worth?)
[Samsung Galaxy Nexus] Culex316:
Why does a recovery take long to build?

A ROM I can understand due to the Java code that needs to be parsed and converted to apk (which takes a loooooong time) but aren't recoveries C++ code (kernel and the recovery "app" itself) ?
[Samsung Galaxy Nexus] dezful:
[MENTION=4608636]bsmitty83[/MENTION]

I found the newest recovery -TWRP-2.7.1.1-F2FS/EXT4- is failed to execute:

assert(getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro");

:)
[Samsung Galaxy Nexus] Marco618:
What is different between DirtyV-URSR and DirtyV-SR?
[Samsung Galaxy Nexus] osm0sis:
We use Synapse, which is like STweaks, but better. (And better to script for). ;)

You using the correct recovery for your device?

Nothing. Read the OPs for more info. :good:
[Samsung Galaxy Nexus] dezful:
There is only one TWRP-2.7.1.1-F2FS/EXT4 on the op, right? :confused:

there is no such issue on TWRP-F2FS/EXT4. :)
[Samsung Galaxy Nexus] osm0sis:
Right. I guess that one was built for maguro, whereas this one is for one of the other variants. ;)

In recovery, flash AROMA Filemanager then open a command prompt and type: getprop | grep product
[Samsung Galaxy Nexus] hp13:
Which version or build date is a stable build for 4.3 Roms? I didn't see it in op.
[Samsung Galaxy Nexus] pvkiniyan95:
i m taking this chance to totally get away from google play services and move to owncloud, my humble request is why not make synapse available in fdroid [MENTION=4544860]osm0sis[/MENTION]

i added it to submission queue, no idea if it was already there
[Samsung Galaxy Nexus] Ziyan:
Hey guys, how do you build your kernels? I've been using my custom kernel building script for other two devices, like this. I'm planning on building this kernel, but - as I never built a kernel for the gnex before -, I don't know which is the best way to do so :D
[Samsung Galaxy Nexus] atoyu:
hi all, i down and install the new twrp 2.7.1.1 in op. but i cant find f2fs option in recovery. please help .thankyou!!
[Samsung Galaxy Nexus] bsmitty83:
check under settings . it's there
[Samsung Galaxy Nexus] bsmitty83:
OK , I didn't know for sure , I'll make a build for toroplus and maguro . although toroplus might be a min since aokp source doesn't have toro+ anymore for some reason .
[Samsung Galaxy Nexus] Atento:
Is there any way to get all the configs from Synapse and make a script to edit the system config files directly? I'm aways using the same config for every version of this kernel and Synapse takes 1 or 2 minutes to apply its configs.
[Samsung Galaxy Nexus] Charmacas:
Is the new TWRP 2.7.1.1 able to adb push? Because with the first recovery smitty posted I wasn't able to.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
should work I adb pushed and side loaded to test . I didn't have any problems.
[Samsung Galaxy Nexus] büscher:
yep with init.d scripts, look in my signature. synapse is able to do a lot more than the script in my sig, but you'll get the idea there.
[Samsung Galaxy Nexus] chongns:
the F2FS are slower to mount than ext4, so wait few mins for it to mount in recovery.
[Samsung Galaxy Nexus] pvkiniyan95:
for all those with adb push annoyance (i m pretty amazed they are still there) why not just buy a otg cable which is so cheap like 2 bucks and copy ur rom, kernel, mods, etc. on it and just mount it in recovery (cwm does it automatically, in twrp u have to manually mount it) and enjoy
[Samsung Galaxy Nexus] bsmitty83:
Op updated , 3 kernels . I patched f2fs up to Linux mainline 3.15

Happy fathers day to all the dads out there . enjoy . [emoji3]
[Samsung Galaxy Nexus] Tribes11:
I've updated to the latest TWRP 2.7.1.1 f2fs and it now says my device is a toro, not a maguro, what's going on here?
[Samsung Galaxy Nexus] Reinvented:
"Android, go home. ur drunk."
[Samsung Galaxy Nexus] bsmitty83:
lol . sorry about that , I wasent sure if I needed to build a recovery for all 3 variants , so I'm doing that now . but until then you can use the multirom twrp link below the new twrp , or remove the lines from the ROM updater-script that check the version of nexus .
[Samsung Galaxy Nexus] crazyeats:
Thanks. Right back at you.
[Samsung Galaxy Nexus] calebv2:
Thank you very much for the kernel your amazing would it be at all possible to add pegasusq.
[Samsung Galaxy Nexus] Danny1976:
I installed the multirom twrp, but when I go to wipe/advance I don't see the change file system option to select F2FS. Am I suppose to select Format Data to change the partitions to F2FS? I just did my Nexus 7 Tablet with the latest TWRP and I was able to keep my internal storage intact and just format the data, cache, and system to F2FS. Is there anyway to do the same with the Gnex?
[Samsung Galaxy Nexus] cujo6801:
So no change for Ext4?

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
in multi ROM its under advanced menu . should be an ext/f2fs switch button
[Samsung Galaxy Nexus] bsmitty83:
no changes . at least none I can think of lol .
[Samsung Galaxy Nexus] bsmitty83:
Maguro twrp is up in the op , toroplus will follow shortly ....
[Samsung Galaxy Nexus] osm0sis:
Not my app, just my scripts. It's the work of [MENTION=4167023]AndreiLux[/MENTION] so I wouldn't feel comfortable submitting it to an app store for him.

Yeah definitely all three required for recovery. Not simple like kernels. :)
[Samsung Galaxy Nexus] mrgnex:
Hotplug governors are not playing nice with this phone. Im sure he could add it and some kernels have but it would be a headache..
[Samsung Galaxy Nexus] bsmitty83:
Toroplus verison is up in the OP

ALL 3 versions should be good to go now
[Samsung Galaxy Nexus] HTID_Pyro:
Thanks for all your hard work [MENTION=4608636]bsmitty83[/MENTION] ^_^

Sent from my Galaxy Nexus running Liquid smooth 4.4.3
[Samsung Galaxy Nexus] calebv2:
I use it every day with neph turnables and never have a problem.
[Samsung Galaxy Nexus] Ziyan:
Anyone?

[MENTION=4608636]bsmitty83[/MENTION] how do you do it? :) I'd like to build the same way you do, with ramdisk, etc...
[Samsung Galaxy Nexus] bsmitty83:
start here . this is where I began . its the best guide I know of .

Obviously it's a little old , so for example the op uses doomlords toolchains , but its the basic ideas your looking at . you have to use common sense and tweak it to work , but I think it'll help

PS a general question like how do I build a kernel is a long lengthy process , I would be much better suited to helping with specific problems . to try to teach someone how to compile a kernel is really tough to do on a thread .

http://xdaforums.com/showthread.php?t=1748297
[Samsung Galaxy Nexus] pattyboi:):
i can tell you how to build the zimage manually lol :D thats the extent of my knowledge xD
[Samsung Galaxy Nexus] Ziyan:
Thanks guys, I know how to build a zImage, but how can I assemble a ramdisk? I can make anykernel2 zips, but ramdisk would be better. I can only do so by replacing the zImage in a working kernel, which is, well, dirty :D or should I simply use boot.img tools to create a ramdisk from the 'ramdisk-DirtyV' directory? :confused:
[Samsung Galaxy Nexus] bsmitty83:
the only way I know how to compile a full boot.IMG is to use a ROM source and your kernel source. then instead of making the ROM you can use "make bootimage" command . but most just unpack a boot.IMG and modify it to their liking and repack it with the zimage of their choice [emoji3]
[Samsung Galaxy Nexus] :
Happy father's day to all parents reading. Be a good daddy to your kids they wont forget it. :)
[Samsung Galaxy Nexus] :
https://github.com/Grarak/RomSwitcher-tuna/blob/master/build.sh
[Samsung Galaxy Nexus] Oehr:
fyi: new kernel (6-15-14) still won't work with encrypted phones :crying:
[Samsung Galaxy Nexus] bsmitty83:
I never said it did [emoji3] , no reason to cry , unencrypt your phone or use ext4 . I would never see the need for encryption on a personal phone anyways ......
[Samsung Galaxy Nexus] Danny1976:
I downloaded the maguro version TWRP-2.7.1.1-F2FS/EXT4-MAGURO and I just don't see the ext/f2fs switch button. I went to Wipe, then Advance, but I don't see it. I also went to the advance menu and not the wipe/advance and I dont see the button. Can you send me a screenshot? Thank you.
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=2052088]Danny1976[/MENTION]

It's in the settings menu sorry , wrong menu reference . its under advanced menu on the multirom twrp
[Samsung Galaxy Nexus] dezful:
the Newest DirtyV-URSR { 6/15 } won't boot on maguro. :)
[Samsung Galaxy Nexus] bsmitty83:
not sure how that's possible . if it don't boot on maguro it don't boot on tuna period . what ROM?

the tuna variant has nothing to do with it booting or not
[Samsung Galaxy Nexus] dezful:
LS 6/12, which I manually modified the updater-script. Some user on carbon rom thread also experienced the similar issue when

assert(getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro" || abort("This package is for \"maguro\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

is enabled. I'm not sure how remove this will fix the issue. I'm testing it right now.

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

somehow, DirtyV-UR { 6/15 } (not SR) boot perfectly on maguro. :silly: [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Oehr:
As you dunno how you broke it, i kinda hoped you also fixed it accidentally.:laugh:

Also, as for encryption: its the same reason people encrypt their harddrives. With the additional risk of leaving your phone in some bar accidentally. You may not need it or even see the need, but I do.
[Samsung Galaxy Nexus] bsmitty83:
does encryption work on ext4 ? because I'm sure it was f2fs that broke it , not me . as ive never used encryption I have no idea what goes on with it , I've never specifically changed anything dealing with it .
[Samsung Galaxy Nexus] Oehr:
yes, im on ext4 and it works flawlessly with your pre-F2FS kernel from 5.3.14 (correct: 14-5-3 :P) and countless before it.

P.S. obviously, i didnt migrate to f2fs (yet), so the f2fs implementation itself shouldn't really break preexisiting encryption...
[Samsung Galaxy Nexus] bsmitty83:
OK, then it must be in the ramdisk changes , that's the only thing I can think of

[MENTION=4544860]osm0sis[/MENTION] ?
[Samsung Galaxy Nexus] dezful:
[MENTION=4608636]bsmitty83[/MENTION]

After testing several times, I can ensure that

DirtyV-URSR { 6/15 } won't boot

DirtyV-UR { 6/15 } perfectly does his job as kernel :D

on maguro. at least my maguro ;)
[Samsung Galaxy Nexus] bsmitty83:
I'm on it.... I'll have a new one up soon . I think I messed something up thank you for the follow through

Edit : yep f2fs security labeles were not enabled , thats why it won't boot in f2fs . sorry about that dude . I'm building a new one right now I'll update the op with the new one as soon as its finished

Edit 2 : should be good to go now .
[Samsung Galaxy Nexus] Oehr:
osmosis did say hed look into it a while back:
[Samsung Galaxy Nexus] dezful:
No need to sorry buddy. I'd like to thank the post yet XDA limit my thanks to 8 per day. Kinda limited edition of gratitude. :D
[Samsung Galaxy Nexus] Shadow Death:
Oh really?

Strange, it works for me. Then again I am on the Toro.
[Samsung Galaxy Nexus] bsmitty83:
is that f2fs ? cause I can't even get it to boot on f2fs , even my fixed one. I'm trying some things now