yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Bladehawkz:
Current default settings for smartmax governor seems to skip 960MHz almost completely, and isn't aggressive enough at scaling any higher than 1574MHz, which causes cpuquiet to continuously turn off and on extra cores at moderate loads.

Changing

RAMP_UP_STEP 200000 -> 150000

RAMP_DOWN_STEP 200000 -> 100000

MAX_CPU_LOAD 70 -> 65 (somewhere between 60-70 would be best, as below 60 it becomes much too aggressive)

DOWN_RATE 60000 -> 30000

This seems to provide smoother down-scaling (hitting that 960MHz spot much more often but overall similar speed to idle due to halved frequency delta but double down rate), and increased willingness to go to higher frequencies (1574-2457MHz) over turning other cores off and on.

It's also notable that the second core often instantly jumps to 1497MHz due to the way sultanxda implemented touchboost (increases smoothness since while touching the screen for any purpose there's a high chance of a 2nd core turning on), so flickering more cores on and off instead of just increasing frequency of one core is probably not in our best interests.

[MENTION=4804871]DerRomtester[/MENTION] any thoughts on this?

Edit: Actually, never mind, you can ignore this post. Even at 65, it appears too aggressive now, even scaling up at simple scrolling events. Still think there's a better settings in regards to the scaling. I'll experiment later.

Edit2: Also, RAMP_UP/DOWN_STEP didn't work as I expected. Current value, +- value, and then finds the furthest value within the ranges. It would jump from 1036 to 883, hence skipping 960. So the only thing we can even change other than skipping even more frequencies is just including that one. Super minor change, probably useless.
[ONE Original Android Development] kalapapa:
But isn't more cores at lower frequency better than 1-2 cores at higher frequency for battery and performance
[ONE Original Android Development] Bladehawkz:
Not really.

First of all, battery life/power consumption is definitely higher with more cores on. The most optimal state a core can be in is in sleep, and turning them on for effectively double the frequency is definitely not as power efficient as just doubling a core's frequency. If you want to check this, you can write out a frequency to voltage table. Even after squaring the voltages, we can clearly see with default (and after my specific device's undervolt settings), that less power is actually used at higher frequencies on less cores than lower frequencies with more cores. (This is also where the basis of the 'multicore power savings' and most hotplugging drivers come from).

In terms of performance, it depends on what you're trying to do. When you're multitasking a lot, I can agree that performance is probably better. This is due to an increase in amount of threads that can be handled simultaneously. However, when we are looking at general usage of one app at a time, we want to keep the threads within the same core, as passing the i/o requests back and forth between different cores requires even more cpu cycles to do so. (passing i/o requests between cores is where the RQ affinity setting comes in.)
[ONE Original Android Development] saiamrock:
Hi, this is my first time using private kernel

So far, it give me good battery saving without performance drop withouy any setting changed

But i have question, how to control kernel setting??

I have try using KA and KA mod, changes did not stick after i reboot the device

I'm on latest RR CAF with xposed installed
[ONE Original Android Development] CooperBrick:
Can you add the ac and usb charger control? Like in lightning kernel
[ONE Original Android Development] Bladehawkz:
Set KA/KA mod (i recommend the mod version) to apply at boot for the sections you want. Also change the delay in the settings to 20 seconds (not sure if this is needed, but apparently some cyanogenmod ROMs take up to 20 seconds to initialize everything.) Because we have things like voltage settings and such, setting stuff to 'stick' (change boot values) can be dangerous.

[MENTION=4804871]DerRomtester[/MENTION] https://github.com/frap129/angler/b...fb9a568d8c8a0e37fc891f9/block/maple-iosched.c

New i/o scheduler (from electron kernel by frap129 http://xdaforums.com/nexus-6p/orig-development/kernel-electron-kernel-angler-t3443431). Thoughts? Seems like a ROW except using SIO/zen-like operations for read and write queues instead of ROW's CFQ-like approach to the read and write queues.
[ONE Original Android Development] DerRomtester:
Sry no. I am not interested in this feature and i already stated my opinion about it. Just search in the thread.

What settings excactly do not stick?
[ONE Original Android Development] LPW00:
All of them. But there's a setting in KA to use a shell script to apply settings on boot, this works.
[ONE Original Android Development] DerRomtester:
I am gonna check this new io scheduler.
[ONE Original Android Development] saiamrock:
+1

Can you give some guide how to do it??
[ONE Original Android Development] LPW00:
Just set this:
[ONE Original Android Development] disperotstop01:
Hello! Great kernel, it improved my battery life a 5-8 percent on latest Darkobas rom.

Just, unfortunatelly camera got broken. Video and picture of the main camera are taken upside down. I tried dirty reflashing darkobar rom over and camera was again ok. But when I reflashed your kernel, camera was upside down again.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Bino92:
That's because Darkobas ROM uses ColorOS camera HAL, causing camera to FC or to be upside down... You need to flash a ColorOS compatible one like Lightning kernel
[ONE Original Android Development] PlusOne3k:
Just a question, what do you think about the hima hotplug?

[MENTION=4206763]Romtester[/MENTION]
[ONE Original Android Development] DerRomtester:
I dont know that hotplug. Who developed it?
[ONE Original Android Development] Bladehawkz:
"Hima hotplug: An optimized hotplug driver based on intelliplug for big.LITTLE architecture. Found on chadouming's HTC One (M9) kernel, it takes advantage of the big and LITTLE CPU cores in order to provide 'butter smooth' performance."

While it's probably modifiable, since we don't even have a big.LITTLE configuration on the OPO I don't even know why we would even consider this as an option.
[ONE Original Android Development] joefso:
Would be interesting if we could.import more.of Franco's kernel mods
[ONE Original Android Development] DerRomtester:
What excactly are you looking for?
[ONE Original Android Development] PlusOne3k:
[MENTION=4206763]Romtester[/MENTION], i send you an pm.
[ONE Original Android Development] Romtester:
pleas use correct usernames ;)

I'm not "DerRomtester" ;)
[ONE Original Android Development] Fenvarien:
Thanks [MENTION=4804871]DerRomtester[/MENTION] for this great kernel and for sharing it with the community! It's really working well and stable.
[ONE Original Android Development] DerRomtester:
Thank you i really appreciate your kind words. I am cooking currently on a kernel for cm13 (non CAF) kernel.
[ONE Original Android Development] KenjiHannya:
Good new!

Maybe work on N Experimental :D
[ONE Original Android Development] DerRomtester:
I dont think so :). It could work. But i am gonna wait until it gets more stable. Than you can expect a new kernel.
[ONE Original Android Development] _ikhan_:
[MENTION=4804871]DerRomtester[/MENTION] would that cm kernel include 3.10? ;)

Also, I can underclock to 1.9ghz with kernel adiutor without interfering with cpuquiet scaling/sultans thermal control right?

Keep up the great work, seriously.

I had to tend to an emergency and I had to use my phone for communications constantly.

Phone stayed 300% reliable and stable with 30% to spare at the end of the day.

I can safely say I can rely on your kernel and [MENTION=4800121]Sultanxda[/MENTION] 's rom with absolute certainty.

Cheers :)
[ONE Original Android Development] DerRomtester:
3.10 = never

It will never become as stable as the 3.4 kernel base without the help of oneplus that can offer us the right drivers. I reall appreciate the work of erorcun but it seems as an endless project. The current state is usable but we need a stable device.

Of course you can underclock. This wont effect the smart cpu hotplug or my tuned franco thermal driver.
[ONE Original Android Development] plantator:
On this kernel I currently run on 1497MHz and undervolted by 105 great! (- 110 now)
[ONE Original Android Development] _ikhan_:
Thanks for the info!
[ONE Original Android Development] Bladehawkz:
Oh wow, CM13 nightly builds :D

Any plans of syncing the two branches so they have the same features :D.

Also, nikhil18 is currently helping getting the maple io-sheduler work on 3.4.0. There's an initial compatibility patch, not sure if it works yet. https://github.com/nikhil18/lightning-kernel-bacon/tree/lightning-caf
[ONE Original Android Development] Fenvarien:
The CM13 nightly kernel r1 runs perfectly smooth here. Thanks for this new option! :)
[ONE Original Android Development] CooperBrick:
Does the cm13 nightly kernel boots on cos13.1.?
[ONE Original Android Development] DerRomtester:
I like both kernels how they are. :) If you need a feature let me know.

My motto is

minimalistic

stable

fast
[ONE Original Android Development] tmimaesk:
I'm currently running cm nightly on my cos 13.1.2

Works fine
[ONE Original Android Development] gamal001:
[MENTION=4804871]DerRomtester[/MENTION] can you add cpuquiet to your kernel ?
[ONE Original Android Development] Fenvarien:
I would suggest 27 MHz minimum GPU frequency as a new option, this is a stable and well tested feature in other kernel projects for the OPO.
[ONE Original Android Development] Renosh:
I can see the GPU idle at 27 MHz in Kernel Adiutor on R20, its implemented already but you just can't select it and I'm assuming you don't want to run it at max 27 MHz
[ONE Original Android Development] Fenvarien:
Sorry, I forgot to mention that I was referring to the r1 CM nightly kernel build.
[ONE Original Android Development] DerRomtester:
Every kernel has this GPU idle step. Only the sysfs is reporting it wrong. Thats why you dont see the step in kernel adiutor. It is just a small patch. I am gonna add it. Than the system will report the correct values back to us. It is just a cosmetical thing that wohnt give us a benifit.
[ONE Original Android Development] Bladehawkz:
Hmm, which do you think is better, msm-hotplug or CPUquiet? Also, why do you prefer qualcomm's input boost over sultan's?

Would totes like the 268mhz on the sultan branch, but not that big of a change so idm if you don't ^^.
[ONE Original Android Development] DerRomtester:
Not sure. I like both kernels how they are currently. It was a lot of work to implement it so i just thought i try msm hotplug. And it feels good to me.

Both hotplugs are good how they are. I think CPUquiet is a bit more intelligent with its calculations. But its a lot of code and i dont understand anyhting of coding. Just a little bit.

I prefer Qualcoms cpu boost driver because it gives me a better experience. It feels smoother to me.

I had problems to implement the 268mhz frequency to the CAF kernel so i decided not to spent my time on it.
[ONE Original Android Development] Fenvarien:
I experienced this msm-hotplug vs. cpuquiet discussion with my Nexus 4 and after a lot of work and time most kernel devs over there returned to msm-hotplug, because it was more reliable and easier to maintain.
[ONE Original Android Development] Bladehawkz:
Any plans on GPU governors?

Which GPU governor do you like the most? Personally I don't like msm-adreno-tz, it seems to like jumping to much higher frequencies all the time, even for simple tasks.
[ONE Original Android Development] billbuds:
Support UKM ??
[ONE Original Android Development] DerRomtester:
Just choose the GPU governor you like.

UKM is not a kernel thing. Of course you can flash UKM and Download Synapse to control the kernel. But i dont know if everything will work. I prefer kernel adiutor.
[ONE Original Android Development] billbuds:
Plz add kexec hardboot for CM13 ?
[ONE Original Android Development] JJohnson1988:
The reason he hasn't added it is because he said it breaks encryption.
[ONE Original Android Development] DerRomtester:
Autosmp hotplug is plugging on/off cores based on the current CPU frequency as far as i know. I think msm hotplug and cpuquiet are more intelligent with their calculations.

Yep it breaks encryption. I want to beware this feature. Also i dont like multirom. It can cause issues. And i think one (stable) rom is enough.
[ONE Original Android Development] Bladehawkz:
AutoSMP is a great hotplug due to its simplicity. It onlines cores based on set thresholds, and turns off cores when loads are decreased. In a way, it 'chains' the cores together to basically have 1 core with 4x the clock speed. This behaviour is great when you're doing simple tasks, and is battery efficient.

CPUquiet is better though. Not only does it do the prementioned AutoSMP behaviour, but also online cores when it sees multiple threads-two cores at lower clock speeds is superior at handling lots of threads than one core at high clock speeds. This way, CPUquiet is better at large multithread tasks/multitasking on your device, with no real battery difference compared with AutoSMP.

[MENTION=4804871]DerRomtester[/MENTION]

https://github.com/nikhil18/lightning-kernel-bacon/blob/lightning-color/block/maple-iosched.c

We added the maple i/o scheduler to lightning kernel, and after applying frap129's revisions, and nikhil18's 3.4 compatibility changes, it feels quite stable.

I also changed the hard coded values back to have HZ dependency, since the nexus 6p had a lower config HZ value compared with the OPO. Ratios are still the same.

You might need this commit (https://github.com/nikhil18/lightning-kernel-bacon/commit/dfe6b37fec3bcb0372b3bbda9818d5a74283507f) (not totally sure, display state is already defined in the i/o scheduler).
[ONE Original Android Development] Bladehawkz:
Let's talk:

Arch power and gentle fair sleepers. Some ROMs have them off, some have them on etc. This kernel has them set on default (arch power off, gentle fair sleepers on). Any opinions on which settings are best?
[ONE Original Android Development] joefso:
[MENTION=4804871]DerRomtester[/MENTION]

can you take more code from franco, whatever adjustments he made to get "unmatched"*(his words) battery life - mods to cpu gov etc..
[ONE Original Android Development] DerRomtester:
Important to know for me is which kernel are you talking about? CM / CAF?

I think i did not touch these two settings. I think they are the default ones.

Important to know for me is which kernel are you talking about? CM / CAF?

What are you looking for ?

I think i have to do a second thread for me cm kernel to not confuse anybody including myself. :)
[ONE Original Android Development] joefso:
CAF. Looking for his modificaitons what turn his kernel into "unmatched battery life"
[ONE Original Android Development] Bladehawkz:
Rather difficult considering lots of people implement his changes, and vice versa. Unmatched battery life often comes with downsides. It also doesn't help that his kernels on the OPO are rather outdated now.

[MENTION=4804871]DerRomtester[/MENTION] for Arch Power and Gentle Fair Sleepers, not asking to implement them, but wondering about their effect on how it will make our device perform if the settings were changed.

Also, for your CM13, not sure if you know but apparently there's an 'enhanced' version of cpu boost https://github.com/nikhil18/lightning-kernel-bacon/commit/83dcd1d97522cae7949b4cce6b83c99ffe4e4eaa (also https://github.com/nikhil18/lightning-kernel-bacon/commit/d2d57860469cf958ec67fc79de37f656f3c393a0 to allow users to set cpu boost to 0)

Also, for the CAF kernel (i suspect this is a Kernel Adiutor mod problem), the defaults for every i/o scheduler assume 1000HZ, despite config_HZ being set to 300HZ in bacon_defconfig.
[ONE Original Android Development] joefso:
interesting, where and with an emphasis on what did they take from him and who in the opo community? I never saw someone take his mods on cpu gov and throughout his releases did he change much on the already done tweaks other than get stuff from cm?
[ONE Original Android Development] Setting.Out:
For me, toggling arch power had little to no effect on performance... Switching off Gentle fair sleepers should give very minor improvements to performance but not enough to notice beyond the amount of error and non-consistant benchmarks.. As per battery, there may be small gains, but again very small and hard to give a consistant result.. This is just my opinion from testing...
[ONE Original Android Development] Bladehawkz:
So what does retention voltage actually do other than decrease voltage used while the CPUs are in c-state? Stability like in undervolting?

I've recompiled the kernel with it at 500000 (vs 600000 in this kernel, and 675000 in stock), and it is still equally stable. (might be unstable at lower? haven't tested yet).

Also, regulator-max-microvolt = <1100000>; is still the same on some other overclocked kernels like lightning, is this a fault of their kernel, or does it get bypassed by the voltage given in their frequency table? (their overclocked voltages go over 1100 volts).
[ONE Original Android Development] DerRomtester:
If you point me to specific github commits than of course. But i need to check it first if it is for our device or if i like it etc..

Puhh i dunnow.

I also dont see any effect at all. So i dont touch them and leave them by default.

As far as i know the retention voltage values defines the range from the min to the max voltage. So your CPU voltage wont go above 1100000 microvolt and wont go below 675000 microvolt. If you dont undervolt a specific frequency of your CPU these settings wont have any effect. Default for 300mhz is currently 770000 microvolt. So if you change the min retention voltage to 500000 you can undervolt your cpu by -270000. I dont think that your device can hold that. It will freeze and shut down.

Correct me if i am wrong.

Edit:

CM pushed a CM14 kernel branch 17 hours ago yeaahhhh :)

Btw. I have currently school and not so much time for xda. Also i started learning c to improve my skills in school and in android development.
[ONE Original Android Development] gamal001:
[MENTION=4804871]DerRomtester[/MENTION] sultan update his ROM , any update for private caf ..
[ONE Original Android Development] DerRomtester:
I have currently school and i dont spent much time with kernels or xda. So no updates till next friday. :(
[ONE Original Android Development] gamal001:
Take your time, I'm currently used private cm . it's amazing.
[ONE Original Android Development] Bino92:
R20 version works really fine even with Sultan's last update, in 2 days I didn't had a problem, so take your time and thanks for your work :good:
[ONE Original Android Development] phaninder.ch:
Hi [MENTION=4804871]DerRomtester[/MENTION]

Donno if its off topic...will you be able to add VoLTE feature?

Is it possible at kernel level? Or should One plus release the source for that?
[ONE Original Android Development] DerRomtester:
I am sure that this is not a kernel feature and cannot be done on kernel side. Maybe oneplus will add that.
[ONE Original Android Development] CooperBrick:
Does cpuquiet reduces performance?
[ONE Original Android Development] DerRomtester:
r21 CAF:

* now we are completly inline with sultanxdas kernel

* i dont know if it boots just try it. There were so many patches and i am not sure about it. Just post last_kmsg and i take a look at it.
[ONE Original Android Development] JJohnson1988:
Does anyone else bootloop on the OnePlus logo with r21?

No kernel log, unfortunately.
[ONE Original Android Development] lomarzo:
Yes, bootloop for me

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] DerRomtester:
Last_kmsg please
[ONE Original Android Development] JJohnson1988:
Here you go.
[ONE Original Android Development] DerRomtester:
Thank you. I need some testers tomorrow. I got an idea.
[ONE Original Android Development] LPW00:
So, v21 should not be flashed, right?

U want testers? I'm here!
[ONE Original Android Development] DerRomtester:
Guys can you try this one please.
[ONE Original Android Development] LPW00:
Of course

Edit: doesn't boot, not even bootanimation is shown, only OnePlus logo
[ONE Original Android Development] Bino92:
Tried but I'm suffering bootloop... Last_kmsg attached
[ONE Original Android Development] DerRomtester:
Last attempt for today. For CAF users only.

Built from scratch. Based on my cm kernel. Not all features are inside yet.
[ONE Original Android Development] Bladehawkz:
Yeah, I would personally build it off your CM kernel. Building a kernel off sultanxda's branch makes it difficult to merge mainstream changes now, not to mention little quirks like not being able to add 268MHz (i've tried myself too now, it just never seems to be applied ehh).
[ONE Original Android Development] Bino92:
Tried and it booted, seems to work but I have troubles in setting CPU frequencies... I think I'll revert to R20. Thanks for your efforts!
[ONE Original Android Development] Bladehawkz:
Try increase thermal threshold temporarily, it's known to **** around with CPU frequencies.
[ONE Original Android Development] DerRomtester:
What excatly is the problem ?
[ONE Original Android Development] DerRomtester:
It is still based on CAF. I just added some features of my cm kernel. Sorry guys if my statement sounded confusing.
[ONE Original Android Development] Bino92:
Unfortunately it's not effective

Basically I am not able to set the CPU max freq, when I set it to the desired value it returns to 2457 MHz automatically. Tried with Smartmax and Ondemand, I also tried to disable the various Hotplug configurations, but it was ineffective
[ONE Original Android Development] DerRomtester:
Hmm ok guys than i have to abadon the CAF project. I cant make a perfect kernel for a rom that i am not using anymore. I tried to update it as long as possible but it seems that i completly ****ed it up and i dont know where the problem is. So for now i concentrate on my cm project and in the near future on android 7. Sorry for that guys. It is hard to maintain something that i am not currently using.
[ONE Original Android Development] PatrickMac:
[MENTION=4804871]DerRomtester[/MENTION] What rom are you currently using? cm nightly?
[ONE Original Android Development] DerRomtester:
Yes. Latest nightly.
[ONE Original Android Development] LPW00:
Nooooooo, first RR-caf now this awesome kernel......

Today, really isn't my day
[ONE Original Android Development] JJohnson1988:
The from-scratch revision is working well so far.

Though I haven't tried to change any settings via Kernel Adiutor (personally don't need to).
[ONE Original Android Development] LPW00:
Which caf rom did u use? Because RR caf got discontinued the same day...
[ONE Original Android Development] DerRomtester:
Guys i am gonna close this thread because i want to start a clean thread for my cm kernel. This CAF kernel is discontinued for now. Can any mod please freeze that project. You can still of course download the V20 kernel but there will be no future updates for it.
[ONE Original Android Development] KenjiHannya:
Tnx dude for all u work ;D
[ONE Original Android Development] Setting.Out:
Danke schön.. :)
[ONE Original Android Development] LPW00:
Thank u for ur work!!!

I'm so sad now.....
[ONE Original Android Development] onlyapilot:
Thanks for the effort. It was a good project. Best of luck.
[ONE Original Android Development] nfin1te:
Oh no :(

Still, thanks so much for all the countless hours of work mate, best of luck!