Root + OverclockWidget = Insane Battery Life 40+ Hours
I have root and Overclock Widget. I have the CPU scale down to the 200 mhz range when screen off and 998 when screen on. Below is a screen shot after 21 hours off the charger at %49. This puts the phone at almost 2 days before a charge is needed.
This is not a root thread. Please do not ask for help rooting and lets keep it on topic!
Hmmm, this seems very interesting and obviously has merit. I will keep watching and learning about this CPU clocking stuff, and maybe explore it one day but for now I'm content with my battery (lasts at least a full day).
I hadnt considered rooting until reading this, but now I am looking at rooting before the week is up. What are the disadvantages to rooting this EVO? Its my first android phone, but I had read a few things about rooting problems with 2.1, etc. Things that wouldnt work right. And other than this, what are some of the great things that will happen after rooting?
Silly question, does it consume battery to make the cpu change speed.
My root is toast, says so in my sig
Of course it uses battery to change freq. You use battery every second your phone is on. The question is how much and really changing the frequency isn't using any more battery than idle.
The Following 2 Users Say Thank You to nick325i For This Useful Post:
downloaded, installed, set up. Phone is off to get a full 100% charge. IF this works...im getting you ALLLL the prostitutes and turkey sandwiches you could ever want lol.
downloaded, installed, set up. Phone is off to get a full 100% charge. IF this works...im getting you ALLLL the prostitutes and turkey sandwiches you could ever want lol.
Hey I forget where to find the info in your screen shot. Whats it under to see % of battery life and temp.
Quote:
Originally Posted by nick325i
I have root and Overclock Widget. I have the CPU scale down to the 200 mhz range when screen off and 998 when screen on. Below is a screen shot after 21 hours off the charger at %49. This puts the phone at almost 2 days before a charge is needed.
Go into advanced settings and change it to the hero style widget, makes it more sense UI looking..
Thanks, that does look a bit better, but was wondering if a widget is really needed to achieve this. Kinda want it to be done behind the scenes, without any knowledge, ya know?
How come the lin pack test from full 1GHz and 128Mhz show the same score. I'm pretty sure this doesn't work. The phone doesn't even feel sluggish at 128Mhz. Too bad cause this is a great idea. I think people are caught in the placebo effect sometimes
How come the lin pack test from full 1GHz and 128Mhz show the same score. I'm pretty sure this doesn't work. The phone doesn't even feel sluggish at 128Mhz. Too bad cause this is a great idea. I think people are caught in the placebo effect sometimes
How come the lin pack test from full 1GHz and 128Mhz show the same score. I'm pretty sure this doesn't work. The phone doesn't even feel sluggish at 128Mhz. Too bad cause this is a great idea. I think people are caught in the placebo effect sometimes
The method here only scales the processor down when the screen turns off.
The Overclock widget scales the processor automatically when the screen is on for usage. When you tell me you can see the widget showing 128 at the same time your running linpack and the screen is off. We'll have something to go on.
I don't have wi-fi off, or GPS off or removed my friendstream like all the other battery gimmick threads. This is working, not a placebo.
Last edited by nick325i; June 11th, 2010 at 03:37 PM.
The Following 2 Users Say Thank You to nick325i For This Useful Post:
i bet this is bs... if lin pack gets the same score then this isnt actually changing the clock rate plus i've gotten these results without root or underclocking
+1 - you'd think Google could have achieved this internally, no?
CPU scaling can lead to sluggishness from the user POV, which then leads to a poor user experience. Not good for how Android is viewed. It is in their best interest to have it running at the speed that consumers purchased.
How come the lin pack test from full 1GHz and 128Mhz show the same score. I'm pretty sure this doesn't work. The phone doesn't even feel sluggish at 128Mhz. Too bad cause this is a great idea. I think people are caught in the placebo effect sometimes
Did you change the screen on freq to 128Mhz and then run the test? If you're relying on the "screen off freq" while the test is running, it isn't a good comparison.
The last three posters, excluding myself, are missing the point.
The CPU scaling is only relative when the screen is off.
No where did I mention you will get better battery while surfing the web or streaming youtube. This is strictly an idle battery savery because none of us have the screen on all the time.
Last edited by nick325i; June 11th, 2010 at 03:37 PM.
The Following 3 Users Say Thank You to nick325i For This Useful Post:
The last three posters, exclusing myself, are missing the point.
The CPU scaling is only relative when the screen is off.
Yes, I agree, some folks missed this, but I caught it.
I get Google won't do this, but couldn't Google do this for phone sleep only like we are discussing here? I don't get why Google couldn't slow it down just for sleep mode.
ps. I still want to hear what folks say about linpack testing WHILE the phone is ASLEEP.
Google shouldn't because it's not up to them to scale the processor. The business model is simple, let the developers develop. Maybe I can see it as an option, but what if you want to crunch numbers or run a webserver or render a movie (crazy I know) on your phone. If the proc got scaled down this would hurt those apps in sleep. It's not a huge popular feature to scale the proc, so I don't see it implemented in the OS, but it's a great idea to have an app for it
nick325i - hmmmm, well the options are pretty clear to me. It says it can scale when it's awake and asleep which is why i ran the test. A processor doesn't run at a lower mhz when it's idle then magically jumps up when needed. It's either running or not running. I'm not trying to poke fun here, but I don't think we are in agreement that it works. I guess if you could explain why the linpack test shouldn't work i would understand it, but as I see the program it's pretty clear that the CPU awake can be changed (it's just not changing IMO)
Google shouldn't because it's not up to them to scale the processor.
I vehemently disagree. You say its up to the developer, well Google developed the OS, so they too are developers. Why did Intel develop SpeedStep and similar and get it integrated into their motherboard mfgrs BIOSs? If the OS is idling, there's no reason to waste electricity. I agree you don't want to interfere with the apps, so maybe Google hasn't found a way to do this (and not interfere with apps).
The Following 2 Users Say Thank You to IPvFletch For This Useful Post:
Yes they do. Assuming the snapdragon operates like any other kind of processor you find nowadays it can very easily scale based on load.
I have to agree, but isn't that BIOS based and not up the chain through the driver?
Either way, to get back on topic someone show me this is working. i guess I could run write some code to run linpack like a minute after it's asleep, buuuuuuuuuttt I'd rather not lol.
i bet this is bs... if lin pack gets the same score then this isnt actually changing the clock rate plus i've gotten these results without root or underclocking
you are missing the point of the app....
It scales the cpu... to the condition of the phone...
when the phone is in standby.. it scales the phone down to it lowest cpu speed to safe power. If there is something that it needs to do.. update info or get data.. while in standby. It can speed up the CPU to the max setting (which you set).
when the phone is on.. it pushes the CPU up...
IF you have the phone on.. but are not doing anything.. but reading a long email or webpage... it can reduce the CPU a little to save power.
IF you run a speed test.. the app see that you are wanting full power... so it pushes it to the max the CPU can do (stock speed)... So the test with and without the app; should show the same result.
the app (overclock) does not really push the cpu speed past the stock speed. I think when we have full ROOT and a developer can really OVERClock it... then you might get real speed improvements.
If you are running Advanced Task Killer (or any other automated task killing app), be sure to go in and uncheck the Overclock Widget from the list of things being killed. Otherwise it won't work correctly.
The Following User Says Thank You to kathrynhr For This Useful Post:
I've been unable to get this to work with the unrEVOked root, so I'm guessing it will only work with Toast's method. I'm not brave enough to attempt that yet, so if anyone figures out a way to make it work with unrEVOked, be sure to post it up.
I've been unable to get this to work with the unrEVOked root, so I'm guessing it will only work with Toast's method. I'm not brave enough to attempt that yet, so if anyone figures out a way to make it work with unrEVOked, be sure to post it up.
what do you mean? I'm on unrevoked and it's working fine
When Sprint announced their first ever 4G handset at CTIA in March 2010, they dropped a bombshell on the mobile world. The HTC Evo 4G is a device that introduces a lot of firsts when compared to other North American handsets. This is the first Andr... Read More
Root + OverclockWidget = Insane Battery Life 40+ Hours
