yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Update to 0.11

Hey guys and girls,

update time again.

So as some of you might have noticed we have sort of an input boost defined in the power hal. I think it is not needed with my kernel, so I advice you to flash one of the zips despairfactor made in order to control this behaviour.

You have the choice between different zips:

schedtunefix.zip : This will fix the incorrect top-app value defined in power hal

schedtunfixyyy.zip : this will fix the incorrect top-app value defined in the power hal and set the input boost frequency to yyy

schedtunefixnohint.zip: this will fix the incorrect top-app value defined in the power hal and completely disable any power_hints (input/interaction boosts)

personally I recommend the last one aka schedtunefixnohint.zip. I get great battery life and have a smooth experience. In my opinion EAS is good enough to run without any input boosts. Just set the schedtune.boost for top-app to something between 6 and 10, and run this value on boot.

You can find the zips provided here. If you are on sailfish ( regular pixel ) choose the the sailfish named one and do a backup before flashing.

https://xdaforums.com/showpost.php?p=71387615&postcount=488

Here is the changelog for 0.11 :

- I added a few additional commits to adrenoboost, it is now more conservative and suited for daily use. I run it on moderate boost and don´t notice any battery drain

- performance of the fingerprint reader may be improved <-- I need feedback from you, don´t use it myself

- update to slimbus OC

- a few patches that may help with stability and performance in general

- many patches to schedutil , it is the recommended governor now in conjunction with nohint.zip

- introduced a new governor, called helix_schedutil based on schedutil; thanks to [MENTION=4388232]ZeroInfinity[/MENTION]

I had a little play with it, if anyone finds better values I can include them.

- for more details check my github

Download link is here and in the OP:

https://www.androidfilehost.com/?fid=673368273298938244

have fun with it and a nice day all!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
Awesome work as always!! Thank you
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kyuubi10:
To anyone tweaking the values of this governor i suggest reading the following post first:

https://xdaforums.com/htc-10/development/kernel-helixkernel-v004-t3571409/post71384478

The values of target_load are closely linked to the energy model.

If you change the values without having a look at the energy model first you risk reducing performance AND increasing battery life :)

Hope i've been of help :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rohitece06:
You recommend disabling perfd?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
DespairFactor recommends keeping it enabled. I gotta take a look at it more but at least on the Nexus 5X it controlled a whole lot of different values with the scheduler and governors.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
Perfd was only disabled to keep schedtune.boost for top-app from reverting to 50.

Despair's zips fix it, so you can keep perfd on.

Unless freak07 says otherwise?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
No this was just a workaround to counter the touchboost and getting the right top app boost value. Just flash the nohint zip and leave perfd enabled.

Look at data/system/perfd/default_values. Maybe you know what all settings are. I only recognize some.

As it is now, just flash the nohint zip and keep perfd enabled. Top-app schedtune boost is default at 10. You can try to decrease it to 6 and see if you still have enough performance for your needs.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Exactly! :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drdrewdown:
nomin now instead of nohint?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
It was a typo sorry. Nohint is still my recommendation. Thanks for catching it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drdrewdown:
tried flashing 0.11 on DU latest RC, bootloops from black screen to google & back. Anyone else try yet?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Eyalkn:
Lol 0.10 bootlooped for me on stock and 0.11 works fine but this time I flashed SuperSU
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
Thank you [MENTION=3428502]Freak07[/MENTION] you no make it easy to from Sharkey & Kirisakura they both great kernels,

trying out this one w/ schedtunefix900 zip small cluster using schedutil, Touchboost set to 9 & tweaks on lspeed battery profile.

big cluster gov conservative (reason it would spike high CPU when not touching when on schedutil or new gov,

on conservative big cluster it just uses CPU 307 & 907 MHz so when using daydream for 10 min it would for some seconds go to higher CPU phone didn't get hot, no lags..

Can you believe I got 8 hrs sot yup!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
I didn't get boot loops but got some kernel panics. I didn't investigate so i can't attribute it to this kernel. I'll have to test another time.

Thanks for the contributions regardless [MENTION=3428502]Freak07[/MENTION]

Edit: I didn't reboot recovery between flashing kernel and Su. This could have to do with my issues

Edit2: tried to sound nicer lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
please follow my instructions in the OP properly. if this happens it means there was no boot.img flashed. The dual slot system on the pixel is quite new. the safer way is to just flash the zimage from my zip via fastboot.

if you can, please provide logs when you have kernel panics. without it I can have no clue what´s happening for you.

as to the bootlooping or not making it to the actuall bootanimation. Please extract the zImage from my zip and flash it manually via fastboot and see if it fixes your issues.

I am also on DU (with a few modifications) most of the time and didn´t have an issue once when following the instructions in the OP.

I am testing each of the actual releases for at least half a day to make sure everything is okay.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
This pretty cool GPU boost & enable disable boost I also went to schedboostnohint zip CPU load is much nicer.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
Here's setup if any is interested I reset CPU times when playing 8 ball pool & they stay low schedtune.boost at 6 helix_schedutil for big cluster/ alucardshed for little cluster this if desire in low frequency saves battery still great performance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Anyone know the governor blu active? I remembered using this governor back on my n6 days. I got very good results with it back then.

It makes no use of the EAS scheduler but I decided to give it a try and it performs quite good actually. Anyone interested in a test build with it?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Eyalkn:
Nice, thank you, I'm always up to testing me things
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Was a favorite governor of mine on Hammerhead. I think [MENTION=1863016]rachanta[/MENTION] brought it over to the Nexus 5X as part of his RACER kernel but ditched it soon afterward because it was a pain in the ass to compile. That being said, I'd be down to give it a shot. I think there are some battery gains to be had, but I have my doubts about how smooth it'll be. Schedutil is incredible.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
BETA Update 0.11_1

hey [MENTION=4752299]Alcolawl[/MENTION] [MENTION=4842752]Eyalkn[/MENTION] and all others :)

here is a beta release. It includes mainly the blu active governor from [MENTION=3873953]eng.stk[/MENTION].

remember you will loose the EAS if you choose the governor.

I got good results with it so far. I will post my settings for big and little cluster in the next post. If anyone is down to some tuning or finds good values I may change them in the next release :) for now we we use default values.

Changelog 0.11_1

- added blu active governor

- updates to helix_schedutil, alucardsched and darknesssched

- updates to sdcardfs

- other things look at my github

Download:

https://www.androidfilehost.com/?fid=745425885120716589

it is also in the testing folder if you follow the link in the OP
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Here are my settings for blueactive

First screenshot is for big and second for little cluster. You can also distinguish them by the hispeed freq. 2,2 ghz is big cluster obviously. :) :good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
[MENTION=3428502]Freak07[/MENTION] would you consider making a build without OC?

I can't seem to run .11 without random reboots, and not sure how to get proper logs.

Sharkey kernel once tried OC and it gave me reboots, so this is why i assume it to be the cause of my issues.

Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
Try setting frequency lower thru kernel app.

Trying out looking good :good:

Thank you :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
That would mean I'd have to try to beat it from OC on boot. It may not be possible or practical
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
Ahh k maybe possible before unlocking device go to battery saver thru notifications & turn on? lol

Could it be some devices CPU are different or defected hardware?

I remember some Motorola devices would not tolerate OC

Pixels too?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
Every cpu manufactured is binned based on performance. Some can overclock while others can't - silicon lottery.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
Yes it's possible my device is binned lower. I suspect this. This is also why i want to test it.

As for justification for building for lower binned devices, not only is OC arguably unnecessary for this device, it may be desirable for a developer to build a more generally compatible kernel than not.

These are my assumptions. I wholly accept whatever freak07 decides to do. I just really want to try his kernel lol
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
If I find time this evening I will compile one without OC.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
So. Any thoughts on blu active?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
It's been working out pretty good I see frequency using 307 the most little 1563, big 2246 cluster

Battery life seems great needs more testing for me.

Performance is awesome!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Hey guys and girls,

update time again. Just in case anyone missed it last time, this is the information about the schedtunefix zips provided by despair.

So as some of you might have noticed we have sort of an input boost defined in the power hal. I think it is not needed with my kernel, so I advice you to flash one of the zips despairfactor made in order to control this behaviour.

You have the choice between different zips:

schedtunefix.zip : This will fix the incorrect top-app value defined in power hal

schedtunfixyyy.zip : this will fix the incorrect top-app value defined in the power hal and set the input boost frequency to yyy

schedtunefixnohint.zip: this will fix the incorrect top-app value defined in the power hal and completely disable any power_hints (input/interaction boosts)

personally I recommend the last one aka schedtunefixnohint.zip. I get great battery life and have a smooth experience. In my opinion EAS is good enough to run without any input boosts. Just set the schedtune.boost for top-app to something between 6 and 10, and run this value on boot. additionally

You can find the zips provided here. If you are on sailfish ( regular pixel ) choose the the sailfish named one and do a backup before flashing.

https://xdaforums.com/sho...&postcount=488

Changelog for 0.12:

- added blu active governor

- updates to helix_schedutil, alucardsched and darknesssched

- updates to sdcardfs

- maybe some performance improvements <-- please give feedback

- other things look at my github

- made a non oc version (no cpu OC) ( [MENTION=5315603]Ofthecats[/MENTION] ) :good:

Downloads are here:

OC: https://www.androidfilehost.com/?fid=673368273298940168

NONOC: https://www.androidfilehost.com/?fid=457095661767146271

Hint: I set schedtune boost of both top-app and foreground to 6. Runs very good for me using schedutil.

Have fun with it!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
Will this kernel work with no root?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
I tried flashing it and it didn't boot.

Edit: It won't work for me without root. I tried only flashing the kernel, it didn't work. I tried flashing it with the kernel and twrp, and it still wouldn't boot. I flashed Elemental-X first try, without twrp, and it boots up just fine. I tried .11 and .12, they both won't boot up for me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kkeith:
Hmmm... Am I the only one who hasn't been able to flash this kernel since .10? I'm on RR build 20170314, which is the only other thing that has changed, I was on an older build of RR when I was on .10. Every time I try flashing either .11 or .12 doing:

-Flash RR

-Flash kernel

-Flash schedtunefixnohint

-Flash TWRP

-Reboot back to recovery

-Flash supersu sr3

-reboot to system

It boots no problem, but I am still left with EX kernel 1.08

Edit just remembered I also just recently updated TWRP to 3.1.0 rc2 is this maybe part of the issue as well?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
I can't even flash schedtunefixnohint on RR without it bootlooping....
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bbender716:
This happens to me too with Sharkey's schedtune fix. It's rr specific and because it's lineage based and doesn't support that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BHermes211:
Is it aosp based only?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kkeith:
Nice, got it figured out, after reading through the TWRP thread it solidified the idea that TWRP was in fact the issue, then flashed the same way I write above and I got the boot loop as you guys described, then tried the same without the schedtunefixnohint and I'm back on kirisakura!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
Did you only flash the kernel zip? I'm not rooted atm and it won't boot with kernel+TWRP or only the kernel. I know it will work with root, but I can't get it booting with root.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kkeith:
Ya I rooted at the same time
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
I thought this kernel also works without root. Is there another zip file or something?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kkeith:
I don't think it really matters with kernels whether your rooted or not, you'll just be stuck with the stock settings the dev provided with it I believe.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
I agree with you, however booting the rom without root is not possible with kirisakura .12 for me. I have tried to flash multiple times in various different ways, and it just won't boot. I know it will work if I flashed SuperSU last, but I don't want to be rooted atm. In theory, without root should work, I just don't know how to get it booting.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] drdrewdown:
agreed, this is the same problem i've been having since DU went root-less. Thanks for helping pinpoint
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Did you guys try what I suggested earlier?

Take my zip, extract the zImage from the kernel folder and flash it via fastboot.

Please report back if this is working.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheNewNEXUS:
Oh sorry, I didn't see that. I just rooted my device earlier. I was bored of the performance of the stock kernel. Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
Im on 0.12. it has mostly been stable. I wanted to see if I could run it before trying nonOC

I just had a random reboot while typing in Hangouts.

https://drive.google.com/file/d/0Bw_7kQg5zZe6SS1KUnVvazROR1U/view?usp=drivesdk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] anomalous3:
Just wanted to let you know the not only is it running great on DU, but any bootloop problems are no longer present for me, and idle battery usage has dropped from 2.8%/hour to 0.75%/hour (helixsched for big, alucardsched for little)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
This file looks corrupted... :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Getting excellent battery life here :)

Just did some reading via palabre, lots of texting in hangouts, streaming music via spotify, xda labs, emails, sms.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
I'm able to view it. Do you mean the text looks corrupted within the file?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
see attachement
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
Yea it keeps getting corrupted for some reason.

For now, I flashed the nonOC.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Report back your results with non oc. Also what rom are you running?

I did not have a single reboot with the release versions of this kernel...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Great to hear and thanks for your feedback.

I have usually an overnight drain of about 0,3%/h. But idle drain depends on many things like cell reception.

If you take a lot of videos and have google photo backup turned on it will drain the battery heavy when screen is off. That is also something to have in mind, because of the unlimited storage from google.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
I was on DU and got reboots with Kiri 0.11.

Now I'm on PN, and had issues with 0.12.

0.12nonOC hasn't rebooted on me yet in the last 4 hours.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Tylog:
That's with blueactive or with a eas gov?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Alcolawl:
Bluactive report

Just finished a whole day of running blu_active governor. Sorry I did not comment sooner, things got pretty hectic over the weekend. Before we jump into comments about the governor I just want to state that I have never had a random reboot or problems booting with this kernel and I've been running this kernel since like the 0.3 release.

Battery Life

I unplugged my phone this morning before work. This was just about 15 hours ago. I currently have 53% battery. Because SoT is a useless metric, let me give you a picture of my setup so you can have some perspective:

Power Consumption Related Stats

Screen off drain since unplugged: 1.95%/hr (Includes 45 minutes of iHeartRadio in the morning and 1 hour of music at the gym)

Screen on drain since unplugged: 13.59%/hr

Current Settings

Screen Brightness: 90%

Adaptive Brightness: On

GPU Boost: Low

I/O Scheduler: Deadline

Readahead Value: 1024kb

Schedtunefix800.zip flashed, meaning input boost of 800MHz

Additionally I tweaked the bluactive governor settings pretty heavily. I'll share them when I'm happy with them, but for now the CPU is behaving too erratically. Need to dial back a few values. I'll probably do that when I'm laying in bed tonight and test drive it tomorrow.

Comments on UX

No slowness, lags, stutters, etc. to report. Some things are a little slow to respond to input in EXKM but those were present when running schedutil as well. My day usually consists of iHeartRadio on my commute to work, Hangouts at work, bursts of Snapchat usage for a few minutes at a time, consistent but sparse group texts from my buddies, light internet usage, light Swipe (Facebook Alternative) usage, and a few phone calls. Silent car ride home so I don't want to murder myself and then an hour of music at the gym. I am running ARISE audio and there are no stutters, cracks, pops, or other artifacts to report when running a less aggressive setup like this, which is great.

All in all, these settings are pretty sweet so far. I'm not ready to say that battery life is better but looking at the CPU clock speed usage graphs in EXKM, one could surmise that there are gains to be had. Max frequency is used much less on both clusters when compared to schedutil in the same conditions. In fact the both clusters spent the majority of their time idling.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
I haven't had any issues yet with nonOC. I said i had this issue with Sharkey and despair determined it was due to OC. I hope I'm the minority when it comes to lower binned SoC.

I don't consider SoT a useless metric when treated with care. However, I haven't had much deviation from my average SoT with this device, so I don't pay it much attention.

Frequency distribution is also an iffy metric, but it's something I always check too. I first tried (~1 day) Helix sched, and distribution seemed well spread with a strong tendency on the low end. Now, I'm going to check out darkness for a day. I expect similar results.

I'm curious about non EAS governors, and I'm curious about tuning governor's for the pixel in general. But, the pixel is kind of awesome out of the box. It doesn't seem like any devs have found significant improvements to be made.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Oh crap I forgot to write it down.

The screenshot is with schedutil, Nohint zip, oc kernel, gpu oc and boost to medium. Screen brightness was about 50% and adaptive.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Freak07:
Next build will have sultanxda’s cpu input boost built in.

As you are already aware I do not like qualcom/googles approach to boost all cores to 1,1 ghz for 1,5 secs when interacting with the phone.

Sultan’s boost is way more subtle. So, when using the nohint zip from despair you can just activate sultanxda’s boost via exkm in case you experience any stutters. By default it is disabled.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Ofthecats:
I'm glad I can use your kernel. It has been stable on nonOC.

I wish others would comment on it, whether or not it helped them run the kernel better.

What are your thoughts on removing OC from the kernel in general, or possibly building two? I assume that i may not be the only one with a lower binned SoC.