Database Users

oc'd phone heating up during normal use and poor battery life

Well ill start off by saying I'm new here and this is my first post. I'm also very new to this stuff and have a lot to learn. A buddy of mine recently rooted and overclocked my phone using the sense 2.6.32.21 1.5ghz oc/uv kernel. I currently have it set to 1.19 max 768 min and am experiencing temps above 107 running emulators and just web browsing.. I am also seeing pretty poor batt life even using battery booster and advanced task killer.. any help is greatly appreciated!

Battery apps and task killers tend to have the opposite of their intended effect on battery. Android has a built in utility to watch battery usage, why do you need a 3rd party one? Also do some reading on task killers, you will see why they are unnecessary on Android. I've stopped using one and my phone runs faster and more stable than before.

768 min is VERY high. Might explain the heating and battery life drain quite a bit.
Try this for me, please. Set your governor to interactive and drop your min down to 245. Run that for a whole charge. You may be surprised.
Sent from my PG06100
Also, I second the post above me. Advanced Task Killer and anything like it ultimately cause more harm than good. Battery apps, such as Juice Defender, also shouldn't be necessary. Although, it is YOUR phone.

Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?

bearsblack said:
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
Click to expand...
Click to collapse
well they gave some suggestions. which it seems you dont want to listen to. you dont need task killers of any kind

Sorry I'm stubborn. Uninstalling now

No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?

Compusmurf said:
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Click to expand...
Click to collapse
because all the cool kids are doing it smurf...duh.
But seriously, min. should not be set at anything greater then 245. Only use performance if you are benchmarking. Default at the moment should be interactive.

Just gonna add my 2 cents in from personal observation....after doing some reading on overlooking and stuff I've noticed when going into the different ## modes, the shift usually drops its processor cycles to pretty low numbers in the 200-300 mhz range when its just in standby or not doing anything...it only kicks it up when you need the power. So the heating up is probably caused by constantly running at what used to be its max territory...PLUS youre going above and beyond the original limits/specs at a constant so it never gets to relax even when the phone is idle...I hope that makes sense. So as one poster mentioned keep the min at the stock setting and if you really want to/need to then raise the max mhz to whatever your phone can handle reliably. Correct me if I'm wrong anyone who is more into the overlooked setups. Me personally, stock has been able to keep up with whatever I have thrown at it after 30 days and still getting 25+hrs on one charge.
Sent from my PG06100 using XDA App

I currently have it governed at 245 max screen off. Running 1.2ghz max interactive with no task killers or batt savers. Batt life seems to be somewhat better but temps still creep past 105. Thanks a lot for the info

alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??

Excuse me if I am wrong it's early and im too lazy to reread up on it but I believe the difference is with on demand there is a slight delay(second or two) and it gradually kicks up to where it needs to be where is interactive is a spike the second you need it...

JAREDR said:
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Click to expand...
Click to collapse
Interactive is, usually, a lot better for battery life.
If you look at your cpu's scaling history when on the two, TYPICALLY, you'll see a whole lot more time in higher frequencies using ondemand.
That's not to say, however, that with some devices and some kernels they will act the same.
Sent from my HTC Speedy

SetCPU vs. CMSettings Built-in CPU manager

For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?

I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.

I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.

Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App

Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier

I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?

Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.

I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2

DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.

ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.

colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.

redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).

At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted

Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...

Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.

SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.

I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison

tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?

im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.

Phone randomly will turn off? CM7.1

Lately I've been noticing when I go to grab my phone, it will be magically turned off. I know it wasn't turned off because it will just sit on my desk, full battery, no loose battery connection (NEVER has the phone turned off while use or moving around, but still an assumption), no crazy setcpu scaling (min: 245MHz max: 806MHz), and no water damage. I haven't had this problem in the past with CM7 nightlies, or CM7 final release. I also know that its not just that problem I have every once in a while where the screen won't turn on but the 4 touch buttons will. But I'm 99% sure that's just a result of my min: 245MHz max: 245MHz screen off setcpu profile. Anyone have this issue or have any ideas why its doing this?
Sent from my HTC Vision using XDA Premium App

You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4 Hope this helps!

carquote said:
You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4 Hope this helps!
Click to expand...
Click to collapse
I checked my battery and my battery does not have the metal strips, should i still attempt his fix even though i dont have that metal on metal contact? My battery looks like the guys GF's battery a little bit down on the 4th page, 4th post.

I would ditch setCPU to be honest. since CM settings now has overclocking built in, it just seems loony to call on another app to manage cpu frequencies.
there is a lot of misunderstanding regarding profiles with setCPU as well...
unless you are running the performance governor (which pegs the CPU frequency at its highest selection), "profiles" are already built in to your kernel.
it is the kernel's job to manage frequencies according to load... which is exactly what you are attempting to do with your screen off profile. if you're on ondemand, interactive, scary, smartass, or any other governor aside from performance, the governor will do the "screen off" profile for you automatically by scaling down frequency based on load.
setCPU is a good tool for roms without built-in CPU management, but for CM7, it's officially obsolete (unless you're overclocking heavily and need a temperature profile... your governor won't do that for you )

Thanks for all the info, i knew CM7 had the built in one but didnt know the kernel handled as much as it did... thanks! (and i pressed "thanks" by the way to everyone who replied ) Since you seem to have some kernel knowledge, whats the smartass and userspace governor?

Kevin001111 said:
Thanks for all the info, i knew CM7 had the built in one but didnt know the kernel handled as much as it did... thanks! (and i pressed "thanks" by the way to everyone who replied ) Since you seem to have some kernel knowledge, whats the smartass and userspace governor?
Click to expand...
Click to collapse
here's a quote from erasmux on smartass (the sleeping frequencies may differ depending on whose smartass you're using):
smartass governor – is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Of course, the frequencies are different than what he used, since we have better processors than the Hero.
Z
Click to expand...
Click to collapse
userspace is problematic in my experience. would not recommend using it. here is a good article explaining what it does (and why it's not the best idea for most of us): http://publib.boulder.ibm.com/infoc...topic=/liaai/cpufreq/TheUserspaceGovernor.htm

G2 randomly turns off
I have been having a similar issue with the phone just randomly turning off, I am not sure if this has to do with the handoff between wifi and network calling but this is a hunch. I do have a logcat with a few shutdowns.

carquote said:
You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. [cant post outside links] Hope this helps!
Click to expand...
Click to collapse
You think you could summarize what the fix is? The link doesn't work anymore. Thanks

j0lte0n said:
You think you could summarize what the fix is? The link doesn't work anymore. Thanks
Click to expand...
Click to collapse
Try this link instead: http://208.74.204.85/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
T-Mobile, in their infinite wisdom, completely trashed the old forums in favor of some new community/social neworking-esque BS. Everything that people had worked on, figured out, and shared was lost for good. After an uproar from the community they temporarily restored a read-only version.
That link should work for now, but T-Mobile stated that the archives would only be brought back for about a week. Tools.

I had this issue. Only with the leaked 2.3.3. I haven't had the issue with the new official 2.3.4. I had to remove the battery and reinsert it. rather annoying especially if I was driving.

CPU Type

Hello!
My "Cpu Type" is Slow and I want to undervolt it (to get better battery and less heat).
What are the best undervolting for keeping the device stable and with better battery and less heat?
Thanks!

Every chip is different, regardless of bin type. You'll have to experiment and see for yourself. Drop it a notch and use your phone to test for stability. If it seems stable, drop it one more. Keep going until you find the place that causes freezes. Then bump it back up and use the "set on boot" option all performance apps have.

estallings15 said:
Every chip is different, regardless of bin type. You'll have to experiment and see for yourself. Drop it a notch and use your phone to test for stability. If it seems stable, drop it one more. Keep going until you find the place that causes freezes. Then bump it back up and use the "set on boot" option all performance apps have.
Click to expand...
Click to collapse
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!

Wassupdog said:
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!
Click to expand...
Click to collapse
Don't set the voltage settings to stick on boot until you find your lowest stable voltage.
Sent from my Nexus 4 using xda app-developers app

Wassupdog said:
I undervolted to 50, will it do what I want or should I undervolt more?
I heard that if I undervolt too much the device won't turn on, how can I avoid that?
Thank for the answer!
Click to expand...
Click to collapse
I thought I explained this already, but I'll try it a different way. I can't answer the question because your chip is different from mine, along with everyone else's. The voltage will not be set until after the boot process is complete, which is why I told you to determine the lowest stable voltage and THEN use the set on boot option. That way you don't get an immediate freeze on every boot. Make sense?
Again, you still need to determine what your optimal voltage change is. We cannot tell you that.
Also, undervolting changes your battery life VERY little. It will likely not even be noticeable. Where you'll see the real benefit is in the area of heat. Even the 50 you've already done should make a noticeable change. On a device with a lot lower throttling point than most, this is a good thing.

Harry GT-S5830 said:
Don't set the voltage settings to stick on boot until you find your lowest stable voltage.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
estallings15 said:
I thought I explained this already, but I'll try it a different way. I can't answer the question because your chip is different from mine, along with everyone else's. The voltage will not be set until after the boot process is complete, which is why I told you to determine the lowest stable voltage and THEN use the set on boot option. That way you don't get an immediate freeze on every boot. Make sense?
Again, you still need to determine what your optimal voltage change is. We cannot tell you that.
Also, undervolting changes your battery life VERY little. It will likely not even be noticeable. Where you'll see the real benefit is in the area of heat. Even the 50 you've already done should make a noticeable change. On a device with a lot lower throttling point than most, this is a good thing.
Click to expand...
Click to collapse
Thank you both!
What can I do to increase battery life?

Wassupdog said:
Thank you both!
What can I do to increase battery life?
Click to expand...
Click to collapse
Play around with different kernels. They will all give you different performance vs. battery life. Use the one that suits you. Personally, I go back and forth between hells core and semaphore.
You might also check out greenify. It will hibernate apps that you tell it to instead of letting them suck up resources in the background.

estallings15 said:
Play around with different kernels. They will all give you different performance vs. battery life. Use the one that suits you. Personally, I go back and forth between hells core and semaphore.
You might also check out greenify. It will hibernate apps that you tell it to instead of letting them suck up resources in the background.
Click to expand...
Click to collapse
I have no problem to move between kernels but just if they have Franco's colors tuning option.
The Nexus screen looks wayyy better with it.

Wassupdog said:
I have no problem to move between kernels but just if they have Franco's colors tuning option.
The Nexus screen looks wayyy better with it.
Click to expand...
Click to collapse
This should help with semaphore. It uses Franco's values, but in a different order.
http://forum.xda-developers.com/showpost.php?p=43828267&postcount=2035

estallings15 said:
This should help with semaphore. It uses Franco's values, but in a different order.
http://forum.xda-developers.com/showpost.php?p=43828267&postcount=2035
Click to expand...
Click to collapse
Semaphore is good for battery life?
And I ran antutu with -75 UV and it is very not stable.
I can stay at 50 .

Wassupdog said:
Semaphore is good for battery life?
And I ran antutu with -75 UV and it is very not stable.
I can stay at 50 .
Click to expand...
Click to collapse
It is for me. That's why I recommended it.
You might take note of those voltages that work for you. I can't remember, but Semaphore might have lower values right out of the gate.
Now stop asking questions and start trying things out If you're scared, make a backup. No matter what you do with the voltage settings, you can always restore the backup.
Happy flashing!

estallings15 said:
It is for me. That's why I recommended it.
You might take note of those voltages that work for you. I can't remember, but Semaphore might have lower values right out of the gate.
Now stop asking questions and start trying things out If you're scared, make a backup. No matter what you do with the voltage settings, you can always restore the backup.
Happy flashing!
Click to expand...
Click to collapse
Thank you very much !

Touch Frequency?

How do I lower my touch frequency? Whenever I touch the screen immediately two cores jump to the highest frequency available which is 1267 MHz, I have the max frequency locked at that in general... So how do I lower it, or would this not help the battery? I am trying to figure out how to lower it to around 883 MHz for the purpose of saving battery? I am using Trickster Mod btw
Optimus DE v2.3 rom
Furnace 2.2.3 kernel

dorimanx kernel and its STweaks app
it doesnt go below 960mhz, but it can be disabled

60nine said:
dorimanx kernel and its STweaks app
it doesnt go below 960mhz, but it can be disabled
Click to expand...
Click to collapse
Thanks will give it a try with this rom, usually doesn't help me with battery life but I will give it a shot! Will report back how it goes. By chance do you know how big of a difference letting the kernel and rom settle for a few days makes?

dunno... what are your expectations on battery life?
with dorimanx kernel the results are usually more noticeable after a charge or two

60nine said:
dunno... what are your expectations on battery life?
with dorimanx kernel the results are usually more noticeable after a charge or two
Click to expand...
Click to collapse
A minimum of 5 hours screen on time... But yeah guess im gonna have to wait a charge or two to see the full effects.
Can you suggest a good settings combination for battery life? Just flashed v5.0 of Dori:silly:

read a few pages back on dorimanx kernel thread, someone posted good overall battery kernel settings, but wait for an 5.x update because something needs to be fixed in alucard governor...
btw STweaks app also has preloaded profiles you can change if you don't want to fiddle with the settings manually...
have fun

60nine said:
read a few pages back on dorimanx kernel thread, someone posted good overall battery kernel settings, but wait for an 5.x update because something needs to be fixed in alucard governor...
btw STweaks app also has preloaded profiles you can change if you don't want to fiddle with the settings manually...
have fun
Click to expand...
Click to collapse
I went about 10 pages back, could you by chance post a link or tell me what page number it was on? I saw screen shots on someones battery life but not settings.

i don't know the exact page, i'd have to search it too...
btw don't be lazy, you can test several settings in stweaks yourself. or use predefined ones... many people find the default ones good enough but not all of us use the phone the same way...
cheers