I am sitting here, testing my battery drain in "nothing going on" mode. Phone is on but asleep, WIFI/GPS/3G all turned off. I'm actually having trouble getting the battery to lose charge - wish we always had THAT problem. Anyway, it's not of much use in this fashion, but I did want to establish a baseline.
My specific question is about processor modes. I have a kernel (I assume, not the ROM) with an associated voltage control app. In that app, I can manage my clock speeds. The question is: would I theoretically get better battery life by limiting my clock to lower speeds? And if no one has done this test, or knows the answer in theory, can we discuss the best way to provide a constant processor drain on the phone (although one that isn't tied to speed like I assume many of the tests would be) so that I can make the observations in a reasonable time span - a sixty minute test that drains 20-30% of the battery would seem to be about what I'm looking for. As I said above, with nothing going on, I haven't drained a single % off the battery in 90 minutes.
I do a lot of backpacking and hiking, and the ability to use the phone and its GPS over a period of 5 days without carrying 5 spare batteries would be a real godsend.
There is a thread on here somewhere that lowering the clock speed actually increases battery consumption under load, as the processor has to work longer to do a task.
nickm50 said:
There is a thread on here somewhere that lowering the clock speed actually increases battery consumption under load, as the processor has to work longer to do a task.
Click to expand...
Click to collapse
+1
Don't lower too much for any reason. For e.g., if u have a overclocked kernel at 1280, u could scale it down to 1000, but don't go beyond that. Values over 800 are used very less unless there is a task demanding that much CPU.
Plus, by math, a task that takes 5 seconds at 1280 speed would take 8-9 seconds at 600-800 levels. So I wouldn't recommend reducing clock speed to such levels, even in standby mode.
I haven't found the thread about underclocking increasing battery drain, but it seems most people believe that canceling overclocking, and also undervolting, will extend battery life. I'll fool around with that for a while.
Soccer_Dad said:
I haven't found the thread about underclocking increasing battery drain, but it seems most people believe that canceling overclocking, and also undervolting, will extend battery life. I'll fool around with that for a while.
Click to expand...
Click to collapse
Yes. Cancelling overclocking means setting at 1000 from 1200 and 1280 or other speeds over 1000.
Under-volt to some extent, but not too much, esp at higher speeds.
diablo009 said:
Under-volt to some extent, but not too much, esp at higher speeds.
Click to expand...
Click to collapse
Yea, in theory, if you under-volt too much, it's going to stress the device to meet the action requirements for the required action. Right now, everything on the phone is calibrated to run on around 3.7v or just a little bit lower, so if a certain process doesn't acquire enough voltage or suck enough amperage from the battery, you'll get one of the common results: 1)Random shutdowns or 2)Battery drain.
vunuts said:
Yea, in theory, if you under-volt too much, it's going to stress the device to meet the action requirements for the required action. Right now, everything on the phone is calibrated to run on around 3.7v or just a little bit lower, so if a certain process doesn't acquire enough voltage or suck enough amperage from the battery, you'll get one of the common results: 1)Random shutdowns or 2)Battery drain.
Click to expand...
Click to collapse
It would lead to stress on CPU too 'cos it would be like putting regular gas and expecting peak hp out of a sports car. I can notice a difference in pickup and power between regular and premium gas in my car when I need quick pickup. For normal use it performs good, but u never know when u need that optimum power. Same with our phone CPU too.
diablo009 said:
Like putting regular gas and expecting peak hp out of a sports car.
Click to expand...
Click to collapse
Great analogy..... But..... You can just disable the knock sensor in the car and bypass the OBDII codes that pop up Yes, I am a gearhead lol. But in a sense, this is exactly what we are doing to our phones, trying to run with the minimum and expect the maximum.
And that brings me to this quick fix: Undervolt as much as possible, install a Nitrous Express kit for those times when you're in need of optimal power
I just don't mess with the OC and UV personally. I'm running everything based off of jk4 with Setiron's kernel with the standard lag-fix that's pre-applied with it, and I got rid of any... hmmm, I don't want to say "useless" apps, but I guess unnecessary or unproductive for me. If I show off my phone, people see how quick it is and like the customization of my launcher and how cool it looks, that's about the flashiest thing on my phone, but once you open the app drawer, it's all business.
Related
I'm a former G1 owner, current Hero owner and soon to be Evo owner. I just have a question. I visit all Android forums on here but this is my first N1 post. I just want to know what undervolting the phone does and if that's N1 specific or anything snapdragon. I assume it saves battery life but that doesn't underclock the processor at all?
I remember reading something about undervolting a while back in this forum and I found it quite interesting. Some are saying that undervolting the cpu doesn't actually save battery on the device, as the cpu will just up the ampere to get the amount of power it needs.
Don't take my word for it though.
SBS_ said:
I remember reading something about undervolting a while back in this forum and I found it quite interesting. Some are saying that undervolting the cpu doesn't actually save battery on the device, as the cpu will just up the ampere to get the amount of power it needs.
Don't take my word for it though.
Click to expand...
Click to collapse
Well that's what my first impression was. I mean, a CPU needs more energy to run faster. So if you lower the voltage I would assume it would lower the power which would either lower the speed or make it increase energy usage to run faster. Anyone else have definite info?
Hey all,
My phone is rooted. I'm wondering how Overclocking might effect battery life. Better? Worse?
Also, what is a solid speed to OC on the Captivate?
It will be worse, but if you do UV it will last a bit longer...
Battery life will go down, but its by such a small amount, you wont even notice it(depending on how much you OC it)
and stable OC values will be different for every phone since all processors are not made equal. For example, my max stable overclock is at 1.2ghz, but my friend was stable at 1.4 with undervolting by 100.
You really just need to play around with it and find what works for you.
If you really want a solid stable number, im pretty sure every captivate I've seen can go up to atleast 1.2 ghz.
Sent from my Captivate using XDA App
Yuna said:
It will be worse, but if you do UV it will last a bit longer...
Click to expand...
Click to collapse
That is very untrue. I read an article (for the life of me can't find it) that overclocking is actually better for battery life. I have in fact had better results on my LG Optimus V with overclocking at 806mHz (highest stable clock setting) than with 600mHz (standard). LeslieAnn (Harmonia dev) linked to the aforementioned article in one of her posts. If I find the link I will post it.
I've only OC a couple of times but 1200Mhz should be stable for the majority of phones out there. The most I've got out of my phone was 1440Mhz on MIUI with Glitch kernel, while my friend was able to hit 1600Mhz with same rom and kernel. It took me quite a bit to figure out what voltages for what steps etc to get it to work well so if you do not feel like tinkering with it for a long while I wouldn't try to push your OC too high.
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
prbassplayer said:
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
Click to expand...
Click to collapse
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
TRusselo said:
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
Click to expand...
Click to collapse
I have my phone and nook's clocking speed set at the same for min/max settings. I play a mean game of RUA and AirAttack HD. I've in fact timed my battery life on standard clock settings and my overclocking. While overclocked, my nook lasted 10 minutes longer than at standard speeds (while playing AirAttack HD, which has intense 3D graphics). And you might suggest I undervolted, but I never touch that stuff. My volting stays where it is.
Hi i have an idea for better battery durability and reduce the heat emitted.i want to change the processor's clock speed.
I think that 1-1.2 ghz is enough for good performance but i don't have rooted my phone yet so could anyone try to change the clock speed and wrote what about the battery drain and heat emitted by cpu?
Thanks!
ebreo said:
Hi i have an idea for better battery durability and reduce the heat emitted.i want to change the processor's clock speed.
I think that 1-1.2 ghz is enough for good performance but i don't have rooted my phone yet so could anyone try to change the clock speed and wrote what about the battery drain and heat emitted by cpu?
Thanks!
Click to expand...
Click to collapse
I'm so glad that you had that idea, because nobody else has EVER thought about doing that
How about you search the forum and look at one of the many, many threads where this sort of thing is discussed instead of asking us to write the same thing over and over again :banghead:
i didn't find anything about that if you can pls share link with those threads or whatever like this
check this out - http://forum.xda-developers.com/showthread.php?t=1854008
Here you got my experience - http://forum.xda-developers.com/showpost.php?p=35517636&postcount=30
ok thanks @danie.wro i have read whole topic and i guess does it this app useful?
i want use all 4 cores but clocking down theirs cores to 1gzh or 1.2ghz in term of battery saving and heat will be change anything for sure?
another question is regular that overnight my phone lost about 15-20% of battery doing nothing?
Try to use CPU-Tuner. I use that and it's very useful.
thanks you too, but this app is for rooted phone instead gearbox runs on no rooted phone too i tried quadrant benchmark and i had lower score, let we see if this change something in term of battery drain and heat emitted xD
ok i have tried and i have positive feelings the battery withstand more time about 15-20% with clock speed set on 1ghz and 4 cores, and power saver with 1 core on 1ghz, but the heat emitted by battery hasn't changed much...
I have a question does NFC take a lot of power?
ebreo said:
ok i have tried and i have positive feelings the battery withstand more time about 15-20% with clock speed set on 1ghz and 4 cores, and power saver with 1 core on 1ghz, but the heat emitted by battery hasn't changed much...
I have a question does NFC take a lot of power?
Click to expand...
Click to collapse
I'm guessing by the facts that it has a lower signal range than Bluetooth it uses less power than Bluetooth but still is a considerably big battery consumer.
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.
Anyone using SetCPU to throttle the device and get tolerable battery life?
I wish. Not on Verizon!
Bump!!
I just started using trickster mod and set max frequency to about 2.0GHz. The battery life has increased with no lag. On Lollipop.
obtained said:
I just started using trickster mod and set max frequency to about 2.0GHz. The battery life has increased with no lag. On Lollipop.
Click to expand...
Click to collapse
What did you have to do to get trickster working? Just download it? It works straight from the market? H3lp!
zgroten said:
What did you have to do to get trickster working? Just download it? It works straight from the market? H3lp!
Click to expand...
Click to collapse
Yeah just download it. You will have to download a busybox installer if you don't have busybox installed as well.
Awesome thanks. What mods and settings have you found useful?
Anyone has had success tweaking new Moto X with SetCPU?
martinezma99 said:
Anyone has had success tweaking new Moto X with SetCPU?
Click to expand...
Click to collapse
SetCPU caused major lag for me personally.. I switched to trickstermod and all seems fine so far
I'm using No Frills, working great across 422MHz - 1GHz ( hardcore testing )
I have never noticed any battery improvement from underclocking, and correct me if I'm wrong but I thought the general consensus (among those actually informed) was that it doesn't actually help because it causes the processor to take longer to complete tasks, canceling out any actual gains.
_MetalHead_ said:
I have never noticed any battery improvement from underclocking, and correct me if I'm wrong but I thought the general consensus (among those actually informed) was that it doesn't actually help because it causes the processor to take longer to complete tasks, canceling out any actual gains.
Click to expand...
Click to collapse
After testing for a day almost, I'll say that's crap.. I'm running this guy comfortably at 0.8GHz with ultra small lags, see the battery for yourself. I used to get 4-4.5 hours of max screen on running it untampered and now this damn battery won't die!
ManiacShri said:
After testing for a day almost, I'll say that's crap.. I'm running this guy comfortably at 0.8GHz with ultra small lags, see the battery for yourself. I used to get 4-4.5 hours of max screen on running it untampered and now this damn battery won't die!
Click to expand...
Click to collapse
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
_MetalHead_ said:
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
Click to expand...
Click to collapse
The reason there's no specific apps you see is because I did what you do in a typical battery test, gaming a bit, reading ,browsing and all the others... So the individual. consumption is well b below 5%.. But yeah even without underclocking i have gotten even 5.5hours which is not bad at all
_MetalHead_ said:
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
Click to expand...
Click to collapse
You can be sceptical because you should be, the cpu throttles already and only uses max speed when needed. With light usage like me (WhatsApp, telegram, 20m phone calls and some mails a day) I get 4 days on 4g and wifi. (I turn my phone on flight mode during the night) I've also disabled moto application (voice is useless in Dutch/not working) The biggest energy consumer is the screen so change your wallpaper to a dark one and close unused background apps (moto voice, google now, virus scanner and all other useless apps. If you use all the social media out there on your phone, no battery capacity is sufficient. I could limit my max cpu speed because the cpu governor probably throttles to max even when launching undemanding apps, but I would probably won't notice any savings.