Database Users

SetCPU Undervolting for Atrix

I understand there are numerous posts in various forums regarding under volting however, none of them relate to the Atrix!
The idea of this thread is to gather enough data that can enable us regular users of the Atrix, to safely and effectively undervolt our CPU's to enable maximum battery life.
I was wondering if you guys and gals would be willing to post what is working for you. I simply lowered mine -75mV for all frequencies on the list in SetCPU and it seems to have given me an extra boost in battery life by about one to two hours.
If you don't have the latest version of SetCPU: buy it off the market or search the forums for it and download it off here.

There's a thread in general from a week ago with some comments on undervolting. Also, in Faux's OC kernel thread there's quite a few posts later on (after he updated it to enable undervolting) with people posting their undervolting tests/settings.
As for me, I just put -50 for all and it's been stable.

People aren't going to waste time searching through the aforementioned posts or threads you've listed. I simply want it easier for people to click on one thread with the specific purpose of undervolting.

rdubyah said:
People aren't going to waste time searching through the aforementioned posts or threads you've listed. I simply want it easier for people to click on one thread with the specific purpose of undervolting.
Click to expand...
Click to collapse
Understood, but faux's kernel is thread is pretty active. Also , as obviously see yourself, the other Undervolting thread (which had the same purpose as this one) has already dropped off the radar (aka out of the first page) which will very likely be the same fate as this thread unless you're bumping it yourself every couple hours or it picks up steam. IMO it would have been easier build on the original undervolting thread so there's more info in a singular thread to build momentum on and keep it near the top.

mysticdrew said:
Understood, but faux's kernel is thread is pretty active. Also , as obviously see yourself, the other Undervolting thread (which had the same purpose as this one) has already dropped off the radar (aka out of the first page) which will very likely be the same fate as this thread unless you're bumping it yourself every couple hours or it picks up steam. IMO it would have been easier build on the original undervolting thread so there's more info in a singular thread to build momentum on and keep it near the top.
Click to expand...
Click to collapse
I cant post on fauxs thread yet. Just building some juice here. Agreed there is the right place for this discussion.
Sent from my MB860 using Tapatalk

where in SetCPU is the option to undervolt??

Like I mentioned in my original post, search the forums for the latest version of SetCPU or purchase it off the market.

Ive got every frequency at -500 except for 1100. Which i have at -100.
Sent from my MB860 using XDA App

Weese said:
Ive got every frequency at -500 except for 1100. Which i have at -100.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
edit: wow you can go -500 and be stable!
right now im stable at -100 -100 -75 -75 -75 -75 -75

I had everything at -50 and my phone was stable until I used my GPS and it rebooted. I now I have everything at -25. So far so good.
Sent from my MB860 using XDA App

Weese said:
Ive got every frequency at -500 except for 1100. Which i have at -100.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I find it hard to believe that your phone is stable at those undervoltage settings but if that is the case (no random reboots) that's pretty impressive.

Weese said:
Ive got every frequency at -500 except for 1100. Which i have at -100.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I'm betting typo...

You can manually make every frequency to -500 or some other crazy settings, and sometimes it will crash and sometimes not. The thing is, the Tegra2 chip only recognizes and performs less than 100mHz change in-between each step/frequency. So is the different between 2 frequencies is greater than 100, it will still only recognize and use only 100mHz. So even if you are able to set every frequency ridiculously low, the chip is not running at those voltages. Read more about this on Faux123's Kernel thread to understand it fully, I'm just regurgitating it. Hope this helps.

I think I have the newest version of set cpu 2.2.4 and I can't find the volt tab am I missing something is there a setting option I need to enable? I was using faux's kernel with ninja rom

TechRebel said:
I find it hard to believe that your phone is stable at those undervoltage settings but if that is the case (no random reboots) that's pretty impressive.
Click to expand...
Click to collapse
isn't there an issue with faux kernel right now where if you go past -100 it still does -100 not that value you've input (i.e. if you put in -500 its still actually doing -100)

i've been running the following setup, on my second day without charging (only moderate use, gaming for about 45 minutes to an hour and a half plus using my phone as internet browser multiple times throughout the day, 5-6 widgets total. sitting at 18% left, and i'm on hour 30 something)
now, keep in mind this is also using the battery calibration app, ninja speed freak and faux's oc kernel.
-25
-30
-30
-50
-100
-100
-150
i've been averaging around 3000-3200 quadrants in the quadrant standard benchmark test, so needless to say i'm extremely satisfied with my settings.
also have custom profiles set up, if my screen is off i run at 608mhz max, 216 min. charging gets 1100 max 216 min, incall gets 216 max 216 min, battery less than 15% gets 608 max 216 min and battery<10% gets 456 max, 216 min.

Alcapone263 said:
i've been running the following setup, on my second day without charging (only moderate use, gaming for about 45 minutes to an hour and a half plus using my phone as internet browser multiple times throughout the day, 5-6 widgets total. sitting at 18% left, and i'm on hour 30 something)
now, keep in mind this is also using the battery calibration app, ninja speed freak and faux's oc kernel.
-25
-30
-30
-50
-100
-100
-150
i've been averaging around 3000-3200 quadrants in the quadrant standard benchmark test, so needless to say i'm extremely satisfied with my settings.
also have custom profiles set up, if my screen is off i run at 608mhz max, 216 min. charging gets 1100 max 216 min, incall gets 216 max 216 min, battery less than 15% gets 608 max 216 min and battery<10% gets 456 max, 216 min.
Click to expand...
Click to collapse
Been using these settings for 3 days and I can honestly say they're fantastic. I was getting 11-18 hours out of my Atrix with other ROM/Kernel/CPU settings; with this setup I get 30-40hours. Simply fantastic.
I'm a fairly light user, but I keep data/wifi on at all times (even screen off) syncing 3 exchange accounts (push); make about 10 mins of phone call in a day; surf slashdot/xda/engadget/etc once every hour or two; and watch 5-30mins of flash vids a day.
Only thing to note is that I had to adjust the UV on the lowest setting to -125 to avoid intermittent loss of WiFi connectivity.

Alcapone263 said:
i've been running the following setup, on my second day without charging (only moderate use, gaming for about 45 minutes to an hour and a half plus using my phone as internet browser multiple times throughout the day, 5-6 widgets total. sitting at 18% left, and i'm on hour 30 something)
now, keep in mind this is also using the battery calibration app, ninja speed freak and faux's oc kernel.
-25
-30
-30
-50
-100
-100
-150
i've been averaging around 3000-3200 quadrants in the quadrant standard benchmark test, so needless to say i'm extremely satisfied with my settings.
also have custom profiles set up, if my screen is off i run at 608mhz max, 216 min. charging gets 1100 max 216 min, incall gets 216 max 216 min, battery less than 15% gets 608 max 216 min and battery<10% gets 456 max, 216 min.
Click to expand...
Click to collapse
Are these voltage settings going from 1100MHz (-25) to 216Mhz (-150)?

crea78 said:
Are these voltage settings going from 1100MHz (-25) to 216Mhz (-150)?
Click to expand...
Click to collapse
Correct from highest to lowest, starting at 1100mhz.
Also, I may have just extended the battery life to 48~ hours last night by using these settings and using a combination of autostarts to stop non-essential processes from starting and titanium backup to freeze non-essential processes that seemed to start anyway.
Also note; when setting up the profiles in setCPU, make sure you get the priorities right; otherwise they can be fairly ineffective.

Alcapone263 said:
i've been running the following setup, on my second day without charging (only moderate use, gaming for about 45 minutes to an hour and a half plus using my phone as internet browser multiple times throughout the day, 5-6 widgets total. sitting at 18% left, and i'm on hour 30 something)
now, keep in mind this is also using the battery calibration app, ninja speed freak and faux's oc kernel.
-25
-30
-30
-50
-100
-100
-150
i've been averaging around 3000-3200 quadrants in the quadrant standard benchmark test, so needless to say i'm extremely satisfied with my settings.
also have custom profiles set up, if my screen is off i run at 608mhz max, 216 min. charging gets 1100 max 216 min, incall gets 216 max 216 min, battery less than 15% gets 608 max 216 min and battery<10% gets 456 max, 216 min.
Click to expand...
Click to collapse
Gonna give you mad props for this. Doing great things to extend battery life.
Sent from my MB860 using Tapatalk

Undervolting a Xoom - battery results included

I haven't been able to find any info on undervolting the Xoom, so have started this thread in the hope that some may find it beneficial.
What is undervolting?
It basically involves reducing the amount of electrical voltage running through the CPU. It does not affect the speed of the CPU at all, just the amount of power that it uses. The stock configuration of CPUs usually has a fairly high voltage, to cater for the fact that CPUs are not exactly identical.
Why undervolt?
Reduce power consumption, and therefore increase battery life.
Why not undervolt?
Can affect stability, and there is a small risk of damage to your device.
Disclaimer: Undervolting, like overclocking, does have the potential to damage your device. It's very rare, but not unheard of. I've never had a problem, but you may. Good luck, and don't blame me.
My config:
Model: MZ601 Xoom
Kernel: Tiamat Xoom v2.1.0
Undervolting software: SetCPU 2.2.4
My voltages before UV:
MHz mV
216 770
312 770
456 825
608 900
760 975
816 1000
912 1050
1000 1100
1200 1150
1408 1250
1504 1325
1600 1400
1704 1400​
So after doing a bit of testing, I've found that I can lower my voltages noticeably throughout the range, reducing the amount of power my Xoom uses, and prolonging my battery.
My UV voltages:
MHz mV
216 770
312 770
456 775
608 825
760 875
816 925
912 975
1000 1000
1200 1075
1408 1125
1504 1175
1600 1250
1704 1325​​
Notes:
It is not possible to UV any less than 770 mV (with the kernel I'm using anyway).
Given that the mV for the 456 CPU frequency is so similar to 216, I set my minimum clock frequency to 456, which makes the device more responsive.
So, you may want to try these voltages, and see how they work for you.
To test: (Instructions for SetCPU)
Set your min & max speeds to the same frequency, for example 456.
Set the voltage of the 456 frequency to an amount lower that the current amount, for example 775. (It's generally best to adjust your voltage down only 25mv at a time.)
Perform a "Stress Test", for at least about 5 seconds.
If the device locks up or reboots, the mV is too low - try a higher mV.
Once you've found the optimal voltage for that frequency, move onto the next one, for example 608, then 760, etc.
If your device locks up or freezes during testing, you can force a reboot by holding down the Volume Up button, and the Power button.
The voltages I've used above may work for you, or you may have to increase them a little on your device. You may also get better voltages than me - if so, please post your results.

Battery test results
Performed some battery performance testing by doing the following steps:
1. Set the screen to not turn off, and brightness to 10% (screen needs to be on to keep the stress test running, and brightness low to minimise the battery drain of the screen, as that's not what we're testing).
2. Disabled all network connections (WiFi, Bluetooth, Data, GPS) to minimise battery drain by other factors.
3. Closed all other apps, and did not use the Xoom at all during the tests.
4. Charged Xoom to 100%.
5. Set CPU speed to 1504mhz using SetCPU (both min & max frequencies the same for accurate testing).
6. Unplugged the Xoom.
7. Ran "Stress Test" for 2 hours (give or take 20 seconds).
I performed the above steps for both stock voltage, and undervolted voltage. Results as follows:
1. For stock voltage (1325mV on Tiamit Tachi kernel), battery life went down to 62%.
2. For undervolted voltage (1175mV, which is nice & stable for me), battery life went down to 72%.
Findings:
I was expecting battery savings, but not quite this much.
Standard voltage (at 1504mhz) at this CPU load, drains at about 19% per hour.
UV voltage at this CPU load, drains at about 14% per hour.
Standard voltage at this CPU load, the Xoom would drain battery entirely after about 5.26 hours.
UV voltage at this CPU load, the Xoom would drain battery entirely after about 7.14 hours.
In addition to the battery savings, the Xoom was only slightly warm after the UV tests, but very warm after the standard voltage tests. (Standard voltage test was performed first.)
Note: For general usage (email, browsing, basic apps & widgets), the CPU is not as heavily used. But in situations where the CPU is heavily used (such as intensive games), these results show there is significant potential for battery savings.

super nice tips. Tq very much

126-608 -175
Others -150
This is my settings... no prob at all.

Would I use setcpu app or just use the Moray(in settings) or does it matter

rayhodge02 said:
Would I use setcpu app or just use the Moray(in settings) or does it matter
Click to expand...
Click to collapse
Not sure what the "Moray" is, but any tool capable of undervolting should be ok. I like and use SetCPU, but I've tried other tools on other devices in the past, and they did similar things.

nobody wants to share their result after trying?

Very good job, I try
Sent from my Xoom using xda premium

pls share ur best result

I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium

Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.

for me i just underclock my xoom to 912mhz. it is almost as fast as 1ghz. and i save battery alot.

Gregus59 said:
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Try bumping up the voltages a little bit at a time, until you find a stable setting. The settings I listed are what are stable for my Xoom (even intensive 3D games), but CPUs vary. What I get, others may not, and others may get better than me.

musashiken said:
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
Click to expand...
Click to collapse
They're not 100%. The longer you stress test, the more likely the CPU is stable, but 10 seconds gives a general idea. If unstable, just do as you did, and increase by 25mv or so.

omnia1994 said:
126-608 -175
Others -150
This is my settings... no prob at all.
Click to expand...
Click to collapse
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?

do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?

baron von bubba said:
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
Click to expand...
Click to collapse
1. It depends what you're using the device for. Games, for example, can use a lot of CPU, so undervolting in this instance, will definitely use noticeably less battery.
2. If CPU voltage throughput didn't make any difference, we'd all just run our devices at 1700mhz all the time.
3. With undervolting, I can run my Xoom at the same voltage at 456mhz, as it run at 216mhz. This means I set my minimum frequency to 456 instead, and for the same minimum battery consumption, my device is noticeably smoother.
If you want to know how much extra time you will get from a fully charged battery, YOU do some tests.

lindsaytheflint said:
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
Click to expand...
Click to collapse
Yes i m sure. Has been using these settings till now.. no prob at all. Using tiamat stock gpu kernal with moray rom

i agree that during low intensity operation the power savings are probably nearly negligible, but during CPU-intense usage it could save a bit.
I myself am not willing to leave my Xoom on full bore for a series of tests lasting 7-10 hours each just to quantify how much power undervolting can save under super extraordinary circumstances.
But even if the energy savings is an arguable benefit, the reduction in CPU temperature is not. That alone makes this worth doing, IMO.

Agree.. after setting it my xoom now has lower temp when playing it

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

Time spent in (clock) governor discussion

So, I futzed around with NStools, and setCPU, trying to find the ultimate governor combination.
With ondemand, no matter what my max clock was, I always had lag, because while it did scale fast, it sampled too slow, even at the lowest allowed.
A big issue was that governors would scale to high clocks, but took too long before it decided to scale up.
I noticed that smartassV2 was willing to scale at smaller intervals, but was WAY too jumpy for going up... after all, why have unused clock cycles. If you're at 75%, and you jump up a notch, you'll be at like 50-60%.
I came to an idea.
I originally tried init.d script to do this, but for some reason on swagged out stock, init.d scripts aren't working for me. Note, I stripped a lot of components from swagged out stock using titanium backup, or just simple uninstalls. It is SOS N running aggressive lionfish 1.8. The stripping of components lowered my memory usage significantly.
I took setCPU, set max to 998mhz, and min to 128mhz, set on smartassv2 with no profiles.
I took NStools, set as follows
scheduler to SIO
cpu to smartassv2
min freq 128
max freq 998
awake ideal freq, sleep ideal freq, and sleep awake freq to 100,000hz,
min cpu load to 85%
max cpu load to 100%
ramp down step to 38400hz
ramp up step to 38400hz
down rate to 10000
upr rate to 10000
Before I did this, I've never experienced this level of smoothness. The real kicker is what setCPU says my "time spent in" is
I wiped my battery stats last night, and let it run down till 10%
I'm at 97.98% of my time spent in 128mhz after over 24 hours, yet it feels perfectly smooth when I play with it. I think part of this is the fast sampling response time of Smartassv2, and also the fact that my rom is running light.
It clocks up, does what it needs to do, and rapidly clocks back down.
How are you guys doing on that chart?

If your phone spent 97.98 % of 24 hours on 128 mhz is not really good. When you don't use the phone, it should go into deep sleep. Download cpu spy from the playstore. If your phone doesn't go into deep sleep, it means you have wakelock issue.
Sent from my lair.

SetCPU was reporting some of the time as 128mhz when it was actually deep sleep.
I checked out CPUspy, and it reads at 51% 128mhz, and 43% deep sleep, with 1036 to 1228 unused, and 62:45:58 of recorded data time.
Out of that, 32:30:15 was in 128, 27:25:01 was in deep sleep, while most of the rest was between 245 and 449, with 00:26:28 on max speed
Does this mean something is waking me out of the 128hz range, while its asleep, and I need to figure it out? I read something about gtalk with video having a wakelock issue, and I have that.

Reduce heat with system perfomance

geowolf1000 said:
Iarge amount of cpu which are enable by default can modified if you do not want extra press the stock pefomance per app at setings
Is was too on cm.12 nightles too but has optoon
Now disable it
IMPORTAMD
FIRST TIME BREAKS DIALER
ONLY REBOOT IS FINE!!
Download an cpu tool you preferp
I downloaded from here
Set to 300 minimum
Get userspace And linux governor cfq.
Set on boot .
Try it .
Noop breakes wifi
Click to expand...
Click to collapse
:good::good:
+50 mA battery power less

Watt?

No need to post
Last battery issue was less than 30 mA and consume your batterry
In one day
Default cyanogen clocks is 1572 minimum....
Perfomance will not affect
Has only stable little heat all the time
And sweater heat with full sensors awake
Lte.,nfc , bluetooth...and calls with proximityis bigger
Heater but not so obvious from previous sudden
Real hot Situations.

Is this battery saver app ?

The minimum frequency is so high because the stock kernel is using MPDecision as the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:

mumaster20 said:
The minimum frequency is so high because the stock kernel is using MPDecision als the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:
Click to expand...
Click to collapse
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.

geowolf1000 said:
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.
Click to expand...
Click to collapse
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!

mumaster20 said:
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!
Click to expand...
Click to collapse
I will collect you the cpu stats with and op settings for all day
Perfomance will be same and post it after for more .

So the stats show that profile per app keep device at 1452mhz double time than without
I examine with same settings almost same hours and almost same usage
The white background screenshots is without
The black background is with
My perfomance is absolute same i only feel diference at low battery level
Lower than 8% at wake up
Ps there is a bug when change this settings
Battery show always awake device but is false
After full charge and shutdown all normal