Related
Thread title says it all. Please answer me
Firstly, no its not safe to run it at 1130MHz all the time. Even, It's not advisable to run at 998MHz all the time. It gets extremely hot. The voltage at 998MHz is high and the voltage and heat is what kills a processor. Also stability might be a issue. It MIGHT be possible to run it at 1130MHz but that would be selectively. It can be done by setting profiles in set CPU. Thing is, DON'T do it ALL the time, BUT SELECTIVELY. use the setting ON DEMAND. also, try to set temperature dependent profiles.
Hope this helps
how I overclok it?
Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.
I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g
i ran these through my seat-of-the-pants benchmarks, are there any other for these sorts of apps? , and can't tell any difference. the biggest difference maker that i have noticed is Titanium backup and freezing as many progs as i could and a better launcher.
i tested the phone as it initially came out of the box, removing the apps i could via app manager.
next, i ran it with JDU for ~4 days.
Then i ran Tit backup and froze many more apps and ran the phone with JD for 3-4 days.
then installed Ram Manager Pro and ran for a few days, then uninstalled JD and Ram Manager by itself for a few days
and finally uninstalled both, factory reset my phone, ran Tit Backup freezing everything i wanted and am now running that config for several days.
i can't see any change in battery life or perf between any of these.
what's your experience? did i miss the benefits? is there a more scientific way to test these apps on our phone?
I could be missing something, but my understanding of Ram Manager is that it controls how the cache works (RAM cache that is), aka, how previously opened apps are being handled, how long they stay in ram, or/and how often ram getting cleanup, etc. So theoretically there shouldn't be much of battery improvement with that app, only the performance on common used tasks.
As of Juice Defender, I've tried once, and realized it's not for me, I use push mail and listen pandora radio most of the time, it requires internet all the time. But in theory it should significantly save on battery if you don't use phone every second minute, cause it turns off everything and only turns data one every so often to check email, news, etc.
I guess it depends how you use your phone...
Have you tried SetCPU or such?
I use SetCPU to change CPU frequency, set min to 190mhz and max to 1500mhz, and max to 190 when screen off, yesterday with minimum phone usage in 7 hours used up 15%
And I wonder, by default, does Nitro set CPU to max and keep it that way or it also uses scheduling and changes speed as needed?
But I can tell you for sure, the network (HSPA+ here) usage uses as much battery as the screen, if not more...and network through WiFi saves on battery compare to HSPA.
[email protected] said:
I could be missing something, but my understanding of Ram Manager is that it controls how the cache works (RAM cache that is), aka, how previously opened apps are being handled, how long they stay in ram, or/and how often ram getting cleanup, etc. So theoretically there shouldn't be much of battery improvement with that app, only the performance on common used tasks.
As of Juice Defender, I've tried once, and realized it's not for me, I use push mail and listen pandora radio most of the time, it requires internet all the time. But in theory it should significantly save on battery if you don't use phone every second minute, cause it turns off everything and only turns data one every so often to check email, news, etc.
I guess it depends how you use your phone...
Have you tried SetCPU or such?
I use SetCPU to change CPU frequency, set min to 190mhz and max to 1500mhz, and max to 190 when screen off, yesterday with minimum phone usage in 7 hours used up 15%
And I wonder, by default, does Nitro set CPU to max and keep it that way or it also uses scheduling and changes speed as needed?
But I can tell you for sure, the network (HSPA+ here) usage uses as much battery as the screen, if not more...and network through WiFi saves on battery compare to HSPA.
Click to expand...
Click to collapse
that's my understanding of Ram Manager as well. but i didn't notice any perf changes in how fast apps open, close or switch v a Titannium freezing showing good results imo for that sort of thing.
i listen to slacker/pandora but it's mostly via wi-fi, so i was able to configure JD to keep the wifi on and turn off all the other radios but that didn't seem to provide me any benefits.
i have not tried setcpu but will def check it out, thx for the heads-up on that one.
re: network, it doesn't even show as a battery drain on this phone and i am in an LTE area, the 4glte status signal is always on. i was under the impression it was a massive drain, maybe the phone searching for a lte signal is the drain but once it finds one and locks on maybe it settles down. i have no idea but it's not on the list of what's using the battery.
Ram Manager Pro has several settings (Balanced, Balanced-More Mem, Hardcore Gaming, etc...). Did you try any of the others? For me I noticed improvement, but perhaps it's also because of the way I use my phone and that Ram Manager is more suited to my ways and habits... Or maybe it's just placebo and I'm drinking the kool-aid.
For Juice Defender Ultimate, I will say probably one of its' biggest capabilities is locking down the apps that turn on the radio for background updates. A definite battery drain for folks that use a lot of social apps as they compound the use of background updates. I personally turn-off ALL background updates except for mail. So JDU wouldn't tremendously help me.
Lastly, I completely agree with [email protected] about SetCPU. I don't know how the OS handles the frequencies but one of the biggest battery savers is definitely using SetCPU for dropping the min/max CPU speeds to minimum levels when the phone is sleeping.
I installed setCPU and it instantly created a laggy interface. very very noticeable. HAs anybody else tried this app with this phone?
Had this same problem. I actually switched of all apps. The phone on idle does not loose that much juice. Overnight I maybe loose 8-10%. I turn data off at night using Tasker.
Sent from my LG-P930 using xda premium
update
I've still been farting around with these apps, going back & forth between using them and not.
best I can tell ROM manager provides ~5% increase in ROM management, which is pretty good for a couple bucks eh.
JD is so much harder to gauge/compare. I think it does defend the juice but I can't tell how much. The one thing I do not get about the app is how it continues to show increased battery savings over the previous 48 hours. I can see how this works when the app is 1st installed but at some point over time that number should = 1 right? JD can't keep stretching battery life 1.5x over its own management system.
scott0,
You're right, unless there's some heuristics built in (probably not).
Sent from my LG-P930 using xda premium
Anyone using a good stats widget that would show mhz of cpu/baterry/ram?
Something light that would not eat battery. I used the one that came with antutu cpu master but that caused more problems.
Sent from my LG-P930 using Tapatalk
Just out of curiosity, do you have to be rooted to use Juice Defender? When I select the app in the market it tells me "This item isn't available by your carrier."
Are they telling me that AT&T has blocked a power saving app?
I recently have bought a Defy plus.
Stock 2.3.4 ROM used so far with LauncherPro.
Doing OK with battery life so far, but now starting to look at the CPU over/underclock capabilities. Started with Antutu CPU Master and CPUTuner also.
One thing I haven't seen as yet is the ability to underclock clock below the min 300MHz.. or even whether this makes sense. I guess undervolting is the other option, but perhaps someone can guide me here.
use setvsel to oc/uv, thats the easiest and best app imo. although underclocking your phone below 300mhz may cause instability and makes the phone wake up much slower in my experience.
sent from my cm7 defy...
I agree with zakoo2: Going below 300 will not be a good idea and it will most likely not improve your battery life in any significant way:
My Defy is running between 300-600Mhz and right now the LCD screen is the biggest consumer: Changing the (auto-)brightness settings in CM7 will do *much* more to your battery life than going below 300mhz.
What really helps saving battery life: use setvsel and leave the minimum clockspeed at 300MHz, but set a vsel value of about 20 for it, then scroll down and enable "limit to vsel1 while screen is off".
Also, going below 300MHz will probably make the phone sluggish when waking up from sleep like if a call comes.
Sent from my MB525 using XDA App
im just change from 300mhz to 330mhz lowest. 300mhz will make my defy+ lag when got incoming call. im using smartass govenor.
I heard some guy out there got 80 MHz and running, but I'm not sure of it.
As people said, clocks lower then 300 MHz would make your phone run horribly while waking up (i.e., it would take a long time for the screen to turn on when receiving a call, and you would probably miss it most of the times). Setting 300 as VSel1 and limitting to it while screen is off (2nd-init enabled bootmenu has this option, and downloading SetVSel - free at Android Market - will also do the trick if you have a rooted, but stock ROM) will help you save a lot of juice. Using a lightweight launcher (I personally recommend MetroUI or Zeam) also boosts up batt saving. Last, but not least, setting brightness to auto or minimum (using frosted/mat screen protectors will help a lot while using the phone under direct sunlight) also saves loads of charge.
Obviously, using a light ROM (I think Barebones may be a good option, though I think it's not suitable for me, but it's a personal matter) and calibrating your battery in a monthly basis (via manual calibration - you can find how to do so by googling -, wiping batt stats in custom recovery and/or using the batt calibration app included in most ROMs - but also free at AM) also help.