Database Users

Set CPU Settings

I was wondering what would be considered optimal settings for SetCpu. I amn running BaconBits and am not sure how I should do the settings.
Any help would be appreciated!
Thanks.

i have mine set at:
Profile 1 : 806 MHz max, 245MHz min, On Demand, priority 50
Profile 2 : 245 MHz max , 245MHz min, On Demand, for when the screen is off, priority 50
if i change the MHz, i change it higher on profile 1 for whatever i need it for then i just scale it back down to 806 when i am done...

Mines pretty much the same as the one above save for max clock speed being 1500Mhz.
Sent from my HTC Vision using XDA App

I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.

If you search google for an "overclocking 101" thread you should find a rather large ongoing break down of setcpu and the most efficient way to use it. I believe its on one of the droid forums, awesome info.

tazz9690 said:
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
Click to expand...
Click to collapse
I just stole the rest of your settings, hope you dont mind!

WarBird87 said:
I just stole the rest of your settings, hope you dont mind!
Click to expand...
Click to collapse
By all means, have at it!

Main profile: 245 - 1017 on demand
Charging/Full: 1017 - 1017 performance 90 priority
Screen Off: 245 - 245 performance; mainly as this mode will bypass the need to poll/sample for CPU speeds, thus reduces some CPU load. 100 priority
Battery < 20%: 245 - 768 on demand 75 priority

i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?

WarBird87 said:
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
Click to expand...
Click to collapse
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?

Speaking of powersave bias, could anyone tell me some optimal settings for the setCPU advanced tab? Don't mean to derail this thread, I've just never used that tab.
Sent from my T-Mobile G2 using XDA App

SeReaction said:
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Click to expand...
Click to collapse
I believe i was right at 20% batt or right below,so that could have been the issue... I havent messed with anything on the advanced tab as i dont know much about it, the powersave bias is still set to 0

I have HTC heroc 200 alltel running fresh 2.40 rom firerat mtd 160 10. what should I set CPU to
Sent from my HERO200 using XDA App

does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?

j.books said:
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
Click to expand...
Click to collapse
I used to get about a whole day without setcpu. With setcpu, same amount of usage, I get well over a day and a half before having to charge it up.

[POLL] What's Your Overclocked Speed?

You might have already figured out that HD2 can be overclocked as high as 1.5 GHz on its powerful Qualcomm SnapDragon Processor. Many people run their devices on default clock speed, but there are few of us who overclock their devices to get max out of it. So i have started this thread to know what your max clock speed is and what governer are you using. Post replies below. Also, don't forget to mention your Phone's Temperature if available.
Mine: 1.2 GHz On SmartAss Governer , Temperature Usually Around 95F
Click to expand...
Click to collapse

1305MHz using interactive, temp alway @ 28°C even when phone get hot?? tho alway careful to let it cool down when it feels too hot.

I have underclocked ... to 720Mhz (interactive)
Performance is okay and saves battery live
Temperature is about 28 celcius.

1267, 768 when battery less than 30%, 422 when screen is off
On-demand w/screen on, conservative when <30% and screen off
Not great on battery, but good performance an no wake lag
CPU Load jump or whatever it is, set to 30%
Sent from my HTC HD2 using XDA App

Sticks with no overclock
using a rom which is fast enough and saves battery life, Dont see a point that needed to overclock CPU

Undervolted to 576mhz, for better battery life.
Runs smooth enough for all apps, including navigation and games

No overclock for me, don't need it, phone is fast enough as it is.
Clock speed: 998mhz (default), governor: ondemand, temp: n/a
Good enough for me sweet onough on may battery.
P.s. there seems to be no difference(performance wise) between rafpigna kernel oc'd @1.5ghz and tytung kernel oc'd @1.2ghz, when testing on linpack and/or other smarbench tools

Overclocked settings,

I've looked around and haven't found much. I anyone know what would be a good overclocked setting but save alot of battery?
Sent from my DROID X running MIUI

It varies from phone to phone, unfortunately.
Jrummy's "Android Overclock" is what I personally use...
My settings are:
Low Voltage 1.2GHz Preset (Set at Boot)
And I then enable profiles for some battery saving.
Profiles:
Screen off %100 priority 800MHz max 400MHz min.
Temp > 42c %90 priority 800MHz max 400MHz min.
Battery < 30% %80 priority 800MHz max 400MHz min.
Screen On %70 priority 1200MHz max 400MHz min.
This ensures my phone is at 800MHz while the screen is off or while the temp is high or while my battery is low (I like that one so I can draw the last little bit of battery out a bit.) I put the Screen On profile just as a fail-safe to make sure I revert to 1.2 max while the screen is on unless the other conditions are met.
You can even make your screen off profile all the way down to 400MHz max and min...but that just makes me nervous for some reason.
I never had a problem for the few days that I used it, but I'm a bit OCD with some things.
I was worried that I wouldn't receive calls or my alarm wouldn't work or something like that.
Hopefully this helps a bit.
Try that as a starting point, and adjust as you see fit.

Awesome this helps alot, i have a few profiles set, mainly so up like yours lol, ill looking the lower voltage cause before when i was overclocked I drained battery like no tommrow
Sent from my DROID X running MIUI

standby time for miui

How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.

Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App

Jasonhunterx said:
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just got Voltage Control (the free one)
but I don't get how to use it. Can you please guide me? Which Mhz is sleep profile? and what do you mean build prop tweaks?

Well its pretty simple open app click second tab the you will see sliders you slide them down slide it down 1 notch
Sent from my GT-I9000 using XDA App

But like which ones? I set the 100 to -25 and went to sleep and most 13% overnight.
Which other ones should I set there.sorry for the questions I just don't want to mess up my phone

Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.

}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
So basically, I have to go through the voltages (-#'s) and see how low i can go without crashing?

}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
What would happen if you set it to 1000= -0 ??? Couldn't you just odin back to stock if the phone crashed?

}{Alienz}{ said:
Start with these
(Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor

check this out
http://forum.xda-developers.com/showthread.php?t=829731

nbhnohome said:
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
Click to expand...
Click to collapse
I don't think I want to go THAT low, maybe it'll crash my phone or someting?
caldran said:
http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
that thread doesn't help. I've seen it before, its just info.

I think people are answering the wrong question. Or I should say, giving answers to a different question.
To the OP: You're talking about Deep Sleep battery usage, right? There's no way to undervolt Deep Sleep. It's already using very minimal voltage. I believe what causes excessive Deep Sleep battery drain is the number of apps still running and using the CPU during Deep Sleep.
Undervolting will help a bit with battery drain during normal usage. For Deep Sleep, turn off your various apps' syncing ability, as well as freezing programs you don't use but that run in the background. For instance, if you don't use navigation very often, consider freezing the Maps app, as it runs all the time in the background. A number of popular games like to run in the background like GunBros and Aqua Pets. Also switch from 2g/3g or 3g to 2g only at night to save battery there.
To recap, the less you have running in the background, the less battery you'll lose when you phone is in Deep Sleep.

I was also going to say switch to 2g if you don't need the speed. It helps a lot for me. I also usually put my phone in flight mode before I sleep. I lose like 0.5% of battery an hr on flight mode. I'm not on MIUI yet, still on froyo, but should still help.

I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV

mohitmoudgil said:
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
Click to expand...
Click to collapse
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.

Can I do voltage Control on stock MIUI Kernal or do I need Neo?
Sent from my Vibrant.

In my experience (admittedly only been on MIUI for a few weeks), Pimp my CPU, Voltage Control, and SetCPU all work fine on MIUI, so yes. You should be able to use Voltage Control. Not entirely sure about Stock MIUI, but if you use the (superior) Revamped version (either SS or Lithium editions) the kernel that comes stock with it allows you to change voltages, though I would still recommend moving to Glitch and using either the ML or LL versions if you want to maximize battery savings.
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Click to expand...
Click to collapse
OV/UV settings can vary widely between phones. Some offer little to no leeway at all, and can't even be overclocked to the rather tame 1200mhz. Others can sit at 1700mhz at 100uv. It's luck of the draw really. Also, Conservative Governor will be kinder to more exotic UV settings, while others like Smartass or OnDemand may only allow for a slight 25 or 50uv for most voltage levels.
Trial and error, my friend. Find what works best for your phone.

Thanks guys.
One more question
If when I test if my phone can handle a certain UV is it good to have it at the lowest I can?
Like example
My 400mhz can go down to -200UV is that good or bad? Should I keep it that low if its not crashing or anything

You need to do some stress testing to be sure it's stable at those frequencies. Depending on the governor you use, your phone may not hit 400mhz often enough for you to really tell if it's stable or not. You could set 800mhz to -800uv, but if your phone tends to skip over 800mhz most of the time...
Undervolting can cause other problems if it's not completely stable. For instance, on Froyo I would get annoying static during music playback. Took me nearly a month to figure out that it was because I was undervolting the 400 to 100mhz range too much.
Undervolting doesn't make THAT big a difference. If you don't want to tweak and stress test and tweak and tweak again and stress test again, etc etc etc, then just reasonable settings that most phones can handle. For instance, 1200 0uv, 1000 25uv, 800 50uv, 400 75uv, 200 100uv, 100 125uv.

xriderx66 said:
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Click to expand...
Click to collapse
In my experience when I switch to only use only 2G networks I get damn near twice the standy time. Also, changing wifi to never sleep and staying connected to wifi has about the same effect. This also holds true for CM7.
3G is a battery killer for MIUI and CM7
The only resolution I see to this is a GB source drop but I'm not holding my breath.
Off topic but does anyone know a good, fast device that runs CM7/MIUI without bugs or this horrible battery drain? I've been running some form of CM7 since Eugene's build this spring and it has gotten MUCH better but I'm kind of disappointed at the lack of vibrant-specific progress lately. There's only so much the devs can do without source (or a working vibrant and a T-Mobile data plan for that matter....). Don't get me wrong, I'm thankful for what we have and what the devs have given us but I'd love GPS that isn't f'd and 3G that doesn't suck my battery dry in a little over 10 hours (working 911 wouldn't hurt either.
Sent from my T959 using xda premium

Best Settings For Snappy Fast Perfrormace/Overclock? Help

Im looking for someone to tell me what they think is there best settings to be used in there prefered app for example setcpu,faux123, do you overclock and to what settings, what has worked for you guys
i generally dont use my phone to much in a day so battery last the day so i dont mind it being overclocked when im using it if it means it runs faster but drains battery, some suggestion please, im a novice
no flames about i used the word 'best' im looking for opionons thankyou if you help

Whelan189 said:
Im looking for someone to tell me what they think is there best settings to be used in there prefered app for example setcpu,faux123, do you overclock and to what settings, what has worked for you guys
i generally dont use my phone to much in a day so battery last the day so i dont mind it being overclocked when im using it if it means it runs faster but drains battery, some suggestion please, im a novice
no flames about i used the word 'best' im looking for opionons thankyou if you help
Click to expand...
Click to collapse
IMO, no overclock is required. The phone is fast and snappy enough.
That said, I underclock the minimum frequency and undervolt throughout the frequency table.
This ensures that I get better battery life, without any decrease in performance.
I'm running CyanogenMod 10.1.0 Stable Release.
I'm using franco.kernel r161, and his companion app - franco.kernel updater.
The following settings are giving me great performance and battery life.
CPU Frequency Range : Screen On - 384 MHz - 1512 MHz, Screen Off - 384 MHz
CPU Governor : Interactive
GPU Frequency: 400 MHz
Frequency Table Undervolt : -125 mV throughout
Disclaimer - This is for a {fast} binned CPU. Check your device's CPU binning via this link, and do some trial-error to find the perfect undervolt for your device.
Good Luck!