I'm on OOS + SPHINX and using kernel auditor I've set the big frequencies to max at 2803mhz and the big governors to Performance, little frequencies and governors are unchanged. Will it damage my hardware in any way?
I think not.. coz it's supposed to work that maxed out.. and the only thing that will be affected is the battery life..
santiagoruel13 said:
I think not.. coz it's supposed to work that maxed out.. and the only thing that will be affected is the battery life..
Click to expand...
Click to collapse
Okk thanks a lot bro
Not much of an effect as long as you didn't also set the minimum frequencies to max! (that will just eat up your battery and decrease its lifespan due to needing to recharge more often).
TBH, why are you messing with the CPU anyway? The 845 is so overkill for today's apps to the point where underclocking it to get better battery life is a very sensible thing to do especially if you're using Franco kernel.
Abd121 said:
Not much of an effect as long as you didn't also set the minimum frequencies to max! (that will just eat up your battery and decrease its lifespan due to needing to recharge more often).
TBH, why are you messing with the CPU anyway? The 845 is so overkill for today's apps to the point where underclocking it to get better battery life is a very sensible thing to do especially if you're using Franco kernel.
Click to expand...
Click to collapse
I'm on sphinx kernel thought
theandroidguy said:
I'm on sphinx kernel thought
Click to expand...
Click to collapse
That's... Not the point, my point was that the CPU is so powerful some Kernals under powers it to save battery without making a difference.
Abd121 said:
That's... Not the point, my point was that the CPU is so powerful some Kernals under powers it to save battery without making a difference.
Click to expand...
Click to collapse
Ohh I see, well setting it to performance was consuming a lot of battery while I was playing PUBG so I reverted it to default settings, getting 10hrs SOT
Related
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
I'm running Bullet 1.420 Kernal, what's a good setting for setcpu for profiles and such? I've been a vibrant rooter for a long time and never looked into it, thanks!
Sent from my SGH-T959 using XDA App
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
kaintfm said:
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
Click to expand...
Click to collapse
Oh okay, thanks, but what will happen if I put 1420 high and 100 min? Cause I want my Kernal to be free and not suppressed at the standard the phone puts, will that "free" it and will it kill battery faster? I hope you get what I mean, lol
Sent from my SGH-T959 using XDA App
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
kaintfm said:
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
Click to expand...
Click to collapse
Oh okay, and Overclocking OBVIOUSLY kills battery right? Ans would 1420 high, 800 min kill much battery?
Sent from my SGH-T959 using XDA App
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
kaintfm said:
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
Click to expand...
Click to collapse
Oh okay, that'll be it then I guess, I appreciate you answering all my questions when we both probably know I could've looked them up, ill be sure to thank you when I'm on a computer!
Sent from my SGH-T959 using XDA App
do underclocking/overclocking influence battery backup time?
Define battery backup time. Do you mean how long the battery last?
gaijinboricua said:
Define battery backup time. Do you mean how long the battery last?
Click to expand...
Click to collapse
If you mean battery life, under clocking will get you better battery life but less performance. Over clocking will get you less better life and better performance.
Sent from my SGH-I777 using xda premium
ariez4u said:
do underclocking/overclocking influence battery backup time?
Click to expand...
Click to collapse
Underclocking gains is entirely dependant on how you use the phone. If your phone spends most of its time just sitting around you wont gain anything from underclocking. On the otherhand, if you play a lot of games (CPU intensive) then underclocking will get you a little more game time. For things like texting, checking Facebook, etc, underclocking wont help much as your cpu doesn't spend much time maxed out anyways. On top of that, underclocking means it will take your cpu longer to complete tasks and therefore your cpu will spend more time at higher freqs to accomplish things it could've done faster at a higher clock speed.
Same goes for overclocking, you will only really see a difference if you play a lot of games or do cpu intensive tasks. Another area you might see higher battery consumption is by overclocking the MINIMUM frequency. This will affect battery even while going the little things. How much the effect depends on how high you go.
Neither oc or uc affect your phones stand by time.
Thank you dear for your detailed explanation
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
What about undervolting? Seems like a much more delicate operation of all things.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Skv012a said:
What about undervolting? Seems like a much more delicate operation of all things.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I haven't ever really experienced much battery life difference when undervolting. Then again I don't undervolt seriously, just lightly. There may be more of an impact when u do it hardcore.
Sent from my SGH-I777 using Tapatalk 2
I underclock 200-800 on demand gov and under volt a decent amt each phone is different how far u can under volt without sod but never set u voltage to set on boot or u mite get stuck but I notice a difference if I forget to apply voltage after a reboot I lose battery much quicker maybe I gain two more hours on my battery but I'm a heavy user with 5 plus hours screen time everyday
Sent from my SGH-I777 using xda premium
First off is this a good idea? can such small devices be over clocked in a safe way without risking damaging the hardware?
if yes which would you say was the best app for doing so?
Hi,
A good idea... maybe, maybe not... it depends on what you want... higher scores in bench?A shorter battery life?A very very hot device while browsing or gaming (if you run at 1.8Ghz for example)?A little extra power for some apps/games?
With overclocking a little (1.5/1.6Ghz) I noticied that some apps open a little faster and the genera UI is a little more responsive...
There is always a (little) risk to overclock our phones, generally due to overheat but also some CPU's can't handle high overclock.
For me I don't remember reading someone burn her CPU with overclocking but...
There are still some software protections before to burn a CPU (thermal throttling, CPU temp limit before shutdown, etc...).
Obiously the duration of life could be reduced mainly if you always run at 1.8Ghz with playing games... So the "safe" way would be no overclock or a little overclock like 1.5Ghz... For you to test and decide...
For the apps: SetCpu, System Tuner... there is a bunch on the Play Store.Just for the CPU settings I would say SetCpu.
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
I can't see the need on this device, I might experiment with uv, maybe even underclocking, but as above, super smooth on siyah, and Slim Rom
Sent from my GT-I9300 using xda premium
Talking about battery life i installed darkys rom 3 onto my i9300 and the battery life is already suffering a loss of maybe around 25%. In saying that over clocking will only cause me to lose even more so ill leave it for now
Sent from my GT-I9300 using xda app-developers app
I'm too running on slim ics and siyah kernel. Best battery life and performance!
GGSunny12 said:
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
Click to expand...
Click to collapse
Overclocking won't damage your CPU unless you set crazy voltages, or let it overheat. Also, it won't lose performance... that's crazy talk. Only if it overheats will it throttle, but that only happens on large clock rates like 1.8GHz or if you're in a hot environment.
I had my old LG GT540 overclocked with no heat problems mind that was only a 600mhz cpu, had it up to 825mhz.
But we already have a powerful cpu in this phone, foe now I don't see the need to overclock.
Sent from my GT-I9300 using xda premium
The best app depends a lot on your kernel and device. For example, for my Galaxy S2 the best OC was with TegraK Overclock.
With my Xoom CPU Tuner is still the best.
With the S3 I suppose CPU tuner would be alright as well, but I haven't had the urge to OC it, because I find SiyahKernel still quite unstable in the S3.
You need an overclockable kernel in order to OC your phone.
As for damages, it is hard to tell if they are permanent, but picture this: your battery will have to be recharged more often, because it will drain faster. Since batteries have a limited lifespan which depends on how many charge cycles they go through, the more often you discharge/charge them, the shorter their lifespan will be.
Also, there is no telling what kind of ill-effects the added heat can do to the phone. It may be totally harmless, but it may also affect the quality of the display, since the added heat will be right underneath the screen.
The lifespan of the CPU will be shortened: instead of being able to work well for 20 years, it will work well for 18, 17, 15, but more than enough time for us to already have replaced our S3 for organic, intradermal smartphones!
Im taking a poll on the average rezound user cpu frequency for development
bunchies said:
Im taking a poll on the average rezound user cpu frequency for development
Click to expand...
Click to collapse
lol... I would always underclock to the 1200Mhz range to save battery, or use the stock 1512 with a more conservative governor like Intellidemand, rarely ever overclocked and when I did it was just to test something or run a quick benchmark, never really saw any real gain to it at all, always thought it was better to lower the bottom end as low as you could get it to 96-192Mhz so that even if something kept it awake, it would barely be running.
Whenever I'm running "Intensive items" I sometimes overclock. Most of the time I try to underclock to save battery as ace said. Although Doesn't really save that much battery. I stay at stock 1.5GHz a lot though...
pball52998 said:
Whenever I'm running "Intensive items" I sometimes overclock. Most of the time I try to underclock to save battery as ace said. Although Doesn't really save that much battery. I stay at stock 1.5GHz a lot though...
Click to expand...
Click to collapse
True... Underclocking the top end doesn't do much, although if you can lower the bottom end, and undervolt some, it can make a big difference when sleeping.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
True... Underclocking the top end doesn't do much, although if you can lower the bottom end, and undervolt some, it can make a big difference when sleeping.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
O you're saying when sleeping. Holy crap YES!! It makes a HUGE difference. I run sense 5 a lot (running that right now) and the battery life on "sleep" is already great, but when I underclock like I did the other day, I forgot to plug my phone in that night, it was at 5% I woke up and it was at 4% 8 hours later only 1% lost. Of course thats on Snuzzo's funky kernel and underclocked, but DANG!!! NEVER seen my battery life that good. The 4% also lasted another 5 hours without use! Don't know how but it did. :laugh::good:
Depends what I'm doing, usually under clocked to save battery throughout the day. I used to record YouTube videos on my rez, I would over clock for recording and benchmarks, finding the perfect i/o scheduler, governor and clock speed to run stable was fun.
Sent from my ADR6425LVW
1728. Fastest mine goes without being unstable.
bunchies said:
Im taking a poll on the average rezound user cpu frequency for development
Click to expand...
Click to collapse
1728 all the time.
Sent from my ADR6425LVW using Tapatalk