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?
Related
Hey, if I'm using SetCPU on the NS4G with the latest stable Netarchy BFS and a smartass governor and I want to save battery, do I need to have a 'screen off' profile and underclock the CPU a bit? I notice that it slows down waking the phone up, which is a minor nuisance and if I can avoid it because the governor will keep it slow already when not in use, then why not?
Using the "smartass" governor and profiles is not a good idea. The idea of using that governor is that you don't need profiles.
Download Proton Voltage from the market and use the suggested voltages within that app and make it boot everytime on start. It will help you conserve battery.
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.
Hi,
I tried even on latest stock rom with stock kernel.
When i set the governor to performance everything is fine until the screen is turned off.
After that i cannot turn the screen back on and sometimes it restarts.
The same thing happens if i set the minimum value to maximum frequency on interactive governor
The closest i could get is to set the minimum frequency to the second highest frequency
Is it a way to get performance governor working?
Thanks in advance
I have the Pure-Z kernel, which has the option for the powersave CPU governor (which basically locks the CPU at the lowest clock rate except when touching the screen due to input boost).
I used Tasker to automatically set the big cores to powersave whenever battery saver is enabled in the hopes that throttling the big cores would save more power.
The question is: Does it actually save power? Or does it waste energy due to EAS not realizing that the CPU is throttled and still trying to send threads to that core set?
The LITTLE cores are still at their default sched governor.