Root Root + OverclockWidget = Insane Battery Life 40+ Hours

[clueless]

Overclock widget code attached...just an excuse to use google goggles This phone rocks!

 

[nick325i]

wait a sec.... I swear android down clocks itself already when it goes into sleep mode.

Refer back to post #88 in this thread. Re-read from there to your post.

 

[saccityp]

Overclock widget code attached...just an excuse to use google goggles This phone rocks!

thanks

 

[milk242]

Quick question, way off topic but hopefully someone can answer. Why do you need to run the updated radio if you already had the OTA update? Didn't the OTA update also update the radio? When I look at my bootscreen on my stock Evo, I see the radio version and it's the same that's listed on the XDA forum.

 

[apollooff320]

Quick question, way off topic but hopefully someone can answer. Why do you need to run the updated radio if you already had the OTA update? Didn't the OTA update also update the radio? When I look at my bootscreen on my stock Evo, I see the radio version and it's the same that's listed on the XDA forum.

if you downloaded the OTA update then your radio got updated.

 

[vihio]

ok, this is a little summary from what I know and have experienced.

first, yes, android does downclock itself. I dealt with this a lot when I had my hero.

second. when I installed oc widget and set it all up, it never once asked me for su permissions. this made me suspicious. I downlocked it so it was forced to stay at 575 or something but another one of my widgets said it was still at 998. I also installed setCPU and it was scaling between 245 and 998. I decided to use setCPU instead seeing as everything points to it working and oc widget not working. (I did linpack, I did cat /proc/cpuinfo and it all coincided with what setCPU was telling me) I also checked the cpu load using setCPU (this was a problem on the hero) and it stayed constant around 3%-5%.

by the way, oc widget did work on my hero and I think it asked for su permissions as well.

lastly, I used profiles on setCPU to determine my clock speed on charge, on standby (screen off) and when the power is <100%

I also do not deny you having better battery life, this might just be MY evo. btw, i am rooted using toasts method on the stock rooted rom

 

[tjwoo]

ok, this is a little summary from what I know and have experienced.

first, yes, android does downclock itself. I dealt with this a lot when I had my hero.

second. when I installed oc widget and set it all up, it never once asked me for su permissions. this made me suspicious. I downlocked it so it was forced to stay at 575 or something but another one of my widgets said it was still at 998. I also installed setCPU and it was scaling between 245 and 998. I decided to use setCPU instead seeing as everything points to it working and oc widget not working. (I did linpack, I did cat /proc/cpuinfo and it all coincided with what setCPU was telling me) I also checked the cpu load using setCPU (this was a problem on the hero) and it stayed constant around 3%-5%.

by the way, oc widget did work on my hero and I think it asked for su permissions as well.

lastly, I used profiles on setCPU to determine my clock speed on charge, on standby (screen off) and when the power is <100%

I also do not deny you having better battery life, this might just be MY evo. btw, i am rooted using toasts method on the stock rooted rom

I haven't had time to test if it works yet, as I'm charging to 100% to let it stay unplugged overnight (last night I left it unplugged prior to installing this to compare it to)
It def asked me for SU permissions, and it shows up in the app as well. here:

 

[liquidtrance]

Question on the rooting, if I root my phone now (obviously I'll lose everything) but can I easily go back to the market / downloads section and re-download all my apps or will I have to re-find all the apps again?

 

[avacomputers]

I don't think you lose anything by rooting. When you flash custom roms that's when you do a wipe.

 

[liquidtrance]

From what I was reading on the Toast instructions loading the Toast root file on a phone reboot I will lose all data on the phone? Is this correct?

LINK:Evo 4G root instructions are here! | Android Central

 

[flukeSG2]

I followed the settings discussed earlier in the thread and at 100% at 8:30pm to 20% at 7:12am, with about 45 minutes of gaming and the rest of the time it was screen off. I also had my 4G and Bluetooth on. Now while I was running my EVO, my friend was running his stock, not rooted, no task killers and played games for the same amount of time as I did and also had his Bluetooth on, but not his 4G. He ended up with 28% battery life left.

So, in comparison, using the Overclock Widget seems to suck more power vs not using the Widget. Again my settings are identical to the OP's that he displayed.

 

[teddykgb]

From what I was reading on the Toast instructions loading the Toast root file on a phone reboot I will lose all data on the phone? Is this correct?

LINK:Evo 4G root instructions are here! | Android Central

My understanding is that the toast root itself does not wipe any data. IF after you root you installed a custom ROM that would be where your data would get wiped.

I used the Unrevoked for now so nothing got wiped.

 

[teddykgb]

I followed the settings discussed earlier in the thread and at 100% at 8:30pm to 20% at 7:12am, with about 45 minutes of gaming and the rest of the time it was screen off. I also had my 4G and Bluetooth on. Now while I was running my EVO, my friend was running his stock, not rooted, no task killers and played games for the same amount of time as I did and also had his Bluetooth on, but not his 4G. He ended up with 28% battery life left.

So, in comparison, using the Overclock Widget seems to suck more power vs not using the Widget. Again my settings are identical to the OP's that he displayed.

In my opinion, having 4G on vs. off could easily account for the 8% difference. However you're right in that there doesn't seem to be much gain. Hmm, more testing required.

 

[oskinosmee]

installed rooted and testing, Thx OP

 

[flukeSG2]

I take back everything I said now. I found out I was having issues with my superuser permissions and I believe now the program was not in fact working. However, I do now have something to base it against. I will test again tonight and report back.

 

[teddykgb]

Im a moron and have no idea how to root my phone. I have some computer knowledge. Quick tips on how to do this?

See first thread in the forum: http://androidforums.com/all-things-root-evo-4g/91831-www-unrevoked-com-went-live.html

VERY Easy.

 

[muncher]

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.

facepalm

 

[bmwboyee]

Question on the rooting, if I root my phone now (obviously I'll lose everything) but can I easily go back to the market / downloads section and re-download all my apps or will I have to re-find all the apps again?

appbrain is your friend!

 

[cyberelex]

I can confirm that this definitely works, i took my phone off the charge last night and as of right now i have 63% battery left with 17hrs off the charge, i have been pushing 3 email accounts and have had moderate internet use. What i have realized though is that if you leave 4g on even if you have good reception, it will drain you battery really fast. So unless you are using it i would recommend turning it off when not in use.

 

[phalcon]

I followed the settings discussed earlier in the thread and at 100% at 8:30pm to 20% at 7:12am, with about 45 minutes of gaming and the rest of the time it was screen off. I also had my 4G and Bluetooth on. Now while I was running my EVO, my friend was running his stock, not rooted, no task killers and played games for the same amount of time as I did and also had his Bluetooth on, but not his 4G. He ended up with 28% battery life left.

So, in comparison, using the Overclock Widget seems to suck more power vs not using the Widget. Again my settings are identical to the OP's that he displayed.

I'm seeing the exact opposite results. My battery only lost about 4% charge from 11:15 pm to 8:00 am this morning using OC Widget. Are you sure your settings are being saved? I thought that this wasn't working either until I realized that you have to manually save the settings and since then I have noticed a dramatic increase in battery life. I've also noticed that when my screen is asleep and using OC widget that my battery charges a lot faster. YMMV

 

[jaysmi32]

Ok just checked my battery level my uptime is 17 hrs and 25 mins, and my awake time 3 hrs w/ 31% battery left I'm assuming this is good

 

[tjwoo]

I'm excited to report that the OC widget works! Previous night under 9 hours unplugged and sleeping before I tried the OC widget, I lost ~20% battery life.
This time, after 9 hours unplugged with OC widget activated, i barely lost 6-7% battery life. Amazing.

 

[nick325i]

Ok just checked my battery level my uptime is 17 hrs and 25 mins, and my awake time 3 hrs w/ 31% battery left I'm assuming this is good

It does really depend on usage and signal but if that's atleast a few hours improvement over previous battery life i'd say were stepping in the right direction.

 

[dmac250]

(NEVERMIND I SEE IT)

Tell me the exact name of this program...ive been looking on appbrain...all i see is :

SetCPU for Root Users






Open Overclocker






Milestone/Droid Overclock
NE

 

[Krandor311]

It does really depend on usage and signal but if that's atleast a few hours improvement over previous battery life i'd say were stepping in the right direction.

I think going off what's been discussed so far, we can say that Yes Android will automatically downclock the CPU when the phone screen is off, but it likely has a timer to where it waits for a certain point in time before it does this action. The widget is forcing it to do downclock as soon as the screen off.

From playing around with normal usage yesterday (i.e. messing around with it every few minutes for whatever purpose), I did see a noticeable difference in battery life. When I went to bed I decided to test it along with unchecking "Mobile Data Always On." The night before when I did this without the widget, I used up 6% of the battery in the 8 hours I slept. My results were the same this time with both Mobile Data unchecked and the widget installed.

So moral of the story is, under normal usage where you will be hitting up the phone a few times an hour and not giving Android a chance to downclock on it's own, battery life improves. Long idle times between use will see no improvement.