Database Users

Phone not waking up after Set cpu?

Hey guys any of you running set cpu? i have a profile set so that when i turn the screen off it drops the cpu down to 250mhz. I'm having a issue where sometimes it dosen't wake back up. Anyone else had this happen?

I noticed this Tuesday. They don't play nice together...yet. setcpu needs info about the hummingbird cpu in order for it to work. Setcpu's dev will most likely have an update for this soon. For now, i'd uninstall it and keep an eye out on the program for an update.

sweet glad to know that its not just me.

I had this same problem with the Overclock Widget for the same purpose (shut down CPU while screen sleeps)... After removing Overclock... I have yet to have a blank screen situation.

I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....

madocs said:
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
Click to expand...
Click to collapse
Scratch that - this morning the EPIC didn't wake. Battery out, back in, screen off, didn't wake.
Uninstalled SetCpu, all is back to normal (except for the crap battery life of course).
Emailed the SetCpu dev, he thinks it is related to the kernel. I'll try out a custom ROM/kernel as soon as one is ready to see if it resolves the issue.

I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.

In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.

Chalup said:
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Click to expand...
Click to collapse
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol

vavaud said:
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
Click to expand...
Click to collapse
How long have you had it in use? I was cool for a day, then it wouldn't wake up.
From the dev: "The scaling is the issue, I think. Ondemand crashes the Galaxy S, but conservative doesn't seem to."
I'm ready to hit some customs, battery life just isn't good enough so far.

2.0t03speed said:
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
Click to expand...
Click to collapse
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.

madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I was using conservative on set cpu when i got the lockup
Sent from my Epic 4G

I have been using setCPU and ATK since 9/2 with no problems so far. I have it set on conservative and 200 when screen is off. I been getting around 10-12 hours with moderate uses. With little use today I am at 9 hours with 50% battery left.

madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I ended up at with over 15 hours logged and ~15-20% battery remaining last night. Good enough for me. Bluetooth/GPS/Wifi on all day, 4G off, screen turned down, ATK.

No Problem with CPU Set at 200
I kept having the same issue until I changed the lower limit to 200 and used Conservative setting.
Now, no problem at all!

I think I tend to agree with you.... I tried running the phoenix kernel on my epic, and the phone would not wake up (was told it was because phoenix defaults to 100/1000) and was told to use setcpu.. tried it... wow... what a disappointment.. setcpu kept giving me way different readings everytime I ran it.... not nice at all....
I've since tried this again, this time, placing setcpu.txt on my /sdcard will see if this helps..... so far, so good......

I have a screen off profile set for 400mhz max 200mhz min with conservative governor. My main profile is 1200mhz max and 200mhz min. This is with the mixup kernel and I never have any lock up issues
Sent from my Emotionless Beast of an Epic using the XDA App

i have my min at 200 for all of my profiles. My screen max is 400 and it keeps my phone from waking up. It's set to conservative. I'm also using it with juice defender, so i'm not sure if that's the culprit or what. Does anyone else have any suggestions on settings for screen off?

Overclocking and black screens when attempting to unlock: Explanation & Solutions

I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
There are a few ways to prevent this from happening (from best to worst):
Create a "screen off" profile in SetCPU to restrict the clock to 800Mhz or below when the screen is off. I think it's obvious why this works. At the same time, a lot of people already do this, which explains why everyone hasn't been having the problem.
Use the conservative governor. Because it scales more gradually, it won't immediately jump past 800Mhz when you attempt to power the screen. There is still a chance of encountering the issue if you attempt to turn on the screen if the device has been busy for a while.
Increase voltages in the kernel. I started experimenting with this before I decided to come here and recommend the first two options. To get the screen to reliably turn on at higher clock speeds, we'd have to raise the voltages substantially. So we'd end up with more risk of damaging components, degraded battery performance and so on. Once the screen is on, the cpu does not actually need more power than it's being given in today's frequency tables. Thus, we'd effectively be increasing power consumption all the time to deal with a need for more power at screen on. Clearly a bad idea.
Unless you're using SetCPU profiles (or equivalent) or the conservative frequency governor, you're going to get black screens. Cyanogen, Pershoot, Evil's and my kernels all use roughly the same voltages, so you're going to need to apply this solution regardless.
There you have it.

*Applauds*
I bow down to your wisdom, sir!

Can you explain why this doesn't happen to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1209/368 (ondemand scaling, no profiles) I have black screens on Virtuous but neveron Cyanogen's mods.

rgl12miami said:
Can you explain why this doesn't happens to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1200/300 I have black screens on Virtuous but never
on Cyanogen's mods.
Click to expand...
Click to collapse
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
There's a simple way to see if it'll ever happen on CM. Set your governor to "performance", with clock speed above 1Ghz. Turn off the screen and see if it fails to turn after a few attempts at toggling it on and off.

I did what you suggested about 30 times and no one has failed. It's a shame,
because I do really love your ROM: speed is incredible. But what bothers me
the most is when the alarm sounds or I receive a call and the screen refuse to
lighten up. I will keep an eye on your rom and for sure I will be back on it soon.
Great job! The best sense rom i've ever seen.

Thanks for this. Works perfectly on my Stock SenseUI ROM with virtuous kernel

Thanks! That explains why the issue hasn't been happening since I set my profile to conservative. That was probably the most annoying issue since I got my G2.

I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.

fastludeh22 said:
I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.
Click to expand...
Click to collapse
What do you mean that every CPU is different? At the hardware, firmware, software level?

gee one said:
What do you mean that every CPU is different? At the hardware, firmware, software level?
Click to expand...
Click to collapse
I think he means every cpu handle overclocking differently, for example ive been very unlucky and my cpu cant handle anything above 1.1 Ghz and it crashes if i set it up any higher but lots of people running theirs at 1.8 and they are stable
its just like overclocking PCs every cpu handle overclocking differently even if they have the exact same spec.

I'm bumping this due to how useful this information is and how often the issue still comes up.
Sent from my HTC Vision using XDA App

rmk40 said:
I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
Click to expand...
Click to collapse
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?

poochie2 said:
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?
Click to expand...
Click to collapse
This was the first question asked (see the fourth post). Here's the OP's theory...
rmk40 said:
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
Click to expand...
Click to collapse
I haven't seen this issue before either.

ianmcquinn said:
This was the first question asked (see the fourth post).
Click to expand...
Click to collapse
My bad, I missed that.

[Q] [Opinions] Undervolt Settings.

First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!

It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?

kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App

Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App

My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app

xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App

I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.

My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.

Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App

Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!

Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.

If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1

I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App

[Q] CM7 + Glitch Kernel not down-clocking

Been lurking for close to a year, but first time posting, so my apologies if this is not the correct forum or location for this question. I would have posted in the Glitch kernel thread but I'm still stuck in the noob-lockout.
I'm running the latest CM7 with the latest, high-leakage Glitch kernel. I became suspicious after I "calibrated" my battery (charged to 100%, reset stats, drained to 0%) and noticed that my battery life was much better while in deep sleep, but with the screen on it was draining at almost 1% per minute. In deep sleep I will get somewhere between 2-5% drain per hour.
CPU Spy shows my frequency breakdown as 1000Mhz at ~10% and Deep Sleep at ~90% with all other frequencies at virtually 0% (this is with resetting the timers and running for a day).
I would think that even with the screen on, there will be moments when the CPU will be throttled down. Running SetCPU on previous roms, I noticed that when idling, the CPU speed would often drop to 100Mhz, but this doesn't seem to be happening with my setup.
I didn't notice any comments in the Glitch or CM7 threads regarding this phenomenon, so I'm wondering if it's something I failed to setup correctly or some other cause.

As an update, I've switched back to the stock CM7 kernel and it is properly throttling down now. 100Mhz is now showing a much higher percentage in CPU Spy.
I would really like to switch back to Glitch, but unless there's some solution it doesn't seem like it's worth the huge increase in battery usage.
Sent from my SCH-I500 using XDA App

You must have a setting incorrect.
Being clocked at 1.2ghz (BFQ i/o and Smartass) CPU spy is telling me the following
1200Mhz - 4:03 - 0%
1000Mhz - 1:01 - 0%
800Mhz - 9:05 - 1%
400Mhz - 7:037 - 1%
200Mhz - 4:59 - 0%
100Mhz - 21:09 - 4%
Deep sleep - 7:40:15 - 90%
What Governor did you try?

I was using bfq with smartass.
Sent from my SCH-I500 using XDA App

I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?

Cota82 said:
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Click to expand...
Click to collapse
Are you experiencing the same increased battery drain with the screen on?

1. Using SetCPU is asking for trouble (random reboots, etc). The Glitch thread OP says to use Voltage Control instead.
2. High Leakage = fewer problems for those with lower quality hardware build (yes, it varies from Fascinate to Fascinate - all Fascinates are not assembled equally), but poorer battery life. Low-leakage = better battery life, but you better hope your Fascinate was assembled well because if it wasn't, you'll have more fcs and freezes than on medium or high leakage.
3. There is no combination of governors, voltages, and schedulers that is the best for everyone - each combo will work better for some than for others
I hope this helps
Another Fascinating post by my XDA app...

I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.

lagbot7000 said:
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
Click to expand...
Click to collapse
Try an overclock - train your phone to use something other than 1000 Mhz
Another Fascinating post by my XDA app...

I decided to restore back to DI01, and use the OTA updates to bring myself back up to ED05. I then reflashed CM7 and Glitch and this problem has gone away. Not quite sure what caused it, but it's running great now.
Running at a solid 1200Mhz with -50mV.

Yes still draining, locked up in 800 mhz cpu freq. (cpu spy) and no deep sleep mode. I'm going to reflash the kernel soon.
Something went wrong I guess (stucked in glitch bootscreen after flashing).
First cleaning scripts and flash the default cm7 kernel for my sgs to be sure.
It should work well according to a member in glitch sgs topic.

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