yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] eng.stk:
Very nice, lot's of people in here should watch that :good:

I think that 1 core @ 1190MHz is enough for 90~95% of the users. I listen to music a lot (using Play music local and network and Apollo) with normal earphones( no Bluetooth) and never had any issues.

I think that some people use sound mods or apps/equalizers that use more cpu, so they should increase min cores to 2 and freq a little. Other have some background stuff syncing and such, so they cold need that extra power.

Or it's something else, but has i said: i use 3 different branches in 3 different ROMs and never had issues.

You should tweak according to your needs.
[Nexus 5 Original Android Development] haasgo:
What nucleotide recommended doing was exactly what dev suggested.

Also there is an option in poweramp where you can set a wakelock to help with the hiccups. That will suck more juice out of the battery for sure though.
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r407

All right crew!

Just pushed r407, go get it. Now. :highfive:

Add the ability of touch boost to blu_plug (now with 1 core min, 2 cores on touch), you can use older setting of 2 always online if you prefer.

Also I tweaked thermal levels to match more conservative values.

CM branch has all the goodies merged now, but I am not happy with dt2w in either branches: I still notice some leakages in some particular situations, will test more during next week. If I am not happy with the results, I am going to remove touchy touch stuff from my kernels.

Some fun facts: r398 just hit the amazing 5,2k hits. Damn :highfive:

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!
[Nexus 5 Original Android Development] radicspeter:
[MENTION=3873953]eng.stk[/MENTION] !

Made my weekend!! :)

Dowload!!
[Nexus 5 Original Android Development] Aerowinder:
I'm glad you made the call to tone down the throttling temps. Just because it can run at 90c, doesn't mean you should let it. Heat kills electronics, everyone knows this. That is why faux's choice baffles me.

On that note, had to revert to 398. Default settings were causing very bad lag every few seconds. It also took forever to boot. Just went into recovery, flashed it, and rebooted.
[Nexus 5 Original Android Development] hooliganx:
[MENTION=3873953]eng.stk[/MENTION]

thanks for update man!

really appreciate your work.

about dt2w... don't remove it. [emoji15]

it's a good feature for some people, and, if someone don't use, just live it off.

thanks again [emoji106]

n5sk8.0.robbie09.17artgapps292

codeblue.r376rd1.16v4atwrp2.7.1.0

------------------------------------------------------------------------

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Original Android Development] theodorius123:
when I tested different kernels regarding DT2W I had some kernels with laggy DT2W and one with perfect working DT2W. cant remember which one....have to go now, maybe i can check later!
[Nexus 5 Original Android Development] radicspeter:
I installed clean for purity and laggy too... :( come back to milensotne 6.
[Nexus 5 Original Android Development] antec123:
first time using r407 kernel i had lag, but increase the minimum cores to 2 that it doesn't have lag.
[Nexus 5 Original Android Development] Aerowinder:
Yes. I suspect at default settings, with only one core online for screen on, that the second core is shutting down too quickly. causing the lag. Either that, or the load on the first core doesn't get polled often enough to prevent the lag.
[Nexus 5 Original Android Development] Grondinm:
Thank you for your continued work. I would hate to see dt2w go since I use it but its your kernel so I would understand.
[Nexus 5 Original Android Development] antec123:
i have to revert back to r398, today release give me lag again when i play clash of clans and tapped out.
[Nexus 5 Original Android Development] whisper13:
Same here constant lag, reverted back :(
[Nexus 5 Original Android Development] Bentso:
I too have lag with r407. Downgraded back to r398.
[Nexus 5 Original Android Development] proyatzu:
Here is alla smooth with 407 stock and slimkat
[Nexus 5 Original Android Development] eng.stk:
Yeah I am still playing with the settings, the sweet spot will need work.

Altough I don't feel any lag in my or my betas tests.

On touch, 2nd core goes online instant and timmings are the same.

I believe some people have more load in idle, you can try lower your load threshold. Something like 50 for instance.

If nobody tests, we'll never know right?

But I bet that people are going to complain first and "other versions are better" before actually contribute with something useful like you did.

I say down_timer 2 or 3 and load_threshold something like 50.

Test and see if it helps guys.
[Nexus 5 Original Android Development] vampsoft:
same here

Team AndroVamp
[Nexus 5 Original Android Development] Assa551N:
Still laggy. :(
[Nexus 5 Original Android Development] eng.stk:
Try increasing the down timer further, lets say 5

You can try lower load threshold alittle more, like 40 or even less.

If you use default settings and 2 min core online all is good?
[Nexus 5 Original Android Development] Hatshipuh:
Using the CM version of r407, everything's fine, no noticeable lag.

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] Marescallus:
I did this, and all is good.
[Nexus 5 Original Android Development] stark_br:
Yes, it does de trick.

Tks
[Nexus 5 Original Android Development] Assa551N:
Where can I do this?
[Nexus 5 Original Android Development] eng.stk:
If you use the most agressive settings I said, you should have the same results as min cores online 2.
[Nexus 5 Original Android Development] Tylog:
0.0000 lag here. Btw. Only writing " lag, back to xxx helps nobody" this is pointless.
[Nexus 5 Original Android Development] FPSKunal:
Too much lag on r407 rolling back to r398 !!
[Nexus 5 Original Android Development] Bentso:
Yes the lag is gone.

Also I noticed you enabled aggressive multi core power saving as default in r407. Does it affect battery life?
[Nexus 5 Original Android Development] Marescallus:
I'm using UKM and Synapse. Just search for them.
[Nexus 5 Original Android Development] sirovai:
For me power saving is disabled by default...

---------- Post added at 06:36 PM ---------- Previous post was at 06:34 PM ----------

With one core min there are too lags. With 2 cores min all is perfect. Thank you eng.stk
[Nexus 5 Original Android Development] GtrCraft:
Only setting min cores to 2 fixes the lag for me, good release for the most part
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Same her no more laggy ? thanks eng.stk
[Nexus 5 Original Android Development] eng.stk:
No multicore powersaving changes on r407, you got something wrong there.

For you with issues: are you on ART or Dalvik+xposed?
[Nexus 5 Original Android Development] borgsta:
This was actually my first time installing this kernel and it was awful with that lag. Was about to give up but then quickly read this last page :good:

I'm on ART running LiquidSmooth ROM, default settings were laggy as all hell. Screen not really responding to touch at all, gestures from NOVA launcher were really struggling.

Switched min cores = 2 and now it is absolutely flying along. Glad I persisted for that extra minute of reading.
[Nexus 5 Original Android Development] haasgo:
Finally somebody DID read whats been said here :thumbup: my hope in xda is slowly recovering :p
[Nexus 5 Original Android Development] Bentso:
Ok my bad then.

I am using dalvik+xposed.
[Nexus 5 Original Android Development] vrda08:
+1
[Nexus 5 Original Android Development] Tylog:
Information about the lag with Build 407

The issues with 407 (some of you report lags) are located, a updated build with the lag fix is coming soon, no ETA, It will work as quickly as possible.

Be patient.
[Nexus 5 Original Android Development] Gallardo994:
407 goes fine. Changed down timer to 5, up threshold to 40, min cores to 2. Same battery (it seems), but godlike performance.

Sent from Nexus 5 using garbage^W Tapatalk
[Nexus 5 Original Android Development] nedooo:
Something is buggy with 407, random freezes happens here and there. Back to 398 I'm fine with that. As I said this kernel is art and I like to use it like no other kernel(without further tuning).

Edit: Oh I see eng.stk is about to crush that bug :)
[Nexus 5 Original Android Development] tcat007:
407 feels great here. Cores to 2 and even Tapatalk feels smooth. Waiting to see how battery goes. 5+ hours SOT seems the norm lately.
[Nexus 5 Original Android Development] neriamarillo:
Yes we are testing at the moment. Fix will come soon. [emoji106]
[Nexus 5 Original Android Development] wardawgmalvicious:
I don't see the 407 builds on the website.. Are they posted somewhere else?

-wardawgmalvicious
[Nexus 5 Original Android Development] sirovai:
It was a little buggy. A new version will be release asap
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r412

All right crew!

input boost bug on blu_plug is fixed. Big shouts to my blue beta posse :highfive:

Both AOSP and CM builds were updated (although the bug in CM didn't show). Never settle for nothing more than perfection.

I also made an improvement on the process, let's see if anybody notices it...

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!
[Nexus 5 Original Android Development] Aerowinder:
Lag fixed, nice work to everyone involved in testing.

I have a question regarding intellithermal. With it, we have the option to both throttle online cores, and to force cores offline. Why are cores shut down before they are throttled? Isn't it better to first throttle the cores, then shut them down if the temperature does not go down? I know that we can change this, I'm just curious to know if there is a technical reason for it being the way it is.
[Nexus 5 Original Android Development] Nucleotide:
Thanks a lot for your awesome work [MENTION=3873953]eng.stk[/MENTION], as well as the beta testers. Love you all! :laugh:
[Nexus 5 Original Android Development] Tylog:
Love is in the Air lalalalalala [emoji445] [emoji443] [emoji12]
[Nexus 5 Original Android Development] ali262883:
Really great kernel.. Flashed it for the first time.. Everything smooth.. Can we get an option to choose between color profiles? Or flash the kernel without enabling the color profile
[Nexus 5 Original Android Development] vickyjusme:
like the op says. flash ukm and use synapse to customize kernel. Default settings work great BTW.
[Nexus 5 Original Android Development] Nucleotide:
Personally, I use Display Control by Franco to change profiles - works perfectly and very easy to use. :good:
[Nexus 5 Original Android Development] Aerowinder:
Getting no deep sleep on 412 stock settings.

The log is a reboot with a couple minutes of screen off. Didn't notice until I had been using 412 for a few hours.

Obviously suspected a rogue app, wasn't it. Secondly, suspected my custom kernel settings, so reverted. Also not it. Returned to 398, no more sleep issues.
[Nexus 5 Original Android Development] allesmeglische:
Same Problem here.

Getippt mit nem Nexus 5
[Nexus 5 Original Android Development] hocruxx:
Me to. I see in bbs and see that the phone keep awake
[Nexus 5 Original Android Development] setiawanjimmy:
I can confirm no deep sleep issue on 412. I clean install twice. First with gapps secondly without gapps. Both cannot get to deep sleep. Revert back to 398 and able to get into deep sleep.
[Nexus 5 Original Android Development] Psycho Orange:
So bad releases 407/412... Back to r398... Eng.stk WTF? :confused:
[Nexus 5 Original Android Development] expiredd:
I'm getting massive battery drains due to RILJ wakelock in 398 kernel. I've been Googling around this issue and I just found old JB issues. Any idea on what can be going on?
[Nexus 5 Original Android Development] Tylog:
Thanks for the Reports, i talk to Eng. Stk about the deep sleep issues.
[Nexus 5 Original Android Development] sirovai:
Hey mate, it's the first time after the r024 that we have these kind of issues...

This comment is very disrespectful!
[Nexus 5 Original Android Development] theodorius123:
So bad post...Psycho Orange WTF? :confused:
[Nexus 5 Original Android Development] Nucleotide:
WTF is with your lack of respect? :confused:

Instead of *****ing like a spoilt brat, you could always help diagnose the problem? Do some testing, provide some "constructive" feedback?
[Nexus 5 Original Android Development] eng.stk:
Sorry mate, I will refund you...

@ the rest: Yes deep sleep issue confirmed.

Yesterday we were focused in input issue in AOSP, i think I know what it is, forgot to change some stuff back.

If I find the culprit, fix will follow later
[Nexus 5 Original Android Development] 5FOOTER:
Aerowinder, coming from Franco I know the 2 files to rename but I flashed purity ROM so I figured I was good. My question is the to files both have .bak on them is this correct for this kernel?

Sent from my Nexus 5
[Nexus 5 Original Android Development] ironjon:
Being disconnected all the weekend but 412 is running perfect here since this morning.
[Nexus 5 Original Android Development] Gallardo994:
Bak is a backup file.

Sent from Nexus 5 using garbage^W Tapatalk
[Nexus 5 Original Android Development] cleancorekiller:
I flashed this kernel over SlimKat8..... just wondering if there's any app or setting for it hiding somewhere, or is everything already implemented as soon as I flash it?

I found something called 'chamber of secrets' in my dev options, unsure if that was already there or not, ticked the box for it... doesn't seem to do much anyway.

Some help would be appreciated.

Thanks
[Nexus 5 Original Android Development] setiawanjimmy:
Flash UKM + install synapse.

Chamber of secrets is slim's feature not kernel's
[Nexus 5 Original Android Development] cleancorekiller:
Cheers fella

---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------

Forgive me, Google saved the day...... I know I should know better

Sorry to be a pain, but what is UKM and where can I get it to flash it?
[Nexus 5 Original Android Development] Aerowinder:
I can't say with certainty. It's so easy to wipe system and reflash the ROM. That's what you should do.
[Nexus 5 Original Android Development] 5FOOTER:
That's what I did so I think I'm good. I just forgot to check b4 I flashed this kernel. Only ran purity for a couple hours then flashed this. Seems like a nice kernel.

Sent from my Nexus 5
[Nexus 5 Original Android Development] eng.stk:
Code_Blue r414

All right crew!

Are we there yet? :fingers-crossed: :p

All seems fixed now, it was what I thought. AOSP and CM builds refreshed, enjoy :good:

Get involved, test, play, donate, help, contribute.

You keep the spirit alive!
[Nexus 5 Original Android Development] hocruxx:
Thanks mate I appreciate your fast response. Going to test new build now
[Nexus 5 Original Android Development] Nucleotide:
Info on UKM (Universal Kernel Manager) is on the OP.

Hint: it's in the dot points. ;)
[Nexus 5 Original Android Development] Darkmasterhk:
here

google : ukm xda ;D
[Nexus 5 Original Android Development] cleancorekiller:
So there is more derp here than meets the eye after all! Ha!
[Nexus 5 Original Android Development] AquilaDroid:
Flashed 412 just before going to bed last night, woke up this morning to find that phone was awake the whole time. Panicked, looked at BBS nothing stood out. Came right to this thread and downloaded 414, flashed and all is well. Thanks, eng.stk! (Don't let the whiners get you down, this is my favorite N5 kernel by far!)

From my Nexus 5
[Nexus 5 Original Android Development] in1400:
Its a known Error, 414 is online!
[Nexus 5 Original Android Development] climhz:
Eng.stk I think recently you release often than before, just take your time, code when you like, test all you want and release when audience deserve it
[Nexus 5 Original Android Development] eng.stk:
Nah, weekly as always. This last build had a know derp, I couldn't have such an issue in my phone.

Mainly I do the kernel for myself and the blue crew, not the "audience".

People with positive attitude, patient and that support me everyday.

Sure it makes me think: if the release is good, all quiet. If there's a derp all hell breaks loose...

Better the support people gives me and the project, better the things turn out .

But I understand: 99% of Code_Blue builds are so solid that 1 or 2 derps people panic ;p

On the other hand, only the ones that try new and different can fail right?

The only ones that don't fail are the ones that don't do nothing :good:

It's all about the positive vibe :)
[Nexus 5 Original Android Development] Corey-:
running r398 of code_blue on stock 4.4.4

I actually dont wanna update, because r398 is kicking ass!!

good job dude :)
[Nexus 5 Original Android Development] marf28101995:
# 414 is even better

Just saying ;)
[Nexus 5 Original Android Development] R3Lax1:
Atleast explain why and in what way.
[Nexus 5 Original Android Development] AquilaDroid:
[MENTION=4499807]in1400[/MENTION] - Did you read my post?

From my Nexus 5
[Nexus 5 Original Android Development] marf28101995:
Cooler!

Better battery!

Smother!

Explained!

:D
[Nexus 5 Original Android Development] Tylog:
xD
[Nexus 5 Original Android Development] adrianocdias:
is necessary fradom with new 414? Thank you.
[Nexus 5 Original Android Development] marf28101995:
It's opcional
[Nexus 5 Original Android Development] adrianocdias:
but is recommended?
[Nexus 5 Original Android Development] marf28101995:
Personally I don't notice any difference with it so I don't flash
[Nexus 5 Original Android Development] in1400:
Sorry, my Tapatalk doesn't Show me the whole message ?

gesendet von meinem Nexus 5 mit Tapatalk Pro
[Nexus 5 Original Android Development] Tylog:
414 is a great candidate for the next Milestone. After long time of working, testing we have in my eyes the Best CodeBlue Build ever.
[Nexus 5 Original Android Development] reddvilzz:
What? 414 already. Just downloaded 412 and the new one come out :D.

Amazing kernel always makes my phone smooth but also battery friendly and also a great kernel for making my phone cold even though I play games a lot it still remains warm very slick.

Thanks for the awesome kernel eng.stk you are the best!
[Nexus 5 Original Android Development] Tylog:
CodeBlue, faster then

arriba arriba andele [emoji12] the older generation know this mouse xD
[Nexus 5 Original Android Development] lalibm:
Awesomeness

Your kernel = pure awesomeness . The best speed the best perfomance the best battery life . Thank you sir .

Running r398 now gonna try r414.
[Nexus 5 Original Android Development] ghismo83:
Last cm 11 nightly wont boot with r414..
[Nexus 5 Original Android Development] Tylog:
It does, i use cm as second rom. All is fine
[Nexus 5 Original Android Development] Boonyard:
All the people saying 414, do you mean the cm version then?
[Nexus 5 Original Android Development] Tylog:
The CM version is in test folder http://www.engstk.org/code_blue/downloads/test/

The Aosp in stable folder http://www.engstk.org/code_blue/downloads/
[Nexus 5 Original Android Development] endomatic:
There is an AOSP version and CM version depending on which base the ROM you are running on your phone is built off
[Nexus 5 Original Android Development] Gallardo994:
Wait wait wait. I remember there was a game about it. If you know it, could you please remind me?

Sent from Nexus 5 using garbage^W Tapatalk
[Nexus 5 Original Android Development] ironjon:
Yesss r414 is really smoooooth

Sent from my Code_Blue Nexus 5
[Nexus 5 Original Android Development] Tylog:
Lol xD speedy gonzales :)
[Nexus 5 Original Android Development] vrda08:
Smoooooooooooth... Even with min. One core... Amazing work!!!
[Nexus 5 Original Android Development] galaxys:
r414 running smooth and so much cooler! :cool:
[Nexus 5 Original Android Development] kcly001:
Audio quality improvements? It sounds pretty good, maybe someone can confirm or is just my mind . BTW r414 very smooth!! Thanks

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] grognaz:
Thanks for the lag fixes, everything seems to be smooth again with 412+ :D
[Nexus 5 Original Android Development] Tylog:
Now the Thread is on the right place :)
[Nexus 5 Original Android Development] ghismo83:
sorry but test r414 cm won t boot..
[Nexus 5 Original Android Development] Tylog:
Did you use a aosp kernel with the aosp patch before?

Please test dirty flash cm nightly, then 414 kernel.
[Nexus 5 Original Android Development] llevo3:
Booting just fine on latest CM nightly
[Nexus 5 Original Android Development] eng.stk:
r414-CM works fine in CM both http://xdaforums.com/showpost.php?p=55742125&postcount=4319

And I'm using M10 (in ART) as primary this last days.

Reflash you ROM (clean cache and dalvik), remove init.d scripts, remove kernel apps and try again.
[Nexus 5 Original Android Development] Audioboxer:
UKM needing an update in general or is it just the CM version of the kernel causing some issues with UKM? Thanks
[Nexus 5 Original Android Development] llevo3:
Is there any noticeable difference between art and dalvik on CM?
[Nexus 5 Original Android Development] eng.stk:
I don't know what you mean, it works normal. I only have issues with gamma, because I merged positive/negative gamma patch, so you could use NOrmal color apps like faux and franco.

But UKM seems to detect that is CM and uses standard gamma values without positive/negative

Yeah I notice alot of diference. I don't use dalvik since... I don't even remember lol

But I don't use nightlies, if you use it ART rebuilding will take lot's of time and stress out the phone everyday.

I'm on M10 atm
[Nexus 5 Original Android Development] Audioboxer:
That explains gamma thanks, but the GPU screen is having issues as well. Will report in UKM topic.
[Nexus 5 Original Android Development] eng.stk:
Yep I think it was reported also. And faux sound not sticking.

But yes post at ukm thread so you can help apb_axel
[Nexus 5 Original Android Development] andredn8:
I have a question here. sometimes my DT2W wont work for so many times due to 'i dont know thing'. So I should turn it on by push the power button twice to make it locked again. And the DT2W works again. I've that issues this last few days. I dont know what the causes. Please somebody help me :(. And for General Instruction, can anybody give a simple procedure to turn on the DT2W for Code Blue in Synapse? Thanks :)
[Nexus 5 Original Android Development] eng.stk:
If you're in r398 flash r414
[Nexus 5 Original Android Development] bigknowz:
Blazing

Flashed r414, set min cores online at 2 and new benchmark record! Thanks [MENTION=3873953]eng.stk[/MENTION], keep up the great work.
[Nexus 5 Original Android Development] reddvilzz:
Does turning on CPU multi core saving to aggressive have any benefits? Or should I just let it off by default?
[Nexus 5 Original Android Development] marf28101995:
Let it off ;)

Sent from my nexus 5 powered by Code_Blue + Android L
[Nexus 5 Original Android Development] Phazmos:
Only thing I've noticed with it is a little performance hit.
[Nexus 5 Original Android Development] mendozaram:
Which theme is that bro? ROM?

Enviado desde mi Nexus 5
[Nexus 5 Original Android Development] lalibm:
Flux white
[Nexus 5 Original Android Development] asdfasdfvful:
Just wondering, is there a kernel cleaning script anywhere for the nexus 5? There was one from my old phone but I'm not sure if they're all the same
[Nexus 5 Original Android Development] modyt:
Congrats team on Original Development move!

Edit: this is weird. I can see the thread on both Original Development and normal Development forum. :what:

Sent from my GT-I9500
[Nexus 5 Original Android Development] Nucleotide:
I'm assuming the link in Development is simply a redirect to Orig Development now. The link in Dev will drop to the bottom eventually (or disappear).
[Nexus 5 Original Android Development] eng.stk:
Yeah it's a redirection, so people can find the thread.

It will disappear eventually.
[Nexus 5 Original Android Development] Gallardo994:
Ninja_blue kernel

Sent from Nexus 5 using garbage^W Tapatalk