Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Markymarc206 said:
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Click to expand...
Click to collapse
I'm not entirely sure, but with your example, doesn't that depend how long you're going 30 or how long your screen is off at a crack? If you turn on your screen for 10 minutes for every 20 it's off, I think it would save your battery more in the long run.
You use more gas in the car analogy as you have to overcome a ton or so of mass driving at 30 mph. Changing clock speeds faces no such resistance, so it won't be the same with the phone.
yes, the acceleration doesn't really affect the drain. the fact you're running at a higher clock speed is the drain. you can adjust your steps and max speed, thus saving a little bit of battery. undervolting can help to, but the cpu usually draws so little power that the savings may go unnoticed.
Related
Anybody notice one performing better than the other with regard to battery life? I have the paid version of SetCPU which I bought for my G1 a while back but I'm not sure I really need it for the CPU throttling on the Vibrant but it does seem to improve battery life and I was wondering if Juice Defender might be better.
JuiceDefender was fabulous for battery life but it did slow down my phone a lot. I ended up uninstalling it. If you want to try toggling your data to save battery, I recommend DCSwitch widget. Works like a charm for data control.
I just started using SetCPU on this phone so I can't say how it affects battery.
Tasker is better then Juice Defender. It does everything JD does and MUCH more stuff.....unlimited possibilities
You should probably understand that lowering the frequency of your processor doesn't save a bit of battery. The only way you can save battery is to lower the voltage which neither of those apps can do so whatever you're seeing as "saving battery" is a placebo effect. When the phone is in sleep mode the CPU is defaulted at 245mhz. Lowering the "Max" frequency does just that; it lowers the maximum frequency the processor is able to use.
bmj1086 said:
You should probably understand that lowering the frequency of your processor doesn't save a bit of battery. The only way you can save battery is to lower the voltage which neither of those apps can do so whatever you're seeing as "saving battery" is a placebo effect. When the phone is in sleep mode the CPU is defaulted at 245mhz. Lowering the "Max" frequency does just that; it lowers the maximum frequency the processor is able to use.
Click to expand...
Click to collapse
It's true that reducing voltage (which we can't do) would be more effective as power consumption at a given clock frequency is proportional to the square of the voltage, but you're wrong to dismiss frequency control as a power saving strategy because at any given voltage, power consumption is proportional to frequency. Hence Intel's "speed step" technology used in notebook CPU's.
Juice Defender and SetCPU are doing more or less the same thing as Intel speed step.
We CAN reduce voltages with the right kernel... Dragon TEST 5 kernel.
^ correct with the voltage control app from the market i believe.
Between setCPU and juice defender..
i say juice defender.
Set CPU is a hassle.
It shuts your phone off sometimes with profiles on, and freezes it etc.
If your phone experiences any of those problems, uninstall setcpu and bam, your phone is normal again.
SetCPU is only good for overclocking, and sometimes sucks at that too.
xriderx66 said:
^ correct with the voltage control app from the market i believe.
Between setCPU and juice defender..
i say juice defender.
Set CPU is a hassle.
It shuts your phone off sometimes with profiles on, and freezes it etc.
If your phone experiences any of those problems, uninstall setcpu and bam, your phone is normal again.
SetCPU is only good for overclocking, and sometimes sucks at that too.
Click to expand...
Click to collapse
Yeah, that's what happened to me with setcpu. Every time the screen turned off, the phone turned off as well.
With juice defender, I lost a lot more battery. About 15% in 3 hrs of standby vs. 3-4% in 3 hrs of standby without any power saving apps.
If people are having good results with both apps, could you please show how you set it up? I may have not set it up right.
burntrat said:
With juice defender, I lost a lot more battery. About 15% in 3 hrs of standby vs. 3-4% in 3 hrs of standby without any power saving apps.
If people are having good results with both apps, could you please show how you set it up? I may have not set it up right.
Click to expand...
Click to collapse
Same here.
I figured that people who got positive results from all the battery-saving apps are the ones that use their phones aggressively and switching between all types of connections (wifi/bluetooth/gps). I use my phone normal, so I'm better off without apps like that.
Yeah, that's what happened to me with setcpu. Every time the screen turned off, the phone turned off as well.
Click to expand...
Click to collapse
If I remembered correctly, it's because you've set the frequencies way too low for your phone to function properly.
Does anyone underclock? I only do it in certain situations. Do you see it as beneficial? Why or why not?
Sent from my Galaxy S2
EDIT: My settings are attached as a screenshot. My device is underclocked 50% of the time.
In my opinion and from personal use, I don't find underclocking to really be beneficial. I never really saw any better battery life. On the same note, I never really found overclocking and undervolting to be extremely beneficial either. It's like the gains aren't worth the time to tweak everything.
Undervolting, yes. Limiting clock speeds, and setting governer to conservative, yes. I say 1ghz is the best spot without losing much performance, and I get 2 days of battery life (sometimes) compared to the one day before... Stock kernel, you aren't going to see much of a difference because you can't undervolt...
I keep my phone at 800max 200min on conservative with a 85% up and 20% down threshold. I don't even see the phone slow down at 800 plus it saves some battery!
I force underclock when I'm in a situation where I KNOW the clock should never ramp up (Screen-off I set to 500) as a "safety measure" to prevent surprises.
I also may force underclock to 800 when running Navigation once my vehicle dock comes in - since we can't crank our charge current up.
Entropy512 said:
I force underclock when I'm in a situation where I KNOW the clock should never ramp up (Screen-off I set to 500) as a "safety measure" to prevent surprises.
I also may force underclock to 800 when running Navigation once my vehicle dock comes in - since we can't crank our charge current up.
Click to expand...
Click to collapse
My screen off is set to this also (200-500, conservative). You can use Tasker to change frequencies for specific apps automatically.
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Hey all,
I've been noticing over the past few times I've been playing GTAIII and MC3 that the internal temp of my phone rises drastically, to a point where I can barely hold one side of my phone without having to let go every few seconds because it is so hot. From where the battery is positioned, I assumed it might be the GPU heating up, but other att gsII users said their batteries were heating up.
So,
1) Is anyone else experiencing these problems
2) If you are, has anything happened to your phone
I'm debating whether to trade it in for a new one, because I'm still under warranty.
Welcome to high performance electronics. If you push the CPU/GPU hard it's gonna heat up. It's like a desktop, if you do something CPU/GPU intensive it'll heat up. It's a simple byproduct of inefficiency.
As to batteries heating up, that could just be because they're close to the CPU/GPU. Batteries will warm up under high current draw as well.
Do you have a case on your phone? Those tend to trap heat in as well.
Sent from my SGH-I777 using Tapatalk
If your phone is overclocked, the processor will be running at the max clock you have set while playing the game, which is higher than what it's supposed to be running at, i.e., the stock clock. Prolonged usage at this higher-than-normal clock will generate excessive heat.
Sent from my SGS II.
Yeah I don't play GTA3 anymore because of this kind of stuff. It doesn't get to the point where I have to literally move my hands because of the heat though. I simply don't like my phone getting even remotely warm. I'm just really anal about stuff like that. I fear that doing it will shorten the life of the device and I love this phone way too much to let that happen.
I'm sure it's designed to run at these higher temps since mine is completely stock with regards to cpu speed and voltage. If I can't play a game due to this, then I simply pass on the game. Same with my computer but I digress...
Download an app to check the temperature. Yes, ideally cooler the better, but the phone is designed to handle a certain amount of heat.
From what the op is describing, that is definitely too hot. Over time the components life can be shortened. But what you'll see first is your battery life going down, even quit working all together.
Underclock the processor. That can help keep the heat down. Even as low as 500mhz can pay many games. 800mhz should be plenty for most high end games.
Sent from my páhhōniē
I'm not overclocked, but yeah, same thing happens with me when I play MC3. I got scaredish since it got a bit too hot, seemed more hot than it was supposed to be.
download the diagnosis app and set it to check your batt temperature, if that gets above 45c I would be worried and think about underclocking/undervolting.
As long as your phone is cool enough to handle, don't worry. There's a lot more to it, but the electronics can take a lot more than most people credit them for. The battery is the most sensitive to temp, but so long as it's not for terribly long periods of time, you shouldn't even notice any additional degradation over the long run.
Sent from my SAMSUNG-SGH-I777 using xda premium
I have the Otterbox, which is probably the absolute worst case for heat efficiency
Kadin said:
Yeah I don't play GTA3 anymore because of this kind of stuff. It doesn't get to the point where I have to literally move my hands because of the heat though. I simply don't like my phone getting even remotely warm. I'm just really anal about stuff like that. I fear that doing it will shorten the life of the device and I love this phone way too much to let that happen.
I'm sure it's designed to run at these higher temps since mine is completely stock with regards to cpu speed and voltage. If I can't play a game due to this, then I simply pass on the game. Same with my computer but I digress...
Click to expand...
Click to collapse
I agree! I baby this phone to every extent and I hate that feeling I get when it gets warm because I just assume the worst. I keep thinking the gpu is going to blow up or some extreme thing like that
What temp ranges are ideal?
gr8hairy1 said:
Download an app to check the temperature. Yes, ideally cooler the better, but the phone is designed to handle a certain amount of heat.
From what the op is describing, that is definitely too hot. Over time the components life can be shortened. But what you'll see first is your battery life going down, even quit working all together.
Underclock the processor. That can help keep the heat down. Even as low as 500mhz can pay many games. 800mhz should be plenty for most high end games.
Sent from my páhhōniē
Click to expand...
Click to collapse
What temp ranges are ideal?
Brodad said:
What temp ranges are ideal?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1372473
Average day to day operating temps are between 30° and 40° celsius.
Sent from my páhhōniē
If anyone's interested, I have pretty much eradicated the heat problem while also boosting battery life and conserving performance. This was done through setCpu: http://forum.xda-developers.com/showthread.php?t=505419
The problem was that apps were just running the processor like crazy on the 1.2 GHz speed setting, and it used a considerable amount of juice that was unnecessary, heating up the battery to a ridiculous amount.
But anyway, here's the profiles/voltage settings I use:
Main Governor: 200 MHz - 1200 MHz on demand
Profiles:
- Charging, 800 max, 200 min, ondemand, priority = 100
- Temp > 44.1 Celsius, 500 max, 200 min, conservative, priority = 100
(this is a conservative temperature, but most place the *dangerous* amount of heat at 50 degrees before battery life starts decreasing, the CPU/GPU components have solder that melts at 70 degrees)
-Screen Off, 500 max, 200 min, conservative, priority = 75
-Battery <25%, 800 max, 200 min, powersave, priority = 75
-In Call, 800 max, 200 min, conservative, priority = 50
Voltages:
(I was able to undervolt by 50-75 mV for each and still remain stable, these are tested btw)
1600 MHz - 1400 mV
1400 MHz - 1225 mV
1200 MHz - 1200 mV
1000 MHz - 1100 mV
800 MHz - 1025 mV
500 MHz - 950 mV
200 MHz - 875 mV
and that's it! It's working great, I don't have the heat issues I used to, now I can play graphically demanding games and the temp doesn't rise past ~42 degrees, pretty solid improvement. I also get 24-28 hours of battery life with 2-2.5 hours of screen on time per day.
No need to worry about this. That's nowaday phones designed to be. Just normal heat.
amtrakcn said:
No need to worry about this. That's nowaday phones designed to be. Just normal heat.
Click to expand...
Click to collapse
I agree that's how they're 'supposed' to be. But things mess up. AMD processors are designed to handle heat, but they are still known for getting too hot and damaging the graphics chip. Better safe than sorry.
Sent from my páhhōniē
Agreed. theory and actuality are two incredibly different concepts
I see alot of folks asking about over clocked kernels best combo and what not. Also they are asking if a over clocked kernel is out and has good battery life.
No over clocked kernel will ever bring excellent battery life lol. Truth is the more you up the cpu the more juice it will need. The stock kernel was set within standard speeds due to keeping things smooth and keep the battery life decent also keeping the heat down on the cpu... If you mess with things you will get faster speeds at the cost of you battery life and heat.
I am not saying not to use them you just can't expect a over clocked kernel to give you better battery life.. Also turning your brightness down will help save battery... Using WiFI will also help if your wireless signal isn't strong enough in your area. Don't run a antivirus program on your phone either lol this will also suck your battery down.. These are linux based phones.
Thought I would help out some of the folks that are asking about things like this..
Just so everyone knows, the power consumption of your phone uses a standard formula:
power = voltage^² * frequency
So for every bit of voltage you go up, power consumption drastically rises. As you raise the frequency then power consumption rises, but you have to double your frequency to double your power drain.
EniGmA1987 said:
Just so everyone knows, the power consumption of your phone uses a standard formula:
power = voltage^² * frequency
So for every bit of voltage you go up, power consumption drastically rises. As you raise the frequency then power consumption rises, but you have to double your frequency to double your power drain.
Click to expand...
Click to collapse
Nice Most kernels do get things thumped up with that route on it. More push means more juice.
Sent from my reaping 3D
I have the same problem!