[GUIDE] *19/8 UPDATE!* 4.3 RESULTS! N7 'Best' Kernel (Performance & Battery Tests)
A lot of people have been posting in these forums, "Which kernel is the best"?
I was intrigued and decided to work this out for myself and share it with the rest of the community.
This is not meant to hurt the makers of these kernels.
But FIRST, it is not a fact that there is a 'best' kernel. 'Best' is an opinion and everyone has a different opinion.
On the Nexus 7, I personally believe there is no 'bad' kernel and none of these kernels I have tested perform badly or lag heaps.
People still like to push their N7's as hard as they can though.
The Main 2 Features people look for in a kernel are:
Performance & Battery Life
Some people prefer performance over Battery, or vice versa, or an all-round kernel.
NEXUS 7
8GB
Paranoid Android AOSPAL 3.97
KERNELS
Kernel[022]JB4.3(1.60Ghz Quad)UV,CIFS+UTF-8,PowerHAL,Linux-3.x Hybrid]
by faux123
Ultimate Edition 22
[KERNEL][GPL][N7] franco.Kernel - r75
by franciscofranco
r75
[KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
[KERNEL] [3.1.10] [JB 4.3/4.2.2] [Purified Kernel r130] [Linaro] [07-08-2013]
by eng.stk
r130
[KERNEL] [GROUPER/TILAPIA] [4.2.2/4.3] OXYDO [3.2.49] [Linaro]
by sgt. meow
v7
[KERNEL][Grouper][JB 4.3] 3.1.12-XPerience-04 [12/08/13]
by TeamMex
v4
[KERNEL] Bricked-Kernel Grouper/Tilapia
by show-p1984
4.3 Stock Kernel
I will test another kernel if someone requests me too. I will not post other's results because they most likely have a different setup and therefore different results making it inaccurate.
NEW! 4.3 RESULTS
19/8 UPDATE
PERFORMANCE
Performance was tested with Antutu. Tested three times and averaged.
1.3 RESULTS
Kernels set to 1.3GHz max and used the default governor for the test.
1. M-Kernel: 13489
2. Franco: 13440
3. LeanKernel: 13298
4. Bricked: 13194
5. Oxydo: 13179
6. Xperience: 13139
7. Faux: 13122
8. Purified: 13102
9. Stock: 12903
MAX RESULTS
Kernels set to highest clockspeed, performance governor.
1. Bricked (1.6): 15339
2. Oxydo (1.6): 14938
3. M-Kernel (1.7): 14463
4. LeanKernel (1.5): 14343
5. Faux (1.7): 14155
6. Xperience (1.6):14147
7. Franco (1.3): 13440
8. Purified (1.3): 13102
9, Stock (1.3): 12903
BATTERY LIFE
Default Governor, 100% Brightness
Watching HD 720p Video on a Loop (MX Player Software Decoding) in a 10% range. The reason for this is not to kill my battery lifetime.
Max Freq at stock speed (1.3GHz)
1. M-Kernel:7 hours 5 minutes
2. Oxydo: 7 hours
3. LeanKernel: 6 hours 20 minutes
4. Franco: 5 hours 50 minutes
5. Purified: 5 hours 35 minutes
6. Xperience: 5 hours 30 minutes
7. Faux: 5 hours 10 minutes
8. Bricked: 5 hours 5 minutes
9. Stock: 5 hours
Max Freq set as high as it can go.
1. LeanKernel (1.5): 6 hours
2. Franco (1.3): 5 hours 50 minutes
3. Purified (1.3): 5 hours 35 minutes
4. M-Kernel (1.7):5 hours 25 minutes
5. Oxydo (1.6): 5 hours 10 minutes
6. Stock (1.3): 5 hours
7. Bricked (1.6): 4 hours 55 minutes
8. Xperience (1.6): 4 hours 45 minutes
9. Faux (1.6): 4 hours 40 minutes
OVERALL
Best Performance:
[KERNEL] Bricked-Kernel Grouper/Tilapia
by show-p1984
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
Best Battery Life:
[KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
Best Overall:
[Kernel][4.2.2] M-Kernel - a61[WiFi/3G]
by Metallice
a61
[URL="http://forum.xda-developers.com/showthread.php?t=1950858"][KERNEL] [ANDROID 4.3] LeanKernel: Minimalistic Kernel [V2.0, 8/2/13]
by azoller1
Version 2
[/URL]
4.3 Results
Nice! This should be a sticky to help reduce unnecessary threads about kernels. My only suggestion would be to run Quadrant 3 times and take the average number. Only because 3 runs will have different results every time
Sent from my Atrix 4.1.1
Best battery life can't really be determined since everyone uses their tablet differently i wouldn't even waste my time.
Sent From My Toro+ via White Tapatalk
I am testing several kernels here. The fastest for me so far is trinity, but the battery is draining really fast. I then tried the 1400 MHz trinity and things got a little better with a good performance in quadrant.
I am testing motley now and seems good but a little slower than trinity. Home screen doesn't look as buttery as in trinity. I will keep testing a little longer.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
Crap...i just had a reboot while using motley and started playing dead trigger. I returned to trinity 111 and it is definitely smoother than the others for me. Maybe it is because it is the first one i flashed and now when i try others, even wiping, something remains and the other kernels don't work right. Who knows....
Sent from my Nexus 7 using xda premium
ÜBER™ said:
Best battery life can't really be determined since everyone uses their tablet differently i wouldn't even waste my time.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
I was going to do a HD video playback test. See how long it lasts on each.
Sent from my Nexus 7 using xda premium
Can't wait for the battery life results!
Sent from my Nexus 7 using xda premium
I posted about the so called battery life screen shot thread in there thread.
the only way to really test battery life is to start with ful ly charged battery each day. 1 TEST PER DAY or charge cycle.
you will have to get a mathematical equation figured out first .it would have to be something like
cpu cycles x screen brightness x memory usage and s on divided by then another equation to determined battery pull watts im guessing
you would have to keep the first exact on each test device to determine the battery life ..
ok while typing this i have decided its way over my head and quite honestly not sure it can be done ..
HELP My brain now hurts ..
The best way to test CPU performance would be to make sure that all kernels are at the same exact core frequency max, and all cores enabled, on performance governor. Performance governor alone doesn't enable all cores, and benchmarks sometimes don't trigger all 4 cores as on either (it can, but not always, and that can lead to totally different numbers on different kernels).
Some kernels have higher max frequencies then others, some use the new CPU quiet driver and some don't (although this wouldn't really matter if all cores are forced on for testing).
Some kernels have higher GPU clocks then others, some have higher refresh rates then others, some have both higher refresh rates and clocks, etc.
Personally, the best way to judge a kernel is by what features are implemented in it for example, is it linaro compiled? Does it use the old hotplug method for CPU cores, or the new quiet driver? Updated WiFi driver? fsync toggle? Was it built with RNDIS drivers?
Quadrant isn't a stable means of benchmarking (run it 3 times in a row and watch those numbers change), but generally speaking, if the same kernel is compiled with linaro, vs no linaro, the linaro build would be faster (don't quote me on this). Not all those kernels are linaro that I'm aware of.
Also, Jay's buttery smooth tweaks, his fsync doesn't work on franco.Kernel. That kernel specifically uses a different command to toggle fsync, and unless that method was used, any I/O results would be void (basically comparing fsync kernels to non-fsync, where fsync would obviously dominate). And there is even the possibility the ROM you were using may interfere with CPU clocks and voltages unknowingly.
So with all that said, trying to find the "best" kernel, is going to take a bit more effort then just benching with Quadrant
And for my own personal opinion (no hard-testing done) I like franco.Kernel Stock clocks and voltage, fsync toggle, new CPU quiet driver and WiFi driver, works awesomely faux's kernel would be my second preferred kernel, only because lack of fsync control, and getting rid of the CPU quiet driver.
espionage724 said:
The best way to test CPU performance would be to make sure that all kernels are at the same exact core frequency max, and all cores enabled, on performance governor. Performance governor alone doesn't enable all cores, and benchmarks sometimes don't trigger all 4 cores as on either (it can, but not always, and that can lead to totally different numbers on different kernels).
Some kernels have higher max frequencies then others, some use the new CPU quiet driver and some don't (although this wouldn't really matter if all cores are forced on for testing).
Some kernels have higher GPU clocks then others, some have higher refresh rates then others, some have both higher refresh rated,
Personally, the best way to judge a kernel is by what features are implemented in it for example, is it linaro compiled? Does it use the old hotplug method for CPU cores, or the new quiet driver? Updated WiFi driver? fsync toggle? Was it built with RNDIS drivers?
Quadrant isn't a stable means of benchmarking (run it 3 times in a row and watch those numbers change), but generally speaking, if the same kernel is compiled with linaro, vs no linaro, the linaro build would be faster (don't quote me on this). Not all those kernels are linaro that I'm aware of.
Also, Jay's buttery smooth tweaks, his fsync doesn't work on franco.Kernel. That kernel specifically uses a different command to toggle fsync, and unless that method was used, any I/O results would be void (basically comparing fsync kernels to non-fsync, where fsync would obviously dominate). And there is even the possibility the ROM you were using may interfere with CPU clocks and voltages unknowingly.
So with all that said, trying to find the "best" kernel, is going to take a bit more effort then just benching with Quadrant
And for my own personal opinion (no hard-testing done) I like franco.Kernel Stock clocks and voltage, fsync toggle, new CPU quiet driver and WiFi driver, works awesomely faux's kernel would be my second preferred kernel, only because lack of fsync control, and getting rid of the CPU quiet driver.
Click to expand...
Click to collapse
Yeah. I know. I'm going to add a other features section. If someone else could do it that would be good. If not, I'll do it later.
Sent from my Nexus 7 using xda premium
bcvictory said:
I was going to do a HD video playback test. See how long it lasts on each.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Who JUST watches video... would be as effective as leaving it on a white screen for hours. Like I said there is no point and would just give false hope.
Sent From My Toro+ via White Tapatalk
Used Motleys 520 at first, probably still my favorite. Used trinity and both of clemsyns latest. Clemsyns elite 1.8 got too hot for my liking, I'm using the 1.5 UV right now and batteries not too great, but its very smooth. Trinity is smooth as well but Motleys 520 seemed to both perform better and give better battery life at comparable clock speeds to the rest.
So Motleys will be my daily, but I refuse to stop flashing!
this is very helpfully
thanx
Hey Guys! I have been running some battery tests over the last week. I'm finishing the results now. Show you guys soon!
Battery Tests are in the OP! Check them out, give your own opinion!
bcvictory said:
Battery Tests are in the OP! Check them out, give your own opinion!
Click to expand...
Click to collapse
Interesting... not what I expected.
They varied so much did you use all the same governor? Stock is interactive. All the same I/O? That is quite a difference a shocking one at that.
Sent From My N7 via White Tapatalk
ÜBER™ said:
Interesting... not what I expected.
They varied so much did you use all the same governor? Stock is interactive. All the same I/O? That is quite a difference a shocking one at that.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Yeah. I used interactive on all of them. Set the minimum at the lowest it could go and the max as high as it could go on each kernel.
bcvictory said:
Yeah. I used interactive on all of them. Set the minimum at the lowest it could go and the max as high as it could go on each kernel.
Click to expand...
Click to collapse
-_- that's not fair.... nobody uses the absolute high... redo... at stock frequency.
You can't tell which is best if they are not under the same circumstances. Obviously Franco is top because his only goes to 1.3 which is stock. While others are over clocked... thats unreliable.
Sent From My Toro+ via White Tapatalk
ÜBER™ said:
-_- that's not fair.... nobody uses the absolute high... redo... at stock frequency.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
All of them at 1.3GHz Max? Whats the point of overclocking then?
bcvictory said:
All of them at 1.3GHz Max? Whats the point of overclocking then?
Click to expand...
Click to collapse
For benchmarks... not battery performance.
So your telling me the benchmarks where at different frequencies too? Wow have you never done a science expierenment? You don't test under different variables... that's inconsistent.
That's like frying an egg at 100F and comparing it to frying it at 120F. Obviously the 120F will fry faster. Cmon man.
Sent From My N7 via White Tapatalk
ÜBER™ said:
For benchmarks... not battery performance.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Yeah. I guess... I was going to try Motley at 1.3 for fun anyway. See how I do...
Please suggest a way to maximize battery life while sacrificing performance(not too much of course).
I tried out various roms, one is problemish over another.
Kernels as well.
I'm on my 3rd full charge on my 3rd day of phone purchase so the battery should have regulated a little.
I tried AOSP by cile and the experience is great but not the battery, overnight 7 hours I dropped 27% of battery.
(greenify on + underclock to 1000mhz + pm.sleep_mode = 1)
Do recommend me a combo best for battery life.
(one needs a stable platform to stand on before moving on to development right?)
Ararargi CM 20130707 + Iodak v6 Kernel.
Trickstermod: CPU Quiet: Userspace
Max CPU Clock:760Mhz
Min CPU Clock: 102Mhz
Scheudler: SIO
FSYNC: Disable
Intelligence Dimmer: Enable
Fast Charge: OFF
Multi Prozessor Engery Saving: Disable
Here my Under volt Values:
The charge insane Fast. In 10 Min 10-15%.
The Phone drain is 1% pro 3Min (less us)
2 % pro 3Min (heavy use)
LG 4X HD - Better than a Smartphone
KiD3991 said:
Please suggest a way to maximize battery life while sacrificing performance(not too much of course).
I tried out various roms, one is problemish over another.
Kernels as well.
I'm on my 3rd full charge on my 3rd day of phone purchase so the battery should have regulated a little.
I tried AOSP by cile and the experience is great but not the battery, overnight 7 hours I dropped 27% of battery.
(greenify on + underclock to 1000mhz + pm.sleep_mode = 1)
Do recommend me a combo best for battery life.
(one needs a stable platform to stand on before moving on to development right?)
Click to expand...
Click to collapse
Cm 10.1 and eternitys kernel, underclocked to 1,3ghz. Really good performance and battery, i do recommend using nova launcher to, because cms stock trebuchet launcher is kinda laggy
Sent from my LG-P880 using xda app-developers app
Nemeziz 56th said:
Ararargi CM 20130707 + Iodak v6 Kernel.
Trickstermod: CPU Quiet: Userspace
Max CPU Clock:760Mhz
Min CPU Clock: 102Mhz
Scheudler: SIO
FSYNC: Disable
Intelligence Dimmer: Enable
Fast Charge: OFF
Multi Prozessor Engery Saving: Disable
Here my Under volt Values:
The charge insane Fast. In 10 Min 10-15%.
The Phone drain is 1% pro 3Min (less us)
2 % pro 3Min (heavy use)
LG 4X HD - Better than a Smartphone
Click to expand...
Click to collapse
jonteftw1 said:
Cm 10.1 and eternitys kernel, underclocked to 1,3ghz. Really good performance and battery, i do recommend using nova launcher to, because cms stock trebuchet launcher is kinda laggy
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Thanks you two.
I will test both out and compare! Then will report the best out of which.
I use SuperXE ROM with iodakv6 - heavily undervolted using TricksterMod.
Governor: Interactive
IO Scheduler: SIO or ROW
stock rom and iodak kernel. Using systemcleanup I converted maps, weather, lg keyboard etc to user apps and then greenify almost everything. Also a little undervolting and I see great battery life and performance.
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.