First off:
Rom:
Virus rom RC1B3
Kernel:
1.8ghz bolted BFS uv kernel
if you overclock, your battery life is less. more power = more usage
so, in theory, if you underclock, less power = less usage..
when I'm at work, I barely use my phone. Maybe to text or a call here and there..
So I wanted to improve my battery life as much as I could,,, I have SetCPU and I have the minimum at 350mhz and the maximum at 650 using the smartass governor when not in use.. Since this is underclocking, the battery life has improved drastically,, though is it safe? I don't see any reason why not, just though I'd like some input on it.
Yeah, you're fine. With the Smart-Ass governor you don't really need to underclock. It's called smart-ass for a reason. It will only use as much is needed. So when your phones screen is off not running any tasks, the governor will underclock itself.
Another thing to add is if you are using SetCPU, then you really do not need to set up any profiles that would underclock the phone if you are using smartass.
Related
I'm a litte confused about which governor to use.
By default this kernel uses conservative and it performs quite well. I would expect it to be less snappy, but the difference is very small. Especially scrolling through the home-screens etc. is fluid.
Now, interactive is supposed to be the new ICS default-governor and normally you would expect it to be sthe snappiest one. Anyway, with interactive scrolling through my home-screens is a little choppy... How can that be?
SmartassV2 seems to be good in an overall-view, but I'm not sure what to think about it, because I generally would prefer using a more classical governor.
What governor would you use on a stock-4.0.3-ROM with Speedy-7-Kernel if you don't use heavy apps or games, but want all those general apps (launcher, browser etc.) to rum really smooth?
Thanks
McDV
Hi,
i use lulzactive on my Nexus S.
If you use it with NS tools, it gives you more option to control screen off freq.
With that it has great battery life.
lulzactiveV2/sio is the smoothest for me. Anyways I don't know yet which is the best governor for the night when I sleep. Can I use powersave? When I don't use my phone it should stay at the lowest clock as possible.
Sent from my Nexus S using XDA App
personal experience: wheatley --> luzlactive --> lazy , best battery-performance balanced
Thanks for all your answers.
I've tried all those governors now and I think smartassV2 seems to be the one I will use for now.
But some other question: The kernel offers Live OC. It seems pretty clear what this is: All the speeds are increased by x%, including the bus-speed of 200Mhz, without increasing the voltages.
Lets say I just overclock about 10%, so the maximum-clock is 1100 Mhz, without increasing the voltage. Will I drain more battery than with 100% speed? And is there any visible advantage in overclocking just about 10% or won't I see or feel any difference at all?
I'm using the Faux Kernel on my Skyrocket. I'm using Set CPU for speed control, under-clocking for more battery life.
I head the terms UC, OC, UV and OC. When I use Set CPU, I assume that when I set maximum CPU speeds, I'm under-clocking. But what is under-volting? Is that different? Is there an advantage to doing both?
Harry
There is an advantage to undervolting you need either fauxs app or systemmtuner to do so.
Undervolting is giving the cpu less power and asking it to do the same amount of work it was doing before
Sent from my GT-P7500 using xda premium
That sounds a bit more dangerous in terms of doing damage to the phone or having reboots etc. when you are giving the circuity less power than it was designed.
For those who chose to undervolt for power savings, it is usually done in conjunction with under-clocking, or is it a one or the other type thing?
Not really, under volting is not as dangerous as over volting (used to also achieve higher overclocks). Over volting can actually damage hardware if you provide too much juice.
Under volting just reduces the voltage, if its not enough the app freezes or worse the phone reboots. If that happens, bump it up one more step (+12500) and you should be fine. Find where you can go low but still be stable (for me it happens to be -87500) you will save more battery.
Dixit
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
icenight89 said:
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
Click to expand...
Click to collapse
My exact setup. -100mV UV, and 1.188 gHz UC. Went from 100% to 0% in 1 day 7.5 hours with 3 hours of screen on time. No juice defender either. I think its pretty food. Using faux 009u, btw.
Sent from my SAMSUNG-SGH-I727 using XDA
Only issue I got with Fauxclock is that it saves the CPU clocks I set (say 1.298ghz max) but it doesnt actually save the voltage after a reboot. I look at the VDD table and its still stock.
So only way to get it to work is to manually edit the VDD table itself. Not sure if this is by default that fauxclock doesnt actually save the voltages after a reboot.
Dixit
Don't see fauxclock in the application store, sorry, Google Play Station.
Thats cause its not in the Google Play. Its a separate app at this location
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
Dixit
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Fauxclock has very basic CPU clock settings, it was created just for that faux compatible kernels so the original developer didnt spend weeks on it. It was just a simple and fast and effective GUI to set min/max clocks and also voltages (global scale). You can however set one other clock which is the "screen off" clock, but thats about it.
harry_fine said:
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Click to expand...
Click to collapse
they will, use one or the other. U can manually change global vdd table and use setcpu, or forego advanced profiles in setcpu, but u can't/shouldn't use both
FauxClock force closes on launch for me..
EDIT: Getting a Faux kernal fixed that. Wow I feel dumb.
Shadeslayers said:
FauxClock force closes on launch for me..
Click to expand...
Click to collapse
Are u using faux kernel?
Any tips or thread about how to manually change global vdd table so that I can use SetCPU for the profiles and adjust voltage manually?
Is there a risk to that? If I set it and the phone won't boot, it sticks!
use Gideon UV/OC script and change vdd as u see fit. If it doesn't work u can always flash Gideon stock back
icenight89 said:
use Gideon UV/OC script and change bed as u see fit. If it doesn't work u can always flash Gideon stock back
Click to expand...
Click to collapse
What exactly is the difference between flashing Gideon's script or just using FauxClock? Thanks!
fauxclock gives u dynamic min/Max and voltage control as per user settings. Gideon is pre-set and makes use of init.d script. u can change it, but every change requires a reboot
i use setcpu (and i believe i actually bought the donate version)...but lately, i've been seeing people recommended against using setcpu.
any reasoning for this? and what is the preferred alternative?
Sent from my Transformer TF101 using Tapatalk
I've used SetCPU since my phone. Work fine for me, no problems.
If it's working good for you don't worry too much
^what he said.
setCPU works fine for me too. I use it to change cpu speed when I am doing benchmarks and I haven't seen anything that indicates setCPU isn't working correctly.
I will say though, that I can OC my TF and I can't really notice a difference from just running at 1 GHZ...But I do see a difference in battery life.
So bottom line, I just leave it at stock speed and enjoy.
I use Systune app (also, lets you modify "nice" settings, io, etc), advanced test's over SetCpu demonstrated it's not optimized for sleep/awake schedules, so do not use it for sleep/awake frequencies
Setcpu works fine for me! I have used it on a Herotab C8 and some other phones.
nothrills is what I have switched to from setcpu as I didn't like when setcpu changed their interface.
I use No-frills CPU control and it works quite nice. It allows you to set min/max frequency, I/O scheduler as well as your governor. I use min 312, max 1600, I/O noop, and Ondemand for my governor and it runs quite fast! Ondemand, however, does increase your battery consumption but it is geared more for performance than battery life. Interactive also seems to be a good mix of performance and battery usage but I tend to go for pure, unadulterated power! ;-P...well...that would be the "performance" governor but...Ondemand is more practical :-D
Using no frills here. Simple and effective.
Hello All.
How is the battery life on the new rom ?
I have the 6.1.0 Rom and its killing my battery , any one has the same issue ?
Was trying to switch Kernel no luck ...
Honestly, best for you to judge for yourself since everyone's configurations differ.
Also, might be a bit early to tell since I don't think the ROM has even been released for a day which means most people may not have even used their phone enough to have an opinion.
biosize said:
Hello All.
How is the battery life on the new rom ?
I have the 6.1.0 Rom and its killing my battery , any one has the same issue ?
Was trying to switch Kernel no luck ...
Click to expand...
Click to collapse
Well, it all depends on how you configure the installation. What options did you choose?
For the one day that I have used Ordroid 7.0.1, I've been quite happy with the battery life.
SetCPU 1188 Max 192 min
governor ondemand
scheduler cfq
ordroid 6.1.0
Kernel 3.0.28-RCMIX
Base 11.69.3504.00P_11.22.3504.07_M
Build 1.78.401.2 CL58751
The ROM was released not very long ago. So there can´t be a right answer until now.
The Phone needs some "Complete empty" -> "Full charge" cycles to show the battery properly. A battery wipe is not the right solution.
Beside the CPU, GPU and stuff setting, lots of battery drain is caused by the synchronisation. So check if everything is really necessary.
Live background wallpaper need energy as well. So with some setup, you can bring your sensa to 1,5 days without surrender on anything.
With stock ROM it´s possible to get 2 days, but dont watch the screen to often ;-)
Well, I've figured that you can get maximum battery without much performance compromise if you configure it as:
Sweep2Wake {Yes (no capacitive backlight)} or {No}
ZRAM {No}
3DGPU Overclock {3DGPU OC disabled}
2DGPU Overclock {2DGPU OC disabled}
Governor {badass}
badass config {Balanced}
I/OScheduler {cfq}
Maxfreq {1566 MHz}
Minfreq {192 MHz}
Screen off max freq {486 MHz}
Keep the screen brightness at 35%. Switch off WiFi when not in use. Remove your HTC Sense account unless really required.
The lesser the number of accounts you have, the better it is.
Hope this helps!
Now its rebooting in a call
kgs1992 said:
Well, I've figured that you can get maximum battery without much performance compromise if you configure it as:
Sweep2Wake {Yes (no capacitive backlight)} or {No}
ZRAM {No}
3DGPU Overclock {3DGPU OC disabled}
2DGPU Overclock {2DGPU OC disabled}
Governor {badass}
badass config {Balanced}
I/OScheduler {cfq}
Maxfreq {1566 MHz}
Minfreq {192 MHz}
Screen off max freq {486 MHz}
Keep the screen brightness at 35%. Switch off WiFi when not in use. Remove your HTC Sense account unless really required.
The lesser the number of accounts you have, the better it is.
Hope this helps!
Click to expand...
Click to collapse
Thanks il do this when installing the new ROM
Any news guys ? Did any one tested the new rom for bat life ?
kgs1992 said:
Well, I've figured that you can get maximum battery without much performance compromise if you configure it as:
Sweep2Wake {Yes (no capacitive backlight)} or {No}
ZRAM {No}
3DGPU Overclock {3DGPU OC disabled}
2DGPU Overclock {2DGPU OC disabled}
Governor {badass}
badass config {Balanced}
I/OScheduler {cfq}
Maxfreq {1566 MHz}
Minfreq {192 MHz}
Screen off max freq {486 MHz}
Keep the screen brightness at 35%. Switch off WiFi when not in use. Remove your HTC Sense account unless really required.
The lesser the number of accounts you have, the better it is.
Hope this helps!
Click to expand...
Click to collapse
I configured the new ROM exactly like this .
Already did one full discharge .
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