Database Develop

Nexus 4 Undervolting

I've always been a big fan of undervolting. These are the lowest voltages I can get stable at these common speeds. I found I can underclock the Matr1x kernel further than some others I have tried for some unknown reason. How low have you been able to go? Also, what programs do you use to test stability? So far, I have been running Antutu test completion as a measure of stability. Any suggestions otherwise?
288MHz - 650mv
1.02Ghz - 800mv
1.51Ghz - 1000mv
ROM: Bionic AOSP V3
Kernel: Matr1x 6.5

Noob question~ Why do people undervolt?

WarToilet said:
Noob question~ Why do people undervolt?
Click to expand...
Click to collapse
To increase battery life,

The Long answer is that the CPU has a number of parameters where Clockspeed (MHz) and voltage (mV) are two. Clockspeed, well that is speed. Voltage is related to the amount of energy provided to the cpu, undervolting means that you feed the CPU less juice but demand that it runs at the same clocks. You are essentially starving the CPU,it uses less energy, but can become unstable if the voltage is insufficient to maintain operations. Manufactures always have extra voltage as a safety margin so power users can check their CPU bin (slow, normal, fast or faster) and lower voltages step by step until they crash the phone during a stress test, increase the voltage slightly and boom, your phone uses less battery power while being just as fast.

I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.

estallings15 said:
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
Click to expand...
Click to collapse
Took words from my mouth. This this and this. It reduces heat, which in turn reduces battery use. UV by itself doesn't save a lot of battery, it's the consequences of it. I'm normally not a fan of UV, but with current N4 sw/fw it NEEDS it. It's way too high.
Interesting observation. As of recently my phone jumps up by 3-5c from 37-38 hover. Never used to do it before, not until i got it up to 50c for about half an hour last week. Previously it would stay steadily at 37-38, now it spikes up now and again during use. What's interesting about is that once it goes over 40c battery use increases drastically. So i wonder if people that have really good battery life don't have phones that go over that temp often and vice versa.

I haven't played around with the values too much yet, just a -100mV across the board. This seems to work just fine, so I might experiment some more..
Using Franco test-r69 at the moment.
Sent from my Nexus 4 using xda premium

I undervolt to prevent heating like others say. My Antutu scores drop like a rock when I'm at stock clockspeeds mostly likely due to thermal throttling. Now I can run it repeatedly without having scores drop. It saves battery and runs faster while running games even for very short periods of time, so I am a big fan of undervolting. :good:

Undervolt to reduce power usage, think of the stock voltage as normally being more than is required, think of running for a bus yet you have 2 minutes why waste energy when you can walk and still make it .
Undervolt for less power usage and less heat produced meaning battery performance is better (cooler battery is a more efficient one) and performance is up as you avoid any thermal limits in place .
Great stuff undervolting, I have managed to get -150mV across the board ( 1.5ghz @ 1000mV) and 288mhz is 162.5mV .

I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The more the heat, the faster the battery drains. Since undervolting decreases heat, im sure it should increase battery life. Maybe not for browsing or calling, but playing a heavy 3D game.

is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...

zakoo2 said:
how can you guys undervolt? is there an app for that? i bought Franco's kernel updater app, but there's no option to undervolt in there.
edit: just found an app called setcpu, is that it?
sent from my Nexus 4...
Click to expand...
Click to collapse
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2

aimcr7 said:
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm familiar with undervolting both on PC and on phone, but i had a Motorola defy before my nexus and undervolting there was a bit different.
sent from my Nexus 4...

zakoo2 said:
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
Click to expand...
Click to collapse
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.

italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Former nexus s user here, the reason nexus s didn't benefit in battery life much was that it only had 1 core, and used a higher nm manufacturing process, 65nm -> 28nm. Lower voltages in the 28nm means that it multiplies the heat/power savings more than a 65nm, and the 4 cores multiply the savings by up to 4.

FatalityBoyZahy said:
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
Click to expand...
Click to collapse
don't know, it was just there. did you try to reboot after installing the app?
I'm on Franco's kernel btw.
sent from my Nexus 4...

Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium

I am new to this and my battery goes +40°C when I play simple games... I am running Franco's kernel r71 should I do UV? If so how much? Thanks in advance
Sent from my Nexus 4 using xda app-developers app

xtremer92 said:
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
this is the lg nexus 4 forum.
sent from my Nexus 4...

Undervolt/Overclock Captivate...

What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.

RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.

Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD

I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.

PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

overclocking to 1200 mhz will made any difference ?

Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.

Overclocking the Nexus 4 - Benchmark of application load time = BIG difference

A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.

please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings

so overclocking makes things faster.. really? who would have thunk. and you just found this out?

my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.

zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.

So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?

well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?

sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **

gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **

If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.

No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.

zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100

is there any kernel that can overclock with 4.3?

Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:

simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?

Check the Development sections.
This thread makes my head hurt.

Question about CPU governors

I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?

Set cpu is working for me, I have the paid version though. I put it on performance governor and it held 1 core wide open at 2265. I then changed it to ondemand and the core dropped to 300. There's also a conservative, interactive, user space and power save governors. Search governors for explanation of each governors settings/purpose.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

kitsinni said:
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Click to expand...
Click to collapse
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.

@rbiter said:
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
Click to expand...
Click to collapse
so this may be a dumb question, but is 300MHz the lowest clock speed it can reach? I just installed Better Battery Stats on my Nexus 7 (2012) and it can get down to 50MHz. Just looking to conserve more battery. Thanks!

Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.

Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
That's not really an option for me. I often rock the phone with no case at all and like it in its 168g form. I already have 30-40 hour batterly life with 3-4 hrs of screen time. But I just noticed the lowest clock speed it 300Mhz and I think it can be lower!

Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
Yes! This is my solution. No worries when mpdecision gets stuck on 4.4.2 and stops sleeping cores, who cares?! Pry-Fi running continuously in War mode, booyah.

PimpYourKernel!! :D LG p880

Hi guys!! I was thinking about opening a thread where everyone can specify what's the better kernel setup, according to her/his own necessities, and share that configuration with all p880 community. Also, it can be submitted the relationship between the kernel and the ROM an user is running on the device, to compare performances and make each other more conscious about kernel tweaking. I think it's better to open it in general section, so everyone can write, without being scared by submitting something not related to developing.
This thread won't to be in any way a substitute of the "Battery life!" thread, so if anyone wants to post specifical results or screenshots about battery duration, please post them here:
http://forum.xda-developers.com/showthread.php?t=2478514
Said that, the idea is to post a message like this:
KERNEL: name of the kernel you are using
ROM: the name of the ROM you are running
SETTINGS: the kind of settings you applied to your kernel (example: Governor=interactive, Scheduler=Sio, Multicore Power Saving=2,CPUquiet=balanced, LP Core uV=-15 mV, MPU uC=+20, and so on)
GOOD: the benefits you experienced with your configuration (the more specific possible)
BAD: the badness you experienced with your configuration
Of course, if the thread begins to grow up, is recommended to read everything before posting a configuration too much similar to another which have been posted yet.
If you think this is a good idea, press thanks, if you want, and let's begin posting, otherwise report it to moderators, like @laufersteppenwolf, and they will close this thread as soon as possible
If someone like @JoinTheRealms is interested to, I'd appreciate very much to create a section dedicated to the scripts, as a second post of the thread, maintained and refreshed by the author.. Let me know, and take your own space here, if you think it's good for you!

So, I'm starting posting my own last configurations:
1)
KERNEL: iodak v9.95
ROM: Beanstalk 4.4.2
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=370 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-30 mV all frequencies, MPU uV=-75 mV all frequencies
GOOD: this configuration improve battery life, without decreasing overall smoothness - suggested to the users who don't mainly use the phone for hard gaming and want to find a compromise between battery durability and overall performance
BAD: some little lags, here and there, randomly happen - I suggest to apply underclock, before changing cpu freq voltage, because this configuration is good for 1300 Mhz undercloked device, but it may cause system freezes on some cpu variants, if you set cpu clock up to 1600-1700 Mhz (tested)
2)
KERNEL: iodak v10
ROM: Beanstalk 4.4.4
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=620 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-100 mV all frequencies, MPU uV=-100 mV all frequencies
This configuration is very battery friendly, more than the last one I was using on iodak v9.95. Nothing is slowing down, btw
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

Saved!

Lol, I'm using almost the same config.
Kernel: Iodak 9.9.5
Rom: Beanstalk 4.4.2
Settings: I haven't changed anything
Good: Very fluid and stable
Bad: battery life, Antutu 3D test score
Sent from my LG-P880 using xda app-developers app

Kernel: 9.95
Rom: CM11 official
Settings: Max Frequency 1150 Mhz Cpu governor:interactive
mpu undervolt -100 on every freq (cpu variant 2, some hangs while waking the smartphone and I need to tap on the screen sometimes, if I press the power button the device won't wake up anymore until I restart it).
Congestion: westwood
Cpu quiet: runnable
Cpu max screen off freq: 475 Mhz
Good: less heat, more battery life, smooth experience
Bad: If I put 1300 Mhz as max freq the battery life will decrease.. And without 1300 Mhz as max freq I feel like cutting this smartphone's cpu potential.
Still bad battery life even with these tweaks, still disappointed, but so far this is my best configuration with Cm11 official.

peppethustra said:
@JoinTheRealms reserve a post to yourself, if you liked my idea to dedicate some space to scripts explaining
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess

JoinTheRealms said:
The scripts i posted earlier, really shouldn't be take too seriously, mainly because they are written for ubuntu and require input. But when i get some time ill modify my post and give some examples of init.d scripts, or more specifically, the commands inside them. That should be somewhat more helpful i guess
Click to expand...
Click to collapse
Take the time you need, the thread seems beginning to live, so we'll read your post for sure, when you will bring it to evolution!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

Kernel: Optimus Play v2.53
Rom: CM11 official
Settings: Max frequency 1200 Mhz (sometimes I tried to put it at 1100 Mhz or even lower, 1000 Mhz, resulting in better battery life)
Congestion: cubic (since there's no westwood implementation in this kernel)
Cpu quiet: not implemented (I think it's put on runnable or balanced as standard)
Cpu governor: interactive
Multi-core battery saving: 1
Gpu frequency scaling: on
Good: awesome perfomances, the games and all the apps are very smooth and compared to the earlier configuration with iodak v9.95, this is very much better, but be aware that I'm trying to have perfomances and battery life balanced, and on iodak v9.95 I undervolted the cpu of -100mv resulting in some cases of hangs and crashes. Battery life is still good, but a bit worse than the iodak configuration.
Bad: Battery life's not very good, it goes harder on deep sleep when the display's off, iodak v9.95 is the best with deep sleep; in fact it takes a while before entering that state, it usually stays on low frequencies but it still consumes the battery.
An other aspect I noticed is that even when the smartphone is on charge, when I'm using it, it doesn't charge much, if ever it looses energy, which is explained by the very good performances of this kernel.
A small bug present in this kernel, and not in iodak, you usually need to double press the power button to wake the smartphone, but it's much better than risking to have your smartphone crashed while waking it up.
Overall: A very good kernel for performances, I don't know if it's the best but it's very good, battery life's "good" if not using the smartphone, otherwise it drains quite fast, I think faster than the undervolted configuration with iodak.
If you're looking for smoothness with games and apps I'd suggest this kernel, if you prefer battery life I'd suggest iodak more, but I remind you the hang problems on it if you decide to undervolt up to -100mv.
I tested both kernels with the same Rom and apps and use more or less, so I'm quite positive it's a good test.
I hope it helps and you can give us tips or suggestions to improve this smartphone's battery life, without losing perfomance. I think this is the thread's goal.
and yeah, every LG Optimus 4x hd possessor's dream is to have a good battery life so well, let's help each other and get the best out from this device, it's not **** yet in my opinion, it just really has a bad battery usage.

@KrisJoe Very good review! I hope many people will follow your example..comparing user's kernel usage and customizations is the better way to help everyone to find the needed configuration, and to let them make whatever they want, with their phone, on the best possible way
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.

KrisJoe said:
I just noticed something going back at iodak v9.95 to try peppe's configuration; on iodak v9.95 the temperature of the cpu is higher, there's a difference of at least 20° C more or less. Problem was that I went back to iodak because charging with optimus play v2.53 was a pain since instead of charging it wasn't. (Of course I mean while in use)
With iodak charging is flawless (I activated the fast charge option, which isn't present in Optimus Play).
Is it because of the fast charging option that's making the difference?
I'n trying the cpu undervolted by -75mv MPU and -30mv LPU, and it seems a bit laggier than the optimus play one, I can feel the difference just typing with the keyboard on the browser, but it's charging despite me using the smartphone.
What do you think it's the cause of the slow charge in optimus? And maybe more important thing, how is it possible that the cpu has a 20° C of difference between optimus and iodak but I keep the same frequency? I even undervolted with iodak, and in theory it should be the opposite situation, with iodak having lower temperature.
Click to expand...
Click to collapse
So, talking about charging, on iodak's kernel you have to consider two situations: if you are charging through USB port, you may experiment slow charging and battery consumption even while charging, if you use the phone in the meanwhile (so, using fast charge solves the problem, but it is recommended to do not use it too many often, if you want your battery to have a longer life)..the problem doesn't exist if you charge the phone through AC adapter, so the phone should charge at a normal speed, even if you use it, whit no fast charge necessity.
Talking about my configuration, yes, you may have some little lags, here and there, 'cause this is a battery saving configuration, more than a gaming performance one..
Finally, temperature: maybe the difference between the kernels is due to a different overall cpu voltage, or the temperature is not really precisely shown, honestly I don' t know for sure
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

I'm using the ac adapter and with optimus play charging was a bit hard and slower than with iodak. With -75mv it seems I don't have problems with waking up the smartphone and it seems a bit smoother, maybe a placebo effect, but I think that it could be the limit of undervolting with variant 2 cpus.
Now that I didn't use the smartphone for while the temperature is lower (49-51° C), the high temperature was due to the 1500 Mhz used at the beginning because I deleted cache and dalvik before installing iodak again (to avoid problems). Let's see how it behaves in these days, but I'm a bit confident iodak's config is better for battery saving, even though with antutu benchmark I did 13000 with iodak and, and 12800 with optimus play (with battery saving and performance balanced). It may be a wrong test but I still wanted to give it a try.

Yep, I tried to uV MPU frequencies at -100 mV, and it freezed my phone, after some seconds or minutes..so, I also think CPU variant 0x2 has this uV limit..maybe it's possible to uV a bit more single frequencies, without causing freezes, but I had not the time to try to individually uV any single frequency
Sent from my ME301T - Beanstalk 4.4.2 - Geass Kernel - using xda app-developers app

I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.

This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.

KrisJoe said:
I was thinking that we should specify what runtime we're using, if Dalvik or ART because I actually felt some differencies. What about you? Do you feel any difference with using one or an other? Sorry for the off topic, but I thought we could talk about the runtime also since we'll looking for the best performance/battery life.
O.T.: Don't activate ART Runtime on the latest cm nightly (3rd of April 2014), it will force close some apps like uicall, dialer, ecc. I had to return to dalvik by installing an older version in which ART was working... quite unconvenient.
Click to expand...
Click to collapse
Yes, everyone is free to talk about ART or Dalvik, of course, it's related to Rom customization, using or not using it! Personally, I'm not using ART, considering it's on an early, experimental stage, and I have no time to switch between the two runtimes, if something should go wrong with ART (I need this phone as my really daily driver, and I haven't too much time to experiment, ATM).. But every single accurate review, also explaining how runtimes work, with a specifical kernel and a specifical Rom, is appreciated here!
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

XxXDarknessXxX said:
This is the best thread ever guys.
I am using iodak 9.95 in Zaiben RC8.
Max 1000 mzh, interactive, no undervolting, Multi core savings 2
The only bad thing is that if i want to wake a the device it doesn't wakes for the first time and I have to press twice the power button.
Click to expand...
Click to collapse
Try multicore powersaving=1, and a little undervolt, you should have benefits in terms of smoothness, without losing battery
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.

ottomanhero said:
KERNEL: Iodak 9.5 (I know 9.95 is newest but I prefer 9.5 as I think it's performance/battery ratio is better.)
ROM: CM 03/30 nightly
SETTINGS(variant1): CPU max: 1500 lowest freq.: 620 screen off max: 475. GPU freq max: 564 mhz
MPU undervolted by -122 mV and LP core undervolted by -10mV but lowest freq. voltage is on default and max freq is on 1230 mV due to 564 mhz GPU freq. ART enabled and Multicore powersaving is set to 2.
GOOD: A lot smoother than 9.95 and with these undervolting I've done, it can survive heavy gaming without throttling.I can say this setup is the best for gaming if you've got variant 1.
BAD: Battery life is a bit worse compared to stock kernel.But with ART enabled it's difficult to notice the difference.Plus if you underclock to 1300 mhz your phone will still be smooth while giving you better battery life.
Click to expand...
Click to collapse
I have double press to wake bug with iodak 9.5 how did you solve it ?

CrazyWinner said:
I have double press to wake bug with iodak 9.5 how did you solve it ?
Click to expand...
Click to collapse
I use volume rocker to wake the phone up as a workaround.Easy to reach it with your midfinger once you have the phone in your hand.Plus you get to press the power button less, extending it's life.
Edit : Incase you didn't know official CM and most of the custom ROMs have volume rocker wake option in settings > button or under some other category.