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

Root SetCPU - Help? :)

D

Deleted User

Guest
What governor/scailing should i use?

What should I use as my min and max

& what profiles should I use.

Also what are u all using? cheers! :)
 
Not all phones are the same, so the max in particular will vary. Could also depend on kernels.

Personally I use Ondemand, 128-998, and that's it, no profiles. ManU 1.4 HAVS AXI kernel with custom voltage levels.

Edit: Tell a lie - I hadn't used profiles since 2010, but did have a play earlier this week, and had still got one active: screen off 128-384, same governor. I've turned it off again now though.
 
I'm using smartass governor with 1113mhz Max and 128mhz min, with a thalamus kernal 2.6.35.14 mod 4
Battery seems fine so far and performance not compromised
 
I dont stream radio because I live in the UK and Radio is appauling.

I use Poweramp and Google music with no problems though. Every now and again it causes an issue but then I find even disabling the profile doesn't resolve, but a reboot does.
 
SUroot... for Priority when setting the screen off profile, what should that be? its my only profile, is 50 okay or should it be 100? cheers!
 
Also how do you set custom voltage levels and is it worth doing?
 
If its the only profile, priority is irrelevant.

You need a kernel that supports voltage changes to do that, such as manu. I use a script to do this but theres an app that will do it. Details in the manu thread
 
cheers, what should the new volatges be and how much better do they actually make the battery life? & does it make performance worse?
 
When I used SetCPU I used Smartass 256-1152. No profiles as Smartass sorts out the screen off itself.

Now use On Demand through Redux : 245 - 1113

Never liked going lower as it can cause wake up problems/hesitation
 
You sure the wake problem wasn't Smartass rather than cpu frequency? I've used 128 min for a long time with little or no problem (none in last several months). But if I ever select Smartass it becomes a struggle to wake the phone.

SmartassV2 seems better in that respect, i.e. no wake problems in a short test, but screen-off current was slightly higher that Ondemand. Haven't given that one a real world drain test yet.
 
Hadron said:
You sure the wake problem wasn't Smartass rather than cpu frequency? I've used 128 min for a long time with little or no problem (none in last several months). But if I ever select Smartass it becomes a struggle to wake the phone.

SmartassV2 seems better in that respect, i.e. no wake problems in a short test, but screen-off current was slightly higher that Ondemand. Haven't given that one a real world drain test yet.
Click to expand...


You may be right. Only really used Smartass to test it. Current kernel doesn't have v2 but am happy with ondemand.
 
hi guys.

been wondering about this topic myself recently.
I've not tried it before because I'm concerned about wake speed. don't like lag :-\

is the main reason for doing this to help battery I'm guessing?

I'm on dGB with manu btw.

cheers
dan
 
Its all about the battery. Most of the time our phones have their screens off. Running the CPU at 1/4 or less clock speed should save quite a bit and won't effect the background data syncs.

SetCPU has a log screen where you can see how long it has spent at each frequency. Most is at the lower value.
 
The thing you don't want to do is set a screen off profile with both min and max set to 128 - that will lag. I don't use profiles at all, but those who do normally set min = 128 (on kernels which support it) and max = 245 or 384, which is enough to avoid that problem.
 
ok cool thanks. I will start without them and
see how it goes
cheer

.....installed and just set min to 128 :-)
 
55% left after 10 hours moderate use. ie no calls. just check these forum
posts and a few texts. not amazing I'm thinking :-\
 
Whats your screen usage? Calls arent particularly a battery killer. Screen is. If you dont touch your phone at all, that 55% will last you days. Thats where the kernel comes into play. Nothing a kernel can do about battery drain when being used by the radio or screen. Kernel can only help with things that use CPU.
 
hi Dan.

right ok. thought that might be case.
I've been jumping on and off it to check the forum updates here.
but other than that its been sat on the desk.
will be interesting to see if it lasts the evening :-)

cheers
dan
 
You must log in or register to reply here.
Back
Top Bottom