yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] lazydognet:
For me, using the latest Vanir, I can't get DirtyV SR2.5.14 to boot when converting to ART.

LDN
[Samsung Galaxy Nexus] adoboyo:
Did you flash them together or boot Vanir into art first, then kernel? Letting vanir boot into art first, then flashing dirty v worked for me on a recent build.
[Samsung Galaxy Nexus] michierusama:
So, everything came back to the start to trace the issues? Hmm. And can we still use Nephi custom settings?
[Samsung Galaxy Nexus] bsmitty83:
Yes .
[Samsung Galaxy Nexus] chainrulez:
Test6 was also passed and new 2.5 is also rocking, no wake up delay or lag ... thanks ... :highfive:
[Samsung Galaxy Nexus] lazydognet:
Actually, I first tried to just wipe both caches and then apply the latest DirtyV SR over my previous DirtyV SR 5 (that was on Vanir 2-3 on ART).

It never got past the Vanir logo, so I restored from backup.

Then I upgraded to Vanir 2-5 by wiping both caches again. Booted and made sure it worked (with Dalvik) and rebooted into Recovery Mode. I then applied DirtyV SR 2.5.14.

It booted fine and seemed perfect. Next I switched to ART and that's when it again wouldn't get past the Vanir logo.

LDN
[Samsung Galaxy Nexus] adoboyo:
Hmmm, while it's amazing and my favorite rom, art seems so iffy sometimes. Well at least enabling it. Some builds work, some builds don't, some don't work, I try again and it works. Not sure what's up?
[Samsung Galaxy Nexus] fracama87:
With number you would soon reach chrome version :D

Dates are good :P

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] ak:
Coooool .... :D

---------- Post added at 06:53 AM ---------- Previous post was at 06:50 AM ----------

Supercool:

http://xdaforums.com/showthread.php?t=2637782

by @itasoulas
[Samsung Galaxy Nexus] sagara.sandaru:
If u r stuck on bootloader go to recovery wipe cache and dalvik and reboot.. It worked for me!
[Samsung Galaxy Nexus] j3r3myp:
The new version works well. Only wake up lag here was mine this morning :)

"Envoyé depuis mon Galaxy Nexus avec Tapatalk"
[Samsung Galaxy Nexus] ak:
Can you post your settings?

AK&4&7
[Samsung Galaxy Nexus] n0ve:
Own neph settings except for GPU @ 384 and min + min off at 230 due to lack of 180...feels noticeably slower during gaming and running large apps. Stutters as stated earlier.. @ Smitty why do you believe 180 is too low ? With correct gov. Doing what a gov does ...there's no such thing as too low..screen off max is there to prevent low being too low if u catch my drift..kindly correct me If my interpretation is incorrect.( of course below 180 would be 'too low' but the mV diff between 180 and 230 can only improve battery life [slightly] wout a downside)
[Samsung Galaxy Nexus] j3r3myp:
Yup, default interactive settings with Nephilim's minfree settings

Default fiops tunables.

RAB 128

"Envoyé depuis mon Galaxy Nexus avec Tapatalk"
[Samsung Galaxy Nexus] metalspring:
I think he was making a joke meaning he had a tough time waking this morning, not the phone???
[Samsung Galaxy Nexus] ak:
Oooooooops ??????

AK&4&7
[Samsung Galaxy Nexus] lordofazeroth:
I installed the latest SR.

I went into trickster after reboot and notized, the interactive was set to go to high load if CPU workload was higher than 50.

Even Nephilim has 78 in his thread, at Stock there should be over 90.
[Samsung Galaxy Nexus] ak:
Go to system app trickster - and clear cache and data.?

AK&4&7
[Samsung Galaxy Nexus] j3r3myp:
Hahaha Indeed !

"Envoyé depuis mon Galaxy Nexus avec Tapatalk"
[Samsung Galaxy Nexus] adoboyo:
New build is flying with 2/5 commotio.

Just changed min and min screen on to 230 and governor to ondemandx.

I kept everything else in trickster stock (Westwood & bfq). I noticed rab is 2048. I've tried to look online but can't really find anything in layman's terms...what do the values mean? How do I know whether to run it lower it keep it as 2048?

Sorry, I'm new at editing kernel settings.
[Samsung Galaxy Nexus] ak:
Is Bfq the def scheduler?
[Samsung Galaxy Nexus] adoboyo:
It was when I went into trickster.
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4608636]bsmitty83[/MENTION] great work with the wake up lag. It's now even better than with V4.1. The device wakes up instantly. Thanks!

And FYI Dynamic FSYNC is still On by default.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nemed:
I agree, [MENTION=4608636]bsmitty83[/MENTION] why don't you let users to choose if use 180 or not? :)
[Samsung Galaxy Nexus] bsmitty83:
Row
[Samsung Galaxy Nexus] Piti8576:
Can anyone please post the default color settings from this kernel for trickster?
[Samsung Galaxy Nexus] mrgnex:
I had that too. But it wasnt a bootloop after all. If it is just go back into recovery and wipe both caches and reboot. It should work then.
[Samsung Galaxy Nexus] bsmitty83:
Got this on my everyday setup

Row + interactive
[Samsung Galaxy Nexus] Vekhez:
We still aren't any where near that MPOKANG efficiency.. I wonder what the f*ck he did..
[Samsung Galaxy Nexus] ak:
is ram related to scheduler r/w?

i dont understand how antutu can test ram oc/timing.

Can you use this app for ram test?

https://play.google.com/store/apps/details?id=org.codedivine.rgbenchbw&hl=it
[Samsung Galaxy Nexus] thagringo:
[MENTION=4608636]bsmitty83[/MENTION] : what cflags are you using to build the kernel and what arch specific tunables are you passing to the kernel build system ( if any) ?

just asking, i build linux kernels almost every day ( not for android though) and maybe some basic tuning helps a bit further.

cheers
[Samsung Galaxy Nexus] metalspring:
No idea on the first question but as for the second one this is what mpokang scored-
[Samsung Galaxy Nexus] ak:
and dirty score?
[Samsung Galaxy Nexus] osm0sis:
I was talking to franciscofranco about this the other day while we were getting f.K r395 out the door, and he thinks mpok cheated on the benchmarks somehow and that might be why mpok never pushed the final v10 sources.

Edit:
[Samsung Galaxy Nexus] metalspring:
The ones I see are -O3, -Ofast, -flto (link time optimization), -fno-toplevel-reorder, -floop-block, -floop-strip-mine, -floop-interchange, -mtune=cortex-a9, -march=armv7-a -mfpu=neon, -fno-strict-aliasing, -fno-common, -fmodulo-sched, -fmodulo-sched-allow-regmoves, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -fno-delete-null-point-checks

Along with various warning, warning=error, and do not warn cflags
[Samsung Galaxy Nexus] Nemed:
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] metalspring:
Btw, I do think that one of the keys to figuring this out is that the ram speed scores are what's really improved, the ram performance scores stay about the same, which just seems a little odd

Also as for placebo effect, idk, mpokang is still one of the smoothest all around kernels there are (some dirtyv versions had about the same performance on most things that mpokang did but GPU was always laggy for some reason)
[Samsung Galaxy Nexus] lordofazeroth:
done...

no change
[Samsung Galaxy Nexus] winamp26:
Please Tell me your rom and kernel setting
[Samsung Galaxy Nexus] thagringo:
looks good to me, a few ideas :

- if you have both -O3 & -Ofast only the first one is passed to gcc afaik, right ? That would be easy to see in gccs output.

- some of the mentioned ( -funswitch-loops for example) are redundant i think, already included in -O3 iirc, at least in 4.7.

- regarding lto : maybe using -fno-fat-lto-objects helps with the final binary size, it helps a bit in x86 and -Os.

- -pipe should help a bit when building ( i would be very surprised if it isnt enabled), same for -flto=4 in case it is quadcore cpu for example.

- as for the graphite opimizations, maybe someone wants to try -floop-parallelize-all and -fgraphite-identity. This last one can lead to runtime breakage so be carefull.

What about linking ? has anyone tried gold linker ( if such a thing makes sense in android world) ?

What gcc version are you guys using ? lto is known to have serious issues in 4.7. ( maybe fixed or backported in linaro or other toolchains, i dont know).

just a few ideas.

cheers
[Samsung Galaxy Nexus] metalspring:
My omnimetal rom, with max CPU freq at 1500, min 384, interactive gov, sioplus I/O, 2048 read ahead buffer, dyn fsync off, GPU 512

(I'm always near a charger so I prefer maximum performance over battery life lol)
[Samsung Galaxy Nexus] oubeichen:
Most developers use GCC 4.7 to build android kernels(even AOSP). GCC4.8 could cause issues.

-O3 is not recommend in kernel building,but I haven't seen problems.And I think -Ofast has the higher priority as it contains -O3 and -ffast-math.

-pipe is to speed up compile times,we dont need it as we only need few minutes to build.
[Samsung Galaxy Nexus] antypas:
Cheated? How can someone cheat a raw memory benchmark like rgBandwidth? rgBandwidth isn't influenced at all by ROM / optimizations / toolchains (unlike other benchmarks). With every rom or android version I get almost the same scores...

And of course there is the feel. It totally backs up the benchmark scores.

It is the faster kernel out there. App opening is the fastest of all kernels I have tried. And I have tried them all.

At some point he posted something related to memory: http://xdaforums.com/showpost.php?p=45852850&postcount=627

Maybe he finally nailed it?
[Samsung Galaxy Nexus] metalspring:
I dont know about aosp gcc 4.8, but I know sabermod 4.8 works, linaro 4.8 does but causes major issues, but linaro 4.7 outperforms sabermod anyway. Also, I dont think -O3 is recommended in building anything android since it can cause issues, but there are plenty of fixes out there, same goes for -Ofast (of which I think only -ffast-math is really added anyway). As for -pipe, even if kernels dont take long to compile, it never hurts to build faster lol

---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------

This is one I'm definitely interested in-

-floop-parallelize-all

since its mentioned by linaro in an older article here that may speed things up for multi core cpus

As for the others, I can help [MENTION=4222651]bsmitty23[/MENTION] test them out if he wants
[Samsung Galaxy Nexus] Edgarngg:
I like dates, v8 would have sound like a fruit juice
[Samsung Galaxy Nexus] osm0sis:
Maybe he did. Even more sad that he wouldn't want to share. :(

Franco was saying you can mount the benchmark directly "on RAM" to cheat it by being faster than anything normally would. No idea how that works though.
[Samsung Galaxy Nexus] Sik-1:
I think he meant the same way you can cheat quadrant by loading specific parts of the app in ram, if you check on the market they have an app that actually does this and you will def see your quadrant score fly
[Samsung Galaxy Nexus] ak:
I have see into ramdisk of mpokwsths kernel that a lot of part of kernel are compiled as module and than installed at boot as modular.

Have anyone tried to do this with kernel? and verify if there are improvements?
[Samsung Galaxy Nexus] aosp:
https://play.google.com/store/apps/details?id=net.danielroggen.rambench
[Samsung Galaxy Nexus] Nephilim:
LMAO!

Hey, did you see my couple suggestions back on the post I made with my test settings?

The two things that I think would be a great addition would be:

1. Dynamic Fsync rather than standard Fsync

2. Interactive governor with "early suspend cpu1 on screen-off" (what AK was using on all of his kernels) It drops idle-drain to virtually nothing.

Also, I'd just like to say, I could have easily switched back to Mpokang SuperRam and updated to 1/19 Vanir but I am having way too much fun on this thread. It's like the early stages of AK Kernel, where every update brings sweet improvements and we all get to contribute to it's evolution by testing. Also, I've never been one to be satisfied with a stock kernel that comes with a rom, I am all about refining and perfecting the experience I get out of a great custom kernel! :good:
[Samsung Galaxy Nexus] pattyboi:):
im gonna test the media profiles XML from the mpokang superram and see if it works like it used to on 4.4, that way youtube dosent go full retard after loading superram up. will report back.
[Samsung Galaxy Nexus] bsmitty83:
I miss that thread , xda is so stuffy . I'm such a lighthearted person and joke constantly its very hard to be all proper ...

Since I use no fsync I'll branch myself a new kernel and I'll start adding what the people want lol . it'll stay current to mine just the most popular things /best things

I'm looking at some very interesting commits right now for WiFi , I might put 3.4 back on . not sure just yet
[Samsung Galaxy Nexus] Nephilim:
You have an issue with Youtube on DirtyV SR version 2? It works fine and in high quality for me.
[Samsung Galaxy Nexus] pattyboi:):
no matter what i did all day it would not load any vids without me fighting the quality control button for like 2 mins lol,maybe i just pissed the gnex off today,ill retry a couple things.
[Samsung Galaxy Nexus] bsmitty83:
FYI it does , I tested it when I build a mpokang type with a bunch of modules I tested his install package too and its included in that

My fault for not including it in my superRam kernel
[Samsung Galaxy Nexus] Nephilim:
Nice, there is alot to cherry pick among AK and Mpokthws. I feel like you could get a great base and then evolve into something insane awesome!

As long as you're cool with it, once I feel this kernel is stable enough for newer users and social users I'll setup a section on my G+ for it, that way we can have a larger mass of users to give you positives and negatives and their personal experiences.

This thread is nice how it is, with just a few that are willing to break sh*t to test each kernel and return the valuable trial and error reports. :)

Are you still sticking with anykernel format or are you planning on making custom ramdisk eventually, or do you already include custom ramdisk lol?
[Samsung Galaxy Nexus] pattyboi:):
dude nothing is your fault,just because it dont work for me dosent mean your liable for it ;) honestly youve worked your @$$ off on alot of things for the gnex,you dont have to be the only one experimenting and doing the work,ill be screwing around with stuff all night lol,so ill probably throw everything into a zip and flash it for funs sake,but getting back on track,its probably just my gnex being pissy lol,it happens,not your fault bro (i just realized how garbled up this is lol,sorry its been a veeeeery long day)
[Samsung Galaxy Nexus] bsmitty83:
Hey its stable enough for me , lol , how's it work for YOU , do you think its stable ? . if so put it up on g+ , Im cool with that .

As for the ramdisk , personally it seems like I always get so many more problems with it . I can't see an upside to it . any script or module can still be loaded . granted idk as much about them .. Its like ROMs to me ... I know some but not as much as I want . so I stay away from ramdisks until I have to
[Samsung Galaxy Nexus] aosp:
Less is more ;)

http://d-h.st (Dev-Host) command line tool

GermainZ/dev-host-cl · GitHub - http://goo.gl/S94w3K
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] If you build hostap

http://w1.fi/cgit/hostap/
[Samsung Galaxy Nexus] Nephilim:
I think it's pretty damn stable too. The only issue is the slight stutter with the keyboard and recents menu. I don't want to hear a group of people whining about the small stuff that is still being cleaned up with each new build. I'm going to go make a section on my G+ for you and your kernel, it's up to you to create a thread and add links to it. I should have it ready within the next few minutes. Also, I'm going to make you a mod so if anyone is being an as*hole you can just boot them. (Provided you give me a heads-up first lol)

---------- Post added at 05:31 PM ---------- Previous post was at 05:05 PM ----------

Alright Smitty, your section is all up and ready over on the G+ Community, now get your ass over there and add a kernel to it!!!!!! :p
[Samsung Galaxy Nexus] Hetalk:
I guess no one's tried this one on ParanoidAndroid 4.0 [BETA], so here's my take on it.

It works and it works just fine.No boot issues. Awesome work [MENTION=4608636]bsmitty83[/MENTION] :good:

No freezes or unlock issues, once I changed settings to [MENTION=2853378]Nephilim[/MENTION] kernel setting from here, only difference being max screen off freq upped to 700 to avoid unlock delays. :good:

I've been [MENTION=2853378]Nephilim[/MENTION] kernel settings ever since good old AK kernel days, and they still rock. :good: :highfive:

Edit: This edit in hoping that this thread turns out to be another one of the epic thread where knowledge and fun do coexist.:D
[Samsung Galaxy Nexus] Nephilim:
If you're using Hyper governor theirs no need to up the max screen-off, but if you are using any other governor you may have to set it to at least 700mhz. :good:
[Samsung Galaxy Nexus] Hetalk:
Even with hyper I had unlock issues, until I upped my max screen off freq. Then everything was perfect. I'll try some more stuff and post if I find something else.
[Samsung Galaxy Nexus] bsmitty83:
I do a lot of Bluetooth music and WiFi hotspot (thx Verizon unlimited 30$ data ; see attch. Lol) and I like to keep my screen off Max high , like me , but really if your phone needs the freq , with the right governor and settings , you can keep all maxs' as high as your normal max cuz it'll stay well below that unless its using CPU then its more efficient IMHO to let it work at whatever freq it needs . try running screen on max at 700 MHz and watch how slow it its , watch your battery melt away . idk I'm not a fan of restrictions lol
[Samsung Galaxy Nexus] jhonnyx:
hey [MENTION=4608636]bsmitty83[/MENTION], offtopic question:

which app/mod do you use to see stats like that on your status bar?

btw, using DVLSR2, no issues on omni latest w/@Nephilim settings

awsm work!
[Samsung Galaxy Nexus] bsmitty83:
Man how does nobody know about this app . its called "Cool Tool" free on the market , I've been using it since gingerbread . its by far my most important app . its updated every half second . so its very useful to see what your CPU and network connection , temp .etc realtime
[Samsung Galaxy Nexus] Vekhez:
I'll break things for testing (not to the extent of the phone, but I can break ROM's, and factory image it up because of broken things, and that ****, idk. I do it all the time anyway) :D
[Samsung Galaxy Nexus] Nephilim:
I gotcha man, the longer I use this kernel the more I will be refining my settings as the kernel is refined. For me it's all about a happy medium of performance and battery (swaying slightly more towards performance). I totally agree with you on being against resrictions also, that's why I love testing out custom kernels like these, so many options compared to stock kernels. ;)
[Samsung Galaxy Nexus] cujo6801:
What's your TCP congestion

sent from the DOG pound
[Samsung Galaxy Nexus] ahmadairfan:
To be honest, mpo's interactive is set to stay at higher frequency. Maybe this can explain why mpokang is hell smooth, just because he set it to stay at higher frequency. Even scrolling makes the CPU go high at 1228 on my phone.

As for opening apps faster, I don't know if its a placebo or something. Maybe it related to his interactive, too.:confused:

Check this screenshots, even the go_hispeed_load is set to 50 which is crazy lol

Testing f.K r395 atm, compare this:
[Samsung Galaxy Nexus] Nephilim:
Is the kernel you are using the exact same as the newest DirtyV 2/5? I don't understand how my settings can give me almost 13000 everytime on v6 SR but I cannot even get above 9800 on 2/5 SR, also, how does my max fps on openGL ES 2.0 antutu test drop to 6fps from the usual 17.8 to 18fps. I literally used the exact same settings except 230mhz min since 180mhz was gone. I did the test 3 times and never broke 10000 then went back to v6 and hit 12834 on my first run while my phone was still hot. 2/5 stutters alot when scrolling as well as on opening/closing animations for apps, it runs fast but looks very jittery.

Can anyone else confirm any of what I have posted? I surely can't be the only one getting this sort of result.

Not knocking on you or the kernel smitty, you know that. Just dont understand why your benchmark is normal but mine is jacked up when I havent changed anything.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
https://play.google.com/store/apps/details?id=net.danielroggen.scimark
[Samsung Galaxy Nexus] metalspring:
I saw him post that compiling a lot of things as modules was more so he could free up more ram while still keeping features and even adding more features

Westwood, mostly just because I like the name lol, I never tested much with them and never really noticed a difference
[Samsung Galaxy Nexus] bsmitty83:
Yea . smittyV . no changes . I'm getting above 12k on dalvik , idk what you did lol
[Samsung Galaxy Nexus] cujo6801:
2 funny...

Thanks....

O and same here... Lol

sent from the DOG pound
[Samsung Galaxy Nexus] osm0sis:
50% go_hispeed_load and 75% target_loads?!

Jesus, with those tunables it will oscillate and ramp up constantly for no reason because it's trying to reach 75% but every time it hits 50% it jumps to hispeed_freq. No wonder it seems fast, the engine is basically always revving up all the time needlessly.

Metallice over on the N7 '12 once said about similar settings "if there was ever a way to be 'mean' to your governor, this would be it."
[Samsung Galaxy Nexus] Nephilim:
I'll try reflashing it again and setting everything by hand.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ahmadairfan:
Crazy right lol. Btw isn't it too risky to our old device? :confused:
[Samsung Galaxy Nexus] osm0sis:
Won't hurt the device, nah, it's just poor governor tuning, and should make battery life worse from all the oscillating ramping. Thanks for bringing that to light. It definitely explains some of why mpok felt faster.
[Samsung Galaxy Nexus] Nephilim:
I went back and input all my values manually for 2/5 on Trickster Mod and the reset their profile names in each section. Turns out you changed voltage values slightly between v6 and 2/5 on MPU so when I tried to use my MPU profile it set some wacked voltages that weren't correct. This time when everything was set manually 2/5 SR is giving me 12500+ benchmarks again. Sorry I made such a stupid little mistake lol.

Btw, please re-add 180mhz to cpu steps. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
He Ike his Tina and she dead :o
[Samsung Galaxy Nexus] sagara.sandaru:
That means it's not faster lol.. I tried mpokang kernel 1hour ago. I also noticed that when I try to set Neph's settings. I did set Dirty_V stock interactive values on mpo's. It was super slow. Here is the benchmark rslts I got

1st one with Mpo's interactive settings, 2nd one with Dirty_V interactive settings
[Samsung Galaxy Nexus] Utkarsh-ezzo:
Guys I have reverted to 4.3, just flashed stock 4.3 and I felt really awesome, and the status bar is so smooth here....

The point is I will test dirty V on 4,3 mostly on purity ...
[Samsung Galaxy Nexus] Nephilim:
Honestly, with my current settings, I feel that DirtyV SR4, SR6 and SR 2/5 are much smoother and faster than Mpokang SR. Literally the only difference is ramspeed benchmarks on AnTuTu, which now I am beginning to think more and more were faked.

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------

Just so you know, the notification shade is perfectly smooth on LiquidSmooth now as well, I've also heard its fine on Vanir. I personally do not see it as a reason to ditch all the benefits of 4.4. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] antypas:
Why would that be crazy???

Stock kernel has it at 50 as well....

:silly:

WTF. Man, there is definitely something wrong with your GNex...

At 1420Mhz with Mpokang v10 (stock settings) I get over 13500 points

Even with Dirty V gov settings I get almost the same results