yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
After an annoying two hours of messing around I have updated my settings once again, I believe these are prime now.

The reason for the second update in less than 24hrs is two things, first I did not research enough to fully perfect them the way I wanted to and second, I found my battery to not be quite as good as it could. The update should help with battery but still give silky smooth performance now.

*ALSO, still no screen wake lag. :silly:
[Samsung Galaxy Nexus] adellon92:
Had a lot of screen lag with the latest kernel build flashed v5 again, everything smooth like it was before!
[Samsung Galaxy Nexus] heXacode:
Are you guys starting to use performance control app instead of trickster mod app? Or combo of both?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

Diff these patches

https://github.com/Quallenauge/kern...3-crazy/drivers/cpufreq/cpufreq_interactive.c

Backport alarmtimer/alarm-dev from google kernel 3.10 fork to suppor…

…t newly introduced clocks such as - CLOCK_BOOTTIME_ALARM - CLOCK_REALTIME_ALARM which where used by the android healthd daemon.

· 570c02c · Quallenauge/kernel-archos · GitHub - http://goo.gl/z1y2S5
[Samsung Galaxy Nexus] gohamstergo:
Has anyone experienced an issue where hispeed_freq (governor setting) overrides max cpu? Right now, whatever i set as the hispeed_freq is the highest the CPU goes, even at 100% load, regardless of what i set as max CPU.
[Samsung Galaxy Nexus] fracama87:
Guys you're giving to much importance to antutu! Don't do! Btw I've seen more than 14500 results with dirty-v... But what means?

I'm using new Nephilim settings but higher go_hispeed (should improve battery screen on time...) to 87.

my battery is becoming old (1 and ½ years charging until 97%)

No any lags, not sure about wake up lags...

Also I temporary gone back to stock minfrees except for last one.

[MENTION=2853378]Nephilim[/MENTION] if you want to try again cm-remix the dev has said he's working on a lighter version ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Because of how many changes are going into DirtyV on a daily basis there is really no point to benchmarks right now, especially if you are just ramping all of your settings up outside your normal daily use. The only relevant way of using a benchmark test is to see how your device qualifies on its daily usage settings. For right now as long as I hit around 12500 I am content. Besides, what people really need to pay attention to is what sections of the benchmark are actually scoring the high points, then work on refining your settings to improve the low settings.

As for your changing of go_hispeed, I'm trying out something new with how my settings are, going to see what the battery ends up being after a couple days, screen on time is not as much of a big deal to me as idle-drain and standby.

Good luck though and I'm glad my settings are working well for you. :)
[Samsung Galaxy Nexus] memaro_maro:
yeah.. seem my benchmarks was the real worst here. just 9000. shame on me!!
[Samsung Galaxy Nexus] Nephilim:
Did you cut it off in the middle? Or did you just set the max cpu frequency to 192mhz lol?
[Samsung Galaxy Nexus] oubeichen:
you should use the latest version of antutu
[Samsung Galaxy Nexus] fracama87:
It's can happens... it's happened to me. I told benchmark aren't ever good.

Last week in the same day with normal settings (lower than today and Nephilim was pretty much for battery) I got 9500 and 10800.

Try on few hours or try to reboot... ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] memaro_maro:
???haha.. max freq just 920mhz (undervolt) and lot of optimizations. more focus on battery usage + stabilities. still flying with dirty v.
[Samsung Galaxy Nexus] bsmitty83:
OK I got one more test kernel for the night , Interactive will probably still lag on wake out of deep sleep .

im still trying to fix it , not a huge bug or dealbreaker for me , but id like to fix it

https://www.dropbox.com/s/p19rur3sm6wo5hk/SmittyV-test.zip
[Samsung Galaxy Nexus] clnzx2:
Check your pm ;)
[Samsung Galaxy Nexus] bsmitty83:
Check yours .... :cowboy:
[Samsung Galaxy Nexus] clnzx2:
No need to be bossy :P
[Samsung Galaxy Nexus] @qawers:
tq.. a lot of testing from dirty-v here. woww!! flash it right now!!
[Samsung Galaxy Nexus] osm0sis:
I've been waiting all evening for [MENTION=4328678]metalspring[/MENTION] to post and show off his shiny new green name. ;)

I'm heading to bed now, so congrats sir! Well deserved (overdue even!), and glad I could help. :D:)
[Samsung Galaxy Nexus] Droid-21:
uses too much battery.
[Samsung Galaxy Nexus] fracama87:
Could be anything but since nobody said that about v6... Probably is not kernel's fault.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] jhonnyx:
Small Idea:

when reporting bugs it's very helpful to:

Mention the version of the kernel you downloaded (since there are 3 variants and lots of versions - kind of Smitty V-Test

Rom you're using

annnnd finally problem / how to reproduce problem

one example might be:

/Newpost

"Hey guys, I've got an error:

Kernel: SmittyV-Test - Feb 5

Rom: Cyanfox 2.0.2

Problem: I don't see sakuractive Kernel because I have sunlight glasses on my face

How does it happen?: I open trickster mod and go into General -> CPU Governor Control -> I don't see Sakuractive in the list

also I'd like to send some hugs to the guys over the G+ Community ;) you rock"

----

Excuse my friggin' mind, I'haven't slept very well xDDDDD

Keep on rockin Smitty!
[Samsung Galaxy Nexus] heXacode:
Anybody?
[Samsung Galaxy Nexus] n0ve:
Im using trickster with perf. Control app not set to boot. Perf. Control great but not detailed enough.
[Samsung Galaxy Nexus] michierusama:
Yeah. Let's not ruin the atmosphere we have here. Let's keep it calm.
[Samsung Galaxy Nexus] zandander:
Yup
[Samsung Galaxy Nexus] metalspring:
thanks, green looks much nicer than boring grey lol :)

Btw, [MENTION=4608636]bsmitty83[/MENTION] do you think any of the most recent commits by Franco would help your kernel as well? It looks like he added a few bug fixes and performance optimizations- https://github.com/franciscofranco/Tuna_JB_pre1/commits/nightlies-4.3
[Samsung Galaxy Nexus] ak:
A lot of these commits are already inside the kernel.
[Samsung Galaxy Nexus] BestBrd:
There is any way to change the i/o tunables via terminal?
[Samsung Galaxy Nexus] büscher:
[MENTION=4608636]bsmitty83[/MENTION] and [MENTION=4544860]osm0sis[/MENTION] just wanted to report that your new kernel zips are fine with CWM.

The status 7 error in CWM 6.0.4.7 comes from the missing dump_image in older zips (like V4) which was already discussed.

Extracting System Files...minzip: Extracted file "/tmp/zImage"

set_perm: chown of /tmp/dump_image to 0 0 failed: No such file or directory

set_perm: chmod of /tmp/dump_image to 777 failed: No such file or directory

script aborted: set_perm: some changes failed

the new ones install just fine!
[Samsung Galaxy Nexus] bsmitty83:
Anyone using my last test kernel ?

Never mind ........
[Samsung Galaxy Nexus] chainrulez:
Somebody clear me, was that SmittyV5 or SmittyV5.1? I forgot that because I deleted that zip from phone. :confused:
[Samsung Galaxy Nexus] pianistaPL:
This is bsmitty's personal build with personal settings :)

[MENTION=4608636]bsmitty83[/MENTION]

I just now read that you shared test version but few minutes ago i installed clean Carbon Nightly with Dirty v6 :( But i can install test version evening (for now it's 12 pm in Poland)
[Samsung Galaxy Nexus] chainrulez:
No no I am sorry if my question is not cleared, I meant that there was V5 or V5.1? because at old page there is V5.1 available but what I remember it was V5. Just a little bit confuse that there was V5.1 or V5? Just want to confirm version. :confused:
[Samsung Galaxy Nexus] pianistaPL:
As i good remember, v5.1 has Dynamic Fsync :)
[Samsung Galaxy Nexus] bsmitty83:
Yes , smittyV5.1 was a version , there was no smittyV5 .
[Samsung Galaxy Nexus] chainrulez:
Oh ok thanks for clearing :)
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION] I thinks that this isn't normal that i can't set min screen on lower than min CPU clock.

For example i'm unable to set min 350MHz CPU clock and min screen on 180MHz.

I never had that problem on Mpokang or ASKP Kernel.
[Samsung Galaxy Nexus] Nemed:
[MENTION=4608636]bsmitty83[/MENTION] i noticed that with the new interactive governor there's something like a "on/off" effect (no matter what settings i'm using). I mean that it almost uses only the highest and the lowest freq. Instead with the interactive from v4 and v5 the scaling was more balanced and all the freqs were used. Maybe it's just an impression but it seemed more snappy and battery friendly (only v4) to me.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] ak:
[MENTION=4315955]Nemed[/MENTION]

Very cool sig. self made?
[Samsung Galaxy Nexus] Nemed:
Yup :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] gh0stslayer:
Yup, It's amazing as before, just that the interactive wake up bug is still there
[Samsung Galaxy Nexus] ak:
can you modify a little the sig and insert under "Galaxy Nexus Kernel" this:

"official supporter"?

thanks a lot

I hope that we can do.
[Samsung Galaxy Nexus] Hetalk:
Just got up for another gruelling day, and flashed your latest test kernel. I'll update this post with my findings on wake up issue.
[Samsung Galaxy Nexus] bsmitty83:
Its gonna do the same . I tested it , still can't trace the cause of it ,

I'm gonna start trying some things today .
[Samsung Galaxy Nexus] Hetalk:
Ok buddy. I'll be online for another 10 hours or so. If you get a build to be tested, post it here and I'll try it out. :good:
[Samsung Galaxy Nexus] Nephilim:
That is impossible. The min is the absolute minimum your device will be allowed to go, if you have that set to 350mhz it will never go below that because it is the absolute lowest you decided. That means the lowest you may set min screen-on is 350mhz.

You could set min to 180mhz and still set min screen-on to 350mhz because min is still lower. The way you are describing is impossible.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Is this a boot logo in the kernel yet, à la AK? That would look pretty sweet. :)
[Samsung Galaxy Nexus] pianistaPL:
Got it but why on another kernels i can do that impossible thing? :) Are you sure that min screen clock is independent of min CPU clock?
[Samsung Galaxy Nexus] Nephilim:
I think you may have what you think you did on another kernel reversed. "Min" has always been the absolute lowest setting your device will go, if you have that set at 350mhz no other setting will be allowed to go below it because that is now the default lowest cpu frequency your device will allow. The minimum screen-on is still based off of that because "min" is the minimum your screen is allowed to go whether on or off. I hope this makes sense.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Guys(and gals, if any), stop responding to posts that you don't find beneficial to this community. Just report them and move forward. Please.
[Samsung Galaxy Nexus] poo706:
Off topic. I'd like to build liquid smooth from source for toroplus. Does anyone know if toroplus is one of the options when you get to the lunch command?

[poo]
[Samsung Galaxy Nexus] jhonnyx:
come on Smitty, shoot the kernels away, we're the Dirty gang, willing to test for more :D
[Samsung Galaxy Nexus] bsmitty83:
Lol........
[Samsung Galaxy Nexus] malybru:
Mod Edit

Thread cleaned.

May I remind everyone that this is a development thread.

Please keep it that way , and stay on topic.

Thank you

malybru

Forum Moderator
[Samsung Galaxy Nexus] pattyboi:):
on topic....ive been using the test kernel since last night,i have all day to test as well.
[Samsung Galaxy Nexus] aosp:
Never feed the troll's ignoring most of time results with them going back to trollville ;)
[Samsung Galaxy Nexus] Nephilim:
Metalspring is the one to ask about that stuff, he's the resident rom guru. ;)

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 09:40 AM ---------- Previous post was at 09:39 AM ----------

That guy is a rare exception. He's been doing this since AK's thread. He never leaves.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Did I miss something? Lol

Anyway, hopefully soon I'll get to finally get to testing how a kernel made with LTO and graphite optimizations works on a rom that also has the same optimizations ;)

Getting both to build were easier than I thought... I think lol
[Samsung Galaxy Nexus] cujo6801:
Nothing of importance... Lol

sent from the DOG pound
[Samsung Galaxy Nexus] sajty:
I have small issue with frequencies.I have set min frequency to 230MHz and min screen on to 350MHz.Everything is working,till reboot.After reboot,min screen on goes to 230MHz,even when set to 350MHz in Trickster.I had to change min screen on to any other value and then back to 350MHz to get it working.But after reboot,same issue again.

Anyone else facing similar issue?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] mutex issues in rom land don't help

Revert "Remove harmful attempts to be helpful in pthread_mutex functions... · e2c1351 · CyanogenMod/android_bionic · GitHub - http://goo.gl/vOTNaH
[Samsung Galaxy Nexus] Shambola:
I still have wake up issue with V6 + Neph's settings and a strange no-sleep effect with fast charge. If it's on at boot, phone doesn't go to sleep mode. If it's off at boot, and turned on after boot, phone goes to sleep....

I like Dirty Gang!!! I've changed my signature :D:D
[Samsung Galaxy Nexus] Nephilim:
Not sure about the issue with sleep and fast charge but after a day with my current settings I noticed some lag in opening and using certain tasks. I have returned to the drawing board and am once again revising my I/O scheduler tunables and my Interactive Control tunables. Stay Tuned.... again....
[Samsung Galaxy Nexus] drmxmyt:
i think, about fast charge no-sleep thing is because fastcharge still allowing to mtp connection. it stays connetced at pc so phone doesnt go to sleep to allow us to see files as far as i understand.
[Samsung Galaxy Nexus] Shambola:
Obviously the test was made with phone NOT connected!! So i say that's strange....
[Samsung Galaxy Nexus] ak:
I love my new Sig. :D
[Samsung Galaxy Nexus] Nephilim:
Nice, what happened to the other two? They seem broken, not visible.
[Samsung Galaxy Nexus] ak:
can you see the red image? ooooh .... :cyclops:
[Samsung Galaxy Nexus] Nephilim:
Nope, neither of the pictures on the left are visible, just broken image icons.
[Samsung Galaxy Nexus] ak:
Azz I have changed my image bucket site ... I have to reupload all ... :(:eek:
[Samsung Galaxy Nexus] metalspring:
Btw, [MENTION=4608636]bsmitty83[/MENTION] I think something got left out again on dirtyv-sr v6...
[Samsung Galaxy Nexus] bsmitty83:
I'm pretty sure you'll be saying that a lot with me lol
[Samsung Galaxy Nexus] cujo6801:
Hey metal your 2/5 omnimetal

Is out of this world...

sent from the DOG pound
[Samsung Galaxy Nexus] Hetalk:
2/5 omnimetal? where? :confused:

Edit: Never mind. It's for a different device.
[Samsung Galaxy Nexus] cujo6801:
Well hell ...

http://xdaforums.com/showthread.php?p=50025432

sent from the DOG pound

---------- Post added at 12:01 PM ---------- Previous post was at 11:50 AM ----------

sent from the DOG pound
[Samsung Galaxy Nexus] jhonnyx:
yeah, too bad it's for toro-ists only :(

We'll have to wait :)
[Samsung Galaxy Nexus] Hetalk:
Yupz. I'd love to test it (taste it) as well. :D
[Samsung Galaxy Nexus] bsmitty83:
K guys , Im back from the sweatshop and have a new build to test , Id be doing it myself but I need my phone on

lemme know how it runs , ill be back in a few , there is a bunch of stuff i gotta catch up on this thread , i dont wanna feel like Im negleting anyone cause their post got buried in an hour :good:

https://www.dropbox.com/s/1iiq7tuqwcndhm0/SmittyV-test6.zip
[Samsung Galaxy Nexus] n0ve:
I ate vanir once....crunchy yet tasted okay...CM tasted like stale bread.. Purity tasted like buttered pancake's tho
[Samsung Galaxy Nexus] Hetalk:
Test6 .. hmmm ... you didnt share test 4 and 5. hmmm

:laugh:

Flashing v6 as i speak. Will report after testing for about 15 minutes.
[Samsung Galaxy Nexus] bsmitty83:
Yea I self tested those at 5am lol as I was getting dressed ... This version will be slower , but just for now
[Samsung Galaxy Nexus] Hetalk:
Slower isn't an issue here.

The big issue is

Screen unlock issue is no more. This build has it fixed. :highfive::good::victory:

Edit: Added image. :good:

Edit: Hide off !
[Samsung Galaxy Nexus] jhonnyx:
ohh, the hidden content! cannot wait till I get home, i'm eating my nails out!
[Samsung Galaxy Nexus] aosp:
This is running like a winner so far guys give smitty the keys to the city ;)
[Samsung Galaxy Nexus] Nephilim:
Can you confirm it has all the Interactive Governor Control tunables from v6?

I'm going to wait until the DirtyV version hits.
[Samsung Galaxy Nexus] bsmitty83:
Present and accounted for :sly:
[Samsung Galaxy Nexus] Hetalk:
Yes, I think it had all the tunables that you have in your settings. I'll post a snapshot in a few minutes.
[Samsung Galaxy Nexus] aosp:
/sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

/sys/devices/system/cpu/cpufreq/interactive/boost

/sys/devices/system/cpu/cpufreq/interactive/boostpulse

/sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration

/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

/sys/devices/system/cpu/cpufreq/interactive/io_is_busy

/sys/devices/system/cpu/cpufreq/interactive/min_sample_time

/sys/devices/system/cpu/cpufreq/interactive/target_loads

/sys/devices/system/cpu/cpufreq/interactive/timer_rate

/sys/devices/system/cpu/cpufreq/interactive/timer_slack

[MENTION=4608636]bsmitty83[/MENTION] Thanks for the wakelagbegone on test6 ;)
[Samsung Galaxy Nexus] Nephilim:
Nice, glad to hear it, these new settings I put together this morning are rocking. I believe I found a keeper finally. :D

Can't wait to try out the new DIrtyV7 when it's ready and I'm sure alot of others are excited to be rid of screen wake lag! ;)

Thanks for the offer but it appears you have been ninja'd with the answer I was looking for by smitty. ;)
[Samsung Galaxy Nexus] bsmitty83:
Ish was driving me mad .......
[Samsung Galaxy Nexus] metalspring:
could someone pull the file /proc/config.gz from v6 of the regular dirtyv (not the sr version) for me? I'm running mpokangs kernel at the moment since I needed logcat but I need dirtyv's proper config to compile it in my rom (the one on github causes it not to boot). I really dont have time to flash the rom again or try to pull the original boot.img to go back and flash dirtyv
[Samsung Galaxy Nexus] Nephilim:
Thank you as well sir, looks like you and hetalk were both ninja'd by smitty lmao!
[Samsung Galaxy Nexus] aosp:
You on you're way dude the smitty KernelFu is becoming impressive ;)
[Samsung Galaxy Nexus] bsmitty83:
It will be a few before I'm ready to push to every branch , still have some things to do , but I'll keep dropping test zips when I can . we'll see how it goes
[Samsung Galaxy Nexus] Nephilim:
No big deal, whenever it's ready. v6 is running fine for me. ;)
[Samsung Galaxy Nexus] aosp:
Don't you dare mpo us :p
[Samsung Galaxy Nexus] bsmitty83:
Lmfao
[Samsung Galaxy Nexus] aosp:
I pity the fool who is not using test6 :)
[Samsung Galaxy Nexus] metalspring:
When trying to test out something new on a rom, ability to get logcats is a must and v6 had it broken :(

But I'll just fix it in my source but need to working config first
[Samsung Galaxy Nexus] Nephilim:
I'm going to stick with v6, I'm enjoying my settings to much to flash test6 right now and have to modify them due to certain things missing. I will sit and wait, impatiently for v7 while making believe I am waiting patiently. :silly:
[Samsung Galaxy Nexus] michierusama:
Just came back from college. Everything here looks great!!! OMG I wanna test test test test and report report report:D
[Samsung Galaxy Nexus] Hetalk:
No worries buddy. I'll try out your settings and report the awesomeness of this new build. :D
[Samsung Galaxy Nexus] Shambola:
Ot : "Azz" make this the post 'o da day for me. (For non Italian speakers, it sound like "fckkk") lol
[Samsung Galaxy Nexus] @qawers:
ninja caught on camera!! finally found a group of ninjas here!!
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Make sure you let the mods know that everybody be kung fu fighting in this thread cause that what ninjas do ;)
[Samsung Galaxy Nexus] michierusama:
Round one. Fight!
[Samsung Galaxy Nexus] Nephilim:
Fresh new 2/5 Toro LiquidSmooth build is up, rkpeterson looks to be wanting some Maguro users to test a build possibly as well. :D

OT FO LIFE!
[Samsung Galaxy Nexus] flip360:
i would like to test out maguro for one, link pls :)
[Samsung Galaxy Nexus] Nephilim:
Go to the Toro LiquidSmooth thread. ;)
[Samsung Galaxy Nexus] bsmitty83:
OK so I reverted back to vanirs of kernel , recommitted all my commits , this time keeping only what I know works AFAIK ,

I'll test each new thing in smittV , releasing test kernels , then I'll move it to dirtyV . I'm trying to get all 3 merged and compiled tonight , and my github straight for [MENTION=4328678]metalspring[/MENTION] , ( I won't let you down ) , so gimme a few and hope for goodness

PS this thread is far more awesome than my kernel could ever be :)
[Samsung Galaxy Nexus] 47th_Ronin:
Dude...

I'm in my 50's and I've seen so much pain and the agony of the human condition that I thought that I'd be immune.

But that broke my heart...

Think I'll go and get drunk and write a country song now...
[Samsung Galaxy Nexus] milojoseph:
[MENTION=4608636]bsmitty83[/MENTION] check your pm plz
[Samsung Galaxy Nexus] bsmitty83:
Op updated

all three kernels and sources ( [MENTION=4328678]metalspring[/MENTION] :p )

give them a try
[Samsung Galaxy Nexus] adoboyo:
So to put it in laymen's terms...this new build is based off vanir with your tweaks that you've tested to make it even better? battery life and all? fastness, smoodness, alladat on top of an already great kernel? :p
[Samsung Galaxy Nexus] bsmitty83:
Lol I hope so ........

I haven't even tried these yet , still running last test kernel lol .

Honesty I'm not the person to ask about battery since I flash alot of kernels , ROMs , WiFi tether . but should be a little less problematic
[Samsung Galaxy Nexus] evilSuRGe:
So basically you started over
[Samsung Galaxy Nexus] bsmitty83:
Yes but I kept all the good stuff and removed the bad and possibly some good that I'll have to reintroduce but its running pretty good .
[Samsung Galaxy Nexus] adoboyo:
I'll test here in a bit with the 2/5 build of vanir. I'm excited lol
[Samsung Galaxy Nexus] Nephilim:
The only thing I noticed missing from today's DirtyV SR is the 180mhz cpu frequency.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] garyngkt:
How does the version from V6 get to V2.5.14? :laugh:

Will test soon thanks [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] bsmitty83:
Not coming back , I took it out . its too low
[Samsung Galaxy Nexus] bsmitty83:
I'm sick of "v" numbers , dates are easier lol
[Samsung Galaxy Nexus] Nephilim:
Just a heads up, runtime, cpu and ram suffer on this build considerably, the worst is gpu though, I lost 2000 points on 3D and about 300 on 2D in antutu. I cannot exceed 6fps on open esgl benchmark, I get 17.8 to 18fps max on all your other kernels.

Just relaying info. This kernel is fast but it stutters.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] garyngkt:
if 2 versions on the same date then "-2"? haha..
[Samsung Galaxy Nexus] bsmitty83:
Figured it would
[Samsung Galaxy Nexus] Nephilim:
What do you think the cause is? I went back to v6 for now.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Cause I had to revert a lot of commits to make it stable lol . it wasent right before .
[Samsung Galaxy Nexus] Nephilim:
Gotcha.

Sent from my Android 4.4.2 Galaxy Nexus