I just installed "Overclock Widget", found here:
http://www.appbrain.com/app/org.freecoder.widgets.overclock
Which not only lets you overclock, but under-clock as well, and set ranges of frequencies for when the screen is both on and off. My phone is rooted and it appears to work fine, I just set it up so we'll see if it helps battery life. I set it so that when the screen is off the max frequency is 400,000 and when the screen is on the max is 800,000. The phone doesn't feel any slower than before -- to be honest, the speed is fine for me, I just need better battery life so we'll see if this helps.
Is anyone else using this app, or tried something like this to help with the battery life?
Another option is "SetCPU", available here on XDA:
http://forum.xda-developers.com/showthread.php?t=505419
I don't know if there really is a need for this. I installed System Panel on my phone and it shows that the phone automatically underclocks based on load. My phone went down to 100Mhz while I was watching it.
I saw on AndroidForums installed a clock manager and was boasting that he set his phone to drop to 700Mhz. So, in reality, he just forced it to run faster than the phone would've on its own!
meatrocket said:
I don't know if there really is a need for this. I installed System Panel on my phone and it shows that the phone automatically underclocks based on load. My phone went down to 100Mhz while I was watching it.
I saw on AndroidForums installed a clock manager and was boasting that he set his phone to drop to 700Mhz. So, in reality, he just forced it to run faster than the phone would've on its own!
Click to expand...
Click to collapse
Interesting, I'll have to check that out. But, at the very least, with an app like this we should able to "throttle" the top speed to 800MHZ or so to save a little juice at the cost of some speed, correct? Or, is even something like that probably not worth it?
So is there no reason for SetCPU anymore? I just downloaded it, but I'll go ahead and uninstall it if people think its pointless on this phone
yeah the phone throttles on its own.
its still usefull if you can throttle voltage i guess
I thought about looking for something like this, but then when I went into system infoormation it showed that was I spending like 88% of my time with the cpu clocked to 100mhz, so there seems to be little point.
the screen is the real culprit in battery loss on this phone. black background swith red streaks are your friend.
Related
I have heard a lot of people saying they can't tell the difference between the underclocked default and running at 172 to 528 so I thought it best to discuss the benefits, disbenefits and thus if it's worth doing, if it's worth slowing it down further and if it's worth going even faster.
So far I have found the most noticable area of improvement to be in file transfer performance. To transfer a 134mb file from SD card to notebook I got 14 seconds vs 19 seconds at stock speed (somebody confirm?).
I have not noticed any change in battery life.
Was it underclocked from new due to cooling issues or battery or what?
I think it was also a bit quicker updating 13,000 camera locations in MySpeed.
A lot of the variables are difficult to test so any suggestions would be welcome.
A
You didn't verify what speed you are running it at. I assume you set it at a constant 528? I overclock it every once in awhile. I think I may set it to 528 and let it sit all day.
I don't know about you guys, but when I leave it locked at 528 for a long period of time. My phone speed gets ****ed. It feels like its running at 172. 528 is great for when you're using your phone heavily, but once you put your phone to sleep, it seems that it drops from 528 regardless of what you have it set at. Try it out... you'll see. Especially when the phone starts getting hot. Left it on all day and the touch screen was way too hot to be normal. Not good.
Why you would **** with the speed/heat consumption of a device that already gets hot charging the battery is beyond me. It's asking for failure.
APrinceAmongMen said:
I don't know about you guys, but when I leave it locked at 528 for a long period of time. My phone speed gets ****ed. It feels like its running at 172. 528 is great for when you're using your phone heavily, but once you put your phone to sleep, it seems that it drops from 528 regardless of what you have it set at. Try it out... you'll see. Especially when the phone starts getting hot. Left it on all day and the touch screen was way too hot to be normal. Not good.
Click to expand...
Click to collapse
Hmm I've had my phone @ 528MHz for like a month now. Even leaving it on for weeks at that speed I don't see any problems. One thing you might try when it starts going slow like that is make sure it's still running at 528(OS resets it sometimes) and check what apps are running.
At any rate, for me overclocking works perfectly and I haven't had any issues at all with it. For battery life it'll probably depend on your usage. Clocking at 528MHz will lower battery life if you leave your phone asleep most of the time(even if you set a lower minimum since there's more of a jump the cpu has to make when scaling back to max speed), but if you use your phone a lot and it's rarely asleep then you'll probably actually get better battery life with it set to 528 max and min, since the cpu no longer has to use the energy required to change speed.
EDIT: @afflaq: It's not the cpu that gets hot from charging, it's the battery. You're not going to overheat the cpu just by clocking it to its rated speed.
Ditto @ marcusmaximus, I got the same temperature readings during 528 and 384 mHz. Been running it on 528 for a while as well.
APrinceAmongMen said:
I don't know about you guys, but when I leave it locked at 528 for a long period of time. My phone speed gets ****ed. It feels like its running at 172. 528 is great for when you're using your phone heavily, but once you put your phone to sleep, it seems that it drops from 528 regardless of what you have it set at. Try it out... you'll see. Especially when the phone starts getting hot. Left it on all day and the touch screen was way too hot to be normal. Not good.
Click to expand...
Click to collapse
Which overclocking application are you using, and which Android version are you running?
Overclocking
It works fine overclocked all the time. I don't even notice any difference in battery life either. My phone is mostly in sleep mode btw. On all day, I only see it drop to 66% with light usage. Overclocked surfing the web, I surfed for an hour continuous and the battery went from 100% to around 80%.
Using Open overclocker and any rooted build should work as long as you have it setup right. Just set it to 528 in both fields and forget it. The app automatically asks permission from the root app every time you reboot.
I am currently using TheDudes build and it works perfect. I have never had it reset the speed either as others suggest. Try one of his builds and get the Open Overclocker app from the market. That is the best build anyway.
Currently running .93 ... waiting for .95 which will be even faster.
JCD4429
So I just got a brand new D2G and thanks to the info in this forum I rooted it and installed fission rom and FRM...Im loving the phone, its fast, smooth and beautiful but the battery is AWFUL. I have read all the info about how to get the most out of your battery and everything on these forums but mine is waaaay worse than anyone has said before.
For instance, last night my phone was charging oernight, at 6 am when i woke up to pee it was at 100% so I unplugged it and went back to sleep, come 10 am when i woke up my phone was down to 15%!!! From just sitting there with the screen off...
Ive set the network to CDMA/Evduo automatic, installed Jrummy's overclock app...Can anyone explain in detail what exactly the settings in the overclock app mean? "set scaling frequencies at boot, cpu scaling frequencies etc?" for instance if I set scaling frequencies not at boot to ultra low voltage and 1 ghz and lower, do i need to also go into cpu scaling frequencies and make profiles and stuff?
Any information is greatly appreciated, Ive been reading up for days but this stuff is hard to find clear answers on specific issues. Thanks!
This is probably the most basic first thing to ask/do, but have you checked the battery useage to see which apps are using the most power? try doing what you did where you charged, and then let it sit for 4 hrs, and after that see what's using the battery, I bet there is some app that just nonstop uses the gps or 3g data or something wearing your battery life out super fast.
Yeah i looked at that this morning to see and all it said was suspend took up like 90% of the battery...Doesnt make any sense
1. Set at boot isn't what you're thinking. Set at boot means that whatever your current settings are will be set the NEXT time the phone boots. This is used when you have a setting you like. The reason you DON'T want to set at boot is that if you accidentally pick a setting that your phone doesn't like, and it makes it crash, then next time it will boot up with normal settings. Otherwise, you'd be looking at some work doing a recovery with either CWR or RSDLite... There are better ways to spend 30 minutes. Disclaimer: I use SetCPU, but the settings are all essentially the same.
2. For scaling, unless you're a power user (read: Geek) who's really up on his stuff, you should just stick with ondemand. This means your CPU will run at the lowest frequency possible, but will scale its speed up when processes call for it. This is efficient.
3. Yes, you should still make profiles. The setting on the main screen where you choose "Set at Boot" (Again, I'm speaking from SetCPU experience, but it SHOULD be the same) is just the main profile, setting the global minimum and maximum. You should leave the minimum on this at 300. The phones don't like to run much lower than that, even with the screen off; They start not ringing for calls, not waking up, etc. Set the maximum to whatever you want the max to be. You can overclock, which will obviously hurt your battery life. You could underclock and set the maximum to 1GHz, or even 800MHz, which would have a decent effect on battery life with no noticeable performance decrease to the average user. I run mine at the stock 1.2GHz and it's fast enough for my needs.
4. I wrote this thread to help people maximize their battery life. It's pretty detailed, you should give it a thorough read, it works well for me, and seems to work for others. I'm at 32hrs unplugged and my battery has gone from 90% to 20%. That's pretty light use, and I have an extended battery, but I still see over a day on my stock battery when I use it. There's a list of my SetCPU profiles there too, that might be helpful in setting up your own.
Thanks for the info on overclocking, I think I have it figured out now...
I will definitely read through your thread, but is it possible that I just had a bad battery? due to a shipping error, when verizon sent me my phone they sent 2 by accident so I just swapped out the battery for the other one and it seems to be doing much better already...
Meaning, does the battery life take a dip when you overclock to 1.5ghz. Does it get any hotter? Is heat an issue at all on this thing? Also, any performance or battery changes from installing the tiamet kernel itself? I'm in the wifi xoom btw.
Strangely enough battery life seems to be about the same. Heat has not been an issue mainly due to having the dual core, however its something you always want to keep an eye on.
Battery life is affected most by the screen. Screen> Network connections > CPU > RAM
There was a thread that someone made a while back about the things that affected battery life the most. If I can find It ill send it your way. After seeing the charts I figured Id try changing some settings.
things I did:
1. Set my max cpu freq to 1.19 min to 488 same for all my cpu tunner profiles ( I wanted to have my phone running the same all the time)
2. Lower'd my screen settings. I didnt need a pocket flashlight EVERYTIME I unlocked my phone.
3. Turned off un needed network connections. Its not hard to turn them back on when you need them.
4. I then looked for things that were running but were not needed by anything ( google maps are used by a few apps so dont disable it haha) I used Uninstaller for root users to get rid of some things.
After all these steps my battery life went WAY up. I have been doing the same thing on my Xoom now and my batt lasts the same at 1.5 as it did at 1.
I still get VERY respectable battery life at 1.5ghz, I can easily get through the day with normal usage. Yesterday night in fact, I left the house with maybe 75% battery life, used my tablet quite a lot throughout the evening(left the house around 9, went to sleep around 1am) and used it all morning basically constantly from 7am to around noon and came home with 9% battery left.
No problems here either. Woke up around 8:30 yesterday and used it all day sometimes pretty heavy. Finally had to plug it in around 6:30. I'm home all day with a broken hip and femur, so I've been putting it through the paces. Running @ 1.5ghz with interactive gov.
Chris
+1 on 1.5GHz having little effect on battery life. I didn't have to change anything else, either.
thats all great to hear! I suppose ill start looking into rooting my wifi xoom tomorrow then. Thanks for the help!
Im very happy with the battery life on this thing. I expected 4 hours max after a few weeks of use/charges. I never thought that it would keep up with anything Apple, Lets face it.. Apple knows how to make stuff run forever. But I was plesently suprised. Xoom +1000
yeah, the battery is good, but i won't know any damage to the cpu when overclocked ?
I wouldn't worry about any CPU damage- too many people have reported success (and no reports of failure).
Anyone else notice with the tiamat kernel that their xoom becomes very unstable overclocked at 1.5 using setCPU? Mine was essentially a soft brick at 1.5 constant rebooting and never able get pass the unlock screen, I had to rewipe with bootloader. I can do 1.2 no problem but don't even want to try going higher.
All of our chips have variations, so the overclock isn't universally guaranteed. That being said, I've been using the Tiamat kernel @1.5GHz since it was released with no problems.
Should have stated that mine is the wifi model, but yea thanks for info.
Here was that post I was looking for on this stuff. http://forum.xda-developers.com/forumdisplay.php?f=946
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Profondo_Rosso said:
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Click to expand...
Click to collapse
I do the same.. just 1 screen off profile to underclock it to 216/216 when the screen is off
regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
Android does regulate the cpu, but I don't think it will take advantage of more conservative governor modes unless you tell it to. That's only relevant if the kernel supports more conservative governor modes. And, as the other responses have pointed out, you can force Android to be more conservative by capping the max clock speed.
Hmm... Guess its worth a shot. Good lookin out guys.
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
charlieb620 said:
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
Click to expand...
Click to collapse
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
regP said:
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
Click to expand...
Click to collapse
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
jayohwhy said:
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
Click to expand...
Click to collapse
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
rhinology said:
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
Click to expand...
Click to collapse
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
jayohwhy said:
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
Click to expand...
Click to collapse
Once we get some custom kernels, we should be able to change the governors in setCPU, dependent upon on what the kernel supports.
SetCPU Custom Frequencies for G2X
I got SetCPU today and was playing around with it and it looked like it was limiting my CPU all the time due to lack of profile, not just when I had the screen off per my profile so I looked into making a text file for custom frequencies and am posting it here since there doesn't seem to be any help for g2x with it.
This is a really simple file, tell me if you guys have any better ideas, I just put in:
216000,528000,712400,1000000
I'm attaching it. I put the file in my dropbox, grabbed it via the app and then moved it to /sdcard/setcpu.txt via astro file manager then loaded custom profile from within setcpu. Hopefully this saves someone some time or you can tell me if I'm going about this the wrong way
I'm sure it could be fine tuned more but I was getting irritated at how much of a pain it was to unlock the phone with it set too low, so for screen off I have it set to 216->528. You could add 254000 in or something. The phone seems to be as usable as before now with setcpu enabled like this while it should be limiting the cpu when the screen is off. It sucked (well not the battery) without a custom profile.
socalTNT said:
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
Click to expand...
Click to collapse
rooted?????? what is that?
TheMightiest1981 said:
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
Click to expand...
Click to collapse
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Profondo_Rosso said:
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Click to expand...
Click to collapse
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
charlieb620 said:
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Actually, your assumption is wrong, as is often the case.
I'd quantify it more as normal use. Lots of texts, some games of Pro pool, a few phone calls, checking Pulse 3-4 times during the day for 10 minutes at a time, some mild web browsing and watching a few youtube videos.
I ended up at around 18-19 hours of of use.
Today, I'm off the charger for 8 hours, and I still have 45% left, and I would say that's with some moderate to heavy use.
regP said:
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
Click to expand...
Click to collapse
Try upping it to 216/312 or a tad higher and you should be fine.
This is what I've done to help my battery life.
Firstly you'll have to root your device, then follow the steps below.
1. Install SetCPU(from Market or where ever you can find it)
2. Run it, allowing root access when asked by superuser.
3. On the Main tab, set Max and Min to 1200000(1.2Ghz), or whatever you want general usage to be. Most users probably want it like this so it will stay at best performance during using, and will not slow down. Also, whatever speed you're using set Scaling to Performance. Even if you are not running at top speed, it is still good to use Performance for the settings you want while using the device.
4. Go to Profiles tab. and check Enable, and click Add Profile. Set it to Screen Off, and you can change the settings to whatever you want. I had it at 100000(.1Ghz) for Min and Max, but when you go to unlock your screen, it lags a lot for a second. I currently have Max and Min set to 400000(.4GHz), and it made it so it does not lag when I go to unlock, but it is still low enough to be very conservative on battery. Set Scaling to Powersave, and Priority does not matter unless you have more than one profile, so don't worry about it.
5. (Optional) Install JuicePlotter from the Market, for free, and it has a nice widget that collects your phone data and after a few days will become very accurate on phone battery life remaining. It will show it after a day or so, but it will tell you how accurate it is, and it might not be very high until a few days later.
And that's it. Whenever your screen is off, it will underclock the processor so it's not using as much battery when not necessary. If you want, you can add other profiles, such as for when charging, and when the battery is low. I originally had it set to 1.2 GHz Max and Min while charging, and set the priority higher than the Screen Off, so it didn't clock down if I turned the screen off while charging, but there is no reason, I'm still not using it when I turn off the screen, so I deleted that profile.
So if your only profile is the Screen Off, then once you turn the screen on, it will change to whatever settings you have on the Main tab.
I unplugged my phone at 6:30 AM, and it is now 5:30 PM here, and I still have 32% battery, with JuicePlotter telling me I have 4 hours and 49 min left, but it only has a 72% accuracy since I just got the app yesterday. That's great since yesterday my phone would have been dead over 2 hours ago. When I woke up JuicePlotter said I had around 15 hours, but it wasn't as accurate as it is now, and it so far is expected to last longer than that..
I just use JuiceDefender free set to Agressive to obtain the best battery life. I got this little vendetta against SetCPU though.
I saw a button on there that said battery saver, what exactly does it do?
apwhitelaw said:
I saw a button on there that said battery saver, what exactly does it do?
Click to expand...
Click to collapse
Not sure. I'm learning JD myself here so .... yeah
apwhitelaw said:
I saw a button on there that said battery saver, what exactly does it do?
Click to expand...
Click to collapse
It takes you to a recommended battery saving app from the market. I haven't tried that app, but I imagine it is probably something similar to SetCPU.
I think this is wholly unnecessary, I'm sure samsung underclocks when not in use already, it's an obvious thing to do. I haven't done any of this and I can get ~40 hours of light-medium use
But try watching justin.tv streaming movie on hspa+ lets see if you even get 4hrs?
Sent from my SAMSUNG-SGH-I997 using XDA App