ZeusTweak (CPU and voltage tweaks) - LG Optimus Black

I'm sorry, but i have already searched the foruns and i did not found any explicit answer, so here it goes.
I recently moved to Zeus v6.39 ROM and i would like to understand how the zeustweak works. I mean, in order to get battery life, should i raise up the CPU frequency (and how much is it safe to raise) and lower the voltage (and, again untill what value may i do it), isn't it so? Assuming i do it, which would be the consequences for my phone?
Thanks
P.S. - is there any way of changing the receiving/making call screen layout?

Don't change, just leave default 0
99% people of Zeus 6.39 getting best battery life. I am also using with same tweak.
Press THANKS button if helped..

The cpu frequency is the amount of calculations per second that the cpu can process so theoretically, the higher the frequency, the faster the ROM will respond. In actual fact the cpu frequency also determines how stable the ROM is and the higher you clock your processor, the more unstable it may be and the more battery it will use.
I would recommend for ultimate stability to leave it at 1000MHz but for negligible performance improvements max could be up to 1350MHz but the difference is minute.
Correct me if I'm wrong but the voltage tweak is the aggressiveness of the governor when ramping the cpu up or down (changing the frequency). The values below 0 indicate that the governor will ramp down the frequency which in turn saves battery life. Values above 0 will make the governor ramp down less aggressively and thereby increase ROM responsiveness and noticeable lag spikes but reduce battery life.
I hope that helps but don't quote me on it.
Sent from my LG-P970 using Tapatalk 2

In my test voltage tweaks works. If I set -7 i could watch the youtube for 4 hours, but when I set 0 I watched only 3 hours continuously. Someone do a test and measure power consumption on charger. With -7 drains about 30% less battery.
Sorry for bad english.

Related

[request, forum] setcpu configuration

Hello, anyone know how to configure setcpu to save the battery while maintaining a smooth flow of the phone?
I saw that we could create "rules": those who did, can you post your configuration.
Thank you
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
see this and I think should be added here. http://www.pokedev.com/setcpu/
Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
With this configuration, you save the battery?
If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?
Formel-LMS said:
If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?
Click to expand...
Click to collapse
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx
tcastel said:
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx
Click to expand...
Click to collapse
Don't hold your breath. Im being serious here. It wont last unless it sits in standby most of the time and then you're still pushing it.
Spend the 25$ extra and get a second battery.
2 DAYS?! Let me know if you are able to accomplish that somehow! I've tried everything; ROMS, Kernels, Juice Defender, SetCPU, anything you can think of and about the best I can get is 15-16 hours with moderate to heavy usage. I think I am actually going to buy a spare battery today.
.. that's not hard to do, 2days... even more.
Just stop all apps to update, stop auto sync, stop background sync...
you will be surprised*
I knocked down my cpu to 500 or so in all conditions, phone still feels responsive.
If you want two days, turn off 3g, turn off sync, turn off brightness. You'll not only get great battery life but a $600 dumbphone to boot!
this is what you need to do...
sleep/standby 245min 245 max cpu governer: powersave
charging 245min 883 max cpu governer: on demand
'normal': 460min 998max cpu governer: conservative
if u find that with normal use the phone isnt as snappy as it used to be, and this bothers u, then change the cpu governer back to on demand for the normal profile.
i've had amazing battery life since i tried these settings.
Also....some apps prevent the phone from sleeping so keep an eye out if ur battery is just literally disappearing!
Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.
djmcnz said:
Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.
Click to expand...
Click to collapse
yeah i heard about this but i have never encountered any problems. obviously its different for everyone but i would say try 245/245...if your getting too much drain with the phone on standby then use 245/576 with on demand governor.
Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
I do not see much difference!!
tcastel said:
I do not see much difference!!
Click to expand...
Click to collapse
To be honest everyone "thinks" you can see a night and say difference just by tweaking the clock's and installing more efficient kernels. You can't and wont.
Those things may save you 5-10% over the course of a day but don't expect miracles. If you look at your battery history information you'll see that the system and any CPU related item can become relatively low doing all the efficiency modifications yet the battery still poops too soon.
Now look at the display. Thats where it's all going and as far as I know there is nothing anyone can do about that on our side. I run with the display back lighting 100% OFF and it still shows at a HUGE portion of my energy use. ~50% and sometimes more.
The day we get more efficient screen technology is the day we will be able to possibly use these things for 2 days on one charge... Either that or more powerful battery technology.
You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?
ma1993 said:
You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?
Click to expand...
Click to collapse
Set a default scaling type that suits you, typically On Demand or Uberspace and then set up your profiles. All of your profiles can use the same scaling (mine do).
The set your profile priorities in the order you want them to apply, 100 is the highest priority. For example, you might want the phone to run with less overclock when the battery is low and you want this condition to apply all of the time then you would give it a higher priority than other rules so it always executes. A better example might be a temperature profile. If the phone is hot you want to clock it down and want this to NEVER be overridden by another profile then you would set this to very high (say 99) so it could NOT be substituted by another rule.

Best settings/frequencies for OC/UV Beater?

Hi there,
I'd like to overclock my IncS to 1,3 Ghz...
But I don't know the right settings.
Can you please tell me the right setting for best performance (e.g. oc to 1,3ghz) and best battery life?
thanks
does anybody know?
Set max to your desired, min to the lowest it will go and scaling to smartass.
I'm OCd to over 1.4 and no issues... UCd to 192 with smartassv2 governor
Sent from my Incredible S using XDA App
the best performance I have experienced in my INC is when I put oc / uv beater to the following:
wake gov: ondemand
wake mins: 245000
wake max: 1228800
Sleep gov: Conservative
my sleep: 245000
Sleep max: 691200
when I take a test in antutu nenchmark for I the following result.
score: 2729
If I clocked lower or higher, the result is lower
Overclocking depends entirely on your chip.
You should use whatever governor suits your needs.
I personally use ondemandx which speeds up on demand (as the name implies), conservative tries to keep the frequency as low as possible, interactive uses max frequency if min isn't enough, smartass is an improvement of interactive that keeps performance high while improving battery life (meaning there's little reason to use interactive).
You can find it in more detail here.
So basically, smartass if you want performance, conservative if you want battery life, ondemand if you want something in between. In reality though, I don't think you'll see much difference between them and I've seen no difference in idle power draws, so if you don't use your phone all that much, they won't be that different.
Once you've picked a governor, you should set min speed to 122000 (no reason to use any higher) and max to whatever you want. Your phone will probably crash or suffer from bad performance if you go over 1.5 GHz, but it varies a lot. Might happen even earlier.
Once you've found your desired performance level, you should start tweaking your voltages. You can do that under the UV profile. In there, you can adjust voltages at different speeds and the phone will automatically use them at whatever speed it's at. You should undervolt to increase battery life, so start by reducing all by 25 or 50 and then temp apply. Use it like that for a couple of hours and if it doesn't freeze, you're probably stable. You can either stop here or spend many hours tweaking it further, but that'll take many hours to get right.
This is my setting
Sent from my HTC Incredible S using xda premium
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Me4oKyX said:
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Click to expand...
Click to collapse
In my opinion, and I'm sure many others', Virtuous daemon is the best by far.
It comes standard in a lot of roms, and using the OC/UV beater
http://forum.xda-developers.com/showthread.php?t=1207546
it would have the best performance. I've set mine similar to yours and with this method, you can set the phone to underclock when battery reaches a low level

[Discussion] Overclocking vs Undervolting

Most people here probably knows that the higher the CPU clock speed is, the higher voltage the phone needs. Which means higher clock speed results to more battery consumption. This is very simple logic, and sure, in real life practice this theory is proven to be true.
One method that is usually used to gain better performance while not necessarily waste more battery is by overclocking and in the same time undervolting. Because there obviously is a certain level of voltage needed to run a certain clock speed, the normal practice is reducing the voltage level to a bare minimum level where the CPU can still run alright while raising the highest clock speed possible. Reducing the voltage too low usually leads the phone to shut off because there isn't enough voltage for the phone to run.
By following the theories above, we can conclude that to achieve the best performance while still considering battery life, adjusting the proper OC and UV level is needed. This is obviously only talking about hardware affecting tweaks.
We now know that the main factor affecting the overall performance vs battery life turns to be the clock speed itself. Now here comes the ultimate questions.
1) How does the phone handle its clockspeed?
2) Does the voltage level change according to; a) the current clock speed the phone is running at, or b) the highest clock speed set/allowed the CPU to go?
3) Does the highest clock speed set (OC) leads to necessary higher voltage, or does the voltage accostumize itself to the running CPU level?
The most logical answer to number 1 would be that the CPU changes its clock speed according to whatever is happening and needs to be done to achieve the best performance. So the clock speed will go up when there's lots of tasks, and go down again when there's little or nothing to do.
Number 2 and 3 I can't explain, but I hope after someone with enough knowledge explains how voltage level works, we can have an answer to the following case;
IF two same phones clocked differently, one at 1ghz and the other at 1.5ghz run the the same relatively simple task for a long time, will the lower clocked one noticeably save/waste more battery than the other one? Or will they consume the same amount of battery because they would most likely be running at the same clock speed (say, at 200 ~ 600)?
Hopefully we'll have a better insight about overclocking vs undervolting
silentmelodies said:
Now here comes the ultimate questions.
1) How does the phone handle its clockspeed?
2) Does the voltage level change according to; a) the current clock speed the phone is running at, or b) the highest clock speed set/allowed the CPU to go?
3) Does the highest clock speed set (OC) leads to necessary higher voltage, or does the voltage accostumize itself to the running CPU level?
Click to expand...
Click to collapse
I believe one would have to set each speed & undervolt up together if one scales the speed. I just run mine straight up at 1300MHz/1325mV all the time & set up profiles for screen off, charging, etc. I get wonderful speed & battery life.
Example:
1300MHz/1325mV
1200MHz/1275mV
1000MHz/1175mV
/800/MHz/1125mV
etc.
Each phone is different due to the variations in manufacturing.
The only way to really optimise your phone is to try all of the various settings and combinations of voltage/speed.
Set the phone to a given speed, stress test and try decreasing the voltage until you get crashes / errors. Then raise the voltage one level (or 2 if you are a bit paranoid) and that is the stable voltage for that speed.
Rinse and repeat for all other speeds...
Then set profiles in setcpu / pimpmycpu accordingly.
Job done.
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
countrycoyote said:
I believe one would have to set each speed & undervolt up together if one scales the speed. I just run mine straight up at 1300MHz/1325mV all the time & set up profiles for screen off, charging, etc. I get wonderful speed & battery life.
Example:
1300MHz/1325mV
1200MHz/1275mV
1000MHz/1175mV
/800/MHz/1125mV
etc.
Click to expand...
Click to collapse
I think you could lower your voltages quite a bit - eg Mine runs at 1.4GHz at 1.2V
Ok my friend... so... having designed a circuit for a mobile phone myself, I'll try to explain quickly what's the deal (tradeoff) between frequency and voltage.
A CPU/GPU basically is made out of MOSFET's (transistors). Lots of them! They act like capacitors. They have to be turned on and off. At a certain frequency. So, basically they are capacitors being filled and emptied at a certain frequency.
In practice, a capacitor being filled and emptied at a high enough frequency can be seen as a resistor. A variable resistor in fact, as you can see (more or less) here:
http://www.electronics-tutorials.ws/filter/filter_1.html
The thing is, the higher the frequency, the lower the equivalent resistance, because the amount of current keeps getting higher and higher. If the current value gets high enough the very tracks (you can think of them as wires) from the battery to the transistors start having a considerable drop in voltage (the resistance in these wires is supposed to be very low but it's not zero!). And if you have to much voltage drop on the wires the transistors don't get enough voltage to turn on/off.
So there you have it! That's the problem with overclocking. Voltage drop at the tracks (wires) because of increased current. You may also run into heat issues
Now, trying to answer your question, even at the same clock frequency a CPU that is processing stuff will use more energy than one that isn't "doing anything", because transistors aren't really changing state. But a CPU not doing anything at a lower clock frequency will waste less energy than another one not doing anything at a higher clock frequency, because energy is required to drive the clocking circuit itself. So it's very non-linear, you get the picture I hope
LarsPT said:
Now, trying to answer your question, even at the same clock frequency a CPU that is processing stuff will use more energy than one that isn't "doing anything", because transistors aren't really changing state. But a CPU not doing anything at a lower clock frequency will waste less energy than another one not doing anything at a higher clock frequency, because energy is required to drive the clocking circuit itself. So it's very non-linear, you get the picture I hope
Click to expand...
Click to collapse
This. This is the answer I was looking for. Thank you for the detailed explanation!
silentmelodies said:
This. This is the answer I was looking for. Thank you for the detailed explanation!
Click to expand...
Click to collapse
You're welcome!
Also, to complete the answer a bit more, lower voltage also helps with getting less energy consumption, because it takes more charge to "fill" a capacitor to, let's say, 1.3 V than to 1.1 V.

Zeus voltage settings

In Zeus 6.39 ROM
(Relaxed voltage interval to [-7,7], ZeusTweaker voltage menu. Now you can set 15 different voltage states from -7 to 7 (-87500 to 87500)).
The above are the features of Zeus ROM
I don't understand what it mean, for better features how much value to set?
If we select -7, what is the result?
And if we select 7, what is the result?
sekhar13515 said:
In Zeus 6.39 ROM
(Relaxed voltage interval to [-7,7], ZeusTweaker voltage menu. Now you can set 15 different voltage states from -7 to 7 (-87500 to 87500)).
The above are the features of Zeus ROM
I don't understand what it mean, for better features how much value to set?
If we select -7, what is the result?
And if we select 7, what is the result?
Click to expand...
Click to collapse
In short, a higher clock speed can require more electricity (voltage). More power = More Powerful = Faster
Lower voltages (undervolt) can cause instability at higher speeds, but can be used at lower speeds (such as at idle), resulting in a pretty aggressive power savings when the phone isn't taxed or idle.
Every processor has different tolerances to non-standard voltages and clock speeds. Your phone may vary, just because mine is stable at 1.5ghz (sadly it really isn't...), doesn't mean that yours will be.
Increasing power will also increase heat, which can decrease the lifespan of your phone. Take it one step at a time, use the phone for a day or so, than step it up a little more until you eventually find the highest level (hanging, locking, odd behavior), than dial it down a couple from there. In my humble opinion a 1.2ghz max clock speed at standard voltage is more than enough to give the phone some oomph.
For the undervolting at lower frequencies, same thing, do it a bit at a time, and dial it up a bit if you get to a point that it won't wake up, or locks up at idle or non-processor intensive tasks.

Concept noob idea for a governor

Hello all !
I was bored in school today so I've written a governor concept idea for quad cores. I'm not a dev AT ALL (for now at least, i'm studying many different stuff, hardware / code related too).
I have no idea if this is possible or if this is clever but I wanted to share it anway. If it gives idea to a developer, that's totally worth it, otherwise, well... I had fun doing it
It's called Progressive.
Progressive
The name of the governor says all. The idea behind it is to be «*progressive*». It means it doesn't unleash the full power when it's not needed. It goes progressively higher in freq with more cores. This should make the phone cooler and the battery better. The delay (3 sec ) is just a number, not sure this is really nice. Also, I'm not sure how the S4 handles temperature.
Max freq 1.5 Ghz
Min freq 384 Mhz
Screen off
=> 384-918 Mhz // not too low frequency to avoid reboot
Screen on without touching since 3 sec // always check after 3 seconds for changing the state
=> 384-1134 Mhz only one core online
Screen on touched
=> 594-1134 Mhz two cores online // bump the min_freq to avoid keyboard lag and to add a bit of butter
Screen on touched with a medium load of task // not sure how quantify this
=> 594 Mhz – 1.5Ghz two cores online
Screen on touched with a high load of task // i.e. Games
=> 702 Mhz – 1.5 Mhz four cores online // max power
We also need a thermal protection to avoid any damage, this should do the trick
If the temp is >= 80°C
=> Two cores online max_freq 1134 Mhz until it reaches 70 °C // not sure about the temp, this can be adjusted
If the temps is >=70°C
=> Let 4 cores being possibly online but lower the max_freq to 1134 Mhz
Click to expand...
Click to collapse
What do you guys think ? Is this even possible ? Good, bad idea ?
I hope you enjoy reading it as much as I enjoyed to writte it
doesn't it do this already?
Fissurez said:
doesn't it do this already?
Click to expand...
Click to collapse
I'm not sure how the ondemand governor on nexus 4 works. So I can't really answer, it's really a noob idea that poped into my head today
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance.
it could be a viable choice for those who go for battery life over performance. :good:
Nuu~ said:
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance
Click to expand...
Click to collapse
Thank you Sir, I understand better how mpdecision works now
Glad to see i'm not completely stupid lol

Categories

Resources