Related
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
Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!
http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.
063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.
Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...
Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.
I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.
dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.
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.
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
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
tinye99 said:
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
Click to expand...
Click to collapse
It will definitely shorten the life of the battery. As for the phone itself I can't really say. I used to use my vibrant @ 1200mhz daily while running bionix 1.3.1. I never really noticed any wear and tear from the overclocking. If your phone runs warm while overclocking you should really consider running the stock voltages. Your phone may overheat and fry your cpu gpu with the high temperatures. So be careful when overclocking.
Meh i dont completely agree...
It will only shorter the life of your battery because the processor will draw about 20% more power which is very small compared to the like 20x more power the lcd takes up.. i dont think youll feel the difference.
The heating up i disagree with too since ive seen processors reach boiling point of water and continue to work.. thats not to say they all will but ive oced my phone to 1.6ghz to benchmark for several minutes and it never got above 41*... the battery heats up alot more when its charging than the processor does most of the time so i wouldnt worry tooo much about that.
Now as to whether the phones llife will lower... yes probably.. youre putting more stress on the processor than if you dont oc.. honestly tho, processors dont die very often so i oc all day as my daily runner, usually to 1.4ghz if my kernel will do it..
Up to you and honestly all of this is my opinion based on my available info etc.. hope this helps
sent from the xda app on my android smartphone.
I have mine Oc to 1.5 and no issues. 1.5 is the Max I would go.
Sent from my SGH-T959 using xda premium
Everything I have read says 1200 is completely safe. I run mine at 1460 with no issues. It obviously draws more battery but using Voltage control app you can adjust the level of battery.
Sent from my SGH-T959 using xda premium
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Like everyone else said, you ought to be perfectly fine with that value.
The highest I would go is 1500 though
kaiser_bun said:
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Click to expand...
Click to collapse
Lol, running an overclock on a phone seems a bit overkill to me...
Think about this.. How much copper is strapped up to your phones cpu?
Would you overclock your desktop on a stock cooler?
I feel sorry for the saps who buy phones second hand(especially after reading this thread). (hey wait a minute, that's me too.. Lol)
I never overclock anything.
Ever.
(learned my lesson with an amd Duron 733 back in the day)
Sent from my SGH-T959 using XDA