Anyone using SetCPU with favorable results for battery?
As far as I know there is no oc-kernel available yet.
Referring to battery life......
Ofcourse you can increase your battery life with using setcpu..for examlpe you chose ondemand governor and put your up threshold and/or your sampling rate higher. But this will make your device less responsive.
I personally lowered those values to increase performance, since the battery life on the one s is pretty awesome
Bump
Sent from my HTC VIE_U using Tapatalk 2
ossy1337 said:
Ofcourse you can increase your battery life with using setcpu..for examlpe you chose ondemand governor and put your up threshold and/or your sampling rate higher. But this will make your device less responsive.
I personally lowered those values to increase performance, since the battery life on the one s is pretty awesome
Click to expand...
Click to collapse
plz let me know which values u use =)
Related
Anyone using "performance" scaling for daily use while overclocked at 1.5 ghz?
If so what its your experience? Battery, stability, heat, force closes,...?
I just rooted and overclocked last nite and it is great, but Iam a little hesitant to go full "performance" for daily use. I love the speed but apprehend some risk. What is your experience?
Performance governor isn't really "scaling." In *nix OSes, performance governor just runs it at the maximum speed 100% of the time. There's usually absolutely no point in doing this.
If you're concerned with the performance of "on demand," just turn the "sampling rate" down in SetCPU's Advanced Tab. On my Nexus S, I find 30,000us with an 85% up threshold to be the best balance between battery life and performance.
Basically, just play around with the settings a bit. Performance is generally not the way to go, unless you're benchmarking.
Setting up treshold can be very important to make the device respond faster. I use 70% on my desktop Ubuntu because the default value (95%, definitely too high!) caused problems with HD movies.
either with setcpu or voltage control...would someone care to just explain how to use these apps.
I understand the governers, and I understand the min / max.
So If I bump that max up to 1400 or even 1600 and leave the minimum down...what exactly does that do?
If paired with on demand does it mean it will use as much processor as it needs to perform a task all the way up to the max of what I have it set to?
also, the thing that seems to confuse me mostly are the individual sliders you can adjust per frequency.
I know this is broad question, but I was just hoping someone wouldnt mind explaining this to me as best as possible...or at least dumb it down for me.
I have googled and searched, and really havent found clear answers to me personally to understand it.
thanks
I personally use voltage control extreme.
In regards to the individual sliders you speak of, I believe that those control how many volts the phone uses at each particular frequency. You don't want to turn the voltages down too low/high though because you can freeze your phone and have other problems.
I use the "conservative" governor and seem to get the best battery life with it.
By overclocking to 1400 or 1600 it allows for your phone to run applications, videos, etc. smoother, by using the remaining cpu capabilities of the phone's hardware. The drawbacks of overclocking are that it sucks the battery very quickly, it can cause the cpu to overheat, and can also decrease the life of the processor.
Hope that helps some!
So what is a safe top end? To run on a daily basis.
Sent from my SAMSUNG-SGH-I997 using XDA App
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App
Perpetrator said:
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App[/QUO
But doesn't overclocking cause the phone to heat up? I suppose it also depends on what temperature the phone is rated to safely run at too though doesn't it? Cause with increased temperatures I am pretty sure the processor's life could be impacted. But that is probably only if you overclock for a extended period of time.
I would suggest staying at 1.2 for daily use, but if you are doing something that requires a little more cpu you can just bump it up until you don't need it anymore.
Just my 2 cents worth.
Click to expand...
Click to collapse
I know that some ppl OC to 1.6 with ondemand gov and use that as a stable setting... others report problems, FCs, ... think it depends on individual phone.
Some stay at 1.4 to be cautious...
The UV section is where I hear a lot of dissenting opinion. Some say -100 across the board gives best battery/stability... others say voltage should be high toward 1600 and UV more as you approach lower frequencies... personally I find that a graduated setup is best but I am not an expert.
Just sayin' what I've read here.
So recently I've become too lazy to constantly charge my Captivate and began to experiment with undervolting/underclocking it. Has anyone found optimal voltage for battery life? I've currently got every step of 200mhz down 100 volts and underclocked to a max of 800mhz. I'm on Semaphore kernel 2.9.5sc.
freshlimes said:
So recently I've become too lazy to constantly charge my Captivate and began to experiment with undervolting/underclocking it. Has anyone found optimal voltage for battery life? I've currently got every step of 200mhz down 100 volts and underclocked to a max of 800mhz. I'm on Semaphore kernel 2.9.5sc.
Click to expand...
Click to collapse
There isn't a optimal setting as all phones act different. Testing is the best you can do.
which cpu governor are you running? that may have more effect than underclocking/undervolting on battery life.
user Stempox has a nice post on cpu governors here
http://forum.xda-developers.com/showthread.php?p=28647926
the screen on time and data/gps traffic, and apps that keep the phone awake, do more to effect power drain than other factors. so, if you manage those, and choose the governor that suits you preferences, then undervolting and underclocking aren't needed, IMHO.
you can tweak the governor settings with Semaphore manager, if you really want to do that too.
the thing is, you may end up keeping the screen on longer than you would at higher cpu speeds, which would counter any battery savings. also, undervolting can increase the error rate, which means further delays while phone is awake.
hope this is helpful in your pursuit of fewer charging cycles.
Sent from my SGH-I897
Finally figured out how to over clock my CPU/GPU on One X with CM11 KitKat rom. Bumped the CPU to 1809 (what I researched is stable) and GPU to 512. My Antutu benchmark score dropped from low 17k's to mid 13k?
Help please!! Could running Trickster Mod App interfere with Performance option in CM11....?
Trickster Mod isn't interfering with the performance, it just means your phone won't perform at its peak with those settings. Higher CPU/GPU clocks don't necessarily mean better performance, I've seen this through extensive personal testing. Dial the settings back to stock and increase the clock speed incrementally while testing after each increase, you'll reach a point where performance suffers, dial it back one notch and there you have your "peak" settings.
Unless you're doing some really hardcore gaming on your phone it's all pretty pointless. There's no advantage to overclocking in everyday use of the device other than to say it's overclocked, you just can't notice a difference, any noticed difference is more than likely a placebo. I actually underclock my CPU to 1242mhz to improve battery life and have zero negative response whosoever, no matter what I throw at it.
Sent from my Evita
I agree with Tim here. I'm running cm11 on power saver mode, and it runs just fine. A little slow opening and closing apps, but buttery smooth for everything else.
Sent from my One X using xda premium
Hai I'm wondering what's the best kernel for battery life is and if they're about the same which would be the best one
ninja85a said:
Hai I'm wondering what's the best kernel for battery life is and if they're about the same which would be the best one
Click to expand...
Click to collapse
There is no "best" kernel as each one will behave differently depending on your usage. Battery life is about trading performance for longer usage... If you don't like to tweak the kernel, leave it stock... the stock kernel and ROM are quite well optimized. Other wise if you don't mind tweaking, try any kernel, maybe start with Squid, and a conservative governor (like lionfish, conservative, or powersave), set the CPU minimum to 200Mhz, and the CPU Max Frequency 1094Mhz, even take a core or two off line if you want to get real crazy. Remember that to make a significant difference in battery you need to make a noticeable change in performance.
acejavelin said:
There is no "best" kernel as each one will behave differently depending on your usage. Battery life is about trading performance for longer usage... If you don't like to tweak the kernel, leave it stock... the stock kernel and ROM are quite well optimized. Other wise if you don't mind tweaking, try any kernel, maybe start with Squid, and a conservative governor (like lionfish, conservative, or powersave), set the CPU minimum to 200Mhz, and the CPU Max Frequency 1094Mhz, even take a core or two off line if you want to get real crazy. Remember that to make a significant difference in battery you need to make a noticeable change in performance.
Click to expand...
Click to collapse
Ah cheers