Not sure it matters but v48 color, is there a hotplug running anyway even without selecting one? which is most like qualcoms standard? Thanks.
Default hotplug on v48 is CPUquiet in CPU table on kernel adiutor, so if you activate any hotplug more it may cause bootlops, deactivate cpuquiet and activate other one if you want
Related
So I flashed Imnuts' new kernel and i am trying to OC/UV. Using the voltage control app i can get the CPU frequencies and I/O scheduler to stick at boot. However, the governor always resets to ondemand. Is there a fix to the init.d script that would change the governor too? I really like this app, as opposed to No Frills Cpu Control, which runs all the time to apply at boot.
Rom: Leedroid V2.1, Axiom S V1.0, TrickDroid V5.0(EU)
Kernel: stock HTC, Lowkernel v1.0.1, Vistuous v06
Apps & scripts: SetCPU, CPU Editor, Quick system info pro
http://forum.xda-developers.com/showthread.php?p=28214411#post28213828
There are also some other people who reported the same issue in this thread.
I'v tried all these kernels on three ROMs and they reported the same problem. The cpu1(2nd core) always keeps as ondemand mode. I've to use CPU Editor and enable Dual Core Mode to force it to other mode but after a reboot, it will reset to ondemand again. Sticky Enabled has no use here.
Another thing is after a reboot, the cpu1 frequency will also get a reset to the kernel's max. frequency supported. I've to set it again too.
Use Quick system info pro, it will shows out the current cpu0/1 governor and cpu scaling range very clearly.
SetCpu looks messed up on One S. The max frequency actually works as cpu1's max frequency while min frequency actually works as cpu0's max frequency.
It has no club to run the cpu1 ondemand at max all day long, it's just a waste of battery. On such a powerful S4 cpu, it's also non-sense to use ondemand governor as default. Interactive, Conservative, SmartassV2 are all better choices.
As a result, by using CPU Editor to lower the cpu1's speed and switch to other governor, my battery on daily use improved.
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
lowmanb94 said:
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
Click to expand...
Click to collapse
I dont think interactivex disables a core but just caps the freq to the lowest on screen off. If you want to disable a core on screen off you can run cpu sleeper. If you wanna check if a core goes offline you can dump a logcat and see if a core is being disabled.
lowmanb94 said:
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
Click to expand...
Click to collapse
if you use the shootout and want to see if itz working properly the app cpuspy should tell you
I have a Galaxy S3 running a custom ROM (WICKED), In the past I have been using the tweaked stock kernel with ondemand the the CPU would sleep at appropriate times. I updated to the newer version of the ROM and for some odd reason setting the governor to ondemand on the tweaked stock kernel would keep the CPU awake at all times. The only change I made was that I added a screen off profile set to ondemand with lower than full max clock speed. Luckily the ROM came with a another kernel option (Deviant kernel, OC'able), however several governors such as ondemand, conservative and intellidemand has the same issue; my CPU was an insomniac. Finally I tried using the interactive governor with the custom kernel and the CPU now sleeps as it should within a few moments after the screen turns off.
tl:dr: this issue seems to be less of one pertinent to my phone and more so a misunderstanding on my part how governors decide when to sleep the CPU. Why wasn't my CPU sleeping? Which governors are appropriate for a screen off profile?
Nexus 6P - Stock - ElementalX Kernel - 7.1.1
While using the ElementalX Kernel Manager app, it will not save my governor profile that i have chosen to use after a boot. I have apply on boot checked next to literally everything in the CPU tab to be sure it is set. The CPU governor is set on boot, and no apps i'm aware of are interfering. I use greenify, but the kernel manager isn't being greenified. Specifically the touchboost setting they won't save. I have touch boost disabled, and it does stick after boot. But when i go into the app, after a boot, it jumps to 1300 hz like i didn't apply any settings! As soon as I apply the governor I want to use, it works and the profile does stick. The problem only happens AFTER a boot. Some settings do seem to stick around, like for how long the cpu will stay at 1300 hz after i touch the screen. Currently using Glassfish 1.2.
Diehminer said:
Nexus 6P - Stock - ElementalX Kernel - 7.1.1
While using the ElementalX Kernel Manager app, it will not save my governor profile that i have chosen to use after a boot. I have apply on boot checked next to literally everything in the CPU tab to be sure it is set. The CPU governor is set on boot, and no apps i'm aware of are interfering. I use greenify, but the kernel manager isn't being greenified. Specifically the touchboost setting they won't save. I have touch boost disabled, and it does stick after boot. But when i go into the app, after a boot, it jumps to 1300 hz like i didn't apply any settings! As soon as I apply the governor I want to use, it works and the profile does stick. The problem only happens AFTER a boot. Some settings do seem to stick around, like for how long the cpu will stay at 1300 hz after i touch the screen. Currently using Glassfish 1.2.
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately this is not something we can really help you with, you need to ask in the kernel thread
Regards
Sawdoctor