Related
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
set to 1.13 ghz
then screen off to minimum 245mhz
josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?
Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.
im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents
Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.
I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.
Give us some feedback
I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.
Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.
liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One
shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.
Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.
A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.
please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings
so overclocking makes things faster.. really? who would have thunk. and you just found this out?
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?
well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **
If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.
No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.
zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100
is there any kernel that can overclock with 4.3?
Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:
simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?
Check the Development sections.
This thread makes my head hurt.
Hi,
I saw BravoMotolora's article about CPU binning, and I thought that it would be great if we compare CPU bin and voltages.
It will be great to know the relationship between voltage and PVS number.
Please follow this procedure
1. Install a custom kernel that lets you do undervolt, e.g. franco.Kernel
2. Do what BravoMotolora said
3. Undervolt your N5 by 25MV
4. Run Antutu
Then, you might see your N5 rebooting or giving you a Antutu score.
If you get the score, go and try the procedure again
I got to -50MV with PVS1 N5.
Please post your results(undervolt that you did and your N5's PVS) here!
Can you not do this?
Do not do what? I mean most of guys here will do undervolt to save battery anyway so won't it be good to share some intel?
Sent from my Nexus 5 using XDA Premium HD app
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
you do realize that many custom kernels set their voltages different than default/stock, and differ among themselves? for example, if you go -50mV less on using franco kernel, and go -50mV less using trinity kernel, it means nothing because their voltages differ to begin with. i mean you cant really compare each others voltages that way. you would need to write your voltages in real numbers, and cpu speed steps.
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
johndrmr said:
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agreed. i personally do better with underclocking, than with undervolting.
simms22 said:
agreed. i personally do better with underclocking, than with undervolting.
Click to expand...
Click to collapse
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
This phone does pretty well arlt idle I think. Can't imagine you would see much gain from UV.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
klin1344 said:
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
Click to expand...
Click to collapse
I have a PVS 2 and can undervotl -75mV accross the board and -87.5mV at 300Mhz.
So 2,26Ghz I can run at 0.975 Volt.
CM11 with Bricked Kernel.
Together with Sync off, Google hotword off and optimized automatic brightness I get constantly 5 - 5,5 hours screen on time with websurfing, mail and music stream.
Marcel
menting said:
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
Click to expand...
Click to collapse
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
rajendra82 said:
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
Click to expand...
Click to collapse
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
I agree with you here. 1036 mhz is a great CPU speed for running the device and most apps. Most games UC the CPU for better battery temp like in PPSSPP. Less temperature throttle and more stable frames per second.
Benchmarks are a difference story though but who cares about those. UC is lag free, and buttery smooth so why not?
Sent from my Nexus 5 using Tapatalk
zz_marcello said:
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
Click to expand...
Click to collapse
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
simms22 said:
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
Click to expand...
Click to collapse
You can do everything you are already doing, but also undervolt, and your battery life will increase, without affecting your performance. Your performance will be different than my performance (because I don't underclock), however imperceptible as it may be. So undervolting is still better than not undervolting, even for you.
Using EX kernel 3.27, underclocked to 1.5Ghz, undervolted to "700 min" and using "stock" thermal throttling setting. Rock solid and it barely even gets warm now. Responsiveness and performance is only a touch worse than stock; the only places I really notice any performance reduction is in intensive games and app install times. Battery life is massively improved.
Although this might seem as a question. It really isnt.
What kind of battery life do you get on the First? Screenshots would be nice, but what is like the max time and min time you got and what kind of setting do you use, voltage, clock speed, usage etc.
Also has anyone been using the MSM-DCVS (dynamic clock and voltage scaling) CPU Governer? And if yes then have you gotten better battery life? I will do a test tomorrow and see how it goes.
My best stats.
Well before i got into cpu governors, by default the phone uses on-demand and i could max out 14 hours with variable usage. screen on maybe 50% of the time the phone was on and minimal gaming. texting. I dont have data so that didnt take any battery (i hear 4g and 3g take away lots of juice, is that true?).
Okay. So just did a quick test with msm-dcvs.
Basically for 5 minutes I tested each governed doing the same stuff.
Msm-dcvs utilizes deep sleep ALOT more. Almost 8 times more than on demand. And doesn't really use anything in between. So it goes from deep sleep to minimum 300mhz to get it going and then jumps to the max of 1.4ghz and if the screen is on it uses 700mhz.
So using deep sleep it saves batter.
On demand on the other hand tends to use 300mhz instead of deep sleep. It also jumps around a lot between all the various clock speeds using just about anything it can. So i guess on demand will get worse battery life but I will report my findings in a few hours seeing bow battery life goes with dcvs.
Sent from my HTC first using XDA Premium 4 mobile app
Just a quick update. On demand is crap. Performance is really good and dcvs is performance just more intelligent
Sent from my HTC first using XDA Premium 4 mobile app
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
abrahammmmmmm_ said:
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
Click to expand...
Click to collapse
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What app do you use for this? All the ones I've tried don't make any custom settings stick
abrahammmmmmm_ said:
What app do you use for this? All the ones I've tried don't make any custom settings stick
Click to expand...
Click to collapse
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
G00fY2 said:
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
Click to expand...
Click to collapse
Wow that's great battery life.
I'm yet to test dcvs in my first and see how long that lasts me. I have Wi-Fi on all day. So I can get up to 14 hours max.
Sent from my HTC first using XDA Premium 4 mobile app
abrahammmmmmm_ said:
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
Click to expand...
Click to collapse
No I have yet to figure out io bit tinkering with voltage isn't a good idea since the battery is specifically set to a voltage the phone needs.
Sent from my HTC first using XDA Premium 4 mobile app
Okay I have some new findings. Idk about the custom kernel...bit with stock you only get 3 I/o schedulers. Noop, deadline, and cfq. Noop is first come first serve. Deadline reorders the task sequence and does what it thinks should come first...good for like gaming. And cfq. Which evenly distributes the power amongst all tasks. If you are using cfq make sure you kill unused tasks all the time. If you use a lot of things on your phone and multitask a lot use deadline. Noop is pointless unless you don't use your phone for anything. And cfq is just an alternative to deadline. So I/o won help much.
Then in CPU master. Go to advanced. And press "disable perflock". It will explain what it does. Hit set on boot. And reset you clock settings. Now we shall see what we get.
Sent from my HTC first using XDA Premium 4 mobile app
Okay guys. I used deadline to see if that would change anything. With the same dcvs setting with deadline I got 15% batter down in 2 hours. That's pretty good. That's 7.5% an hour.
And this is with screen on and wifi on about 70% of the time.
Sent from my HTC first using XDA Premium 4 mobile app
Okay this is my final say on how to get the most out of your battery life.
There are two set ups
1. Lag free/ smooth set up
Min 384mhz, Max 1080mhz
Governer: Performance
i/o Scheduler: Deadline
-This set up will save battery why? Because 1. You don not need your max 1.4 ghz to keep the phone running lag free, and in performance mode, the phone is LOCKED into 1.4ghz until you dim the screen and it goes into deep sleep. no inbetween. So clocking down will help save EVEN MORE battery. So unlike dcvs you will not have lag when you turn your screen on. It will jump from zero to 1ghz in a few milliseconds.
2. Inteligent
Min: 432mhz, Max 1.4ghz (default max. Dont over clock)
Governer: MSM-DCVS
i/o Scheduler: CFQ
-This set up will save battery, i go down about 1% every 6-20 minutes depending on usage. (6 being max usage and 20 meaning iddle). Once you turn the screen on your device will lag slightly and then will work just fine. This set up is good for those people who dont ALWAYS need max performance. Example: Reading an email doesnt require your phone to be locked at max frequency all the time so it will down clock the device. It simply takes time for it to rev the engine.
3. On Demand
Well this is simply absoule minimum to absolute maximum with NOOP as the i/o. This is the ultimate ondemand set up as it will do what you are currently doing first then do the rest while constantly changing clock speed.
Also...btw changing clock speed takes battery that is why performance saves batter not uses it. Its either deep sleep or max and thats it.
I will add screenshots to this soon once im done with all my tests.
Battery life today on msm-dcvs
I should be at 30% right now bit pretty good battery tight now
Sent from my HTC first using XDA Premium 4 mobile app
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Hulo_ said:
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Click to expand...
Click to collapse
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
russian392 said:
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
Click to expand...
Click to collapse
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
abrahammmmmmm_ said:
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
Click to expand...
Click to collapse
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I should add that the optimized battery life for LTE is only true tho for new snapdragon CPU's including Apple's processors as well. I'm not aware of tegra or any exynos at the moment.
Can anyone explain to me what is better?
I know that underclocking reduces cpu frequency, which means lower temperatures and also better battery, but performance is worse, so it takes longer to complete tasks...but if it takes longer to complete tasks, it means it will also have screen on for a longer time right?so it saves power from the cpu, but keeping the screen on for that extra time also means it will consume extra power right?
About undervolting, is it better to undervolt or to underclock when it comes to battery life?i know that with undervolting there is less heat produced because of the reduced voltages. From what i have read (i dont know if it is correct) the power consumption is given by this equation: P = f*c*(V^2) where f is frequency, c is capacitance and v is voltage. It makes sense that reducing voltage means less heat, but if i reduce CPU frequency it also produces less heat because it reduces power. Most of the time i read that underclock is better for battery because it uses less power, but like i said earlier, it takes longer to complete tasks and in result i have to keep the screen on for a longer time.
About hotplugging, i have seen some users with good battery life screenshots, and mentioning that they disabled hotplugging, because they said that turning cores on and off also wastes energy. So is it better to hotplug or not?
would really like to get some answers because i know nothing about this..I also know that i could test each setting and and see which is better, but i dont use my phone the same way everyday so its kind of hard to determine...
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
RASTAVIPER said:
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
Click to expand...
Click to collapse
nice to have some feedback from someone that tested=p. what about hotplugging? Today i disabled hotplugging and had always 4 cores on and it does not seem to be wasting more battery than with hotplugging enabled
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
Also lot of discussion about Uv here
http://forum.xda-developers.com/showthread.php?t=2137034
Unleashed from Onda v957m on TDT
n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
migueldbr said:
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
Click to expand...
Click to collapse
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
C4SCA said:
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
Click to expand...
Click to collapse
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
migueldbr said:
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
Click to expand...
Click to collapse
Different things but on stock kernel touch boost is implemented on the hotplug and not the governor.
Any difference btw 4 cores online or hotplugging must minor, and have draw backs on heat wich affects the battery capacity.
Eventhough u can say that hotplugging may drain an amount of battery to plug and unplug cores, i would say its minor.
Talk to @simms22 , he is the "trinity kernel guy", four cores online is a must for him
sent from my diabetic Nexus 4 (too many KitKats).
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
no matter what you do , its still going to be a mediocre battery life , best leave it as it is because the way nexus 4 is designed its still going to be getting annoyingly warm on games
Well, from my own experience undervolting definetly reduced heat and made the battery last longer. Don't expect 2 hours more sot, though. Its most notably while the device is idle.
Sent from my Nexus 4 using XDA Free mobile app
nice man
very helpful...
Help pls..
Can any1 help me undervolting Unleashed kernel.. providing tips or the link ll be vry helpfull..