Related
I've seen a few different posts in some of the kernel threads debating whether SetCPU is helping or hurting battery life. SO, I'm just kind of curious to see what results are on a larger scale? Based on your own experiences, do you have SetCPU installed and if so, does it help or hurt battery life generally? Also, if you do have it installed, do you use profiles? What are the most beneficial settings to use?
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
5. It's been discussed ad nauseam.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
THATTON said:
SetCPU is not intended for battery life? Go to the Market and look at the description. If I posted this in the wrong section I apoligize. But, I think you are mistaken with your comment about SetCPU not being intended to increase battery life or increase performance...
Click to expand...
Click to collapse
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Thread moved as it does not pertain to N1 development.
I see very little gains from setcpu but I use it because I purchased it from the market and why not use it if you bought it right?
This method does not apply to drug addiction LOL
-Charlie
bri3d said:
SetCPU only sets clock speeds and governors already in the kernel. If you just install SetCPU and adjust no settings your battery life will not change. Thus, "does SetCPU help battery life?" is utterly and completely meaningless.
Discussion of different governors and clock speeds has occurred (and is still occurring) ad nauseum and is really more suited for the General forum.
Click to expand...
Click to collapse
lol Why would you download an application, not use it, and expect results?
If you throttle your CPU down you WILL get better battery life. My phone is set to never go over 600mhz and I get bettter life with it than if I turn off setcpu altogether.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Hey djmcnz thanks for the indept look at this app but more importantly thanks for showing respect to those of us who are just learning. We all have to learn information at some point and there are people that forget that at one point some one had to tell them.
Thank you for the clarification on that! Djmcnz-that was exactly what I was looking for in terms of an answer. I really appreciate you taking the time out to explain everything for me and anyone else that may have been curious.
charnsingh_online said:
1. Not in right section
2. SetCPU not intended for battery life
3. It only adjusts CPU clockspeed
4. This thread is mostly meaningless
Click to expand...
Click to collapse
Don't know why you're so pissed off by a thread...
1. Not a very big issue. We have mods here to take care of this.
2. I don't know if SetCPU affects battery life or not but similar thing on a PSP device does increase the battery life. I have tried it on my PSP and setting the clock speed to the lowest acceptable level (depending upon what you're doing) does help maximizing the battery life.
3. You're absolutely right here.
4. Don't know what to say man.. but being a little humble doesn't hurt....
I never meant to be rude. I always get pissed off when people post in wrong sections Seriously. If people post in right section it just frees up moderator time. And about CPU nexus CPU has same voltage for many frequencies like 998,960 have same voltage. Going so down doesn't mostly benefit. So setcpu is only good for overclocking IMO. Display uses most of the power along with radio n CPU is one of those in middle of usage maybe 3rd or 4th. So underclocking will give a big battery boost is just a placebo. Atmost 10 minutes more is what underclocking can provide. N its not worth sacrificing the performance. Go for something underpowered if u want to underclock IMO. So setcpu serves more purpose of power than battery
I use it for the cool widget and standby/idle profile. B-)
you know what?youre allright.i follow your threads and you explain things well for someone like me learning all this ****.i got no time for keyboard commandos.thanks for the explanation.
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
djmcnz said:
You have a lot of knowledge, this is obvious but you're unnecessarily harsh (mean).
It's boring but's it's a legitimate question because people still make inaccurate conclusions about CPU and battery life. Those of us with some knowledge can really help those that are trying to understand.
#2 above is correct. But the question remains, does a forced lower clock speed ceiling have an effect on battery life? It could do, of course it could, but without a baseline and a control environment it's impossible to prove either way. I suspect the OP is simply looking for subjective opinions.
And on this basis I offer:
The CPU only has a material effect on battery drain when it's being utilised.
When the Nexus CPU is not required to work it idles using the lowest power possible
The radio (network) interface is the second most demanding element of on your battery over time (next to the display). Although the CPU peak demand is higher than the radio.
SetCPU does not impact radio battery use.
SetCPU can not have a positive effect on battery usage if it's using more power to run it's clock cycles.
SetCPU can force the processor to use less power (wind down speed).
Slowing the processor means some tasks will take longer to perform.
If those tasks require a high-drain elements (display, radio, WiFi or BT for example) then it's counter-productive (battery wise) to slow them down.
However, because CPU power consumption does not have a liner relationship to clock speed, then some tasks that don't use high-drain elements will consume less power to complete.
So, whilst it's unlikely that your battery life will benefit from the use of SetCPU alone there is a chance that it will.
SetCPU is a fantastic app designed for overclocking, the profiles are niche facilities that may offer battery benefit to a narrow range of users.
Click to expand...
Click to collapse
HUH English Please
Kidding
mikey1022 said:
huh english please :d
kidding
Click to expand...
Click to collapse
34567890
Personaly done many tests and the result was:
Test config: WiFi tethering all the way, screen 100% Playing video all the time 2G only
4:10 @ 245Mhz hard
3:30 @ 998Mhz hard
No use actually - using N1 on 245Mhz is impossible - too sluggish.
SetCpu is ussefull:
1) If u have OC kernel to set OC mode for games like Asphalt
2)For letting android vary frequence ondemand instead of 998 all the time
3)For downclocking while in sleep mode (why use full power when u dont use it?)
4)For using Failsafe profile, to prevent battery and hardware damage.
That's all.
No use trying saving battery setting profiles like 100% - 998, 50% - 576, 20% - 499. This is useless.
On UV kernels the same thing +\-30 minutes battery life. And UV kernels themselfs dont give segnificant battery life increase, only lags and unstability ti system.
Dont believe me try yourself - Create yourself some actions fo testing and repeat them 2 time (Min cpu and Max cpu) on any kernel. Results will be very close.
SeriousX said:
3)For downclocking while in sleep mode (why use full power when u dont use it?)
Click to expand...
Click to collapse
The CPU steps down to it's minimum speed by itself. It never uses more juice than it needs to.
As far as i know, it is always at maximum, but maybe im wrong and you are right - then theres even less sence in this app.
Can an informed person contrast these 2 roms for me please
Sent from my SCH-I500 using XDA App
I am not informed but I can tell you dl09 broke my GPS. It takes 10 minutes to get a sporadic lock. I had to revert to dj05 in order to fix it.
I'm curious too. So far, I haven't really seen anything, so I haven't upgraded.
I've been running it for a week now. Looks like the GPS doesn't lock as fast anymore compared with DJ05. It also currently has me on the wrong side of the freeway by my office so it's not that pinpoint accurate either. I think the WiFi is faster & stronger on DL09 than DJ05. It's probably not worth making the jump to DL09 but I'm not going to revert to DJ05.
Dj 05 works better...everything works on it. Dl 09 not so much...
Radio DL09 gps did not lock as fast wifi about the same on each.
Move back to dj05 working great for me.
Sent from my SCH-I500 using XDA App
For me, I noticed tremendous increase of battery life with DL09
hkseo100 said:
For me, I noticed tremendous increase of battery life with DL09
Click to expand...
Click to collapse
You are correct. After 8 hours I'm at 72% battery remaining. I think it's because of the under volted kernel.
voghan said:
You are correct. After 8 hours I'm at 72% battery remaining. I think it's because of the under volted kernel.
Click to expand...
Click to collapse
I am starting to not believe that undervolted kernels actually do not save any battery.
I've noticed this pattern with all of the kernels that claim undervolting.
But if what you're saying is true, you can run Adrynalyne's kernel with DJ05 and get better battery life.
I think that's what I'm running. I'm also running a Gingerbread Theme which displays everything black when possible thus reducing battery consumption from the screen, but my phone is still sucking for battery life.
2cents.
RacerXFD said:
I am starting to not believe that undervolted kernels actually do not save any battery.
Click to expand...
Click to collapse
Do you mean you don't believe they do save battery?
I had a UV kernel on my phone for a little while, and there WERE noticeable gains in battery life. It wasn't anything crazy, but running the same programs and the same activity over an 8-9 hour span (sitting at work), I had more battery left at the end of the day with a UV kernel than I did running a normal one.
I didn't really pay much attention to it until I forgot to charge my phone on my way to practice one night. Phone would usually be *****ing to be charged, but it was doing good.
I have been running a lot of different UV kernels over the past few weeks, and there is a point where you go from the UV helping your battery and it hurting battery life. From my testing, as the size of the UV increases, the processor will reach a point where it can keep up at a given clock speed and will then move up as needed. It will get to a point where it's staying at 400/800 clock speeds more often than the 100/200 clock speeds, and the effect is negated.
I'm sure this point is going to be different on all phones, but for my phone is somewhere around a -100mV drop from stock voltages. It will help your battery when sleeping since your phone isn't doing anything, it will use even less power, but as soon as it tries to do something again, the battery life will tank. I also used PowerTutor to look at the usage trend for the CPU, and the system was using more power on average for some larger mV drops. I also started to notice lag as the drops increased, likely due to the processor being unable to keep up.
At the moment, I'm trying to see how a big drop on just the lowest clock speed, and then less of a drop on 200-1000 does. I also made a few adjustments to the scaling factors to help reduce lag at 100/200mhz and keep it in the lowest possible clock speed when running. So far, it seems somewhat promising, though I've only been running my current test for a few hours.
Voltage has nothing to do with how much work the processor can do in a clock cycle. Higher voltages allow faster clock speeds, but the voltage itself doesn't matter if the circuit is synchronized (i.e. has a clock). It's just more likely that you won't be able to run at a given clock speed with a lower voltage, but that will just cause glitches and instability, not less work being done and needing to run at a higher speed.
I realize that it shouldn't matter, but it did. I'm guessing that the lower voltage preventing the CPU from running at the actual clock speed, causing it to high the usage threshold sooner. I could barely keep the phone at 100mhz after restarting with just SetCPU running in the foreground. I didn't look into what was happening much because the battery drain was pretty bad, so I went on to a new test.
Also DL09 is officially supported by vzw....
jv
Hello everyone.
I used to be very disappointed on the battery performance of our stock roms. Our customs roms solved many problems but this battery problem stayed for some people like me.! So i started experimenting on various categories and now i finally have a sufficient battery backup of around 40 hours that keeps me and my android going!!
So here is how to save your damn precious battery!!
It has worked for some people i know and i hope it do work for you too!!
I am using fugumod ultra kernal and it gives me absolutely no lags at all + a super duper battery!!
-Battery Calibration [ROOT]
Whenever you flash any new custom rom, you should always calibrate your battery! Here is an app that does that!!
<Appbrain Link>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Flash Fugumod ultra kernel (Strictly for Fugumod Ultra) )<link>
Flash this kernel and use set minimum frequency for 780 hz and Maximum frequency to 1366 hz.
Set the governor to Performance
CONFUSED Yes this thing sounds crazy!! But you can always try. I have written this after experiencing it myself!!
-For G3Mod Kernels & Other Versions Of fugumod [OverClocked]
Follow these steps:
Install Setcpu/ Any other cpu controll app
Set Max value to the highest frequency. Minimum between 300-400.
Now using the profiles option set POWERSAVE governor to those times when you wont be using your phone much (ex:while sleeping).
Then for other times use ONDEMAND governor.
While charging profile is set then make sure that governor is set as PERFORMANCE.
You may also try other governors. Haven't tried... (suggestions welcome)
-Install Auto Memory Manager app[ROOT]
Auto memory app automatically kills apps that runs in background based on the profile u set!! After installing the app, use the aggressive profile and the lower the Hidden Application slider to in between 30-40 mb, so that your important background apps are not killed unless the ram is very low..!!
<Appbrain Link>
----------------Alternative For Auto Memory Manager-------------------------
- Supercharger script
Supercharger script is also a great alternative.. You need to run the script from your rooted rom using terminal emulator. See this <link>
This script is included in most of the recent custom roms. See their respective version changelog for info.
Now your phone will be lag free..!! It has been tested and working!! My android phone runs the way it should!!
Lets jump to battery problems
-Battery Calibration has to be done.!!
-After that I recommend you to use your resources a bit cleverly!! Data connection takes a lot of battery for me.! Now fine you need internet when you are on the move. But you don't need it while sleeping do you??
android apps requiring data connection to retrieve data keep on retrieving it even while you sleep but you only see that data after waking up and getting out of our bed. So you should shut off internet while sleeping!!
-Now display.
display consumes battery!! best is to keep display to 10 when its dark!! And around 40 during the day!
I keep it to zero all the time and use keep toggling it to max only when i need it using dimmer!!
<appbrain link>
-3d Gallery. (thanks rai_tushar)
Consumes a lot of battery!! Use quickpic. Better and faster alternative
<appbrain link>
More tips by rudolf895
*Not using set CPU for short time profiles.(not using different frequency while phone is on standby)
*Exiting apps using the back key, home key put the apps to background task.
*using 2g when needed..
*use wifi for bigger than 10mb download as it woudl be fast n easy.
*least brightness
So i think that should be it.!!
One last trick.
If you use tasker or any other automation app try this.
(With respect to tasker)
Make a new context>state>plugged in
Then make a new task for the context>app>load app>Fast reboot <link>
So whenever you will plug in your phone the app be will run automatically and then your phone will be free from any lags.
Data Connection uses lots of battery and will result in battery drain. Most of the time many data is retrieved when you wont be viewing it/using it. But it will result in wastage of data. So u need to make sure you use your data connection wisely
i would highly recommend you all to use tasker app for automation of your android phone. Automatically toggle display, mobile data etc depending upon various contexts (application, time, location). Read THIS thread for more information on tasker.
Conclusion
If you want a rock solid battery and an android phone that should be proud of its speed, and you are not getting any solution, go ahead and try the above..!!
Battery setting may or may not suit you!! This was just a sharing of my experiences which i had en-route to getting a lag-free/rock-battery.
Happy Androiding!!
Thank you for it, but your "this" does not link to any thread. However, I'm assuming you mean for it to be the link that the "here" for the 'ultimate android app' links to. Might want to change that. Thanks for the tips, though.
Mohit12 said:
Thank you for it, but your "this" does not link to any thread. However, I'm assuming you mean for it to be the link that the "here" for the 'ultimate android app' links to. Might want to change that. Thanks for the tips, though.
Click to expand...
Click to collapse
Thanks a lot for that!! Fixed the link!!
Yes its the ultimate app!!
Idk why keep higher minimum CPU frequency your battery should have drained faster even when your phone would be idle..
For me this worked :
*Not using set CPU for short time profiles.(not using different frequency while phone is on standby)
*Exiting apps using the back key, home key put the apps to background task.
*using 2g when needed..
*use wifi for bigger than 10mb download as it woudl be fast n easy.
*least brightness
Hope this helps some one. ;-)
Tapatalked from my super smooth, ultra fast samsung galaxy s2.
neo1691 said:
-Flash Fugumod ultra kernal (this worked for me, havent tried G3mod kernals)<link>
Flash this kernal and use set minimum frequency for 780 hz and Maximum frequency to 1366 hz.
Set the governor to Performance
Click to expand...
Click to collapse
this doesn't make sense, if you set governor to performance your phone will be running at 1366 mhz at all times regardless of minimum frequency and that will murder your battery. Make a profile for screen off and set it to 83 or166min and 222 or 333 max and ondemand governor, that will save you some battery. When you use the phone set the max frequency to 667 or 800 with conservative or ondemand. Use high freq only when needed - for playing heavy games
rudolf895 said:
Idk why keep higher minimum CPU frequency your battery should have drained faster even when your phone would be idle..
For me this worked :
*Not using set CPU for short time profiles.(not using different frequency while phone is on standby)
*Exiting apps using the back key, home key put the apps to background task.
*using 2g when needed..
*use wifi for bigger than 10mb download as it woudl be fast n easy.
*least brightness
Hope this helps some one. ;-)
Tapatalked from my super smooth, ultra fast samsung galaxy s2.
Click to expand...
Click to collapse
this doesn't make sense, if you set governor to performance your phone will be running at 1366 mhz at all times regardless of minimum frequency and that will murder your battery. Make a profile for screen off and set it to 83 or166min and 222 or 333 max and ondemand governor, that will save you some battery. When you use the phone set the max frequency to 667 or 800 with conservative or ondemand. Use high freq only when needed - for playing heavy games
Click to expand...
Click to collapse
I was excepting this post from someone.. Yes you might say why keep governor to performance with 1366 max.. well thats how we tackle lag!!!
@rudolf!
Surprisingly battery drain is very less for me (and some others too) with these tweaks.. otherwise why would i share them!!
1 more solution:-gallery 3d uses more battery
u can use quickpic as a replacement
rai_tushar said:
1 more solution:-gallery 3d uses more battery
u can use quickpic as a replacement
Click to expand...
Click to collapse
exactly.. Thank you. will update the op as soon as I find a laptop., I always use quick pic but never really considered it a battery saver..
Disabling SNS is also a good way to save battery.
Not applying the RAM optimization script provided in the Dev section will also save battery 'cus I have faced increased battery drain with it.
And does reducing the voltage save battery? If so.. can you please provide some info about it..??
Enviado desde mi Galaxy 3
thanks for the info as i was just about to install the ram optimization tool but considering that it sucks more battery, i wont do it
danveer said:
thanks for the info as i was just about to install the ram optimization tool but considering that it sucks more battery, i wont do it
Click to expand...
Click to collapse
Try the above . Of that still don't help you, then you are can try ram optimization
"-Flash Fugumod ultra kernal (this worked for me, havent tried G3mod kernals)<link>
Flash this kernal and use set minimum frequency for 780 hz and Maximum frequency to 1366 hz.
Set the governor to Performance"
with this, the battery will last a full day maximum (with normal-low usage)!
kyrillos13 said:
"-Flash Fugumod ultra kernal (this worked for me, havent tried G3mod kernals)<link>
Flash this kernal and use set minimum frequency for 780 hz and Maximum frequency to 1366 hz.
Set the governor to Performance"
with this, the battery will last a full day maximum (with normal-low usage)!
Click to expand...
Click to collapse
agreed.. theoretically it should last not more than one day!! but seriously i have tried that and my phone practically lasts for more than 35 hours..
And that's y i am sharing the info!!
EDIT: setcpu v 2.1.3
ron_gangte said:
Disabling SNS is also a good way to save battery.
Not applying the RAM optimization script provided in the Dev section will also save battery 'cus I have faced increased battery drain with it.
And does reducing the voltage save battery? If so.. can you please provide some info about it..??
Enviado desde mi Galaxy 3
Click to expand...
Click to collapse
Reducing the voltage to the CPU may cause problems and will not save any battery. You can think of it like a simple circuit, with the CPU effective being a "resistor". so you have just a battery, voltage regulator, and CPU, as you reduce voltage, amperage will increase (and battery drain will actually increase!!!) Amperage is what drains your battery, not voltage.
My recommendations (I have tertiary electrical engineer qualifications to back me up)
- Stick with the stock voltages for the different frequencies you use.
- To save battery, turn off wifi & bluetooth when you are not using them.
- Install APNDroid, to easily switch 3G/EDGE data off when not needed (still allows you to receive MMS messages when data is off, and has a widget)
- Set your screen to the minimum brightness that you can (but so that the display is still bright enough to use)
- Turn of "Power Saving" in display settings (actually uses more power than it saves 9 times out of 10)
- Use task manager, or a ram management tool to kill apps that don't need to be running in the background, and always use the back button to go out of apps, the home button will leave the app running in the background (sucking battery and slowing the phone down)
- If using a CPU management tool set minimum to 83MHz (or lowest your phone is happy with, or that you are happy with to kill lag), set maximum to whatever you like (that phone can handle) and use a governor like "on demand". Set up profiles to lower maximum frequency when screen is off, or temp is high (higher temperatures will result in faster discharge off battery)
I do all of this, and I can get up to 3 days use without charging (depending on usage)
Things that will drain your battery the most (highest power usage):
- Wifi
- Bluetooth
- 3G/EDGE
- Screen
- Phone calls
nrk_2k said:
Reducing the voltage to the CPU may cause problems and will not save any battery. You can think of it like a simple circuit, with the CPU effective being a "resistor". so you have just a battery, voltage regulator, and CPU, as you reduce voltage, amperage will increase (and battery drain will actually increase!!!) Amperage is what drains your battery, not voltage.
Click to expand...
Click to collapse
sry, but this is completely wrong.
if it was true what you said increasing the voltage would save power...
decreasing the voltage DOES save power, but unless the CPU isn't running at maximum load the whole time you won't see a big difference.
the frequency of the CPU raises the consumed wattage linearly while voltage goes into the calculation by square. so decreasing the voltage is the best option to lower the consumed power of the CPU as the speed isn't affected. problem is of course that the CPU won't run below a certain limit. the CPU in my G3 is running 800MHz @ 1.125V which is 75mV below stock (667MHz).
the amperage does not change while undervolting.
sharukins said:
sry, but this is completely wrong.
if it was true what you said increasing the voltage would save power...
decreasing the voltage DOES save power, but unless the CPU isn't running at maximum load the whole time you won't see a big difference.
the frequency of the CPU raises the consumed wattage linearly while voltage goes into the calculation by square. so decreasing the voltage is the best option to lower the consumed power of the CPU as the speed isn't affected. problem is of course that the CPU won't run below a certain limit. the CPU in my G3 is running 800MHz @ 1.125V which is 75mV below stock (667MHz).
the amperage does not change while undervolting.
Click to expand...
Click to collapse
First off, I never said anything about saving power, as power is the resulting work of voltage vs. amps, I was talking about battery drain, not power (they are totally different things). The voltage of a battery will not change greatly until it is nearly empty (if it did, it would be pointless rating a battery to a certain voltage), where as the amperage will lower as the battery gets drained. The amount of time a battery lasts is determined by its amperage, not voltage (hence why a 2100mAh battery will last longer, doing the same amount of work as an 1800mAh battery). So if what you claim (amperage not changing while undervolting) were true, then you would see NO change in battery drain due to undervolting. Voltage NEVER drains a battery, it's the amount of amps being drawn that drain the battery. P=IV is the power equation for a closed DC circuit. If we assume P is a constant (which it has to be, to be getting the same output from a CPU) then when you lower V, I must therefore increase. and Likewise, if you raise V, I will decrease.
nrk_2k said:
First off, I never said anything about saving power, as power is the resulting work of voltage vs. amps, I was talking about battery drain, not power (they are totally different things). The voltage of a battery will not change greatly until it is nearly empty (if it did, it would be pointless rating a battery to a certain voltage), where as the amperage will lower as the battery gets drained. The amount of time a battery lasts is determined by its amperage, not voltage (hence why a 2100mAh battery will last longer, doing the same amount of work as an 1800mAh battery). So if what you claim (amperage not changing while undervolting) were true, then you would see NO change in battery drain due to undervolting. Voltage NEVER drains a battery, it's the amount of amps being drawn that drain the battery. P=IV is the power equation for a closed DC circuit. If we assume P is a constant (which it has to be, to be getting the same output from a CPU) then when you lower V, I must therefore increase. and Likewise, if you raise V, I will decrease.
Click to expand...
Click to collapse
well i am having just perfect battery without undervoltage..!! :
but ya definitely learned many new things from the above discussions
nrk_2k said:
First off, I never said anything about saving power, as power is the resulting work of voltage vs. amps, I was talking about battery drain, not power (they are totally different things). The voltage of a battery will not change greatly until it is nearly empty (if it did, it would be pointless rating a battery to a certain voltage), where as the amperage will lower as the battery gets drained. The amount of time a battery lasts is determined by its amperage, not voltage (hence why a 2100mAh battery will last longer, doing the same amount of work as an 1800mAh battery). So if what you claim (amperage not changing while undervolting) were true, then you would see NO change in battery drain due to undervolting. Voltage NEVER drains a battery, it's the amount of amps being drawn that drain the battery. P=IV is the power equation for a closed DC circuit. If we assume P is a constant (which it has to be, to be getting the same output from a CPU) then when you lower V, I must therefore increase. and Likewise, if you raise V, I will decrease.
Click to expand...
Click to collapse
I didn't want to start a discussion about this...
the wattage isn't constant as you calculate it.
calculation power is not equal to electrical power.
voltage itself of course does not drain battery, but what drains battery is wattage, and wattage is reduced due to lower voltage.
the problem is that the unit mAh isn't really the capacity of the battery. the right unit would be Wh or mWh.
so you have to multiply the mAh with the voltage of the batter to get the real capacity.
so decreasing voltage in fact does save you some battery life, but as I said, you wouldn't notice it unless the CPU is under full load the whole time as in smartphones biggest power consumption comes from display and other parts (at least with the slow CPU in the G3).
sharukins said:
I didn't want to start a discussion about this...
the wattage isn't constant as you calculate it.
calculation power is not equal to electrical power.
voltage itself of course does not drain battery, but what drains battery is wattage, and wattage is reduced due to lower voltage.
the problem is that the unit mAh isn't really the capacity of the battery. the right unit would be Wh or mWh.
so you have to multiply the mAh with the voltage of the batter to get the real capacity.
so decreasing voltage in fact does save you some battery life, but as I said, you wouldn't notice it unless the CPU is under full load the whole time as in smartphones biggest power consumption comes from display and other parts (at least with the slow CPU in the G3).
Click to expand...
Click to collapse
now thats what i call some serious battery saver
sharukins said:
I didn't want to start a discussion about this...
the wattage isn't constant as you calculate it.
calculation power is not equal to electrical power.
voltage itself of course does not drain battery, but what drains battery is wattage, and wattage is reduced due to lower voltage.
the problem is that the unit mAh isn't really the capacity of the battery. the right unit would be Wh or mWh.
so you have to multiply the mAh with the voltage of the batter to get the real capacity.
so decreasing voltage in fact does save you some battery life, but as I said, you wouldn't notice it unless the CPU is under full load the whole time as in smartphones biggest power consumption comes from display and other parts (at least with the slow CPU in the G3).
Click to expand...
Click to collapse
Would have to disagree about a true measure of battery capacity being the Wh, or mWh, as wattage depends on load, and since you never run a battery with 0 load, you cannot represent its capacity using Wh or mWh. I have studied batteries intimately at university level, and know exactly how & why they work. the mAh (Ah) is the industry wide accepted unit for battery capacity, as no matter what the load it is always constant. I am happy to agree that wattage is not always constant for a set frequency on a CPU (as it is possible to over-voltage for that frequency), but for processors such as those which are used in our phones, you very rarely find any substantial over-voltage as due to modern manufacturing techniques there is a much tighter range of voltage acceptance for the core. Hence why most people get only a minute (completely stable) undervoltage. And anyone who would actually gain from undervoltage, would be able to tell that their CPU is using excess energy as ALL this energy would be dispersed as heat. Any extra wattage drawn over what is actually required by the components inside the CPU will be converted to heat as it is not required by the components to run. So unless you see excess heat from your CPU, undervolting will only achieve degraded performance, or CPU stalls. And it is at this point that it will drain the battery more, as there is a minimum wattage that a set frequency requires, if you drop the voltage below what it should be, the amperage will increase to mantain the minimum wattage required (or the CPU will stall and the phone will freeze/switch off). The only real world point to undervolting a CPU is for cooling purposes, the energy savings from doing so are minuscule, to none, and can to a point end up consuming more battery. You would save far more battery by lowering your screen brightness by a few percent.
Hi there many of you have thought about battery saving apps.
Do they really work?
Are there some apps that instead of saving battery just drain your battery even more?
Do you know any methods that really save battery?
Just post your oppinions about this subject.
nikeradsn said:
Hi there many of you have thought about battery saving apps.
Do they really work?
Are there some apps that instead of saving battery just drain your battery even more?
Do you know any methods that really save battery?
Just post your oppinions about this subject.
Click to expand...
Click to collapse
Battery saver apps are useless. just turn of data, sync,WiFi, Bluetooth when not in use. decrease screen brightness and screen timeout to 30 seconds. Use 245-806 with ondemand goveror for better battery.
mittalmailbox said:
Battery saver apps are useless. just turn of data, sync,WiFi, Bluetooth when not in use. decrease screen brightness and screen timeout to 30 seconds. Use 245-806 with ondemand goveror for better battery.
Click to expand...
Click to collapse
I've read many people saying that using the ondemand governor wouldnt save that much battery because of the continuous search for cpu activity, actually i'm using performance at 1024 and i also have another profile with 806 performance aswell.
I have to test it better in order to see which governor saves more battery.
I think a good set may useful
nikeradsn said:
I've read many people saying that using the ondemand governor wouldnt save that much battery because of the continuous search for cpu activity, actually i'm using performance at 1024 and i also have another profile with 806 performance aswell.
I have to test it better in order to see which governor saves more battery.
Click to expand...
Click to collapse
I used to use 806 on demand, 1024 ondemand and 1200 ondemand... now I'm using 1024 performance, and I dont see any battery difference.. damn thing still drains.
The battery lasts 4/5 days on idle, what more do you want? It's par for the course.
why do you need the phone to stay on idle? for that you could buy a 10$ one =S
nikeradsn said:
why do you need the phone to stay on idle? for that you could buy a 10$ one =S
Click to expand...
Click to collapse
Because it's an indicator of battery performance and proves there's nothing wrong with battery life on Aurora, despite what many believe. Having ~1 day of battery life with heavy usage and 4-5 days (or even more) on idle is on par with the battery specs.
faekplastik3s said:
Because it's an indicator of battery performance and proves there's nothing wrong with battery life on Aurora, despite what many believe. Having ~1 day of battery life with heavy usage and 4-5 days (or even more) on idle is on par with the battery specs.
Click to expand...
Click to collapse
Actually we all know that the battery life in aurora its not full optimized. what i mean is what can we do in order to get the best performance without having to spend so much battery life. maybe its not possible but who knows
Fact: ICS produces more traffic than GB. A lot of apps (like browser) use more memory, so background processes die more quickly. You cannot except to get the same kind of battery performance out of an ICS rom and that's the end of it. This has nothing to do with Aurora.
When I dont need to use the phone I put the governor in powersave with a low Mhz and the battery is more safe with little use.
Phone become a little more slow but work.
When I really need to use the phone I change the governor to Smartessv2
hy there,
im on latest sokp rom on my g2 (d802)
i want to get more juice from my battery, so I setup my core setings at 1036 mhz max and minimum 300 mhz.
wil this provide me a lot off battery in real life and will it also reduce heat ? even if i watch hd movie or play graphical games
In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power
drivenby said:
In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power
Click to expand...
Click to collapse
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.
abati said:
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.
Click to expand...
Click to collapse
you also can try custom governors
Hey there, you may be suffering a placebo effect, it can give you a little extra juice, but in my opinion you get most of your battery with these 4:
1. Reduce timeout to 15sec.
2. Adjust screen brightness to be as low as possible (lux helps with this)
3. Eliminate vibrations of any kind (haptic feedback, notications that make your phone vibrate ex. whatsapp) and so on...
4. Data (Use Wifi if possible, 2g when you are not using your phone and airplane mode in some cases extend your battery for a lot too)
Don't expect to get more than 30 min of extra use changing your kernel configurations. ALTHOUGH if you are a heavy user (let us say, in this case, a heavy gamer) there are some kernel configurations you should check.
Also remember, if a task takes you 30min but only consumes 1 % per 30 min compared to doing the exact same task in 30seconds consuming the same 1% which one is worth it?
Phones hardware is way above the software we have available at this time, underclocking and undervolting is an option and you won't feel the difference but, as I've stated before, those are not the main issues of the battery drain.
I hope I've helped you out!