2 parts - one question one observation.
Stock everything.
While playing around with battery savers that change cpu frequency when the screen is off, I noticed no thrills cpu stats, that the default GRAND`s behavior is to auto switch to 312MHZ and deep sleep while idle and screen off, is that the case? is there no real need for apps like no thrills cpu/cpuspy to set min-max?
Is there a real need for battery savers?
egor27 said:
2 parts - one question one observation.
Stock everything.
While playing around with battery savers that change cpu frequency when the screen is off, I noticed no thrills cpu stats, that the default GRAND`s behavior is to auto switch to 334HZ and deep sleep while idle and screen off, is that the case? is there no real need for apps like no thrills cpu/cpuspy to set min-max?
Is there a real need for battery savers?
Click to expand...
Click to collapse
Yes, our Galaxy Grand will auto-reduced the frequency to lowest 312MHz on stock kernel when the screen is off, after a few moments later it will enter deep sleep which will conserve battery usage.
Unless you want to Max / Min performance all the time, I would say yes, you don't need those apps to take control over your CPU frequency.
It seems like the min-max is working beyond the screen off situation,
even if the defaults shown by no thrills cpu are 1200MHz .
Related
I'm really struggling with battery life at the moment. Has anyone got settings I can use to save on battery life in SetCpu? Profiles etc
+1
I'd like to know too.
I would also like to know =[ my battery dies wayy too fast. I have the darkstone froyo build on my htc hd2 phone energy rom. Any programs or SETcpu settings that will help out?
If your on a rom with preflock disabled then you can underclock.
The only thing you need to change in setcpu really is to make a profile for screen off and set it to 245 (or whatever is the lowest I can't remember) both max and min (leave it on demand, or interactive if your rom has that).
This should give you about 10-15 hours longer battery life
so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?
No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.
No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.
i think im kinda get what you're saying (sorry im kind of slow) so i had just deleted my other profiles and made a screen off one have it set to max all the way right and min all the way left, on demand, priority 100. Now on the main screen i think i touched it cause i read somewhere for max all the way to the right and min all the way to the left. This is confusing lol
The settings I have for my Desire:
Default:
Conservative 245-998
Profiles:
Screen Off - Priority 100 - Powersave
Charging/Full - Priority 50 - OnDemand 245-1305
Battery < 30 - Priority 0 - PowerSave
Running along side JuiceDefender, battery life is acceptable to me
jdeezyboo said:
so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?
Click to expand...
Click to collapse
Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE
Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE
__________________
When Chuck Norris holds the Iphone4, the signal increases
That totally defeated the purpose of my question and others before me. Our battery lifes sucked without any programs so now we delete it?
I used darkstones froyo for awhile too. Battery drain killed it for me. I had no luck with anything. Changed to a nand build and its much better. Apparently SD builds just use more battery. With the SD froyo I could never stay below 60ma a few times would drop to less than 10ma but just not consistent. I lost about 8% an hour in sleep mode. Give a well designed nand build a go. In sleep I hover AT 4ma. My battery with Moderate use easily last the day, heavy use (multiple calls, emails, and browsing for an hour or two) still does require a recharge
Im using carbon ara theme with pcb just turn data off wen aint using it via toggle and have a profile for sleep in set cpu for min and max of 245 and from full charfe at 7am by 6 pm im still 65%. Thats using fb checkin email playing angrybirds and checking the forum
Sent from my HTC Desire using XDA App
I also use advanced task killer and kill all tasks wen not in.use
Sent from my HTC Desire using XDA App
bad idea as you are actually making your battery work more by doing that.
Sent from my HTC Desire using XDA App
What's the lowest you've set for Setcpu's 'screen off' profile? I tried 200 min/200 max and it didn't wake my phone when I tried turning it on. I have it set at 200 min/500 max right now. anyway to go lower than that? I'm trying to conserve battery as much as possible.
i got mine set to 200/500 mostly because 200/200 caused glitchy wakeups and occasional glitches when running background tasks with screen-off such as navigation/music/etc.
i also undervolted both 200/500 to 825mv/850mv so either way they both are barely using any of the battery
main reason for locking CPU to 500mhz max with screen off is in case something goes haywire and goes crazy on cpu, at 100% cpu usage @ 500mhz won't heat up the battery at all.
Just 200/500 for me, 200/200 at one point and no more than about 15 minutes later the screen wouldn't wake up.
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.
Ive got blu Kuban 1.0.4.3 ROM on my phone with the attatched Kuban Kernal 3.0.15 and am having battery issues. I just recently deleted my facebook widget thinking maybe thats doing it, but it will last about 4 hours before it dies. Im downloading bad ass battery monitor to see if I can further look into whats sucking the battery power.
GO to developer option and click do not keep activities
maybe there something runing on the background you have to look at under battery or in appliication
OK I did that ill see if it changes anything. As of 72% battery left, battery monitor shows 69.8% app usage, and 51.8% is the Kernel. All of the apps listed don't use much under app usage its the kernel that is killing it. Does this mean I need a new Kernel? This cant be normal right? Can I use just any Kernel? Thanks
51% kernel is high, yes. See if other people have the same percentage with that kernel. If not, then maybe try a different kernel. agat's or sleshepic's kernels are also good and built from source. Btw, I wouldn't advise doing the Developer Options setting change to close all activities. That setting isn't meant for ordinary use and severely limits your multitasking abilities. "Closing apps" also has a minimal effect because of the way Linux deals with RAM. It turns out that opening and closing apps takes away more battery than keeping one running in the background.
If your battery isn't good, diagnose why with the following apps:
Betterbatterystats - Download this app and check your "Partial Wakelocks". Basically this checks what apps are waking your phone up when it's sleeping.
CPU Spy - This allows you to easily see how much time your phone has spent in each state. You get really bad battery life if your phone idles on 200 Mhz instead of Deep Sleeping. Your phone should be on Deep Sleep when the screen is off, or else your idle battery drain will be fast.
Other ways to save battery life:
Tweaking system settings
Get SetCPU/Tegrak/Voltage Control/Any other CPU Settings app and undervolt each of your processor states to -50 mV. By stock your phone's states come "overvolted" and you can conserve battery without loosing performance if you slightly tweak them. Don't go too low or your phone may get unstable and crash.
Use those same apps to underclock or set profiles to underclock under certain circumstances
Use those same apps to change your governor. Read up on different governors and how they scale your processor when needed. Here is a link that explains different governors - http://forum.xda-developers.com/showthread.php?t=1369817 . Usually "conservative" and "SmartassV2" and "Lulzactive" are pretty good with battery life. It all depends on how much performance you are willing to give up for low battery life.
Use those same apps to change your I/O scheduler. The scheduler, in simple terms, basically describes in what order apps will run, which will be prioritized, etc. The "SIO" scheduler is probably the best balanced one. "Deadline" I believe saves more battery life but maybe slow you down a little.
Apply tweaks that do it for you
In the general section of our forums, a developer named PhAkEer has posted some tweaks. His "dietpill" battery ones are really good for keeping your phone fast but saving battery life. If you have these tweaks though, they automatically choose a governor and I/O scheduler so manually changing them will only interfere if you decide to do this.
Change simple unneeded settings
Another reminder is that simple things can save you a lot of battery life. Turn off haptic feedback. Take off pulse light notifications (there are reports that these wake up your phone from Deep Sleep and put the processor back into the 200 Mhz state... thus taking away battery life). Turn off 3G when not needed (3G and 4G are huge drainers). Set WiFi to turn off when your screen is off. There is a ton of other stuff you can do.
Well I hope this long post helps you in your quest to find better battery life. Good luck
Tried putting the new agatas kernel on my phone and nothing has changed. CPU Usage shows 200MHz is 79% of sleep while deep sleep is only9. How to I go about dealing with this?
Check your wakelocks with Betterbatterystats. Otherwise just play around with some settings. For me it's usually WiFi that keeps my phone in 200 Mhz. I set WiFi to turn off when the screen is off. Maybe you have an app running that actively requires your phone's processor or something.
partial wavelocks is MAIL SERVICE - at 6.5% 5m 54s count 1953, AudioOut_! is 4.9% count 7 5m 54s, Juice defender 1.6% count 447 2m. So is it my email then? What is Kernel wavelocks?
any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...
I saw a post saying these are stock voltage -- is it correct?
200 MHz = 950 mV
500 MHz = 975 mV
800 MHz = 1075 mV
1000 MHz = 1175 mV
1200 MHz = 1275 mV
1400 MHz = 1275 mV
1504 MHz = 1350 mV
1600 MHz = 1425 mV
1704 MHz = 1475 mV
bhollehday said:
any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...
Click to expand...
Click to collapse
What is your awake time versus you screen on time. If you are having signal problems test out other modems which are in the updater. Make sure you update prl and profile afterwards in about phone. Not having signal/service will kill your battery no matter what because it then tries to search for it constantly. Last week I was somewhere that had no service in my hotel room. For 18 hours in my lab it only drained 10% with about 2 hours of usage, then I went to sleep for 6 hours and it was down another 40%. I turned it on airplane mode to save battery. Hopefully trying a different modem might help. If not I have some suggestions for that too.
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
T.J. Bender said:
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
Click to expand...
Click to collapse
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
P1 Wookie said:
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
Click to expand...
Click to collapse
Thanks for that. I had to restore (luckily I'd done a Nandroid yesterday!) because the system wouldn't boot past the Samsung splash. I've been anti-Juice Defender for a while here, but it seems like a decent chunk of the problem with my battery has been wlan_rx_wake, most likely caused by network traffic. That's what I get for letting my wife share my phone's wifi router instead of leaving her on the house.
Much as I hate to do so, I've put JD Ultimate back on my phone in hopes that its control over wifi and data will prevent those wifi and data wakelocks from happening. Hoping that 500 max with pegasusq (I'd put it back at 600 after restoring) will alleviate things.