yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] ironjon:
Enjoy the beast!
[Nexus 6  Original Android Development] eng.stk:
Guys beware of Play services v7, it will kill your deep sleep with a wakelock.

Not kernel related, but better some of you know before *****ing about battery...

http://xdaforums.com/showpost.php?p=59233924&postcount=6741
[Nexus 6  Original Android Development] rebretz000:
Thanks for the heads up.

Spent the last 3 hours at work unistalling app, reflashing ROM and kernel.

Good to know what it is. Hopefully the Googlers get it fixed soon.
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r128

All right crew!

Just pushed weekly update, lot's of goodies inside, go get it :)

Changelog http://goo.gl/ePDsEh
[Nexus 6  Original Android Development] RhapsodyK:
Happiest thing on Friday - flashing code blue :)
[Nexus 6  Original Android Development] chopt51:
I was just looking into encryption and thought I was decrypted. That this kernel is. Maybe I'm looking at the wrong thing.

Currently on dirty unicorns and latest kernel.
[Nexus 6  Original Android Development] marf28101995:
This kernel doesn't force encryption so
[Nexus 6  Original Android Development] chopt51:
Just want more clarification. My settings say encrypted. How do I decrypt I thought I was.
[Nexus 6  Original Android Development] ilanor:
Hello. You'll have to format data from recovery. You'll lose all your files so make a backup to external. If/when you go to update your ROM be sure to flash Code Blue kernel before booting. Let us know how you get on.
[Nexus 6  Original Android Development] clothednblack:
I'm still on v5 lol. Guess I need to search for v6.
[Nexus 6  Original Android Development] marf28101995:
That's playstore version lol
[Nexus 6  Original Android Development] clothednblack:
Oops lol

Then I'm on 6.6.0.3 ?
[Nexus 6  Original Android Development] ironjon:
I can smell 5.1

http://www.amongtech.com/google-release-android-5-1-march-11/
[Nexus 6  Original Android Development] joshnichols189:
I'm probably missing it, where is the CM kernel?
[Nexus 6  Original Android Development] marf28101995:
Cm is aosp so.. Its the normal one
[Nexus 6  Original Android Development] joshnichols189:
I'm fairly certain CM makes changes through CAF which require a different kernel.. especially considering the normal one bootloops on CM.
[Nexus 6  Original Android Development] marf28101995:
Cm is 90% aosp for now ** so the kernel works with the normal version of cm

If you're using a caf build that's different

Caf isn't supported here
[Nexus 6  Original Android Development] jeromechrome1:
Does latest build have kexec-hardboot patch? https://plus.google.com/106544733723469872647/posts/FZ2cSzTQwBH

Sent from my Nexus 6
[Nexus 6  Original Android Development] marf28101995:
Not yet
[Nexus 6  Original Android Development] neriamarillo:
Multirom devstated that he won't release the patch for other kernel devs until he can get it stable. It should not be too long.
[Nexus 6  Original Android Development] ironjon:
Anyone knows if kernel adiutor supports kcal v2?

Seems I cannot apply a lot of profiles

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] jeromechrome1:
Where can I find these profiles? Been searching all week long

Sent from my Nexus 6
[Nexus 6  Original Android Development] ironjon:
There are a lot of profiles out there :)

I took a few of them in Franco and Chroma thread and put in a sheet https://docs.google.com/a/solvay.com/spreadsheets/d/1JnUlmjUQEBU0OA0EptEno4-Z5qFUzOLJ73me4tzg968/edit#gid=0

But there are some values like saturation that I cannot insert, it has a maximum of 158 in kernel adiutor
[Nexus 6  Original Android Development] Riddlah:
If you have synapse, use that to change the screen values. Synapse uses the layout like franco kernel.
[Nexus 6  Original Android Development] joeyddr:
If i run Synapse i get no UCI support detected....
[Nexus 6  Original Android Development] Riddlah:
Make sure you have the latest version of UKM installed. If you do, you may need to reset uci
[Nexus 6  Original Android Development] ironjon:
Device not supported :( (Latest version of UKM installed)

EDIT: Solved!

Thanks
[Nexus 6  Original Android Development] ZeppelinJ0:
How did you solve the device not supported
[Nexus 6  Original Android Development] ironjon:
Reading the UKM post :)

In terminal emulator type su then /system/etc/ini.d/UKM

Then you can launch synapse
[Nexus 6  Original Android Development] ZeppelinJ0:
This is what I get when trying to run that, does this mean my init.d isn't supported?
[Nexus 6  Original Android Development] wrongway213:
Try downloading Universal Init.d from the Play Store and turning it on.
[Nexus 6  Original Android Development] ironjon:
You are typing \system\etc\init.d\UKM instead /system/etc/init.d/UKM
[Nexus 6  Original Android Development] eng.stk:
Of course they work and of course it's kcal v2. I was the first to have it on any kernel out there ;)

The thing is that kcal min values are not zero and Kernel Adiutor developer made it zero, he used offsets.

For instance, saturation min value is 224 and max 383: on the app min is (224-224 = 0) and max (383 - 224 = 159)

The same for value and contrast min ( 128-128 = 0) and max (383 - 128 = 255)
[Nexus 6  Original Android Development] joeyddr:
Here is your document adjusted for use with Kernel Adiutor, offsets applied where needed.

https://docs.google.com/spreadsheets/d/1Lm1o941EsF-dHGCqZZAlErGMfXwJEkwCwVaEiBWUHhk/edit?usp=sharing
[Nexus 6  Original Android Development] ironjon:
Huge thanks to both guys :)
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r163

All right crew!

Just pushed Code_Blue r163, go get it :)

This is only for Lollipop 5.1 and next releases will be also.

For now supports stock ROMs and most AOSP. CM12.1 when be ready when they are.

You have a Nexus, move on :)

Changelog: http://goo.gl/C6BjoA (full rebase)
[Nexus 6  Original Android Development] clothednblack:
Downloaded and stored in my "soon to be flashed" folder ;). Thank you
[Nexus 6  Original Android Development] joeyddr:
Working good vanillapop 5.1. Will you be sticking with the default all cores online like stock?
[Nexus 6  Original Android Development] eng.stk:
Nope , it's nonsense
[Nexus 6  Original Android Development] joeyddr:
Lol ok
[Nexus 6  Original Android Development] papikev:
There seems to be an obvious split on the opinion of having all 4 cores on all the time. Neobuddy and eng.stk (maybe others as well)seem to have the same perspective about it, yet Franco seems to be of the other opinion of it having a positive impact on performance. I think I understand both viewpoints, but wondering why two different thoughts between respected kernel devs?
[Nexus 6  Original Android Development] joeyddr:
Running a stock based ROM with latest blu and I get a reboot during antutu. No lask_kmsg
[Nexus 6  Original Android Development] wrongway213:
I would also like to hear more viewpoints from kernel devs on this. Neo and Franco could not be any further from one another in how they seem to view the change and they're two of the smartest kernel devs I've ever seen easily.. gotta be something in the middle ground, I have a hard time believing any of them are just "wrong"
[Nexus 6  Original Android Development] eng.stk:
Everytime I read this I just wonder why people don't use their heads..

A feature? Onlining all the cores, all the time you can do in any device since ever.

Google did it in the shamu because of encryption the device is crap, the device needs power because of the qhd display and the crappy cpu-boost implementation (which I never used).

Where on earth 4 cores online will use less juice thean 2? There would be no hotplugs at all if this is true.

And while we are at it, remove freq scale also.

The truth is in balance: Our device use most of the time 2 cores and load is still very low, 3rd core and 4th don't come online that often. And I don't have any performance issues on my kernel, so...

Either way you can set min cores on blu_plug like 4 to have all the cores online all the time.
[Nexus 6  Original Android Development] eng.stk:
Antutu crashes sometimes even in 5.0, not kernel related.

I run it a couple times, no issues.
[Nexus 6  Original Android Development] USA-RedDragon:
That is wrong. Where is your proof? And to assume Google did it to cover their tracks for shamu's encryption is slanderous. They have teams of electrical engineers to figure these things out. I personally have proof using a simple equation. Power=Voltage^2 * frequency * cores online. If you plug in 980mv at 2035mhz at 2 cores and divide that value by the result of 760mv at 806mhz at 4 cores, you get a ratio of about 2:1. Meaning 4 cores at 806mhz uses roughly half the power of 2 cores at 2035mhz.

Tl;dr You're wrong. 4 cores uses significantly less power
[Nexus 6  Original Android Development] wrongway213:
I'm clearly WAY less informed on this than eng.stk who you directed this at, so my apolgies if this is significantly more simple/obvious than what you intended to discuss here, but I am curious where in that equation you find proof that cores will all follow that numerical logic? Is that just standard procedure, i.e. if I was to turn all 4 cores on in Synapse right now on 5.02 on any given kernel ,would I observe this behavior? Or is this specific to certain kernels, dependent on 5.1 changes, etc? I am just curious as to how we arrived at these numbers being "proof" = I am inferring from your use of that word in this context that it should be obvious to a kernel developer, but as a simple user I would quite like to understand as I don't know how to feel about this four core 5.1 thing, especially with your equation here, Google and Franco on one side and eng.stk and neobuddy89 so far on the other.
[Nexus 6  Original Android Development] marf28101995:
Seems all good on the paper ?

Big lol

Where is the power consumption needed to hot plug all the cores when the phone leaves deep sleep state ?

Even math can't explain somethings...

And when the phone is at minimum load possible... Tell me how 2 cores at minimum frequecy is worst than 4 cores at minimum frequency... Two times better...maths....
[Nexus 6  Original Android Development] USA-RedDragon:
Its a rough equation for Static power consumption. If you look it up in google you'll find several write-ups by collegiate students and professors on the subject.

And personally, I get 6+ hours SOT with this 4-core setup I've been using a long time on Vindicatior
[Nexus 6  Original Android Development] papikev:
To follow that up, I am at almost 7 hours screen on time running all 4 cores on code_blue with 15% battery left. Browsing/music and downloading. Granted, still on 5.02. Anyway...
[Nexus 6  Original Android Development] USA-RedDragon:
I tend to play games with at at 6+hr sot. http://forums.anandtech.com/archive/index.php/t-119229.html
[Nexus 6  Original Android Development] papikev:
Looks like a good read. I'll check it out later. On paper + stats in real time use == :)
[Nexus 6  Original Android Development] eng.stk:
No, you're wrong because you're choosing limits.

Load works with probabilities and percentages. Scheduling of jobs and tasks have an important thing to say here.

And because most of the time you will have 4 cores using power and the device don't need it.

And on 4 cores you will have 1 or 2 cores at higher frequencies, not always at very low freqs like you've been told.

Time dependent systems aren't linear and there is things like boosts and so on in game

.

Imagine this: the loads asks for 2 cpus at 1036. You will have around the same on 2 cpus on the 4 core situation because load isn't spread evenly on the 4 cores. Also you you will have the other 2 cores at 300 or 422 sitting there.

Where this saves battery? And i don't have any performance issues in my kernel to justify some situations.

I'm still waiting for that good proof on the 4 core situations.

All that fuss about a thing that is so old: 4 core always on kernels are been around for quite some time and only a couple people use it.

In a couple weeks I'll be seeing all that hype vanish and I will laugh.

And get this: I'm not here to proof anything to anyone.

Read above: I am not here to make right or wrong: if we believe anything we are been told, we would be using stock kernel, stock ROM and probably an iPhone.

I do a lot of testing and code a lot also. I don't go get my thinkings out of google and wikipedia.

You can tweak everything in the kernel: tweak to suit your needs.

I try to give a balance between battery and performance, but tunables are meant to be used if you want /need.
[Nexus 6  Original Android Development] USA-RedDragon:
I never said your purpose here is to prove yourself. Just asking you to verify your idea in some way. And shamu's kernel should have power aware scheduler. Especially if its based on lk. Plus if cores 3 and 4 were not processing anything they would just go into power collapse and use very little power, anyway.

---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------

We had one person in the Vindicator beta testers group get 8hr sot with all four cores on
[Nexus 6  Original Android Development] ironjon:
Tried stock 5.1 kernel and I can not feel any lost of performance with 2 cores instead 4.
[Nexus 6  Original Android Development] neriamarillo:
Remember that sot is always subjective. Not even the same person can achieve the same usage 2 days in a row, not even leaving the screen on and not doing anything with it.

The 4 core logic would work but not if you're keeping all cores going up to the max frequency. For this to have the same impact you would have to measure and adapt the frequency of each core to around half of the 2 core setup so that each core would have more or less the same amount of load per frequency. You just can't turn 4 cores on and expect it to magically make millions of differences.
[Nexus 6  Original Android Development] DontPushButtons:
Really, what it comes down to is what side of the fence you're on.. Trinity kernel (at least on the n4) worked on the premise of 4 cores actually saving some power because most of the consumption comes from plugging them on/off.

Different chip obviously, but same argument for years now. Different strokes for different folks really. Like eng.stk said, its why most kernel devs allow tunables in their kernels.

Maybe [MENTION=1811927]simms22[/MENTION] could chime in with a little insight, since I'm sure he bears the brunt of most of morfic's kernel testing lol.
[Nexus 6  Original Android Development] joeyddr:
http://xdaforums.com/showthread.php?p=59540555 not sure what needs to be done permission wise. But can confirm the FC
[Nexus 6  Original Android Development] franciscofranco:
eng.stk you're forgetting about cpus hitting idle/power-collapse being online. Between tasks they sleep/idle and the scheduler's work is to pack tasks accordingly so that those cores can sleep as much as possible while maintaining some sort of perceived performance. On older Kraits these power states were pretty much broken, only starting with SD801 we're seeing an increased emphasis in leaving those cores online and leaving the scheduler dealing with 'em for allocating tasks and guaranteeing that they sleep enough., because the drivers that deal with power states are much better than before. There's a good discussion about this on an older LKML thread where Linus and other scheduler guys are discussing unplugging and hotplugging cores vs leaving them on.

Just something to think about.
[Nexus 6  Original Android Development] s2kpdx:
Yup, System UI FC's for me on the new Euphoria 5.1 build...
[Nexus 6  Original Android Development] marf28101995:
Fc is caused by theme engine

The kernel doesn't have yet the patches to supporting it

Should be fixed in the next version :)
[Nexus 6  Original Android Development] eng.stk:
Well I still don't see a definitive perspective on this.

On the case of the N6 I clearly see the correlation between the /O issues, the need for increased pipelines because of encryption and the hiccups some people had in games because of the gigantor amoled.

I discovered there's a clear performance regression on Samsung eMMC if you don't use mpdecision for instance.

Obviously, low freqs in more cores compared to hi freqs in less cores would use potentialy less power, but I don't see this linear behavior on task management.

I always see some higher freqs in place probably because of boosts and the likes and at the end 2 cores at 300 or 422 will still use less power than 4 cores in the same or similar states.

For the time being I stand my case.

Did you tested the 4 core situation on the OPO?
[Nexus 6  Original Android Development] mwebb34:
This work on 5.0.2? Thanks

Edited,

Nevromind
[Nexus 6  Original Android Development] ironjon:
R163 only for 5.1
[Nexus 6  Original Android Development] joeyddr:
Not all of them... Doesn't work cause of some permissions...patiently waiting for my boy blue lol
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r175

All right crew!

Just pushed weekly update, go get it!

Build features new Linaro 2015.03 toolchain, KCAL updates and a blu_active improvement.

For the rest of the goodies, check changelog.

From now on, my releases will be anykernel zip installer.

This means it uses previously installed ROM kernel Ramdisk, make it compatible with 99.99% of the stuff out there with minimum changes by me.

If already have Code_Blue just flash over, if you come from other kernel dirty flash you ROM and flash Code_Blue after.

Changelog: http://goo.gl/PL7hPi
[Nexus 6  Original Android Development] clothednblack:
So, they will now work on 5.0 and 5.1?

Sorry if I read that wrong.
[Nexus 6  Original Android Development] eng.stk:
No, 5.0 is dead.

They will work in any 5.1 ROM
[Nexus 6  Original Android Development] clothednblack:
Lol, I'm on a dead rom. Thanks for the response
[Nexus 6  Original Android Development] eng.stk:
Yep you are, you have a Nexus move on :cool:

On OP:
[Nexus 6  Original Android Development] clothednblack:
I was waiting for exposed to update and RRO, Layers is good to go so I might just do it tonight.
[Nexus 6  Original Android Development] eng.stk:
If you need RRO you can try Chroma, works good.
[Nexus 6  Original Android Development] clothednblack:
Was on chroma 5.0.2, just flashed latest with your kernel. All is good!
[Nexus 6  Original Android Development] ironjon:
Using this combo for a month and really happy with it.

Thanks for the update [MENTION=3873953]eng.stk[/MENTION]
[Nexus 6  Original Android Development] boysetsfire:
Been trying this kernel for the first time, I've always heard good things about it even in the Nexus 5 forums :) for now all good! Thank you :)

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r186

All right crew!

Just pushed weekly update, lot's of goodies inside, go get it!

This is for Lollipop 5.1 ROMs only.

Changelog: http://goo.gl/mkj3OV
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r189

All right crew!

Just pushed an update with Multirom support, go get it!

This is for Lollipop 5.1 ROMs only.

Changelog: http://goo.gl/9B6IUt
[Nexus 6  Original Android Development] clothednblack:
Thank you for the update, keeps my phone happy and my flash withdrawal at bay.
[Nexus 6  Original Android Development] otisman:
[MENTION=3873953]eng.stk[/MENTION] what twrp you running for f2fs on 5.1 tried latest dhacker 2.8.5.0 but no luck much alohas
[Nexus 6  Original Android Development] eng.stk:
Yes used that one, now I'm using multirom one 2.8.6.0, it has f2fs support
[Nexus 6  Original Android Development] otisman:
Got link for multirom one much alohas

Found it! Thanks for the info
[Nexus 6  Original Android Development] rebretz000:
where you find it.
[Nexus 6  Original Android Development] otisman:
Here you go

http://tasemnice.eu/multirom-test/
[Nexus 6  Original Android Development] eng.stk:
Code_Blue r196

All right crew!

Just pushed weekly update, go get it!

This is for Lollipop 5.1 ROMs only.

The zip uses anykernel installer, this means it uses previously installed ROM kernel Ramdisk.

If already have Code_Blue or ROM default kernel installed just flash over.

If you come from other kernel dirty flash you ROM and flash Code_Blue after.

Changelog (small rebase): http://goo.gl/QWeAsF
[Nexus 6  Original Android Development] ac3theone:
Been running this 2 days now, so far so good
[Nexus 6  Original Android Development] ironjon:
Yes, perhaps a bit faster than previous build with same amazing battery life
[Nexus 6  Original Android Development] eng.stk:
Yep, working very good indeed :)
[Nexus 6  Original Android Development] galaxys:
Just got my Nexus6 and glad to see CodeBlue here! :)
[Nexus 6  Original Android Development] eng.stk:
Good to see you here mate :)
[Nexus 6  Original Android Development] glitchhawk:
I'm loving this kernel. I've only had 1 hard reset that i know of in like a week and a half and it was caused by an app. Thanks for the awesome kernel!
[Nexus 6  Original Android Development] galaxys:
Flashed the latest Chroma rom with r196 and my new Nexus6 hasn't felt better! Kudos
[Nexus 6  Original Android Development] eng.stk:
I used stock most of the time, 5.1 is very nice.

I also went with CM 12.1 and Optipop, they are nice.

But now I'm with Purity 5.1 merged, I don't need anything else really :D
[Nexus 6  Original Android Development] eng.stk:
Everything that has a beggining has an end

I will not continue this thread for the time being, those of you that want to follow my wicked endevours, you can find me at G+.

[YOUTUBE]YvIrW0mPs2s[/YOUTUBE]
[Nexus 6  Original Android Development] eng.stk:
blu_spark r21

The era of the blu_spark is here.

Enjoy :good:
[Nexus 6  Original Android Development] mkcbbusiness:
Welcome back, loved your kernel on my n5
[Nexus 6  Original Android Development] ztotherad:
can't wait to try this awesome kernel on my shamu.
[Nexus 6  Original Android Development] mkcbbusiness:
Don't see any download links.
[Nexus 6  Original Android Development] spevil07:
http://xdaforums.com/devdb/project/?id=11176#downloads

Gesendet von meinem Nexus 6
[Nexus 6  Original Android Development] Byrd San:
Welcome back! Just when I try to put an end to my kernel flashing days too.....oh well
[Nexus 6  Original Android Development] resynx:
Time to give this a spin :D
[Nexus 6  Original Android Development] CrashTestDroid:
Welcome back eng.stk!

A note from using it a bit, the max freq stays at 2.6 GHz regardless of settings in Kernel Adiutor or Synapse. Great performance, super fast hotplugging, love it so far :D
[Nexus 6  Original Android Development] eng.stk:
Maybe, I'll take a look later.

I don't UC.
[Nexus 6  Original Android Development] Rykochet:
Thank you for coming back! I missed Code Blue.
[Nexus 6  Original Android Development] Rich508:
THANK YOU for coming back welcome back I miss code blue kernel the best kernel I ever used on shamu :)
[Nexus 6  Original Android Development] Mervingio:
Woooohoooooo Thank You Rui!
[Nexus 6  Original Android Development] puritan007:
I was still running code blue. Lol now I'm on this ty
[Nexus 6  Original Android Development] DespairFactor:
[MENTION=3873953]eng.stk[/MENTION] welcome back
[Nexus 6  Original Android Development] eng.stk:
blu_spark r23

quickfix is up!

Seems like new thermal driver is derping max freq, so I reverted to previous driver while I don't have the time to get it sorted.
[Nexus 6  Original Android Development] resynx:
Sweet! Judging from the past few hours blue has been running really smooth, thanks for the kernel and the comeback man.
[Nexus 6  Original Android Development] skeamznz:
Good to have you back mate. Running perfectly as always.
[Nexus 6  Original Android Development] Mervingio:
No Faux Sound on M version???
[Nexus 6  Original Android Development] eng.stk:
The driver is half broken since lollipop, I will not use it anymore
[Nexus 6  Original Android Development] galaxys:
Good to see ya back rockin again on XDA! Cool