[Q] Underclocking Query - Galaxy Note II Q&A, Help & Troubleshooting

How much can the phone be underclocked while maintaining the stability of the system?
What would happen if i set Max freq to 600 Mhz?
What is the best thing to do to save up the very last bit of juice in the battery for emergency situations where i would only need the phone and message facility? Besides switching off Bt,wifi,sync.
Im asking because i was wondering if underclocking "too much" saves a substantial amount of battery when my battery is quite low and I am "hours away" from a charging port!
And is there a way to change the carrier name on the notification drop down to whatever we want.
Sorry if i sound noobish or if a similar query has been asked before
Thnx.

Underclocking the CPU dramatically isn't going to gain you a great deal in the way of extra battery life because:
1. Unless you are heavily taxing the CPU (complex 3d games etc), the biggest drains on the battery are the screen and the radio.
2. If the screen is off, the phone will drop the CPU frequency right down anyway.
The best way to get extended battery life is simply to carry spare batteries!
Regards,
Dave
Sent from my GT-N7100 using Tapatalk 2

I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium

bushako said:
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thats quite informative. Thanx!

Related

SetCPU saving power potential?

Heya,
I've heard of this SetCPU program, and figured it has some solid potential of saving battery power.
My question is - does it work? I've read several post claiming that SetCPU doesn't work on HTC phones.
If it does - will using the "Mix \ Max frequency" mode will save battery during stand by and normal usage, or just slow down the phone?
Using Rooted Desire, LeeDroid 2.2d.
Its primary use is to overclock the CPU, its secondary use is to create profiles and reduce the clock or change the governor. This will improve battery life slightly but also decrease responsiveness, depending on how far you go.
You'll need root if you want to use it.
To really increase battery life you have to use a custom ROM with an undervolted kernel.
So you're saying that the saving in battery life is insignificant considering the slowdown in performance?
yes, you use LeeDroid which is undervolted, thus perfect conditions.
It also uses a custom governor 'Smartass' which gives you best performance while using it and limits the max. clock while sleeping. That's the most common method to increase battery life with SetCPU while maintaining performance. So no, you don't need SetCPU, LeeDroid handles everything perfectly already.
However, the Desire has a very powerful CPU, compared with other Smartphones. So you can use SetCPU to limit the clock to maybe 700MHz or 800MHz. This will increase the battery life but also reduce the processing power. If you don't play games, don't do a lot of simultaneous things or browsing huge websites, don't use heavy loaded homescreens, it's possible that you don't notice the reduced processing power.
Thanks again
I guess there is no damage to the SnapDragon if I lower clock speeds a bit...
But, if I want to do some overclocking - how far is it safe to go?
When I OC'ed my Q6600 CPU I used the TheremalRight Extreme 120 with two Slip Stream fans to cool it off.. So, will heat damage be a constant threat to an overclocked Desire?
I currently live in Israel, and it's hot as hell even on stock speeds
CoreOxide said:
Thanks again
I guess there is no damage to the SnapDragon if I lower clock speeds a bit...
But, if I want to do some overclocking - how far is it safe to go?
When I OC'ed my Q6600 CPU I used the TheremalRight Extreme 120 with two Slip Stream fans to cool it off.. So, will heat damage be a constant threat to an overclocked Desire?
I currently live in Israel, and it's hot as hell even on stock speeds
Click to expand...
Click to collapse
I for one has chosen to disable the default powersave in Auraxt sense, and then using SetCPU to control it, i get a day of power easily, and still goes to bed wit 50% power, that is with stock clocks on normal usage, but with minimum power (245) on screen off
Re overclocking:
To reach high clock speeds you also increase the voltage on your PC, else you can't increase the frequency that drastically.
Because you can't improve the cooling on the desire you have to keep stock voltages but also can't overclock that much.
The overclocking methods on the desire keep the voltage at stock values or even lower (defrost rom).
I don't know the voltage values for LeeDroid.
I it shouldn't get warmer. In the worst case it will crash and reboot until you reduce the clock speed.
Sent from my HTC Desire using XDA App

[Q] what exactly is undervolting

i have used the search and not found any solid info
what are the benefits of it if any
I haven't heard of people undervolting their fone, although i haven't looked to much.
This would mean though reducing the power that the CPU gets. I would imagine this increases battery life among other things.
Your right about what it is, but almost every custom rom/ kernel is undervolted in development section.
Sent from my HTC Desire using XDA App
Undervolting means, the CPU (or hardware in the phone) gets lower voltages, thus saving more battery & not loosing performance.
Undervolting is a process which reduces the excess "voltage" given to the CPU using a software. This is widely used as a cooling solution and in my opinion more effective than any other cooling solution available (thermal paste, cooling pad, etc) at NO cost. Undervolting will NOT compromise performance at all. Underclocking and Overclocking (clock speeds) is whats responsible in regards to performance. Benchmarks will also prove that performance remains the same.
Click to expand...
Click to collapse
Not excess voltage but fully, manufacturer guaranteed, stable Core voltage to lower guesswork voltages which may or may not work and may or may not cause data loss/corruption.
------------------------------
- Sent via HTC Desire -
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
Very sensible answer..Thanks
koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
How would one go about under volting .i have tried everything suggested to me and nothing really seems to make a difference
Sent from my HTC Desire using XDA App
Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.
TheGhost1233 said:
Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.
Click to expand...
Click to collapse
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %. And its only taken2 mins to write
Sent from my HTC Desire using XDA App
adz63 said:
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
So in short you havent tried any kernel with undervolting at all!
Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).
At the moment I have the havs kernel that comes with oxygen 2.0 rc6. I have posted another topic about is the kendal good for battery life etc and no1 has told that another kendal would make anything better
Sent from my HTC Desire using XDA App
TheGhost1233 said:
Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).
Click to expand...
Click to collapse
@TheGhost1233, how exactly does one decide which kernel suits us best..
Eg: I see two undervolted kernels (I think) at 875 and 925 mV. I have no idea how to decide. Trial and error?
Froyo Kernel [email protected] min
Froyo Kernel [email protected] min
@droidzone Yes trial and error. The mentioned voltage is the lowest the cpu will get at 245MHz. Not all devices are stable with 875mV (you will know if your phone freezes up) so then you move up to the 925mV min. Other than the voltage there is no difference between 875mV or 925mV.
With the HAVS kernels it can take a while before you notice the freezes cause the voltage is dynamic, so be careful if you need your phone as a alarm clock.

Setcpu Profiles

Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
kazemagic said:
Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
Click to expand...
Click to collapse
i i think that ondemand is the best for daily using... i'm using cm10 rom and i have some music problem so i'm using interactive and it's ok. if you don't use games or heavy apps, you can underclock it to 1ghz or even less and put on powersave.. but you have to try and find the best for you
My setup is a little complicated. I use the ondemand governor, then for the profiles I make it use powersave and under 760mhz between 1am and 8:30am which seems to really help during the night. Also set it to use 760mhz max when the screen is off.
When charging or above 40% battery I allow it to run full speed, but only when the screen is on, therefore helping charge times. On charge or above 80% I set the governor to performance.
In call I set the clock to max 1000mhz and conservative to try and allow calls on low-battery to work properly without lag but also without killing the battery.
I have a couple of other options set for very low battery ( < 12% ) too, but those are only to extend the battery if it's dying.
I wouldn't say all this is necessary... but I need my phone to keep working at all times as I use it for receiving business calls.
It's just a matter of playing around really... depends what you use the phone for. For the most part tell it to use lower clock speeds when you don't need them so much (when phone is off, during the night, during call etc) but you will really notice the speed difference if it's underclocked while you use it, so I tend to allow it to use full whack when screen is on, unless the battery is low.
I also set up profiles to make things like Bloons TD4 run in performance mode and min of 1000mhz, to keep them smooth . Drains the battery though!
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
kazemagic said:
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
Click to expand...
Click to collapse
If you mean decreasing the voltage on the CPU, no I haven't. From my experience in desktop PCs however, if the CPU voltage is too low it can lead to hardware issues and instability.
If something needs a certain amount of power, and you give it less, it will either try and draw more amps which increases heat and can fry components, or won't work properly. You could probably "under-volt" the CPU at the same time as reducing the clock speed however, but your performance will suffer. When the processor is set to be ondemand it underclocks itself when not in use anyway
The biggest battery drain is screen and radios, concentrate on using them less. Underclocking the CPU will make the phone last longer when in use, but usability will suffer and turn your super fast smart phone into a sluggish one. I only make mine stay underclocked when the screen is off, during a call, or on low battery. During general use I let it do its thing .
UV(Under volt) is actually not to bad. Don't ever set those values at boot, else when they are too low, it will cause BOOTLOOPS. It just reduces the amount of power allowed for the cpu to use, thus it won't use more than required. You can't really ask a person for his/her uv values, as no 2 chips are created equal.
People stating that they UC(underclock) their device is not quite right. We don't have much control over our cpu's to be honest. If you run tegra stats whilst using you're phone, you'll see what I mean. It will sometimes(happens quite often) just bump up to higher frequencies to which you UC them. Also as soon as the screen is locked and unlocked the max cpu frequency set by the governor will just return(for example: say stock is 1500mhz, and you set it to 1400mhz, it will return to 1500mhz after an unlock). Ondemand is very very good for battery and performance. But remember you have to tweak those values individually in order to optain the best possible performace for the given task you want. Whether it is for battery or performance.
It's actually also a lot better to just tweak those values as to TRY and uc. Uv will stick, UC not!
Here is a small example as to battery saving and performance values for ondemand governor:
sampling rate:---------60 000 ----- 30 000
up threshold:--------------95 ----- 60
sampling down factor:-------2 ----- 8
powersave bios: ------------3 ----- 0
ignore nice load:------------0 ----- 0
io is busy:------------------0 ----- 0

[Q] Has anyone ever underclocked One X?

So I tried to underclock my One X to around 640 MHz and it was running VERY smoothly and stable with only 2 cores active. I was using the ViperX 2.2.1 ROM and the Kernel was the no OC NCX 0.99a. The battery life wasn't bad, but has anyone tried underclocking to 1 GHz or lower? If so, how is the battery life and what kernel and ROM did you use?
With SetCPU you can change the max. CPU, but why should you? When the phone doesn't need much processor power, it just scales down by itself.
So, it already has the best underclocker there is.
Mayby you could try undervolting to save even more battery, but that means the CPU can be somewhat less steady.
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
ricopoetra said:
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
Click to expand...
Click to collapse
underclocking means the CPU runs slower so should use less battery but slower CPU speeds also means to takes longer to preform tasks which could use more battery, check on google most places say its not worth it as that battery saved is tiny and not worth the drop in CPU performance.
undervolting however lowers the voltage that CPU uses while working this does save power and also lowers heat (less voltage less heat) but if you lower it to much then the CPU becomes unstable due to lack of power and well crashes and restarts the phone in most cases.
to get the best out of undervolting you need to lock the max CPU speed to each step (CPU speed, 300mhz, 600mhz and so on) and slower the voltage and then run a bench mark (like antutu) and see if its stable, if it is you lower the voltage again and repeat until it crashes at which point you have found the lowest voltage that the clock speed can handle so you jump up a voltage then more on to the next speed.
it takes along time but that would get you the best undervolt your phone and hardware could handle.
or you can just use the global to lower the voltage for every speed, this is much faster and much less time consuming but you don't get the most out of it.
for this you basically drop the voltage then use your phone for different things; browsing, games, benchmark and see if it crashes if not lower again till it does then go back up a step.
thanks for explaining. I'm getting some of the points that I missed Awhile ago. I guess I'm going to try the longer way of doing it.
Sent from my White HOX JB PA 2.10

[Q] If CPU Sleeper is present, does Underclocking save battery

Like I stated. This may seem like an overasked question, but the parameters of the question are a little bit different than normal.
Considering how some ROMs come with CPU sleeper, would underclocking save battery?
What I mean by this is, since you are underclocking, I assume that other cores turn on more to compensate, so would that consume more power?
Or would the underclocking benefits outweigh the other cores turning on?
Thanks
Underclocking slows down the cpu/gpu which keeps them awake longer thus using more battery. Some different governors would probably make the most difference but not sure how much better battery life this phone could get.
Sent from my SGH-T889 using xda app-developers app

Categories

Resources