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.
I know overclocking is all the rage for more performance. I myself would prefer the gains of overclocking (probably wouldn't be 1.7 ghz atm since that is the performance based kernal, but 1.5 ghz might be doable) with a combination of undervolting for longer battery life.
I know when I was considering a viewsonic gtablet, that most of the kernals that overclocked also undervolted at the same time (how much depended on the kernal and how much of an overclock too).
Advantages to overclocking are pretty obvious, more performance. Undervolting makes the processor (this case SOI) run off of less power, thus more battery life (can be significant if undervolted enough) and less heat, which translates into a tablet that potential has a longer life (heat overtime wears away at life of SOI/processors and sometimes other components), plus much lower risk than overclocking. I undervolt all my laptops, I mostly get my laptop with 3 hour battery life to 3 hr 30min or even 3 hr 45 min on a moderate undervolt. A little undervolting could take this tablet from 8-9 hours to possible 11-12 hours of battery life (plus a little overclock included will add some performance too).
Do any of the present kernals out there try this? If not, I would like to make a request for such a kernal.
Undervolting might cause the TP to be unstable and crash.
Sent from my MB860 using XDA App
neer2005 said:
Undervolting might cause the TP to be unstable and crash.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
it would need to be done in small increments just like overclocking. Same methods are used undervolting as you would overclock. Yes they could both cause instability, if you double the clock speed or cut the voltage in half, it takes time to know the limit of the SOI by using small increments.
You will need to your favorite custom kernel and adjust the volts yourself using Govnah.
But then I also was reading on forums on webosbuzz and you can have screen wake issues to with undervolting
Metalshadowx2 said:
But then I also was reading on forums on webosbuzz and you can have screen wake issues to with undervolting
Click to expand...
Click to collapse
Really? If that is true, I wonder how undervolting would cause that.
The webos-internals-testing kernels include initial experiments with undervolting.
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
Hello. I'm looking for troubleshooting advice. My son is home for Christmas, he likes the ROM I put on his S3, Beans build 6 JB, It was installed with a full wipe with the latest KT747 kernel, the Touchwiz version. He was getting terrible battery life on his kernel so two days ago I switched to KT747 to see if it improved.
The maximum speed is under-clocked to 1026 for better battery life, minimum set to 192. For governor I've been rotating between on demand, Wheatley and Conservative, modified using ktweaker. Checked all else, polling frequency, options, killed some more bloat with TB. Screen brightness is set to lowest. Problem is he is still getting crummy battery life. Radio is off as he is roaming, just uses wifi when home. Voltage set minus 25 across the board.
I have an S2, and when I use CPU Spy I almost never see the full CPU speed being used, most time in state is the minimum, or somewhere between minimum and 1026, and only occasionally the maximum 1026.
Yet using CPU Spy on my son's S3, the time in state is either deep sleep, minimum or maximum. It's like the governor is not... well... governing. Also using built in battery tool, Android OS is far and away the biggest consumer of power, we'll below screen.
Anyone suggest what may be happening, why the CPU states seem to be either full or minimum?
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