yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
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.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
As you wish ;).
[OnePlus 3 & 3T Cross Device Development] marian daciu:
Wow...Render here on Op3,amazing.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks!
[OnePlus 3 & 3T Cross Device Development] genesixxbf3:
Good to see you here bro !
[OnePlus 3 & 3T Cross Device Development] tmimaesk:
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
[OnePlus 3 & 3T Cross Device Development] 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 [MENTION=5438598]RenderBroken[/MENTION] for the fun! :good:
[OnePlus 3 & 3T Cross Device Development] 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 !
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
[MENTION=5438598]RenderBroken[/MENTION] 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 :)
[OnePlus 3 & 3T Cross Device Development] helandortega:
Will this work on FreedomOS 2.3 Stable? Im currently running on franco kernel and I want to try this one.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I have it working 100% alright with FreedomOS 2.3 stable (based on OOS 4.0.2)

---------- Post added at 08:46 AM ---------- Previous post was at 08:44 AM ----------

1- try another ROM like FreedomOS

2- make sure you flash SuperSU 2.79 stable (already included in FreedomOS)

3- if all that fails, try entering terminal emulator, then type "su". Then type "setenforce 0" and then quit Terminal emulator app and see how it behaves.

4- make sure you wait at least a couple of minutes before actually judging it.

5- try eliminating the kernel tuning apps (sometimes they do some weird issues like that)

---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------

By time we will get to the perfect setup :good:

---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------

That's a hell of informative post! Thanks a lot!!

---------- Post added at 08:55 AM ---------- Previous post was at 08:48 AM ----------

See here:
[OnePlus 3 & 3T Cross Device Development] helandortega:
Can I dirty flash this one over franco kernel? :)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
There is nothing complex about it, just dirty flash your current ROM (pro tip: backup your /system and /boot in TWRP after for easier changing between the kernels ;) ) then flash the EAS kernel by RenderBroken

:)

---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------

Currently AFAIK it is NOT compatible with the OP3T, however, that doesn't mean that OP3T won't be supported in the future. Renderbroken to reply :good:
[OnePlus 3 & 3T Cross Device Development] peshellas:
Im also on experience rom, when you edit boot.img(flash magisk, phh superuser, custom mernel, and some versions of supersu), the phone instead of booting up in PERMISSIVE as it is configured by default (experience 10.1 and freedomos i think), boots up in enforcing and that causes issues with overheat and huge drain.

Steps to be fine i use it and many users a lot

1.after every reboot open a terminal app

2. Type "su" (without the quotes)

3. Type "setenforce 0" (without the quotes)

Have fun
[OnePlus 3 & 3T Cross Device Development] helandortega:
Can flash this one over franco kernel without dirty flashing the rom?
[OnePlus 3 & 3T Cross Device Development] peshellas:
Still well done mate, you certainly did a hella of a job with this one. (I know you put tons of work here) ;)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
If it was possible, I wouldn't have wrote such instructions in my previous post
[OnePlus 3 & 3T Cross Device Development] peshellas:
Well if there is even a slight tweak to be fone at some point we all know who will be the guys, to tear it apart to find it :p

Now on topic, how does it perform? I ask cause right now i am in the middle of testing AKT with a 3rd Kernel and can't flash yet ;)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Well, it is quite lovely. You'll love it :good:
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
i clean flashed freedomos 2.3....here again i am having that same issue....phone is getting hot and max cpu freqncy used higher....what should i do?:crying:
[OnePlus 3 & 3T Cross Device Development] comediiian:
try another Rom?
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Using experience ROM, getting high frequency too. I :(

Fyi, and dirty flash ROM then flash kernel.
[OnePlus 3 & 3T Cross Device Development] svandasek:
Oh nice, the main aim of this is performance, right?
[OnePlus 3 & 3T Cross Device Development] manjartens:
I repeat myself:

Had same problem. Flashed supersu 2.79 stable after (!) Kernel. Solved Problem for me.
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Will try and report. I
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
https://xdaforums.com/oneplus-3/development/kernel-render-kernel-t3505956/post70842287
[OnePlus 3 & 3T Cross Device Development] Giocarro:
Thanks for the heads-up; so the short answer is no, because I read "performance most of the time is less than stellar unless you bias the global sched settings fully towards performance murdering your battery life completely".

Now looking for a performance oriented kernel...
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I didn't say that performance is compromised.

It is all about giving every task the amount of power it needs via specifically tuned cpusets.

On Render's kernel, the performance is splendid and smooth with considerable battery savings.

And what you said about the global boost stands true if you have no cpusets set.

Please reread the post again. And mind you, schedutil has passed that point too, still investigating the changes in schedutil compared to sched-DVFS.
[OnePlus 3 & 3T Cross Device Development] vinax89:
EAS v1.2 has been pushed to google repo for the 3.18 kernel by Linaro and ARM engineers.

https://android.googlesource.com/ke...d-msm-marlin-3.18-nougat-mr1-eas-experimental (Released: Sun Jan 29 18:40:13 2017 +0000)

"EAS 1.2 is intended to be the next iteration of EAS for AOSP,

including improvements to the wakeup path to better support

big.LITTLE and trialling other upstream scheduler enhancements such

as schedutil along with some important load/util tracking enhancements

to PELT.

Although EAS 1.2 will be primarily focused on a 4.4-based kernel, we

are making this experimental branch available on the 3.18-based Pixel

kernel (marlin_defconfig) in order that we have a readily-available

real platform with an optimised userspace for experimentation.

There are some differences in the scheduler task wake-up path between

this release and that shipping in the Pixel kernel which should be

taken into account when using this kernel.

The most visible change in the wake-up path is the removal of the

is_big_little sysctl. Wake-up now uses a single cpu selection

algorithm (the same one used previously for !isBigLittle) but modified

to remove the assumption that the highest capacity cpus have the

highest logical cpu number. We now allow cpu topology independent

selection of max capacity cpus for tasks which belong to a schedtune

group which has some boost applied irrespective of the cpu numbering.

This changes the iteration order of cpus when looking for a place to

run these tasks from [3,2],[1,0] to [2,3], [0,1]. This has an impact

on runtime configuration. Not making a change to this configuration is

likely to have a small impact for lightly-loaded systems where there

will usually be two idle high-capacity cpus, but we should anyway

match cpuset configuration to the selection ordering to restore the

expectations used when tuning.

In Pixel, cpusets are arranged such that one of the highest capacity

cpus is available only to tasks belonging to the ‘top-app’ cpuset. In

combination with the cpu iteration order used for schedtune boosted

tasks, we hope to find an empty cpu more often for these tasks to wake

on. As a result of the changed iteration order, the top-app should now

be set to the lowest numbered high capacity cpu (in this case #2 for

Pixel). The impact of this is likely to be small for most light use

cases if not changed. This is done in the initrc:"

It seems like this version of EAS is inherently different from Pixel EAS (V1.0). If AOSP changes for EAS will be included, we can clearly see a truly efficient OP3. I heard that Arter was tinkering with EAS in AOSPA N.

AH! Good times ahead fellow members! :)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Spectacular!!
[OnePlus 3 & 3T Cross Device Development] Konskl:
Did that and nothing... :/ Experience rom stable 4.0.2
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Give the phone some time to settle. It takes longer than 2 seconds.
[OnePlus 3 & 3T Cross Device Development] habylab:
Hey,

Can you confirm SR3 SuperSu still has issues? I know SR2 did. Is Stable recommended then still?
[OnePlus 3 & 3T Cross Device Development] Konskl:
It's been 2hrs now. I really think there's an issue there. Not sure whether it's experience rom's or kernel's fault. You have both clusters in schedutil right? Also which SuperSU are you using?
[OnePlus 3 & 3T Cross Device Development] AlkaliV2:
You gain no outright benefit from using the SRx versions of superSU over the stable version, you only create potential incompatibilities. That is why SR versions are for testers and not for daily use.
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Consider good now? ?
[OnePlus 3 & 3T Cross Device Development] IvanSoria:
After flash kernel and su , the phone goes with ultralag.

Whats wrong?

Regards
[OnePlus 3 & 3T Cross Device Development] Konskl:
[MENTION=5438598]RenderBroken[/MENTION] which governor are you using with the eas kernel version? Schedutil? Are there any parameters that are tweakable. I saw a post of yours with schedtune.boost where If you increase the parameters performance is increased against battery life. Is there something similar here? I feel like I could make it use a bit more power for a bit more performance :). Great addition. I suppose you're the pioneer here porting eas to our device :D many thanks!!!
[OnePlus 3 & 3T Cross Device Development] sarus_b:
Try with some different kernel manager.. Kernel adiutor is buggy... Do share the results without using kernel adiutor at all
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Suggest?
[OnePlus 3 & 3T Cross Device Development] sarus_b:
Just try any one out there... Play store has couple of them
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
S-s-super post!!!!

I used the new unified N source to build my N OOS Kernels, So R1 and R2-EAS should both work but I have not verified. I would be grateful if you could let me know. Just backup /system and /boot before so you can revert back to what you had if it doesnt boot or whatever but I feel good about it.

EAS does not use frequency steps like we are used to seeing. Look in Kernel Aduitor and see the live freqs used when looking at the Overall Tab. You will see the phone using freqs not even on the freq table. EAS sets frequency and voltage per task. Before with HMp, you had interactive and timers. Interactive would look at load and make decisions on what freq step to use and for how long. But this was a reactionary way to complete work loads or tasks. EAS essentially gave the scheduler the power to dictate freq and voltage. Since this is what load is generated/calculated anyways. So EAS is trying to cut out the middleman.

Should be ok. just make sure Schedutil gets set as the governor. backup /system and /boot. Normally you should only need to backup /boot but to support EAS I had to make edits to /system on flashing.

See above ^

U think there was an issue using experience. Need more confirmation though. I personally use Freedom and have since I got the OP3.

Try these settings if you are aiming for more performance without being ridiculous.

I use a file browser to nav to these files. Seems easier.

Use these values:

/dev/stune/background/schedtune.boost 0

/dev/stune/foreground/schedtune.boost 5

/dev/stune/top-app/schedtune.boost 15

/dev/stune/schedtune.boost 10

But do keep in mind that I don't have a perfect EAS implementation yet. I am missing changes in framework that would put the UI into top-app. So the UI tasks would always be boosted. Its kinda like the input_boost from cou-boost. I am working on a possible fix for this ;) Also, it is Energy Aware Scheduling. It was designed for optimal energy output.

I already use this in my last EAS build (OOS-N-R2-EAS)

Yes, just schedutil. See above ^^
[OnePlus 3 & 3T Cross Device Development] pan466:
Guys the problem is kernel aduitor and not the kernel itself. I just flashed the kernel over experience rom. If I open kernel aduitor it looks like one core is stuck on 100%. Then I opened system panel 2 to check it and it looks the same BUT in system panel you can clearly see that this usage comes from kernel aduitor itself. And when you kill it you can see that cpu usage immediately drops to normal values in system panel. Btw this new system panel is really very informative and it also has a good design.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for reporting!
[OnePlus 3 & 3T Cross Device Development] Giocarro:
[MENTION=5438598]RenderBroken[/MENTION], I tried to edit these files with Solid Explorer but it looks like they are not editable.

I also tried to manually echo the values with > redirection but that failed, too.

Any hint?

/dev/stune/background/schedtune.boost 0

/dev/stune/foreground/schedtune.boost 5

/dev/stune/top-app/schedtune.boost 15

/dev/stune/schedtune.boost 1
[OnePlus 3 & 3T Cross Device Development] kash296:
I use root explorer. I was able to edit it with the app's text editor feature. Works well.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Stable is always recommended
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Where u find system panel?
[OnePlus 3 & 3T Cross Device Development] sarus_b:
[MENTION=5438598]RenderBroken[/MENTION] Since this kernel uses EAS does changing schedulers settings have any effect of then frequency ramp up/downs?

For eg the most obvious setting people change is type of scheduler and read ahead.. Does it affect the governors decision?
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
I can confirm that kernel adiutor doesn't show proper stats in this case . There's no problems, stable enough for a daily driver but I get only 4 hrs SOT idk why, I used to get 6 hrs on stock HMP.

Very rarely there's some scrolling issues though: I stress, rarely.

And I wanna know how you'll fix the framework dependencies?

For guys who thing sr3 gives issues, there's none here. I've been using sr3 all the time.
[OnePlus 3 & 3T Cross Device Development] Stroky:
Just installed this kernel on open beta 11

Running Really great so far!

Governor was set to performance but I changed it.

No Problem so far. Feels really quick.

Let's see how the battery goes :)))
[OnePlus 3 & 3T Cross Device Development] abhi0502:
I reverted to stock kernel but im not getting wifi now. Tried even clean flash but still no wifi
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
you did a dirty flash of your ROM ?
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
what's the solution?
[OnePlus 3 & 3T Cross Device Development] abhi0502:
Tried clean flash too but still no wifi. Any way of installing stock wifi module?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
what ROM are you on? tbh it is very strange that even a clean flash does not restore your WiFi

what TWRP did you use?
[OnePlus 3 & 3T Cross Device Development] abhi0502:
Im using multirom recovery with flashing stock rom as secondary rom and then swap it to primary rom
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Most probably that's the issue: using multi ROM
[OnePlus 3 & 3T Cross Device Development] abhi0502:
Dont know. Again swapped to secondary rom wifi started working again
[OnePlus 3 & 3T Cross Device Development] Stroky:
Can copy that.

I restored the stock kernel and WiFi was gone.

Flashed another custom kernel, WiFi is there.

Going back over stock to Render everything is fine again.
[OnePlus 3 & 3T Cross Device Development] Ashtrix:
Well, thanks a lot to [MENTION=5060769]Mostafa Wael[/MENTION], [MENTION=5438598]RenderBroken[/MENTION], [MENTION=5207359]vinax89[/MENTION] for the heads up (Out of thanks for today lol ) on the EAS. Looks like the 820 will live very long, So does this device !!
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Flash supersu 2.79 stable. And then reflash the kernel again.

---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------

Try reflash the kernel again. That solved my WiFi issued..
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Thanks for the kind words, much appreciated!

Yep, it seems that the OP3 (and [MENTION=5438598]RenderBroken[/MENTION] ) will be a legend :) :good:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
You are talking about the I/O Schedulers (For Read/writes) and no, those are completely unrelated to the scheduler.

Did you have EX Kernel? I think he does something different with his kernel and wifi. Don't quite remember though.
[OnePlus 3 & 3T Cross Device Development] abhi0502:
No i was on stock kernel before. Restoring system only does not solve. Only flashing your kernel again wifi is working
[OnePlus 3 & 3T Cross Device Development] habylab:
Coming from blu spark direct to this works.

And it works like a dream so far!

Any kernel managing app working okay with this, or are they all causing issues at the moment?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Ehm, KA works okay here. Your mileage may vary a lot however, just saw bedalus saying that removing KA solved his benchmarks problem or something like that, so i can't guarantee anything ...

However, the effective EAS tunables are out of reach via kernel tuning apps. Only I/O and GPU only are what you can tweak via KA
[OnePlus 3 & 3T Cross Device Development] habylab:
And changing to Westwood too!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Yeah forgot about that :angel:

Anyways, i would like to state that I may have reached something extremely good with some tunings done. 47 minutes SOT with 10% drained.

40% brightness, constant typing and multitasking, XDA, Chrome (browsing facebook), Whatsapp, Slack and some YouTube. Auto Sync is on, Location at high accuracy, basically this is a no-compromise usage pattern.

Will see how much SOT the charge cycle will end up with..
[OnePlus 3 & 3T Cross Device Development] Konskl:
Performance wise??? Is it comparable to the speed of interactive? Personally I'm undecided yet. Though I'm sure there is a lot of potential here.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Comparable to stock HMP (interactive governor) speed and smoothness :good:
[OnePlus 3 & 3T Cross Device Development] habylab:
Any IO or GPU changes?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I/O

But I have gone beyond I/O
[OnePlus 3 & 3T Cross Device Development] madsponge26:
No tweaks and no changes feedback will be 48 hours of usage.
[OnePlus 3 & 3T Cross Device Development] liam_davenport:
Some feedback from what I've used so far will be using it for longer to test the battery life

Clean flashed on top of Stock OOS 4.0.2 zip

On boot had no wifi had to re flash the kernel fine now, Performance seems hit and miss sometimes it's smooth but mostly pretty stuttery and 1 second delays

Battery drain seems average so far will test it more and report back, Plenty of potential here keep up the good work ^^
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Waiting for all of your testing for atleast 2 days before jumping to this kernel. I miss those days when i could also flash and test things on my own but because of my job and limited time, i am completely Stock ROM/Kernel person nowadays for best stability.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
It's super stable! If you don't trust it backup system and boot and you can revert to stock within 5 minutes. Haven't had any weird drain whatsoever no crashes either!
[OnePlus 3 & 3T Cross Device Development] habylab:
Usually lose 4-6% overnight with other kernels, lost 26% with this. No other changes apart from kernel swap.
[OnePlus 3 & 3T Cross Device Development] kash296:
That's weird i lost 1% overnight on this. I've been on the kernel for the last couple of days. Check up on SELinux will you? I kept to permissive for the timebeing until they truly fix the issues persistent on enforcing right now. And which OOS rom are you on? Stock or a custom OOS build?
[OnePlus 3 & 3T Cross Device Development] habylab:
I'm not going to permissive because I like security.

Completely stock, none of the Freedom OS rubbish.
[OnePlus 3 & 3T Cross Device Development] kash296:
Hmm. Well guess you could try reflashing the kernel again, because the 26% drain sounds kinda bizarre. Hope you somehow overcome the issue. :)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
That's very weird, I just had a flat line..
[OnePlus 3 & 3T Cross Device Development] habylab:
I don't think reflashing will fix the issue as it will replace x with x. I'll wait for another version I think.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
here are the suggestions:

1- reflash ROM (believe me sometimes it is more effective than you think)

2- track down your wakelocks

3- wait for some days for it to settle down a bit. Maybe it needs a battery recalibration

Zero issues here with FreedomOS 2.3 + SuperSU 2.79 Stable (if that matters...) + RenderKernel-EAS.
[OnePlus 3 & 3T Cross Device Development] :
I got 4h 33min sot with 36% still left so all is good but android system and os are at top and consuming battery.

I have done

1)wiping caches

2)using stable supersuu

3)changed kernel to permissive

4)dirty flashed the rom before this kernel so stock

And after that also deep sleep is not affected. I do have kernel auditor installed. Suggestions are welcome