Database Users

SetCPU safe?

Doesn't SetCPU overclocks our device? I heard constantly overclocking your device will kill it less in a year. Is this true?
Sent from HTC HD2 using XDA app.

HeavyComponent said:
Doesn't SetCPU overclocks our device? I heard constantly overclocking your device will kill it less in a year. Is this true?
Sent from HTC HD2 using XDA app.
Click to expand...
Click to collapse
I used setcpu on my g1 (overclocked from 384mhz to 528mhz) for almost the whole time i had it and it didnt do any damage. The overclocking on snapdragons is more of a wait and see as no one has overclocked a snapdragon for that long but its HIGHLY unlikely that it will kill your cpu that quickly (ive been overclocking devices for years and never seen it happen). Leo users dont need to worry about overclocking with setcpu as it hasn't been enabled in the kernel we are using so the only thing setcpu is good for is underclocking and setting profiles.

So once it is enabled in our Kernel that's when we should be worried? What's the worse that can happen?
Thanks for the reply.
Sent from HTC HD2 using XDA app.

HeavyComponent said:
So once it is enabled in our Kernel that's when we should be worried? What's the worse that can happen?
Thanks for the reply.
Sent from HTC HD2 using XDA app.
Click to expand...
Click to collapse
I dont think we should, people on the n1 have been doing it for months and i havent seen any posts of things going wrong and even if it is enabled in the kernel you can choose weather to use it or not via apps like set cpu

JJbdoggg said:
I dont think we should, people on the n1 have been doing it for months and i havent seen any posts of things going wrong and even if it is enabled in the kernel you can choose weather to use it or not via apps like set cpu
Click to expand...
Click to collapse
It will cause lower battery life!

hazard99 said:
It will cause lower battery life!
Click to expand...
Click to collapse
if you choose to use it.

JJbdoggg said:
if you choose to use it.
Click to expand...
Click to collapse
I know I use it to underclock. I was just saying. I actually use it as a means of making the battery last. and also the reaction time at which the cpu scales.

JJbdoggg said:
I used setcpu on my g1 (overclocked from 384mhz to 528mhz) for almost the whole time i had it and it didnt do any damage. The overclocking on snapdragons is more of a wait and see as no one has overclocked a snapdragon for that long but its HIGHLY unlikely that it will kill your cpu that quickly (ive been overclocking devices for years and never seen it happen). Leo users dont need to worry about overclocking with setcpu as it hasn't been enabled in the kernel we are using so the only thing setcpu is good for is underclocking and setting profiles.
Click to expand...
Click to collapse
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?

dbiggss said:
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?
Click to expand...
Click to collapse
A faster cpu is generally a speed increase and at certain points the gains are null. so its usually a small mhz boost.

dbiggss said:
So if I understand this correctly, setcpu does nothing to improve performance as far as Device speed?
Click to expand...
Click to collapse
it does, keeping the device at 1ghz (998mhz in our case) at all times will provide better performance than scaling from 245mhz to 1ghz. read here for more info http://www.pokedev.com/setcpu/

hazard99 said:
I know I use it to underclock. I was just saying. I actually use it as a means of making the battery last. and also the reaction time at which the cpu scales.
Click to expand...
Click to collapse
i use it for those reasons too

OC'ing SGS

Hi there,
I actually want to know if it is harmfull to OC your SGS to 1.2GHz. Ofc it's better to run stock but is it of any real harm and how do you OC? I had a quick test with Galaxy Tuner and I must say when I use my phone heavily 1.2GHz is better. So if this is safe and done easily I would like to do this . Thanks in advance!

Well that seems like a small overclock, so if you have setcpu to your minimum with screen off, it should be OK.
Sent from my SilverBullet "HTCDesireZ running CM7"

Alright and how long can i use my phone when its on 1.2? Also next to that my phone is in a leather case when not being used so cooling will be a bit harder. Some more information from other people plz? I just want a consensus . Thanks for the quick reply.
Sent from my GT-I9000 using XDA App

my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.

darkside748 said:
I actually want to know if it is harmfull to OC your SGS to 1.2GHz.
Click to expand...
Click to collapse
No one can say for sure what would happen when you push a chip beyond its design parameters. Not all chips are made equal. Usually the standard speed rating is what all chips passing QC should be able to operate at. However some chips may be able to operate at higher speeds without ill effects while others may fail catastrophically even with a slight increase in frequency. So its anyones guess...
Frankly I dont see the need to overclock right now. What ROM are you using ? Flashing to a newer / better ROM can give you a bigger improvement than what 200Mhz can give you on a laggy unoptimized ROM, so why risk it ?? .

minjiet said:
my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.
Click to expand...
Click to collapse
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
+1, charging and gaming at the same time is never a good I idea. They both heat up the phone greatly
Sent from my GT-I9000 using XDA Premium App

Hmm I'm running docs mod v9.9.5 XD with speedmod kernel and twlweaks enabled. So it pretty fast already however with the oc there is just less loading time. But you are saying that its useless?
Sent from my GT-I9000 using XDA App

minjiet said:
my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.
Click to expand...
Click to collapse
If you can oc, that means you root right! either that or droidclock/setcpu correct?

darkside748 said:
Hi there,
I actually want to know if it is harmfull to OC your SGS to 1.2GHz. Ofc it's better to run stock but is it of any real harm and how do you OC? I had a quick test with Galaxy Tuner and I must say when I use my phone heavily 1.2GHz is better. So if this is safe and done easily I would like to do this . Thanks in advance!
Click to expand...
Click to collapse
it depends. i personally use tegrak overclock and for battery saving, i use overclockwidget. my sgs has been going for 2 days in a row with battery life only at 48% even with moderate usage(making smses, playuing games occasionally, etc.)

Hmm alright, these apps seems legit. What are your settings with these apps? Or should I use setcpu?

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
If the phone reaches a certain temperature, the phone stops charging, so i dont think playing a game and charging at same time is the culprit.
Granted that the phone would heat up A LOT quicker than usual, but being so hot, the phone wouldnt of been charging even with the charger connected.
there is now way of knowing whether overclocking is dangerous. Personally i think it is, you have to modify the kernel, modify system settings, modify battery voltage.
None of this is recommended, but we do it at our own risk...
Its as dangerous as running a custom ROM or LagFix. some devices are fine, some brick and burn to a crisp.
So choice is yours

Hmm i guess ill be sticking to 1ghz then... thx for the replies!
Sent from my GT-I9000 using XDA App

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
i do the same for my x10 n the phone running just fine.
in fact, before i sent my i9000 to samsung for warranty claim, i pass the phone to a local shop, the tech told me the OC cause the board overheat, then burnt it....

darkside748 said:
Hmm i guess ill be sticking to 1ghz then... thx for the replies!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Actually tegrak oc works fine. ocing at 1.3 will crash first time but not crash anymore after the first time. ocwidget is not really useful for ocing but just to same battery life. when not really using my phone i will set it at 100mhz-400mhz. you can play angry birds on stock rom with little lag.

So you're saying i can oc.... but im running setcpu. I can OC with setcpu right? That brings another question when my screen is off what setting should i use for setcpu? In other words what is the minimum frequency?
Sent from my GT-I9000 using Tapatalk

100MHz is fine for the minimum frequency (for me at least) - this may vary between phones, give it a try.
On the subject of over-clocking though, you should take a step back and ask yourself "How much do I really need those few milliseconds less to load up Angry Birds".
I would suggest that Samsung did more testing than anyone on this forum.
All that said though though I take my phone up to 1.2 sometimes for ****s and giggles & to shut up smug iPhone fanboys

lamacow123 said:
Actually tegrak oc works fine. ocing at 1.3 will crash first time but not crash anymore after the first time. ocwidget is not really useful for ocing but just to same battery life. when not really using my phone i will set it at 100mhz-400mhz. you can play angry birds on stock rom with little lag.
Click to expand...
Click to collapse
No. Don't set set setcpu to anything below 400mhz because when the galaxy slips into idle mode it cn sometimes be difficult to wake up
. I'd imagine such a low clockspeed would encourage such behaviour. I set my minimum at 400mhz and max at 800mhz. Spot on.
my i9000..running gingerbread. perfectly.

jj03 said:
No. Don't set set setcpu to anything below 400mhz because when the galaxy slips into idle mode it cn sometimes be difficult to wake up
. I'd imagine such a low clockspeed would encourage such behaviour. I set my minimum at 400mhz and max at 800mhz. Spot on.
my i9000..running gingerbread. perfectly.
Click to expand...
Click to collapse
A bit off topic but gingerbread official or custom? And my phone works perfectly fine. No hard to wake up syndrome.

800mhz is enough

Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App

Yup, I agree with you

+1
I had a Milestone for 1.5 years on stock ROM (that is 550Mhz), pretty much served most of my needs perfectly....you know, the normal stuff you use your phone for.

I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.

synaesthetic said:
I rarely notice my phone is underclocked... with smartass governor, it's more responsive than stock clocks with a less responsive governor.
Battery life doesn't seem improved, but I know that my weak signal is causing the problem here.
Click to expand...
Click to collapse
I Sunni it's different for me.. When in use it seems to drain about the same but last night I set the phone down around 11 worth 84% battery life and got up at 6 with 78% still and that's setting the governor to smartass

It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.

synaesthetic said:
It's bad for me because my phone goes without signal about half the time in my apartment. I'll be moving soon so it's not a huge issue, but it is kind of disconcerting to feel my phone heating up from just sitting around doing nothing.
Click to expand...
Click to collapse
You could try disabling the governor and let one like, setcpu do it? Before I went Incredikernel I set up a profile in setcpu that whenever my screen was off it wouldn't run any faster then 128MHz but when on was set for either on demand or performance. Using two governors at the same time causes lag I've found so you'd have to be running a rom that doesn't already have one (that you can see and change) built in

Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.

kijp15 said:
Yea, this is true. OC'ing I thought it was giving me speed, but I actually took the time to really see the speed on OC'ing and to me it dosent seem to change. Well maybe alittle bit, but still. But yea, so I just hit 1ghz and I just leave it there.
Pete's latest w/Yennob-Base2 kernel at 1ghz and its going good.
Click to expand...
Click to collapse
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol

IAmTheOneTheyCallNeo said:
Yeah I honestly can't tell a difference between running at 998 MHz and 1,113 MHz other than a physically hotter phone and faster battery loss lol
HTC-Incredible on Android 2.3.5
CyanogenMod-7 Nightly (8/18)
Chad's Incredikernel-GB #9 (SA)
Click to expand...
Click to collapse
Ahaha, yea. Everytime I would hit 1.3ghz or 1.4ghz for the fun of it, my phone would get that way too. It would get hot and it feels like it would explode in my face and yea battery life would drop like crazy.

Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.

No problems with overclocking: http://forum.xda-developers.com/showpost.php?p=16791637&postcount=124

Well the SuperOSR is only for nexus s.. If there was one for the ns4g, well then after reading that, I would be OC'ing like a maniac.

zorak950 said:
Personally, I find myself running into a wall with RAM more than with processor power. I really hope the next Nexus at least doubles it.
Click to expand...
Click to collapse
This. I'm really feeling the loss of RAM coming from a mytouch 4G. That extra 256MB really made a difference. Using juwe's RAM optimization script seems to help, though.

Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Sent from my Nexus S using XDA App

rentaric said:
Ehm, how can Ram be a problem?
Android is managing it itself and can't run out of it, usually.
Click to expand...
Click to collapse
Things get killed that you don't want getting killed, and when it starts to run low things slow down considerably. It's not that something won't run, but it may run badly, or cause other apps to close that you were multitasking on, which is inconvenient.

I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App

Skimp Killah said:
I average 16 hours with normal for me use, which is a lot of texting, Facebook, internet browsing, listening to music.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
How so? I normally get around 9-10 hours max with moderate use, also depending on the signal i get half the time.

I use netarchys latest bfs kernel with proton to undervolt all CPU frequencies to -20mv. And I have the CPU limited to 100-800mhz, with the on demand governer. With those 2 thing I get 15-16 hours everyday. I also usually let my batter get down to atleast 5% before charging.
Sent from my Nexus S 4G using XDA App

Skimp Killah said:
Quick, and great battery. Overclocking is pointless unless you play games on your phone, or care about your quadrant score.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
it's true
i always Under clock the phone with SetCPU to save battery life

Old battery.

As batteries get older do they tend to run hotter? Or just make the phone hotter in general? I remember the phone running pretty cool in the beginning now it gets quite toasty from time to time.
Sent from my HTC Vision using xda premium

Do you use it more? Changed any CPU setting? I am also inclined to think that they would run hotter as they get older
Sent from my SilverBullet 'HTCDesireZ running CM7'

yes i think they run hotter and they hold less of a charge so you will see a decrease in battery life

evilcuber said:
yes i think they run hotter and they hold less of a charge so you will see a decrease in battery life
Click to expand...
Click to collapse
this is true...sometimes mine gets so hot i cant even hold my phone...no joke

smokeuout said:
this is true...sometimes mine gets so hot i cant even hold my phone...no joke
Click to expand...
Click to collapse
whats the temperature on your battery? are you overclocked?

smokeuout said:
this is true...sometimes mine gets so hot i cant even hold my phone...no joke
Click to expand...
Click to collapse
Well thats not good whether your battery is brand new or a couple years old. Are you OC'd? If so, do you run temperature profiles? How long / hard do you use the phone before it gets that hot?

Any li-ion battery will eventually be useless over time. My phone has always run very hot when using gps(rooted with oc's and all that jazz or unrooted).
Sent from my HTC Vision using XDA Premium App

Spastic909 said:
Any li-ion battery will eventually be useless over time. My phone has always run very hot when using gps(rooted with oc's and all that jazz or unrooted).
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Mine also gets hot when using gps

evilcuber said:
whats the temperature on your battery? are you overclocked?
Click to expand...
Click to collapse
yeah im oc to 1305 an it really only happens when im playing a game and charging at the same time....but battery temp always stays in the green and batt health is good ive had it tested before

smokeuout said:
yeah im oc to 1305 an it really only happens when im playing a game and charging at the same time....but battery temp always stays in the green and batt health is good ive had it tested before
Click to expand...
Click to collapse
well thats to be expected. remember the phones default clock speed is only 800mhz, so with that big overclock+gaming+charging you shouldn't be surprised to get a hot battery.

Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?

ohgood said:
Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?
Click to expand...
Click to collapse
ive been oc at low levels and extremely high levels and i found a spot where it seems i get the best all around performance....each phone will vary but you should try oc to higher levels if u havnt yet...careful around 1497 though, my phone just gets weird

ohgood said:
Never seen a g2 get hot to the touch myself. The battery warms when discharging heavily, but not hot. What's the point of overclocking past 1024mhz ?
Click to expand...
Click to collapse
Mine would get warm to the touch using it heavily on the charger and overclocking to 1.2ghz or so.
Not sure why you'd overclock past 1ghz. I've never seen my phone bog down with anything at 1ghz. Some like to do it though. The usual level for overclockers is probably 1.2ghz. I personally keep it at 806mhz...

martonikaj said:
Mine would get warm to the touch using it heavily on the charger and overclocking to 1.2ghz or so.
Not sure why you'd overclock past 1ghz. I've never seen my phone bog down with anything at 1ghz. Some like to do it though. The usual level for overclockers is probably 1.2ghz. I personally keep it at 806mhz...
Click to expand...
Click to collapse
so u dont see much of a increase in speed when oc above 1ghz...i think i might mess around with the numbers again just to make sure....thanks for the tip

smokeuout said:
so u dont see much of a increase in speed when oc above 1ghz...i think i might mess around with the numbers again just to make sure....thanks for the tip
Click to expand...
Click to collapse
Well I'm sure if u run benchmarks you'll of course see better performance at higher clock speeds. I'm just expressing that in my uses, I've never seen any reason to clock past 1ghz, not to mention the increased battery drain of overclocking in most cases
Sent from my CM7-powered T-Mobile G2

Somwletimes custom roms includes a different kernel that are already overclocked. Some people tend to missed this.
Sent from my HTC Vision using Tapatalk

Battery truth. Our assumptions are wrong. Probably

http://www.xda-developers.com/andro...ry-study-brings-about-surprising-conclusions/
Sent from my SCH-I500 using xda premium

hmm very interesting

If you read through the whole thread you'll see that much of his research is still inconclusive. For instance, his assertion that undervolting does nothing for battery life.

k_nivesout said:
If you read through the whole thread you'll see that much of his research is still inconclusive. For instance, his assertion that undervolting does nothing for battery life.
Click to expand...
Click to collapse
Hence the "probably" in title.. But his work does show that undervolting does not give a gain large enough to justify pushing uv to its limits, and for people to pull their hair out stressing over weather they should uv to -100mv art the 100mhz step or not. It's just not worth it. People should be more concerned about stability. And of you want REAL gains, put a black wallpaper on your homescreen and find all the black themed apps you can. As this is a much bigger gain for battery.
Sent from my SCH-I500 using xda premium

neh4pres said:
Hence the "probably" in title.. But his work does show that undervolting does not give a gain large enough to justify pushing uv to its limits, and for people to pull their hair out stressing over weather they should uv to -100mv art the 100mhz step or not. It's just not worth it. People should be more concerned about stability. And of you want REAL gains, put a black wallpaper on your homescreen and find all the black themed apps you can. As this is a much bigger gain for battery.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Agree 100% with this!

Or get one of these xD
http://www.thinkgeek.com/interests/dads/ceca/
Sent from my SCH-I500 using xda premium

I have noticed that I get much better battery life on the ICS Roms after I run down the battery and fully charge a couple of times.
I am also using V6 Supercharger. I can't tell if this is helping or not but it seems to extend my battery life.

bedalus said:
Coming soon, a more thorough test of deep idle and undervolting, thanks for the ideas from OCedHrt. Please ignore points 1 and 2 until the results are completed. [Q] when's that? [A] soon enough [Q] that's not soon enough? [A] Is that a rhetorical question? [Q] Is this? [A] Yes.
Summary of Results
1 - PENDING FEEDBACK FROM OTHERS--- The main shock was that Deep Idle did not work as intended. There are three forms of Deep Idle: the CPU Idle backport from kernel 3.2, Eugene's Deep Idle, and Ezekeel's. All three were tested, and no battery saving was measured. I also tested Deep Idle in Carbon (Jonathon Grigg's ICS themed Oxygen 2.3.1, android version 2.3.7, gingerbread) using Ezekeel's last kernel for gingerbread, and that showed no battery saving either. With the option for 'Screen Off Maximum Frequency' set to ON, the battery drain was higher (both in ICS and GB). --- PENDING FEEDBACK FROM OTHERS
2 - UNDERVOLTING---Everyone can safely ignore my earlier conclusions about it having no impact, because it looks like once you fix the CPU to a certain frequency, changing the voltage doesn't work. For some reason, it needs to move to another frequency, then back to the frequency you changed the voltage for. I will retest UV with this in mind, and should be able to produce accurate results for the battery savings offered. This is my next priority.
Click to expand...
Click to collapse
Taken from the 2nd post of the thread linked to.

Hm.interesting
Sent from my SCH-I500 using xda premium

I think undervolting helps.
At least I thought so
Sent from my SCH-I500 using XDA App