Hey all. Which ROM, kernel, and governor do you recommend I use on my N6? There are so many options that I figured I'd ask. Currently running Benzo ROM and the kernel it came with. Thanks!
"Best" ROM.
There is no such thing as a best ROM.* The question itself is ambiguous.* "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded.* You will likely be able to read about this in the ROM threads.* ROMs do not impact battery life.* The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel.* What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life.* Let's get this cleared up.* Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life".* This is actually wrong.* Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning.* The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings.* This is what we refer to as out-of-the-box settings.* The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance.* The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
rootSU said:
"Best" ROM.
There is no such thing as a best ROM.* The question itself is ambiguous.* "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded.* You will likely be able to read about this in the ROM threads.* ROMs do not impact battery life.* The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel.* What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life.* Let's get this cleared up.* Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life".* This is actually wrong.* Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning.* The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings.* This is what we refer to as out-of-the-box settings.* The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance.* The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
this. and its very well said at that.
Thanks for the reply root.... However, nowhere did I ask what the "best" ROM is, I totally disagree that the stability will be equivalent because there are AOSP ROMs out there that are all in alpha for 5.1, as well as stock ROMs that may have certain rather experimental things, with nightlies being released. I guess the goal of my query was to find out what people have set some of their variables to (ROM, settings, kernel, kernel settings) to get better battery life with minimal performance drop.
YevOmega said:
nowhere did I ask what the "best" ROM is
Click to expand...
Click to collapse
Its my generic answer. Copy and paste. But you asked for recommendations and that gets the same answer because other than semantics, there's no difference in the question.
YevOmega said:
I totally disagree that the stability will be equivalent because there are AOSP ROMs out there that are all in alpha for 5.1, as well as stock ROMs that may have certain rather experimental things, with nightlies being released
Click to expand...
Click to collapse
That's you're prerogative but I'm not really talking about feature sets. That aspect of the answer is more generic, usually for people coming from HTC or Samsung where "camera sux" because the binaries were never released.
YevOmega said:
I guess the goal of my query was to find out what people have set some of their variables to (ROM, settings, kernel, kernel settings) to get better battery life with minimal performance drop.
Click to expand...
Click to collapse
Performance uses power, which uses battery. There is no way to get more battery life back than the amount of performance you're willing to sacrifice. Its a direct correlation.
I can tell you my settings, but they're not magic. Everything I gain in battery life, I lose in performance.
Edit. I think a good thing to do would be to pick a kernel based on features, then speak to users of that kernel to see how they set it up
@YevOmega, please check post #5 of the stickied Q&A thread for details on this question.
Sent from my Nexus 6 using Tapatalk
YevOmega said:
Hey all. Which ROM, kernel, and governor do you recommend I use on my N6? There are so many options that I figured I'd ask. Currently running Benzo ROM and the kernel it came with. Thanks!
Click to expand...
Click to collapse
The answer depends on how many ROM/kernel/governor combinations there, because that is how many answers you are likely to get. Stock based are usually the most stable, and everything is likely to work the way its's supposed to while CM/AOSP ROMs will have more cusomization and tweaks but are often troubled by instability or things that are broken. Me, I'm on Stock rooted 5.1 for now, until I flash something else. What is it that's important to you when it comes to the ROM?
I want it to be crisp most importantly, but it's nice to have things like PIE. Minimal bloatware, because yes there are still some system apps that I don't want but can't uninstall without jumping through hoops.
rootSU said:
Its my generic answer. Copy and paste. But you asked for recommendations and that gets the same answer because other than semantics, there's no difference in the question.
That's you're prerogative but I'm not really talking about feature sets. That aspect of the answer is more generic, usually for people coming from HTC or Samsung where "camera sux" because the binaries were never released.
Performance uses power, which uses battery. There is no way to get more battery life back than the amount of performance you're willing to sacrifice. Its a direct correlation.
I can tell you my settings, but they're not magic. Everything I gain in battery life, I lose in performance.
Edit. I think a good thing to do would be to pick a kernel based on features, then speak to users of that kernel to see how they set it up
Click to expand...
Click to collapse
Again, please read my statement. I understand that I can't just get better battery life out of thin air. I said minimal performance loss, not none. There is a variety of optimizations and my hope is that there are combinations that will improve my battery life without compromising performance too much.
YevOmega said:
Again, please read my statement. I understand that I can't just get better battery life out of thin air. I said minimal performance loss, not none. There is a variety of optimizations and my hope is that there are combinations that will improve my battery life without compromising performance too much.
Click to expand...
Click to collapse
You've misinterpreted what I've said. There is no minimal. Its loss or its not. Its an direct correlation. If you want to save x battery you must sacrifice y performance. There's no magic, smaller z performance that still gets you x battery.
I didn't say you wanted to get battery out of thin air (perhaps you need to read my statement). I'm saying you want to get battery out of medium air, but I'm telling you that it only comes out of thick air.
Let me try something else.
To increase battery by 6, you must decrease performance by 6. There is no magic setting that will allow you to get 6 battery out of 3 performance. If you only want to sacrifice 3 performance, you'll only get 3 battery.
Break it down. What uses battery most?
-Screen
-Radio
-CPU
So forgetting screen and radio which are out of the scope of this thread, let's look at CPU.
CPU voltage is controlled by the kernel. The kernel has a table that has a predetermined amount of voltage for every clock cycle step. As you can see here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So how you save power on CPU is to either prevent certain CPU frequency being used, limit the time it is being used for or try to not need that frequency. This will save 6 battery, but will lose 6 performance because in each case that battery is being saved, the CPU frequency is not being used. Its a relative battery to performance ratio.
So I can list all the kernel settings that will save you battery, but they all have an equal performance hit - which is what I'm trying to explain.
Alright thanks. Go for it. I have vindicator kernel, as a reminder, so if you don't mind listing some settings, that would be nice ?. Thanks!
YevOmega said:
Alright thanks. Go for it. I have vindicator kernel, as a reminder, so if you don't mind listing some settings, that would be nice ?. Thanks!
Click to expand...
Click to collapse
I use elementalx, but here's some things I like to do.
1 set up threshold higher (99) CPU ramps up at 99% load
2 hot plugging set to 2 cores offline when not in use
3 turn off all touch boosts
rootSU said:
I use elementalx, but here's some things I like to do.
1 set up threshold higher (99) CPU ramps up at 99% load
2 hot plugging set to 2 cores offline when not in use
3 turn off all touch boosts
Click to expand...
Click to collapse
How much SOT do you get, and what carrier are you on?
YevOmega said:
How much SOT do you get, and what carrier are you on?
Click to expand...
Click to collapse
It depends. At home, I can get 6 or maybe 7. On a work day, perhaps 4 or rarely 5.
I live in the UK so not sure the Carrier matters.
YevOmega said:
How much SOT do you get, and what carrier are you on?
Click to expand...
Click to collapse
rootSU said:
It depends. At home, I can get 6 or maybe 7. On a work day, perhaps 4 or rarely 5.
I live in the UK so not sure the Carrier matters.
Click to expand...
Click to collapse
Carrier only matters if you are comparing signal strength in regards to the same bands. Kernels can also allow you to undervolt if you forgot, there are other things we can do such as drop voltage on certain parts of the device, though this can cause instability.
Optimizations on ROM and kernel side can reduce the overhead on the CPU and we can also increase throughput on several aspects of the device such as memory and BUS. Other things that "may" increase battery life could be removing code for rotational storage and using flash based alternatives/optimizing it for non-rotational storage.
Thanks. And yeah, I know why carrier matters
Related
Hello, here are some benchmark i made to test if some features being used in kernel development are usefull, useless, bull**** or make things worse.
HOW I DID THE TESTS
DEVICE= i9023.
ENVIRONMENT= fixed 25° Celsius.
OS= ANDROID 4.4.1 JRO03E Factory Image by Google.
SOFTWARE USED= 0xBenchmark 1.1.5 - AnTuTu Benchmark 2.9 - Screen Timeout Toggle.
OTHER TOOLS= A/C Charger / Standard Chronometer.
KERNEL= Kernels are built from source using the standard herring defconfig.
Additional notes:
The system is booted up once, every tutorial is closed, 0xbenchmark, Antutu and Screen Timeout Toggle are installed, airplane mode is toggled, system is rebooted in recovery, battery stats are deleted, cache and dalvik are cleared, system is nand backupped.
Every test starts after 30 min of phone off to let him cool, restoring the nand backup and waiting 5 min after system is booted up. Phone is connected to A/C charger.
Kernel are swapped after the nand restore.
Tests are done 5 times and then the average is calculated && till results are almost the same every run.
TEST N. 1
".. i use teh latest toolchain, mah kernel is imba ima pro !!111!1one!!eleven"
Google toolchain 4.4.3 vs Google toolchain 4.6
This test is inspired by an Ezekeel work that demonstrate how every different toolchain from the google base 4.4.3 used to compile our NS kernel resulted in 0 increased performance. Same goes for "optimized" compiler flags. You can see some bench here.
What i'm going to do is to test latest google prebuilt toolchain and see if it differs from above test.
- 0xBenchmark reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
Linpack [COLOR="Red"]18,81[/COLOR] 18,31
C [COLOR="Red"]21,65[/COLOR] 21,15
FFT [COLOR="Red"]13,92[/COLOR] 13,59
JSOr [COLOR="Red"]39,79[/COLOR] 39,14
MCi [COLOR="Red"]7,20[/COLOR] 6,60
Smm [COLOR="Red"]17,80[/COLOR] 17,45
dLUmf [COLOR="Red"]29,61[/COLOR] 29,17
- AnTuTu reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
RAM [COLOR="Red"]260[/COLOR] 257
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 105
GFX 2D [COLOR="Red"]278[/COLOR] 277
GFX 3D [COLOR="Red"]1115[/COLOR] 1111
TL;DR
USING LATEST GOOGLE TOOLCHAIN DOES IMPROVE KERNEL PERFORMANCE? NO
TEST N.2
"..undervolting teh lcd display MUST save battery!!"
LCD @ 3.0 V vs LCD undervolted to 2.4V
Same environment as before. Since % battery are not always accurate i made 3 tests:
2.1: let phone fully discharge, charge it up for 30 min. Boot it up, put max brightness and count how much time passes till it poweroff by himself.
2.2: let phone fully charge, boot it up, put max brightness and count how much time passes till it loose 10 points %.
2.3: let phone fully charge, boot it up, put max brightness and count how much time passes till it goes from 60% to 50%.
RESULTS
After days of tests, can pretty sure say that at the cost of 20% undervolt (from 3.0 to 2.4) there isn't any noticeable battery saving. What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
Remember these tests were made on a slcd panel not amoled.
Did i say these tests were made on an i9023?
Tests made on slcd i9023.
TL;DR
THERE IS ANY NOTICEABLE BATTERY SAVING UNDERVOLTING THE LCD?NO
TEST 3
".. ye ye but removing lot of crap makes mah kernel faster!"
Stock Kernel vs Config tweaked (debug and crap removed) Kernel
Removed all possible debuggers, governors, tv tuners radio and all unused crap.
Let's see if it's really better.
- 0xBenchmark reds results are better.
Code:
Stock Kernel Cleaned Kernel
Linpack [COLOR="Red"]18,81[/COLOR] 18,72
C [COLOR="Red"]21,65[/COLOR] 21,54
FFT [COLOR="Red"]13,92[/COLOR] 13,65
JSOr 39,79 [COLOR="Red"]39,85[/COLOR]
MCi [COLOR="Red"]7,20[/COLOR] 6,77
Smm 17,80 [COLOR="Red"]17,82[/COLOR]
dLUmf [COLOR="Red"]29,61[/COLOR] 29,54
- AnTuTu reds results are better.
Code:
Stock Kernel Cleaned Kernel
RAM 260 [COLOR="Red"]261[/COLOR]
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 104
GFX 2D 278 278
GFX 3D 1115 [COLOR="Red"]1116[/COLOR]
TL;DR
REMOVING CRAP FROM KERNEL LIKE UNUSED DRIVERS, USELESS GOVERNORS, ALL DEBUGS, DO INCREASE KERNEL PERFORMANCE? NO
TEST 4
".. ye ye u fools seeking big numberz! Merging kernel with latest linux mainline makes teh battery drop fastah"
Kernel merged with linux 3.0.39 / 3.0.40 / 3.0.41
Same standard condition, let phone full drain with all 4 kernels in idle / airplane mode and standard usage.
RESULTS
After comparing 4 different kernel the battery stats were all the same, no weird wakelocks no battery drains. Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome work!
Good work.
I respect your work.
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain? I'm not too familiar with all the technical stuff, so if anyone can explain exactly what the kernel is, that might help explain things even further. I do know, and everyone else (hopefully), more aggressive scaling can have an effect on battery life . Nice to see another test showing undervolting is pretty much not needed and isn't worth the instability it may cause. But hey, whatever floats your boat.
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
"It depends on what the meaning of the word 'is' is."
"... I didn't inhale ..."
what CPU speed(high/low) are you benchmarking, I don't see it posted.
I'll just come out and say it: seems fishy.
I've seen you obsessed before at some kernel "myths" like thalamus claim that latest mainline updates were hurting performance/battery and to be honest I don't see in these studies a sufficient amount of rigor, objectivity and data to withdraw any conclusions except your clear agenda against some things that are said.
For example, some flaws:
1. 0xBenchmark and AnTuTu only measure one kind of performance, you may think you are gauging something when you're not.
2. A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
3. Such benchmarks have fluctuations, they are not particularly accurate.
4. The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
6. And once more, removing debug/crap should improve other things which were completely ignored (mm, pm, etc).
7. The last test just doesn't make sense, there are too many things involved to be that linear.
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Long story short, I can't really bring myself to take this too seriously as it lacks data and there's just too much hate undermining the credibility of the post. I should also mention that I don't have a position regarding each of those claims; I believe we should experiment, analyse, collect feedback and withdraw conclusions for everything but this just didn't convince me, especially when it comes to your neutrality. Thanks though.
chronophase1 said:
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain?
Click to expand...
Click to collapse
I guess I know whom you are talking about, but may be you have not read his latest thread. lol...
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
I am glad this test has proved it actually doesn't matter.
anshumandash said:
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
Click to expand...
Click to collapse
I said generally, which is correct. The vast majority of the time the kernel has nothing to do with battery drain.
And yes, merging mainline does make a difference.
If you actually bother to read my blog post, you will see I don't actually mention battery drain at all as my reasons for ditching mainline updates.
Personally, I don't use the Nexus S enough to notice increases / decreases in drain, it's my development phone. However, quite a lot of users *have* told me that they have noticed improvements since I rolled back. Perhaps they are all wrong too?
It's not wakelocks, it's not obvious drain, it's subtle increases in drain which are impossible to track down.
However, In the case of the GNex when I merged to .40 I got 6% an hour drain, but when I went back to .31, I got less than 1% an hour drain. Merging back up again gives me the 6% an hour drain again with *nothing* else changed. It doesn't take a genius to figure out that it must be the kernel merging which has caused it, or is someone going to argue with that too? Lol.
I'm not entirely sure what myths have been busted here. It seems like a non kernel developer wasted their time to prove utterly nothing, which amuses me slightly. Do you honesty think I apply any modification, tweak or anything without testing the impact? If it makes no difference, it doesn't go in.
Removing unused stuff is simply to make the compile slightly quicker and the resulting zImage smaller. I don't believe there are any performance improvements to gain by doing that, but what is the point having junk built in which isn't needed?
As for removing all debugging, it's not a good idea, because how are you going to get a stacktrace if you panic? Again, that is something I won't do, and I know it makes little difference.
Anyway, if you want to test more accurate real world usage, use the 2D tests on 0xBench. They are CPU bound and they are greatly affected by small changes. Here are some I did a few weeks ago to test the best toolchain for the Nexus 7.
As you can see, there clearly is a difference between the speed of code that they produce. Raw speed is one thing, but graphics benchmarks more accurately represent real usage.
tl;dr: Ignore the agenda driven opinions and dubious results in the first post, they are meaningless.
simms22 said:
what CPU speed(high/low) are you benchmarking, I don't see it posted.
Click to expand...
Click to collapse
Performance, 1000.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
knzo said:
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Click to expand...
Click to collapse
If you read carefully i tested the battery with daily use aswell.
Quoting myself : " Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge..
knzo said:
A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
Click to expand...
Click to collapse
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
After tons of test around the web can pretty much assure you that toolchains may give something good compiling the OS ITSELF not the kernel.
knzo said:
The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
Click to expand...
Click to collapse
This is a rude attitude. Why don't you explain why the methods are wrong?
If after days of testing with almost just the lcd on, seeing wich charge lasted longer isn't good feel free to explain why.
Maybe i should've used a tester? I simply want to see if my phone last longer with lcd undervolt, simply.
About data results: the results is around 5%, would it better if i wrote how much every % lasted and then making simple math operations? No thanks.
i don't like to edit OP posts so i'll write it here. Quoting myself:
What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
i meant 10 minutes more screen time
knzo said:
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
Click to expand...
Click to collapse
I disabled them one by one aswell and never noticed an increase performance. So your statement is wrong. I don't have the config anymore but for sure kernel, slub dm and cgroup subsys were disabled.
I develop my own rom and kernel just for myself. I make these tests for myself not to prove anything, i'm just sharing.
These tests took me one week to be made. Do you really think i would ruin them posting wrong informations or ruining my reputation?
Actually i was surprised by some of them.
You're welcomed to made them again or better since you didn't like the methods.
atl4ntis said:
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
Click to expand...
Click to collapse
That single sentence sums up this entire thread.
Basically, you started these tests with an agenda which was to validate ezekeels tests and you 'proved' what you wanted to prove to fit your agenda.
Anyone can do that. It doesn't actually prove anything though, it just generates FUD. Congrats.
No just one test and just becouse similar test were made.
Go troll somewhere else.
atl4ntis said:
No just one test and just becouse similar test were made.
Go troll somewhere else.
Click to expand...
Click to collapse
I'm not trolling. I'm rightly questioning your extremely dubious results and the fact you have an agenda, which you clearly do. If you don't want people to question them, perhaps go and post them on Rootzwiki instead where they will be blindly accepted as gospel.
The definition of trolling is here.
Your post is simply confusing users and generating FUD, but perhaps *that* is your true agenda, is it not?
If you think these tests are wrong just provide some proof instead of offending people or talking about agenda or even worse reporting them as wrong because "other people said so" instead of testing them by yourself or saying some issues are not trackable.lol.
Some moderator should get rid of this thanks.
I think the OP has good intentions and had shown aptitude in collecting data, which deserves praise.
Just because something isn't perfect in the first attempt doesn't mean it deserves to be torn down.
Efforts like this need to be carefully nurtured because they go towards dispelling the prevalent aura of general guff that is spouted here in the development section on a daily basis.
To improve the study, make sure you are clear about the test conditions, and run the same test repeatedly until the mean and median converge to within some acceptable tolerance, e.g. 1%
You can then use standard deviation to make accurate statements about the data including its variability.
If you run multiple benchmarks you can later do regression testing to eliminate the tests that aren't correlated to the end result. You can combine the results of multiple benchmarks using the geometric mean.
If that's confusing, then I'll happily explain it in more detail.
Any more shenanigans, this thread gets locked. Either discuss the post like an adult or don't post.
You quoted my post about battery screens + on screen buttons but have not answered what is the deal with it.
What are those on screen buttons doing there on a official ROM for the 9023?
Already answered but maybe i wasn't clear enough.
I tested those kernel with daily usage aswell, that mean with mods apps and every crap i use daily. Those ss refers to the daily usage with my rom.
Hello World! What's your current ROM and kernel you're running on, and what do you normally get for screen on time? I'd like to get some suggestions.. Would like to get through a whole day comfortably
It doesn't really matter how much screen on time someone else gets, it doesn't mean you'll ever achieve that same amount. Screen uses a pretty constant amount of power per brightness setting, but the other things that use power will take away from that and not all those things are to do with CPU usage, which is the only thing a ROM/Kernel can affect.
On top of which:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
rootSU said:
It doesn't really matter how much screen on time someone else gets, it doesn't mean you'll ever achieve that same amount. Screen uses a pretty constant amount of power per brightness setting, but the other things that use power will take away from that and not all those things are to do with CPU usage, which is the only thing a ROM/Kernel can affect.
On top of which:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are you running on your Nexus 5 thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
Yup that does help... No such thing as 'best'. I didn't make the best title lol.. Currently happy with SlimLP and Franco, just wondering what you guys were getting . What are you on, as of now in terms of ROM/Kernel?
samdroid24 said:
Yup that does help... No such thing as 'best'. I didn't make the best title lol.. Currently happy with SlimLP and Franco, just wondering what you guys were getting . What are you on, as of now in terms of ROM/Kernel?
Click to expand...
Click to collapse
Slim + ElemantalX
samdroid24 said:
Hello World! What's your current ROM and kernel you're running on, and what do you normally get for screen on time? I'd like to get some suggestions.. Would like to get through a whole day comfortably
Click to expand...
Click to collapse
I hate the "it all depends on your phone, each one is different" bullcrap. That may be true to an extent, but some combos are generally going to be better than others. Besides, most people who ask this question just want to know what people are using and what is working for these people. So now that my rant is over, I'm using BrokenOS with Sensei Kernel R52. I'm getting roughly 4-5 hour SOT with roughly 50-60% brightness and 18 hours off the charger. I'm using the blacked out gapps that are linked with BrokenOS and using the black Swiftkey keyboard theme. All of the black saves battery when the screen is on because those pixels are off when using amoled screens. Don't know if you know that or not, but hey, it's there. Also, I've set the kernel minimum frequency to 223mhz using intelliplug with fsync and mpdecision off using the trickstermod app. I've set the scheduler to fiops and changed the read ahead value to 1024. This has consistently given me these results which I consider to be great! Hope that helps!
ccoulterjg1 said:
I hate the "it all depends on your phone, each one is different" bullcrap. That may be true to an extent, but some combos are generally going to be better than others. Besides, most people who ask this question just want to know what people are using and what is working for these people. So now that my rant is over, I'm using BrokenOS with Sensei Kernel R52. I'm getting roughly 4-5 hour SOT with roughly 50-60% brightness and 18 hours off the charger. I'm using the blacked out gapps that are linked with BrokenOS and using the black Swiftkey keyboard theme. All of the black saves battery when the screen is on because those pixels are off when using amoled screens. Don't know if you know that or not, but hey, it's there. Also, I've set the kernel minimum frequency to 223mhz using intelliplug with fsync and mpdecision off using the trickstermod app. I've set the scheduler to fiops and changed the read ahead value to 1024. This has consistently given me these results which I consider to be great! Hope that helps!
Click to expand...
Click to collapse
That helps greatly! Yes, this question was more of a 'Which ROM/Kernel is the best for you' type of question. And yup, I do know that AMOLEDs give you those pitch black blacks, which is good for battery, since those pixels aren't being used. I myself, am a big flashaholic, tried at least 5-6 Roms and a bunch of kernels.. Best battery life so far for me seems to be Slim + Franco.. Never tried BrokenOS, will flash tonight Thx a lot for your detailed response :good:
ccoulterjg1 said:
I hate the "it all depends on your phone, each one is different" bullcrap. That may be true to an extent, but some combos are generally going to be better than others. Besides, most people who ask this question just want to know what people are using and what is working for these people. So now that my rant is over, I'm using BrokenOS with Sensei Kernel R52. I'm getting roughly 4-5 hour SOT with roughly 50-60% brightness and 18 hours off the charger. I'm using the blacked out gapps that are linked with BrokenOS and using the black Swiftkey keyboard theme. All of the black saves battery when the screen is on because those pixels are off when using amoled screens. Don't know if you know that or not, but hey, it's there. Also, I've set the kernel minimum frequency to 223mhz using intelliplug with fsync and mpdecision off using the trickstermod app. I've set the scheduler to fiops and changed the read ahead value to 1024. This has consistently given me these results which I consider to be great! Hope that helps!
Click to expand...
Click to collapse
Each phone is different but that really has nothing to do with battery life, except that maybe some CPU's can undervolt more. I'm not sure anyone has given this "bullcrap" answer you eluded to.
samdroid24 said:
That helps greatly! Yes, this question was more of a 'Which ROM/Kernel is the best for you' type of question. And yup, I do know that AMOLEDs give you those pitch black blacks, which is good for battery, since those pixels aren't being used. I myself, am a big flashaholic, tried at least 5-6 Roms and a bunch of kernels.. Best battery life so far for me seems to be Slim + Franco.. Never tried BrokenOS, will flash tonight Thx a lot for your detailed response :good:
Click to expand...
Click to collapse
Check out my rom chroma. Franco kernel is preloaded. Huge update coming very soon.
Sent from my Nexus 6 using Tapatalk
I've tried most of the roms and kernels and have always gone back to BlissPop and either Lean or Francos. BlissPop for the features and Lean/Franco for the battery life. I would consider myself a moderate to heavy user and get between 4 - 5 hours of sot, but more important to me, I start my day at 5am and shutdown around 10:30 - 11:00 pm and I generally have 35% - 40% or so left. Of course your milage may vary, I also greenify what I can, but I refuse to lose any features i use, why have a fantastic phone and cripple it. I generally don't change any of the kernels, except maybe set it to conservative, I've had issues in the past undervolting, but thats just me. For the slight battery savings I don't find it does that much. Again, my opinion.
Just take a nandroid of where you are and try some combinations. Give it a few days to settle in. Repeat until your happy with the combination.
zephiK said:
Check out my rom chroma. Franco kernel is preloaded. Huge update coming very soon.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Will most definitely flash Chroma... Looks like one of the best designed ROMs.. Will flash it either tonight or tomorrow morning... And your name seems familiar from the numerous pages I've went through on Franco's Kernel lol. Thx :laugh:
how many hour is stay on the stock ROM ?
Chroma with FK and vomer are poetry in motion. Use it and prosper.
using the rom that i use, and kernel, and the way i set up my cpu, i see between 5.5 and 7 hours sot. which rom and kernel? try them all out, find your best rom/kernel.
dan04103 said:
Chroma with FK and vomer are poetry in motion. Use it and prosper.
Click to expand...
Click to collapse
Glad you're enjoying the combination
zephiK said:
Glad you're enjoying the combination
Click to expand...
Click to collapse
Does Chroma have omniswitch? Cause that's a deal breaker
Just flashed Chroma... This ROM is buttery smooth
Sent from my Nexus 6 using XDA Free mobile app
I am on Terminus currently with Franco Kernel undervolted all frequencies @-50 which is 100% stable in my case. -75 crashes on games and/or benchmarks. My Snapdragon has a PVS 5 binning.
samdroid24 said:
Just flashed Chroma... This ROM is buttery smooth
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I'm glad you enjoy it. A new build was pushed out if you didn't get it, 01/24.
jiv101 said:
Does Chroma have omniswitch? Cause that's a deal breaker
Click to expand...
Click to collapse
Nope, I personally don't find the feature useful.
Sent from my Nexus 6 using Tapatalk
Right now I'm on validus ROM with Franco kernel. I only changed the max clock in Franco kernel down to 2.2ghz. Right now I'm at almost 36 hours on time and 4 hours and 40 minutes sot
zephiK said:
I'm glad you enjoy it. A new build was pushed out if you didn't get it, 01/24.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yup, flashed the 1/24 build last night
Hey XDA,
my Z3 broke and my insurance gave me 500€ to get a new phone so i got the Nexus 6 32GB Blue for 490 € at my workplace.
Before my Z3 i had many different Phones like the S5, LG G3, NEXUS 5, HTC ONE m7 and more
Well what mostly use me device for is communication, A LOT (LOT LOT³) OF Fn READING (Manga and Reddit Sync) and hearing my music on the way to school/work/whatever .
I am a experienced user with roms and flashing but with this new device i just want to flash something daily driver friendly but feature heavy rom and a good battery conserving kernel
So far ive looked around for some roms available here and already choosen the
CHROMA Rom because it seems to be popular here (Not sure why ?!) (What is "Layers" ?)
and the Vindicator Kernel because it looks very promising (Not sure if its the case tho) and it has a lot of features (for a kernel..)
So what do you guys use and show me some screens of your themes becuase i like the possibilty to use the cm theme engine
Thanks
RainbowSix
For stability.. Chroma/hellscore kernel
Or use the JDX based on latest android M which is pretty stable too but you may encounter few bugs
dex2grigg said:
For stability.. Chroma/hellscore kernel
Or use the JDX based on latest android M which is pretty stable too but you may encounter few bugs
Click to expand...
Click to collapse
What bugs may i encounter ?
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
danarama said:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
Wow thats an awesome and big post with a lot of tought from you, thanks
I never asked for a best rom/kernel.. just your recommendation and im sorry that i didnt see the other thread you showed me
Do you have a tutorial for kernel settings ? because i didnt have a nexus for a long time now i never messed with kernel settings that much
And what is your opinion on my choosen rom/kernel ? what are you using and why ?
rainbowsixpro1 said:
Wow thats an awesome and big post with a lot of tought from you, thanks
I never asked for a best rom/kernel.. just your recommendation and im sorry that i didnt see the other thread you showed me
Do you have a tutorial for kernel settings ? because i didnt have a nexus for a long time now i never messed with kernel settings that much
And what is your opinion on my choosen rom/kernel ? what are you using and why ?
Click to expand...
Click to collapse
No worries, but recommendations kind of fall under "best" in a way anyway and it is all subjective.
FWIW, I like to use Slim Alpha and ElementalX kernel.
As for tweaks, it all depends what you want. Performance Versus Battery. Easiest thing to tweak is the governor settings. Some governors will allow you to change the Up Threshold. The % of CPU load before it steps up to a higher frequency. Set the up threshold high, it will stay at a lower frequency for longer, of course that impacts performance.
danarama said:
No worries, but recommendations kind of fall under "best" in a way anyway and it is all subjective.
FWIW, I like to use Slim Alpha and ElementalX kernel.
As for tweaks, it all depends what you want. Performance Versus Battery. Easiest thing to tweak is the governor settings. Some governors will allow you to change the Up Threshold. The % of CPU load before it steps up to a higher frequency. Set the up threshold high, it will stay at a lower frequency for longer, of course that impacts performance.
Click to expand...
Click to collapse
Well i am thinking to go battery but not 100%. but more like 80%
Problem is i dont know what the apps need to work fluid (or not?)
With recommendation i meant something like this
"AWESOME DUDE, I HAVE A NEXUS 6 WITH ROM X AND KERNEL X AND USE IT FOR DD AND LOTS READING
ITS WORKING LIKE A CHARM NEVER hv HAPPIER BEFORE BECAUSE THIS DOES THAT AND THAT DOES THIS"
sounds stupid, i know but maybe someone else using the N6 is in the same scenario as i am.
Got some good news 3 hrs from now i will hold a fresh Nexus 6 in my handy and now someone is offering me a GS6 32GBlack for exchange xD
GOT IT GOT IT GOT IT earlier but happy about this new awesome toy to play with
Hello everyone.
I am looking for the best fit for me as far as a rom / kernel combo. I have had the phone a week and was on stock for a day. Battery life was decent but i was looking for more longevity out of the device. I then flashed Dirty Unicorns and love the battery life but not all the theming and black. Is there something stock like with very awesome battery life I can try out? I do like the stock look L / M. I like simple and clean looking with no extra apps. What is the best recommendation for me?
Thank you in advance.
"Best" ROM.
There is no such thing as a best ROM.* The question itself is ambiguous.* "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded.* You will likely be able to read about this in the ROM threads.* ROMs do not impact battery life.* The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel.* What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life.* Let's get this cleared up.* Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life".* This is actually wrong.* Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning.* The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings.* This is what we refer to as out-of-the-box settings.* The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance.* The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
There's no best combo either. Get the features you want and learn to tune the kernel to your desires
Hope this helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, I'm sure many of us have the burning question of which ROM/kernel any of us should use when it comes to pure performance. With so many ROMs out there, ones based on OOS, Havoc, Paranoid Android, crDroid, OmniROM, MIUI, the list just absolutely goes on. I want to use this thread as a way to inform people of any potential performance gains/loss when it comes to choosing a ROM, as well as just a thread to compare/talk about benchmarks in general.
So I've taken the liberty to run five different setups, (I can take some more as requests, if necessary.) and ran A LOT of benchmarks between all of them to see which ROM provides the best performance. These tests include four various games, some synthetic benchmarks, and storage tests. At the end of it all, I ran all the tests with some pretty heavy kernel based performance modifications that gave a surprising amount of performance gains in some scenarios.
The ROM setups I am using are:
Completely Stock (OOS Beta 11 with zero modifications)
Stock OOS Beta 11 but Magisk / xXx NoLimits xXx 10.1 / Data Formatted as F2FS
HavocOS 3.3 Build 3/17 w/ F2FS
Paranoid Android Quartz Beta 5 w/ F2FS
& Paranoid Android Quartz Beta 5 w/ F2FS AND SmurfKernel 3.5.1 rc17 slmk w/ Overclocks Enabled
All benchmarks were ran under the scrcpy ADB screen mirroring software, and under the settings I've used, it's shown to not provide any amount of performance loss. The command/options I've ran are "scrcpy --render-expired-frames -b 2M -m 768". That makes scrcpy not drop any lost frames (which will increase delay but make frame rate recording much more accurate), have a bitrate of 2Mbit/s, and have a screen height of only 768, which is easy for the phone to do while not incurring any performance loss. Game performance was recorded using MSI Afterburner over the scrcpy window, which isn't THE MOST accurate, but is the only option available due to certain apps not being able to be run under OOS (i.e. KFMARK actually offers these features in app, but crashes on OOS.)
So, lets get started, first, with the gaming benchmarks. I've chosen these games because they are the only ones that are intensive enough on the phone's hardware that can run without hitting the game's frame rate cap. The overclocking kernel of choice for these tests are @pappaschlumpf's SmurfKernel, all my settings can be found here.
GAMES:
Game 1:
Game 2:
Game 3:
Game 4:
ANTUTU:
3DMARK:
Test 1:
Test 2:
Test 3:
Test 4:
Test 5:
GFXBench 5.0:
Set 1:
Set 2:
Set 3:
Set 4:
Geekbench 5
AndroBench (Storage):
Set 1:
Set 2:
So, what is the takeaway from all this? Which is the winner of the best performing ROM? I think the short answer is, well, no one. Long answer? It really depends. Currently, I don't think ROMs alone can offer any amount of increase in CPU/GPU, giving any extra gaming performance. That seems to be solely up to the kernel.
At a glance, it may look like Havoc offers an immense increase in gaming performance from looking at all of the benchmarks. However, after checking Kernel Tuner, I actually noticed its kernel overclocks the GPU to 675 MHz, (up from 585).
Strangely, OOS seems to offer better SQLite performance than both other ROMs until some serious kernel tweaking is introduced. It may look like xXx NoLimits xXx gives higher storage based scores, but the gains were due to /data being formatted to F2FS. Thus, it seems like NoLimits provides zero recordable performance difference. Not sure what they mean by Speed/RAM optimized. Maybe it's just purely a debloating and keep-more-apps-in-Ram tool.
CPU scores between all ROMs is all within margin of error. I noticed higher MEM/Storage benchmark scores on AOSPA, as well as slightly faster app install times. However I imagine that comes from the fact that it uses the @arter97 kernel, not due to the ROM itself.
So, with all this said, I think the best ROM to choose is whichever one you feel like has the best features / ability to be a daily driver, not what you think will be better performance. I am personally sticking with Paranoid Android because some others have one or two annoying bugs that they haven't squashed and apps like Reachability Cursor and KFMark work seamlessly on it (unlike OOS).
remarkable
I miss crDroid, AOSPA and TreskMOD in that comparison. Good work anyway !
Mystenes said:
I miss crDroid, AOSPA and TreskMOD in that comparison. Good work anyway !
Click to expand...
Click to collapse
How on earth did you miss AOSPA?
rejectedjs said:
How on earth did you miss AOSPA?
Click to expand...
Click to collapse
Should be AOSiP
Mystenes said:
Should be AOSiP
Click to expand...
Click to collapse
AOSiP is based on pure AOSP and doesn't have any official Android 10 releases, it's still running Pie, so I don't want to waste time getting into it. TreskMod is just another mod of OmniROM, which HavocOS is already largely based from. crDroid looks interesting, so I'm currently running it and trying it out for myself and will update with benchmarks eventually.
for a reliable test, you must flash the same kernel with same settings in all roms, smurf kernel for example works in stock and customs.
You have smurf kernel with forced 90 hz, the same setup must be in all customs and is misconfigured, if you have surfaceflinger boost on, you must disable frame commit boost and viceversa.
how about call of duty mobile game?did you test it out?thanksyou
Toni Moon said:
for a reliable test, you must flash the same kernel with same settings in all roms, smurf kernel for example works in stock and customs.
You have smurf kernel with forced 90 hz, the same setup must be in all customs and is misconfigured, if you have surfaceflinger boost on, you must disable frame commit boost and viceversa.
Click to expand...
Click to collapse
I know SmurfKernel works on OOS / AOSP, the overclocking benchmarks weren't there to show "Look! SmurfKernel + AOSPA is so much better than others!", it's to show people how much of a difference overclocking can make, for them to make the decision of whether they think SmurfKernel's overclocking is worth flashing for or not. I didn't flash the same kernel to all ROMs because that's not the way the developers intended it to be. If the developers wanted their rom to be best experienced under SmurfKernel, they would have either explicitly stated it or packaged it in with the ROM. For example, the way AOSPA does with arter97's kernel. Flashing Smurf to everything would have defeated the purpose of comparing the ROMs.
xNovaLeader said:
how about call of duty mobile game?did you test it out?thanksyou
Click to expand...
Click to collapse
Call of Duty Mobile already runs at it's frame rate cap of 60FPS on our phones, there would be zero difference between ROMs.
rejectedjs said:
I know SmurfKernel works on OOS / AOSP, the overclocking benchmarks weren't there to show "Look! SmurfKernel + AOSPA is so much better than others!", it's to show people how much of a difference overclocking can make, for them to make the decision of whether they think SmurfKernel's overclocking is worth flashing for or not. I didn't flash the same kernel to all ROMs because that's not the way the developers intended it to be, if the developers wanted their rom to be best experienced under SmurfKernel, they would have either explicitly stated it, or packaged it in with the ROM, like the way AOSPA does with arter97's kernel. Flashing Smurf to everything would have defeated the purpose of comparing the ROMs.
Call of Duty Mobile already runs at it's frame rate cap of 60FPS on our phones, there would be zero difference between ROMs.
Click to expand...
Click to collapse
isee..thanks for the info..its suck when its come to flagship phone with higher refreshrate..
Wow, that's great! Now it seems almost strange why this wasn't done so far What about battery? It would be interesting to benchmark idle / active drain (maybe in 2 scenarios like chrome browsing and other in gaming?), just a though
spawnn617 said:
Wow, that's great! Now it seems almost strange why this wasn't done so far What about battery? It would be interesting to benchmark idle / active drain (maybe in 2 scenarios like chrome browsing and other in gaming?), just a though
Click to expand...
Click to collapse
I would like to do a battery life test but there are so many variables that would really come down to end user experience that I don't think it would be an accurate representation of the ROM's performance. If there's an app that just constantly drains the battery life, maybe I could try that, but I feel like that would take a really long time to post results for since that would be one ROM's results a day.
Thanks for this. I'm currently running OOS 10.3.1AA with arter97 r54 kernel ?? pretty happy with performance and kernel overall.
Best thread I've seen on xda in years. Thanks for this! :good:
Pfeffernuss said:
Best thread I've seen on xda in years. Thanks for this! :good:
Click to expand...
Click to collapse
Thanks! Lol, I'm glad it's getting some attention considering all the time I spent wiping and having to restart so much to get all the info!
rejectedjs said:
I would like to do a battery life test but there are so many variables that would really come down to end user experience that I don't think it would be an accurate representation of the ROM's performance. If there's an app that just constantly drains the battery life, maybe I could try that, but I feel like that would take a really long time to post results for since that would be one ROM's results a day.
Click to expand...
Click to collapse
PCMark has a battery test which works really well, but it takes like 9 hours to run haha
Would be awesome to see though
Thua far, the absolute smoothest experience Ive had on this phone has been OOS + Smurf + xXx. Without smurf, Ive seen no difference with or without xXx, however with it, the phone is butter smooth, its an enormous difference. Benchmarks on my phone are lower because I keep clocks low to save on battery, however even then the phone blazes through everything. Has a few kinks here and there that are admittedly quite annoying, though, so I am looking into other kernels a bit. Appreciate the post. Ill probably continue avoiding AOSP roms, Oxygen has spoiled me, such a good Rom.
Ruvaldak said:
Thua far, the absolute smoothest experience Ive had on this phone has been OOS + Smurf + xXx. Without smurf, Ive seen no difference with or without xXx, however with it, the phone is butter smooth, its an enormous difference. Benchmarks on my phone are lower because I keep clocks low to save on battery, however even then the phone blazes through everything. Has a few kinks here and there that are admittedly quite annoying, though, so I am looking into other kernels a bit. Appreciate the post. Ill probably continue avoiding AOSP roms, Oxygen has spoiled me, such a good Rom.
Click to expand...
Click to collapse
Arter kernel is a rather nippy and no stutters or hickups noticed yet, perhaps give that a whirl!
And how about battery drain ? Sot and idle ?