[UNIFIED] Render Kernel [OOS-N-EAS-R2][LOS-N-EAS-R8]

[DespairFactor]

Hi, I know you only support OOS. Having said that, will it cause any problems if I use it over custom roms?

Custom ROMs may cause issues with WiFi, not sure how he is loading the module, I know on CM in previous OP devices we needed to compile the qcacld driver inline for it to work properly.

 

[Mostafa Wael]

This sounds incredible! Will do what it takes to test that Kernel !! EAS for OP3, that is very incredible!! I am just speechless, can't say how exhilarated I am just to flash that kernel. Shame i am on Nougat and have to charge and flash OOS, would like to just flash it now. I am on it!!

Thanks Thanks....million of thanks! :good::good::good:

 

[Jole7]

Render kernel is here great news many thanks man

 

[abhibnl]

Welcome to op3 forum Render. Looking forward to try this baby out soon.

 

[ZeNiXxX]

@RenderBroken

wow nice to see you here in the oneplus 3 world. I was always using your kernel on my lg g2. Cant wait to see your magic happen to cm-kernel

 

[NOSTALGIA]

im so late but welcome @RenderBroken

 

[1337jay]

Wooah, yet another great developer for this awesome device!

Thanks for doing this, @RenderBroken.

 

[=dave=]

Looks very promising.

Testing it for the last hour now and what I can say so far:

1) seems very smooth
2) when the device is idling, little cores rarely dip below 556 MHz, BIG cores rarely below 883 MHz, even sometimes occasional jumps all the way up to 2150 MHz

 

[tmimaesk]

2) when the device is idling, little cores rarely dip below 556 MHz, BIG cores rarely below 883 MHz, even sometimes occasional jumps all the way up to 2150 MHz

Yea I lowered the schedtuneboost to 8 and now it enters 307 mHz.. default was 20

 

[RenderBroken]

SUPER POST!!!

Great! EAS is really where I was hyped for! Thx for your amazing work!.

I'm going to run it 24 hours and see if there are any reboots, if there won't be ill let you know. I noted that the Cpu frequency stays quite high when there is barely any load? Is this normal?

Edit: issue with standby, couldn't get my phone on when I didn't use it for like 3-4 minutes. Had to reboot, but couldn't reproduce the problem
Issues I encountered:
1. Had an instant where my phone's screen was off for 2 minutes, i couldnt get the screen back on so i had to reboot. Yet i failed to reproduce the issue. (Logs didnt show anything)
2. CPU frequency seems to be really overkilling a task. It doesnt like to stick to 300Mhz either.
Other then that it works smooth and flawless! Even Snapchat is now using all 4 cores instead of only 2 little ones on HMP.

Yea, EAS is what I was looking for as well.

1. Did you look here for the log: /sys/fs/pstore/console-ramoops ? This is the only one that will survive a reboot.

2. Sorry, I had it set higher for testing. I needed to see that it was working. Setting stune like this should help:

/dev/stune/schedtune.boost to 10.

Remember, this boosts the minimum frequency to use per task by 10%. So this also means that you will not be getting 307MHz while doing any task, other than idle I should say. I have set another tunable:

/dev/stune/schedtune.prefer_idle to 1 to enable

Sorry for disturbing, but OP need some correction

Anyway, I'm impatient to test it !

Oh, you didnt know? This is only for Froyo. yea, sorry bout that.

Thanks for the heads up!

Yea I lowered the schedtuneboost to 8 and now it enters 307 mHz.. default was 20

I think settings to 10 will be a daily driver. I am still working on this though. I have setup cpusets, meaning that I can set tasks per core, etc. I am working on setting the top-app tasks as the only ones that get boosted while letting foreground and background tasks not be boosted at all. I have just not found a way to do so yet. CM uses a binary to handle setting and mirroring cpuset/top-app to stune/top-app. Its not easy to implement something and inject via kernel. Still, I feel that I can figure it out.

 

[=dave=]

I think settings to 10 will be a daily driver. I am still working on this though. I have setup cpusets, meaning that I can set tasks per core, etc. I am working on setting the top-app tasks as the only ones that get boosted while letting foreground and background tasks not be boosted at all. I have just not found a way to do so yet. CM uses a binary to handle setting and mirroring cpuset/top-app to stune/top-app. Its not easy to implement something and inject via kernel. Still, I feel that I can figure it out.

thank you for your hard work! devs like you, with such a drive to deliver real progress, is what keeps this community alive!

 

[RenderBroken]

Looks very promising.

Testing it for the last hour now and what I can say so far:

1) seems very smooth
2) when the device is idling, little cores rarely dip below 556 MHz, BIG cores rarely below 883 MHz, even sometimes occasional jumps all the way up to 2150 MHz

1. Thanks!

2. try lowering schedtune.boost to 10.

Also remember that EAS will set the core > Frequency > voltage per task. If the scheduler decided that a task needs a higher freq then it supplies that before the task is placed on a core. Also the great thing about EAS (When tuned and setup properly) is that it is setup to not overshoot and overpower task workload. Unlike our standard governor like interactive that does sampling and cpu-boost. These both can overshoot the performance needs pf the current workload thus leading to energy loss. EAS is supposed to be like Goldilocks, just right.

 

[Puddi_Puddin]

1. Did you look here for the log: /sys/fs/pstore/console-ramoops ? This is the only one that will survive a reboot.

As you wish .

 

[marian daciu]

Wow...Render here on Op3,amazing.

 

[RenderBroken]

As you wish .

Thanks!

 

[genesixxbf3]

Good to see you here bro !

 

[tmimaesk]

1. Thanks!

2. try lowering schedtune.boost to 10.

Also remember that EAS will set the core > Frequency > voltage per task. If the scheduler decided that a task needs a higher freq then it supplies that before the task is placed on a core. Also the great thing about EAS (When tuned and setup properly) is that it is setup to not overshoot and overpower task workload. Unlike our standard governor like interactive that does sampling and cpu-boost. These both can overshoot the performance needs pf the current workload thus leading to energy loss. EAS is supposed to be like Goldilocks, just right.

I was searching for eas and I saw google trying eas on hikey board and I didnt dig too much but in their init.hikey.rc, they set global /dev/stune/schedtune.boost to 0 and set /dev/stune/foreground/schedtune.boost to 10 and /stune.prefer_idle to 1

I am trying that right now and it makes idle freq to 307mHz and boosts if foreground task is found

https://android.googlesource.com/device/linaro/hikey/+/master/init.hikey.rc

 

[Mostafa Wael]

just hopped in the train and man sched is so much fun for me.
used the latest post's settings and it was very battery oriented. Switched to the default ones and it became zippy again, however i notice that it still lags behind interactive a little bit, still cannot catch up with my Burnout Profile of governor settings. But it will so soon I believe. Thanks @RenderBroken for the fun! :good:

 

[otonieru]

Wow, am glad that even after OP3T was launched, many recognized dev still come and develop stuff for this amazing phone,

Happy to see you here !

 

[Puddi_Puddin]

@RenderBroken had another reboot, my phone was in standby laying on the table, randomly it rebooted and it went into a bootloop (at least it tried to boot twice). So I flashed your kernal again and everything seems fine. Let's hope it's not too hard to solve

Edit: Another random reboot when screen was on this time! Didn't happen the whole day until now. Switched back to stock kernal. Currently waiting on a new build, take your time