Related
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
How do you guys test the stability of your undervolts?
I have been setting Max & Min CPU Speed to the same in SetCPU, then changing the voltage in the voltage tab in SetCPU, and then if it doesn't crash straight away, running a quick Stress Test in SetCPU and then going down a bit more?
Does this sound reasonable? Managed to get 350Mhz down to 750mV and 700Mhz down to 900mV so far.
Stewart
Whoa, that's a he'll of an undervolt! I am running 1125, 1000, 875, 750. No rigid testing, but I like your method. How is it when going back to normal govener?
StuMcBill said:
How do you guys test the stability of your undervolts?
I have been setting Max & Min CPU Speed to the same in SetCPU, then changing the voltage in the voltage tab in SetCPU, and then if it doesn't crash straight away, running a quick Stress Test in SetCPU and then going down a bit more?
Does this sound reasonable? Managed to get 350Mhz down to 750mV and 700Mhz down to 900mV so far.
Stewart
Click to expand...
Click to collapse
I know all phones are different but try using those settings throughout the day with all of your apps. I have mine overclocked to 1.4ghz and have it undervolted at 1225, 1125, 1025, 925, 825. Anything lower than 925 and 825 for the lowest two and my phone would lockup in weird places. Example, Astrid would lock the phone after clicking the menu button and clicking settings.
Yeah I have had a couple of random lockups, however I don't know what voltage it was on when it crashed. Would I be able to pull logs after it rebooted to tell me what frequency it was running at when it crashed?
I have just added 20mV to both and see how that goes?
Still got to spend a bit of time on the other frequencies!
Sent from my Amiga 500 using Workbench
StuMcBill said:
Yeah I have had a couple of random lockups, however I don't know what voltage it was on when it crashed. Would I be able to pull logs after it rebooted to tell me what frequency it was running at when it crashed?
I have just added 20mV to both and see how that goes?
Still got to spend a bit of time on the other frequencies!
Sent from my Amiga 500 using Workbench
Click to expand...
Click to collapse
One other way you could test the individual voltages is to set the processor to 350mhz for both the min and max values and test it with random apps and run a stress test. Repeat with each value.
Hello,
Just wondering if anyone has experimented with Tegrak Overclock Ultimate's GPU optimization settings. It allows you to undervolt the GPU. Has anyone tried this and is there any benefit to battery life savings with this? I am playing around with the settings right now, so I'll post my results later. So far been able to undervolt the 267 mhz step by -75mv from 1000mv down to 925mv (900mv is unstable for me). And I undervolted the 160 mhz step by -150mv from 900mv down to 750mv. There is also a 200 mhz step I haven't played with. Perhaps keeping the GPU at 200/160 can yield potential battery savings when playing games because games drain the battery so fast.
Hm. I seem to be able to undervolt the 200 mhz step to 750mv as well. I'm going to run a 200/160 gpu setup at 750mv and see if I can save any battery playing Gun Bros and will let you guys know.
caaznkid said:
There is also a 200 mhz step I haven't played with. \
Click to expand...
Click to collapse
Really? I only have the 267 and 160 MHz clock settings available. Any thoughts anyone?
Oh, I have underclocked my GPU settings but only by a modest 25mV each.
There's only 2 steps, but u can change the clock between 160, 200, and 267
yep ... good results
Yep I've been experimenting with GPU undervolting and had some sucess. So I was methodically working downwards and testing stability... then i saw this thread and thought what the hell, right? I shot for lowest mv of 750 and it's rock solid at 200mhz.
Can confirm 750mv stable at 100, 134, 160 and 200mhz. 267mhz can't be undervolted that much.
I've locked 200mhz 750mz for both speed steps and left it at that. Phone has yet to display any instability in a couple of days of mixed use including gaming. Battery life better? Subjectively yes, mostly I notice phone doesn't get so hot playing Dead Space.
Power consumption scales down almost linearly with clock cycles, and exponentially with voltage (right?). So by my math GPU is using about 40% of the power it does at full 267mhz. I wonder what the TDP of the exynos 4210 is and how much the Mali 400 contributes to that, would give some idea of what battery life to expect. Since GPU sits idle a lot, I doubt it's a magic fix.
Such is the power of our phones I have to underclock the CPU and GPU quite far before any 3D game gets too choppy to play. 160mhz is more than fine for most.
Usually undervolting makes the most sense for power saving because a given computing workload takes a certain number of cpu cycles. But 3D usually tries to render as many frames as it can, with the exception of S2's 60fps frame cap. So slowing down the GPU to no more than you need might improve gaming battery life?
My SGS2 is a bit sensitive to undervolting although underclocking of CPU, so I'm happy be able to so agressively undervolt the GPU.
I'd be interested to know who else can just set 200mhz & 750mv and have it rock solid? If not, 200/800 or 160/750?
I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.
jyaworski said:
I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.
Click to expand...
Click to collapse
I had the same problem with Gunslinger, I decided to keep my phone on Rogue Stock EL29.
I've been able to drop my GPU Level 0 Clock to 160mhz and voltage to 850mv with out any issues.
I also keep my GPU 1 Clock at 100mhz and my voltage at 750mv without a problem.
Using noop of course.
Changing GPU clocks and volts doesn't help much.
Keeping your CPU Internal Voltage and Core Voltage -50mV and keeping it scaled 200-800 MHz will give you much better battery.
I think the effect would be more significant in ICS since ICS use GPU to render UI
I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.
Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium
Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X
If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.
Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.
Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.
I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
I've read many times undervolting isn't worth it.
Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.
I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse
I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).
Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?
Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.
Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.
I've been playing around with undervolting my Epic 4G with SetCPU and Voltage Control and have noticed that it does not crash if I force it to operate at one frequency -- apparently it is the switching from frequency to frequency at too low a voltage that crashes it. But what I'm seeing seems absurd -- I can overclock to 1200 MHz and set voltage to the 600 mV minimum and run just fine, so long as set the minimum to 1200 MHz as well.
I've run benchmarks with SetCPU and it definitely is running faster at the 1200 MHz setting. I am wondering if the 600 mV is "real" or if perhaps SetCPU and Voltage Control are misreporting what the CPU is actually running at.
I would think that half voltage would result in one quarter the power consumption, but I have not had a good opportunity to observe its battery life yet.