Post your daemon controller settings which can save battery and speed up our phone! - HTC Sensation

I wonder which freq can save more battery and not slow
Mine:
Wake up
max:1512
min:168
Wake Governor - interactive
Sleep:
max:540
min:168
Sleep Governor - conseractive
Kernel UNITY V7
And here is the freq settings recommended by CdTDroiD:
Recommended Daemon Settings:
Wake Min 384000
Wake Max 1296000
Wake Governor - Ondemand
Sleep Min 276000
Sleep Max 384000
Sleep Governor - Conservative
Guys,please post your settings here and discuss what is the best freq settings

Mine:
Wake up
max:1512
min:168
Wake Governor - ondemand
Sleep:
max:384
min:168
Sleep Governor - conseractive
Kernel UNITY V7

jerrylzy said:
I wonder which freq can save more battery and not slow
Mine:
Wake up
max:1512
min:168
Wake Governor - interactive
Sleep:
max:540
min:168
Sleep Governor - conseractive
Kernel UNITY V7
And here is the freq settings recommended by CdTDroiD:
Recommended Daemon Settings:
Wake Min 384000
Wake Max 1296000
Wake Governor - Ondemand
Sleep Min 276000
Sleep Max 384000
Sleep Governor - Conservative
Guys,please post your settings here and discuss what is the best freq settings
Click to expand...
Click to collapse
I'd lower your sleep. No need to sleep at 500 mhz.

I have the Sensation and the Revolution HD rom installed. The rom came with the CPU upped to 384000/1512000/ondemand; 192000/384000/ondemand but I'd like to take it back down to defaults. I'm a little worried that its running too high/hot. The phone yesterday got really really warm and wouldn't turn on until I pulled the battery and restarted it. So to be on the safe side, I'd like to just put it back to defaults and then remove the Daemon Controller. My Google searches for "Daemon HTC Sensation" have come up empty handed. Any help would be appreciate! Thanks in advance.

Sleep:
All lowest setting
Wake-
Min: 1.4Ghz
Max: 1.78Ghz

*Subscribing*

Just put wake to whatever you want and sleep.to lowest settings. I change them on the fly depending on if I play games or not. Lower them when your not doing anything that needs high cpu usage

I use the stock settings that Mike has in the latest ARHD and performance is seems ok along with battery life.

jacksparr0w said:
I use the stock settings that Mike has in the latest ARHD and performance is seems ok along with battery life.
Click to expand...
Click to collapse
same for me even tough its on the inc s.

Related

[Q] What is your setcpu settings for G3...everybody pls share here without fail...

hi guys..,
pls share ur setcpu settings here...so that we can get some idea...we can choose the better ones...
To start with..,
i 've kyrillos rom 9.2 oc.., g3mod v2.2.2
My Settings:
- Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
- Profile (1): In call: 83min, 400max, Scaling: Ondemand, Priority:100
- Profile (2): Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
- no voltage profile...
but it lags a bit at times....
pls share ur setcpu settings....here...
G3Mod 2.2.2.
Main profile : - Min 83, Max 800, Profile Lagfree.
Profiles, priorities in descending order.
1) Battery<15 : 400 Max 83 Min, Powersave.
2) Screen off : 400 Max 83 Min, On Demand.
3) Charging : 600 Max 83 Min, On Demand.
4) In call : 400 Max 83 Min, On Demand.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: 400-1000 - ondemand
time profile (00:00-06:59): 83-200 - conservative (priority: 100)
screen off profile: 400-500 - ondemand (priority: 99)
no undervolting and other settings, just sampling rate set to: 10000
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
LooksLikeSmart said:
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
Click to expand...
Click to collapse
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
I dont think so... It will just shorten the life of the cpu.
Sent from my GT-I9003 using xda premium
hi bscraze.,
i've posted my setcpu settings above...is it safe...?? whether i've to change max to 800Mhz...what about scaling...conservative or lag free..
pls post urs if u have...
My profiles for i5801:
Main tab - 200~700mhz on demand/lag free both works for me
Charging - 300~1200mhz on demand
Screen off - 83~500mhz on demand
Time 1am to 5.30am 83~83mhz powersave
You can try my profile, may work, may not but i advise you to change to 800mhz for your main tab.
Sent from my GT-I9003 using xda premium
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
. No it won t.
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
LooksLikeSmart said:
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
Click to expand...
Click to collapse
You should keep it 800 max for normal usage because keeping high frequencies shortens processor life. Use higher frequencies(1000+) only when needed like when playing games and etc. At 800, in normal usage, all works smooth. Note I use lagfree as main profile. I suggest you also try lagfree once.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: min 83 - max 700 - ondemand
In call: min 83 - max 400 ondemand(priority: 100)
screen off profile: min 83 - max 400 - ondemand (priority: 98)
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
They are perfect. You don t have to worry about anything with those settings. If you use 1000+ frequencies for longer periods continuously then it may reduce your CPU life. Use only when required.
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
Cpu chips are made to last at least 5 yrs so dont worry about it and like what dhirend said, only if you keep it at high frequencies for long times will it dmg the cpu more.
Sent from my GT-I9003 using xda premium
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
lefar333 said:
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
Click to expand...
Click to collapse
try cm7 marcellusbe or kyrillos, then you will never have a freeze again!
I'm on Kyrillos v9.4, kernel G3Mod v2.3
83Mhz, Max 800-1200MHz, Scaling: Ondemand
In call: 83min, 400max, Scaling: Ondemand, Priority:100
Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
Screen off: 83min, 400max, Scaling: Ondemand, Priority:98
my battery lasts three days with normal/heavy usage
Hi,
I'm on kyorarom 0.5.1 with kernel G3MOD-Kyorarom-0.5.0
main: 83 - 800 lagfree
1. in call: 300 - 800 lagfree (if less I have to wait a lot to see the screen waking up) priority 100
2. screen off: 83 - 600 lagfree priority 100
3. charging: 83 - 900 lagfree priority 99
no freese, no FC, only one thing: when I wake up the phone from screen off I sometimes see the last screen before the lockscreen appears and I tried to change the off screen values and it was all the same...
baterry lasts at least 3 days with some wifi use, low BT use, some apps and games, but a lot of phone calls and sms
Everybody over here just check out this(forum.xda-developers.com/showthread.php?t=1369817) thread to understand the things better. (about governers, modules, etc) . Must see thread!!!

Could any developer kinda fix cpu1 battery drain issue?

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.

[Q] Best settings in SetCPU / CPU tuner for STOCK KERNEL???

What are best settings for optimal/same performance and maximum battery savings in SetCPU or CPU tuner for stock ICS 4.0.4 KERNEL?
Thanks
I have Arc S LT18i (model 12w17). I can't unlock bootloader with testpoint at the moment and I do not wan't to do it officialy. I'm using SetCPU.
I have ondemand, conservative and interactive governors and noop and deadline schedulers. I'm always using using noop scheduler.
I have set ondemand 122-1401MHz for ScreenON & InCall profiles with sampling rate 40000 and up treshold 95.
I have set conservative 122-1024 for ScreenOFF profile with up treshold 70 and down treshold 30 and sampling rate 200000 (lowest possible for my stock kernel).
Will test it for a few days. If anybody has better settings and tested ones please help...
I think conservative is best for screen off, thinking about lowering freq to 122-806. What I'm mostly interested is if interactive is better for ScreenON and InCall use than ondemand for battery durability?
Updated some setting based on CPU Spy and some reading on xda forum.
ScreenOFF profile
Up/down 70/30 thresholds no good for conservative, changed to 90/40. Enabled ignore nice load. Changed freq_step from 5 to 10 to balance change of thresholds.
When playing music in background freq was 368 and was jumping to 768. With new settings freq was mostly 245 with jumps to 368.
ScreenON or Incall profile
Ondemand up threshold changed to 90 (smoother), enabled ignore nice load, sampling rate left to 40000.
Unsure if 122MHz freq is good to use because when playing music in background there are significantly more jumps to 1401 than from 245MHz.
On stock kernel, 122 and 245 both run on 900mV. Read on forum that 122MHz can use more battery because processes need more time to finish than on 245MHz, instead processes finish faster on 245MHz (and what bugs me is that both freq uses same voltage) and phone enters deep sleep faster.
245MHz is stock kernel minimum default. Any HELP?
you can search on xda about the settings of setcpu... there is a detailed description about all the settings and you can choose the ryt one according to you usage:good:
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
hope this may help you http://forum.xda-developers.com/showthread.php?t=843406
Imho profiles are useless since the more profiles you have, the more often the app needs to get active to check for a particular situation such as screen of, and governours already do that - they are profiles for the cpu

[Q] Issues with Governors and CPU Sleeping

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?

EAS and powersave governor

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.

Categories

Resources