• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root What SetCpu?

3nyqG.png


and here's the batt stat page:
t8f8C.png


I've been getting pretty good battery life with this - running the latest Fresh rom. Currently at 31%
 
Meltz014,

what kernel? i was under the impressing the fresh stock kernel (w/havs) didn't play nice with profiles. are you not having issues? have you tried a run WITHOUT profiles to see if there is an improvement in life?

I am using fresh and a netarchy kernal but have stayed away from profiles due to all the warnings
 
Mr. Ed said:
Meltz014,

what kernel? i was under the impressing the fresh stock kernel (w/havs) didn't play nice with profiles. are you not having issues? have you tried a run WITHOUT profiles to see if there is an improvement in life?

I am using fresh and a netarchy kernel but have stayed away from profiles due to all the warnings
Click to expand...

Great question.
I'm using the Fresh 3.3.0.1. with Netarchy 4.1.9.1. cfs and was using SetCPU with very similar profiles. Battery life was ridiculously good. I then read here that SetCPU profiles conflict with H.A.V.S. kernels, so I disabled "Profiles" in SetCPU, set Main to 128 min & 998 max Conservative." I'm still getting ridiculously good battery life. I see no difference.

I don't know what to tell you.
 
I simply use SetCPU with 245000 MIN/MAX with stock ROM and Kernel.

My device will last for 11 Hours and be at 75% before I actually start using it after I get off work. I've hit 35 hours once before charging. Didn't do a thing on the phone for the whole time, just let is run.
 
Im also using the stock Rom and Kernel and have a question about Setcpu . Do I have to set this up every time ? I have checked start at boot and it doesnt keep the settings .

*nevermind* duh its taking now /slamsheadondesk*
 
Pardon my ignorance here:

SetCPU needs to be running in the background for it to do it's job I'm assuming here. If I do a bunch of other things it can be killed by the OS correct? So I need to make sure it's on every once in awhile?

Sorry I'm new with rooting and wanted to get some insight here. Thanks for your patience and any clarity you can give. :)
 
JunBringer said:
Pardon my ignorance here:

SetCPU needs to be running in the background for it to do it's job I'm assuming here. If I do a bunch of other things it can be killed by the OS correct? So I need to make sure it's on every once in awhile?

Sorry I'm new with rooting and wanted to get some insight here. Thanks for your patience and any clarity you can give. :)
Click to expand...

It has a setting that trays to prevent itself from being forced closed by the low priority setting in the device. You shouldn't really have to worry about it much, But it is recommended you can keep an eye on to make sure. No worries though.
 
Mr. Ed said:
Meltz014,

what kernel? i was under the impressing the fresh stock kernel (w/havs) didn't play nice with profiles. are you not having issues? have you tried a run WITHOUT profiles to see if there is an improvement in life?

I am using fresh and a netarchy kernal but have stayed away from profiles due to all the warnings
Click to expand...

Oh sorry, it's been a while since I checked the forums. Im just running the stock kernal.
KXoZH.png
 
Matlock said:
It has a setting that trays to prevent itself from being forced closed by the low priority setting in the device. You shouldn't really have to worry about it much, But it is recommended you can keep an eye on to make sure. No worries though.
Click to expand...
Oh ok, so I use that Priority slider in the app to make sure it doesn't get killed. I think I'm getting this now.

Thanks for your help dude!
 
You must log in or register to reply here.
Back
Top Bottom