[22-Nov] NEW: ArrowOS v8 with alternative cpu governors. Check it out in post #127.
Here is my first series of PC Mark Battery Life Benchmarks for the Xiaomi Mi Max 2.
Let me first say that this is not a "best rom" thread. There is no absolute best rom. What is best for one user may not be best for another. To give a simple example, battery life is very important for some users while performance is priority for others.
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats for many hours, until battery drops below 20%, a series of tasks including web browsing, photo and video editing, text editing and data manipulation. Then it extrapolates the SOT that would be obtained with 95% of the battery charge.
For each rom I made a clean install and a simple setup with basic settings and a added a few apps necessary to monitor/admin the runs.
The tests are run with the screen brightness calibrated at 200 lumens as required by PC Mark and all sound levels set to zero, so results are better suited for comparison.
Each benchmark run takes between 9 and 11 hours. So this test is also a stability test. Some rom/kernel combinations simply fail to complete the benchmark.
If you want to learn more about PC Mark take a look at the site: PC Mark for Android.
These are the roms included so far:
AospExtended-v4.6-oxygen-20180425-0949-UNOFFICIAL by @eva0034 - [ROM][7.1.2_r29][UNOFFICIAL] AospExtended ROM V4.6 [OMS/DUI]
lineage-14.1-20180318-UNOFFICIAL-oxygen by @ashwin007 - [ROM+TWRP][UNOFFICIAL][oxygen][7.1.2] LineageOS 14.1
DOT-N-v1.2-20180503-oxygen-UNOFFICIAL by @Jay_B - [Unofficial][ROM][7.1.2] dotOS VoLTE (Airtel and Vodafone Working)Final
Lineage 14.1 (30.10.2017) by @xuefer - LineageOS 14.1 for MI MAX 2 (oxygen)
XenonHD-180329-Unofficial-oxygen by @Jay_B - [UNOFFICIAL] XenonHD_Oxygen 7.1.2 With Substratum Support Final
RR-N-v5.8.5-20180412-oxygen-Unofficial by @iscle - [ROM][FINAL][7.1.2][2018-04-12] ResurrectionRemix 5.8.5 [UNOFFICIAL]
RR-N-v5.8.5-20180321-oxygen-Unofficial by @kenzolo - [21March][ROM][UNOFFICIAL] Resurrection Remix v5.8.5 [7.1.2][Nougat]
Some might be wondering why it took so long for me to add first results.
I have already run literally hundreds of benchmarks, mainly for the Samsung Galaxy Note 3 and the Xiaomi Redmi Note 4. I had very few situations where a benchmark would not finish.
With the Mi Max 2 I had to spend almost a month testing a few roms and modifying my test environment so that a benchmark would finish. It was happening with every rom I tried. Very frustrating.
Eventually I reduced the number of apps I use during tests from 22 to 8 and was able to start completing benchmarks. Failures still happen, but now at least I have an around 60% success rate.
I added a line with the number of failures for each rom in my results table. Keep in mind that failing the benchmark does not indicate that the rom is unstable and not suited to be a daily driver. These roms may never fail in normal day to day use.
I also noticed that battery SOT varied a lot between my two Mi Max 2, so I had to give up using both. All tests were run on the same phone.
Anyway now, even with only one phone, progress will be faster.
Enough talk. Now Let's see the results:
{
"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"
}
Score is a performance index - the higher the better.
SOT (Screen On Time) is an estimate of the number of hours the device may be used until battery drops almost dead (from 100% to 5%). It's a very good estimate because the test starts with the battery at 80% and ends when the battery drops below 20%.
There is no clear advantage comparing the roms tested so far. They all offer similar performance and battery drain.
So any of these roms will serve you well and you should pick one based mainly on features you want the most.
11-Jun-2018 Update:
Added three more roms to the results table.
I was so wrong when I predicted next results would come faster.
Lost about 10 day trying every possible way to benchmark ashwin´s LA15.1, but benchmarks would simply not finish.
Also had big variances between runs for Jay_B´s XenonHD and iscle´s RR-N. So I ran extra benchmarks to have more meaningful averages.
With more Oreo roms showing up my plan is to focus on Oreo roms for the next benchmarks.
29-Jul-2018 Update:
For the last (revised) preview of Oreo Roms head to post #87.
16-Aug-2018 Update:
For the last preview of Oreo Kernels head to post #95.
22-Nov-2018 Update:
Time for Pie, thanks to @hardrock_82. Check it out in post #105.
.
Instructions to vote in poll:
If you are using an app to access the thread, the poll will not be displayed.
To access the poll you must open the thread using a browser, login, and then you see the poll and be able to vote.
In XDA Labs, for example, once viewing the thread, you may open the three dots menu on the top right and just use the "Load in browser" option.
In other apps there is probably a similar option.
Also mine!
One more!
Ok. Enough.
haha i especially like the part about @pranavaryans slowing down for you to catch up
prioritizing via poll is a good idea, curious to see what the users will choose
what kind of benchmarking tools will you be using? same as with the redmi note 4?
and what kind of rom settings? especially concerning performance mode, kernel settings and powered sensors (wifi, bt, gps, etc.)
Sent from my Xiaomi Mi Max 2 (Oxygen) using Tapatalk
Xuefer's LOS 14.1 still the best rom for me :laugh: with "Brevent" Module to increase the battery life and no bugs in my opinion
congminhmc said:
Xuefer's LOS 14.1 still the best rom for me :laugh: with "Brevent" Module to increase the battery life and no bugs in my opinion
Click to expand...
Click to collapse
@svbarbosa contact me via pm if ure interested to include xuefer´s LOS 14.1 build
jbmc83 said:
What kind of benchmarking tools will you be using? same as with the redmi note 4?
Click to expand...
Click to collapse
I use PC Mark for Android - Battery Life Benchmark.
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats a series of tasks including web browsing, photo and video editing, text editing and data manipulation.
I am predicting each test run on the Mi Max 2 will take 10-12 hours. During all time the phone has to remain untouched. Receiving a call or SMS makes the test stop.
For more info take a look at their site: PC Mark for Android.
And what kind of rom settings? especially concerning performance mode, kernel settings and powered sensors (wifi, bt, gps, etc.)?
Click to expand...
Click to collapse
I am a little paranoid with the benchmarks. I try my best to have comparable results by doing the following:
- Clean install the rom
- Install always the same 20 apps, mainly support utilities, using Titanium Backup to restore them
- Use the same basic settings (no optimizations - no kernel tweaks)
- Sound always set to zero
- Brightness always set to 200 lx using the same meter (as required by PC Mark)
- All auto brightness settings disabled
- Wifi on and always connected to the same router
- Bluetooth always on but not connected to any device
- Location set to High Accuracy
- Benchmark always start with battery at 80%
- Reboot phone before each test
- Phone stays still always in the same place in my home office
svbarbosa said:
I use PC Mark for Android - Battery Life Benchmark.
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats a series of tasks including web browsing, photo and video editing, text editing and data manipulation.
I am predicting each test run on the Mi Max 2 will take 10-12 hours. During all time the phone has to remain untouched. Receiving a call or SMS makes the test stop. [emoji14]
For more info take a look at their site: PC Mark for Android.
I am a little paranoid with the benchmarks. I try my best to have comparable results by doing the following:
- Clean install the rom
- Install always the same 20 apps, mainly support utilities, using Titanium Backup to restore them
- Use the same basic settings (no optimizations - no kernel tweaks)
- Sound always set to zero
- Brightness always set to 200 lx using the same meter (as required by PC Mark)
- All auto brightness settings disabled
- Wifi on and always connected to the same router
- Bluetooth always on but not connected to any device
- Location set to High Accuracy
- Benchmark always start with battery at 80%
- Reboot phone before each test
- Phone stays still always in the same place in my home office
Click to expand...
Click to collapse
very thought out experimental setup my friend, good job there
Sent from my Xiaomi Mi Max 2 (Oxygen) using Tapatalk
Good job man
lol
Nice to know that my name is mentioned there.
You are doing great work on that OP, keep it up.
And yes, i have slowed down for now.
And what is the meaning of these synthetic tests? They do not give information in full. There are so many other factors. I know 3 Roms, where there are problems with voice communication. On 2 other "departing" applications. Sense in such tests? For example, we see one of the highest scores in these tests. But there will be problems with communication and other things. What is the point then? Only because of the greatest number of points in the test? For daily use, they are not suitable. Everyone has their own personal preferences. I tested all the roms for this device. For me personally, the best of them - crDroid and AOSP Extended from pranavaryans. Now I use AOSP Extended from pranavaryans
Excellent rum. But why is it not in the survey. All this is my personal opinion. Personally for me, such a waste of time. Everyone is very individual. The test is just numbers. They do not give complete information.
But ... maybe someone will be interested. Good luck
destroyer71 said:
And what is the meaning of these synthetic tests? They do not give information in full. There are so many other factors. I know 3 Roms, where there are problems with voice communication. On 2 other "departing" applications. Sense in such tests? For example, we see one of the highest scores in these tests. But there will be problems with communication and other things. What is the point then? Only because of the greatest number of points in the test? For daily use, they are not suitable. Everyone has their own personal preferences. I tested all the roms for this device. For me personally, the best of them - crDroid and AOSP Extended from pranavaryans
. Now I use AOSP Extended from pranavaryans
Excellent rum. But why is it not in the survey. All this is my personal opinion. Personally for me, such a waste of time. Everyone is very individual. The test is just numbers. They do not give complete information.
But ... maybe someone will be interested. Good luck
Click to expand...
Click to collapse
this thread isnt supposed to be an "end all discussion" solution concerning the "best" rom. u said it yourself, everyone has their own personal preferences! so what if someone doesnt care about those "departing apps" because hes using different apps, but really cares about cpu / gpu performance due to gaming?
this data doesnt give you an excuse not to do your due diligence, so ALWAYS read the respective rom threads to find out what kind of bugs / functionality they have.
BUT
it helps you make a more informed choice when, say, youre stuck between 2-3 roms which might be very similar in mods and functionality / design. having more information at your disposal is always good, so this is far from being a "waste of time"
I dont get this negative vibe from a lot of users here. trying to shoot down threads, discourage devs or criticize projects such like this which take a LOT of time and work for their initiators to complete. And all that because "they personally" are not interested in it and think its "a waste of time"? Well guess what: not everyone shares your opinion / your everyday usage cases / your preferences concerning ROMs, Apps, settings, design choices, etc. And thats totally fine! Everyone has different requirements, so lets just collect all the info we can so that everyone can make his/her own choice.
What would you get if everything was shut down just because we have different requirements? Well then there wouldnt be ANY choices left. Congratz, youve just made XDA superfluous
jbmc83 said:
this thread isnt supposed to be an "end all discussion" solution concerning the "best" rom. u said it yourself, everyone has their own personal preferences! so what if someone doesnt care about those "departing apps" because hes using different apps, but really cares about cpu / gpu performance due to gaming?
this data doesnt give you an excuse not to do your due diligence, so ALWAYS read the respective rom threads to find out what kind of bugs / functionality they have.
BUT
it helps you make a more informed choice when, say, youre stuck between 2-3 roms which might be very similar in mods and functionality / design. having more information at your disposal is always good, so this is far from being a "waste of time"
I dont get this negative vibe from a lot of users here. trying to shoot down threads, discourage devs or criticize projects such like this which take a LOT of time and work for their initiators to complete. And all that because "they personally" are not interested in it and think its "a waste of time"? Well guess what: not everyone shares your opinion / your everyday usage cases / your preferences concerning ROMs, Apps, settings, design choices, etc. And thats totally fine! Everyone has different requirements, so lets just collect all the info we can so that everyone can make his/her own choice.
What would you get if everything was shut down just because we have different requirements? Well then there wouldnt be ANY choices left. Congratz, youve just made XDA superfluous
Click to expand...
Click to collapse
You misunderstood what I wanted to say. I'm not against flows, quite the opposite. I expressed only a personal opinion about such tests. If it helps someone, that's fine. The results of daily use will differ from the test results. That's what I wanted to say
destroyer71 said:
You misunderstood what I wanted to say. I'm not against flows, quite the opposite. I expressed only a personal opinion about such tests. If it helps someone, that's fine. The results of daily use will differ from the test results. That's what I wanted to say
Click to expand...
Click to collapse
yes, totally agree on that. battery life is extremely dependant on personal usage cases. still, since your own usage pattern basically stays the same no matter which rom ure using, it makes sense to compare the roms with one and the same strategy.
lets say testing shows that ROM A provides 2h more SOT than ROM B, with a total of 14h SOT on A vs. 12h SOT on B.
With your usage pattern you might only get 10h SOT on ROM A due to heavy usage of GPS and LTE mobile data. Still, due to overall higher system energy consumption on ROM B, you know based on the given testing data above that your own usage pattern will most likely net less SOT on ROM B than on ROM A. So in your case, you already know that you might get 8h SOT on ROM B just by looking at the 14h vs. 12h data from testing
When you start to test roms?did you wait for specific vote number?I'm just doesn't unlock my device because of your test
I'm waiting to see the results then compare them to stock miui and then decide what to do because I can't see the big devlepors(with respect to all of them) or teams for this device(like leedroid or viper or eliminator purefusion for htc)
So I make a choice totally base on your tests
Thank you so much for your time spending for community
mesarabi said:
When you start to test roms?did you wait for specific vote number?I'm just doesn't unlock my device because of your test
I'm waiting to see the results then compare them to stock miui and then decide what to do because I can't see the big devlepors(with respect to all of them) or teams for this device(like leedroid or viper or eliminator purefusion for htc)
So I make a choice totally base on your tests
Thank you so much for your time spending for community
Click to expand...
Click to collapse
i can tell you right now that it will not make sense for you to wait for his tests to be complete this will take weeks if not months, i doubt ull wait that long
jbmc83 said:
i can tell you right now that it will not make sense for you to wait for his tests to be complete this will take weeks if not months, i doubt ull wait that long
Click to expand...
Click to collapse
I thought he starts soon(for example this week or next) and test roms with some scripts and then test another one
So I thought test will take at most two weeks
Am I wrong?he doesn't use script for test?or benchmark app?like gsmarena or others
destroyer71 said:
And what is the meaning of these synthetic tests? They do not give information in full. There are so many other factors. I know 3 Roms, where there are problems with voice communication. On 2 other "departing" applications. Sense in such tests? For example, we see one of the highest scores in these tests. But there will be problems with communication and other things. What is the point then? Only because of the greatest number of points in the test? For daily use, they are not suitable. Everyone has their own personal preferences. I tested all the roms for this device. For me personally, the best of them - crDroid and AOSP Extended from pranavaryans. Now I use AOSP Extended from pranavaryans
Excellent rum. But why is it not in the survey. All this is my personal opinion. Personally for me, such a waste of time. Everyone is very individual. The test is just numbers. They do not give complete information.
But ... maybe someone will be interested. Good luck
Click to expand...
Click to collapse
destroyer71 said:
You misunderstood what I wanted to say. I'm not against flows, quite the opposite. I expressed only a personal opinion about such tests. If it helps someone, that's fine. The results of daily use will differ from the test results. That's what I wanted to say
Click to expand...
Click to collapse
Yes, benchmarks are misleading most of the times. I never liked benchmarks myself. Real life usage is affected by so many factors.
But PC Mark Battery Life is not the usual benchmark. You should visit their site to better understand what it does.
PC Mark for Androd - A Better Benchmark for Android Devices
In a few words, this benchmark runs a series of simulations of day-to-day tasks , including web browsing, video watching, text writing and photo editing. The series is repeated until the battery drops below 20% and then you get an extrapolated SOT and a performance index.
I start the test with the battery precisely at 80%, so it uses about 60% of the battery charge, and the extrapolated SOT is very meaningful. The phone has to remain still during all time. If you run any app or receive a call/SMS while the benchmark is running, PC Mark simply aborts the test.
Since the benchmark runs for hours it is also a stability test. If the rom has, for example, memory leaks, it fails the test. I had it happening a few times with the two other devices I tested.
I truly believe my work produces useful info to help users make a more educated rom choice.
Of course there are many other important points that should be checked when choosing a custom rom, like customization features, active development/support, user base, etc... and the info I provide should never be the only basis for a decision.
mesarabi said:
When you start to test roms?did you wait for specific vote number?I'm just doesn't unlock my device because of your test
I'm waiting to see the results then compare them to stock miui and then decide what to do because I can't see the big devlepors(with respect to all of them) or teams for this device(like leedroid or viper or eliminator purefusion for htc)
So I make a choice totally base on your tests
Thank you so much for your time spending for community
Click to expand...
Click to collapse
Tests will start this weekend. I am having an unusualy tough work week, with long hours.
The votes will only help me defining a test sequence and have a feeling of how much people are really interested.
Running these benchmarks is a very time consuming task. The phones remain unusable for days/weeks.
The more people interested, the more motivation I have to keep benchmarking roms and kernels (yes, kernels eventually will appear for the Mi Max 2).
Right now I am benchmarking all important kernels for the mido (Redmi Note 4). There are 10+ kernels available.
The Mi Max 2 will be the third device I run benchmarks.
It all started for my main device, the venerable Samsung Galaxy Note 3, because its SOT is usually 3-4 hours, and battery life is a really important factor when choosing a rom. For the Note 3 I made a few scattered XDA posts. No dedicated thread.
Then I got my midos and decided to open a thread for my benchmarks. It was very welcome by the mido community, including developers, because the results helped them adjusting roms to better achieve their goals.
Now here I am with two Mi Max 2. Let´s see how it goes....
Related
additional details on test:
The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc/uc.
This is supposed to show how well a ROM performs by itself and how well it works while oc/uced since a lot of us do use custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
All ROMs will be using sense except CM6
Update 8/6: Updated the spread sheet and put it up and google docs Niefs Rom Comparison
There are now explanations of the tests and I am going to start testing today. Also, looking for testers.
I have posted my scores for part of Fresh.
update: 8/12
Most ROMs are completely filled out under features
Most performance test have been ran
Few battery tests
http://i996.photobucket.com/albums/af90/nief1313/test.jpg
{
"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"
}
I think it will be a great idea... google docs might be a good way to let people collaborate, otherwise some kind of wiki.
Might be easier to organize by features such as "stripped of sprint apps" or "added X app" vs things like battery and performance which can sometimes be highly variable by device. Also, if you run performance I would maybe do a baseline of 998mhz (since we all know we can hit this clock) and then another showing oc'd (since some people can barely OC one tick).
I think there are enough people across all the roms that if the spreadsheet were public you'd gather a lot of data. I also have NAND backups of a few of the froyo roms so it wouldn't be hard to boot into recover, reflash a nand, run the benches, then reflash back to whatever i was on.
The battery ones will be a little tough #1 cuz i'm not sure how many people wanna completely lock up their phone for several hours waiting to see how long it lasts. #2, depending on how some people's batteries are calibrated and what they're running in the background, MMV.
Great idea tho!!! I think the ultimate key is thinking of a good way for everyone to easily submit their data. Anyone have suggestions?
u could add it to our wiki and update it like monthly. idk just an idea
Looking forward to it
This is a great idea, and i look forward to seeing this list grow. This could really help someone new to Android like me.
toastcfh said:
u could add it to our wiki and update it like monthly. idk just an idea
Click to expand...
Click to collapse
I think adding it to the wiki would be really nice. I will try to come up with a spread sheet that only a few can edit(I don't want one person to delete or mess up all the data). I rather have were people pm there scores and other data so i can add it in.
I will finish tweaking on how to tests and how the spreadsheet will look tomorrow.
You should add 2 additional categories:
Does WiFi Tethering work with 3G speeds Y/N
if yes, which version of Wifi Tethering
Does WiFi Tethering work with 4G speeds Y/N
if yes, which version of Wifi Tethering
rek410 said:
You should add 2 additional categories:
Does WiFi Tethering work with 3G speeds Y/N
if yes, which version of Wifi Tethering
Does WiFi Tethering work with 4G speeds Y/N
if yes, which version of Wifi Tethering
Click to expand...
Click to collapse
I have just added that to the spreadsheet, the versions will be written down in the additional notes. Also, i just posted the link to the spreadsheet in the OP. I will be looking for testers if anyone is interested to help.
nief, im running EViO 2 V1.0.2
ill post results for you later.
nenn said:
nief, im running EViO 2 V1.0.2
ill post results for you later.
Click to expand...
Click to collapse
Sweet thanks for the help.
Which version of CM6 were you going to test? RC1 is getting pretty old, a lot of us are using nightlys. RC2 should be out soon though.
OgremustCrush said:
Which version of CM6 were you going to test? RC1 is getting pretty old, a lot of us are using nightlys. RC2 should be out soon though.
Click to expand...
Click to collapse
I was planning on testing RC1... at least until RC2 has been released.
if some one wants to do the tests for a nightly build, i will gladly add another row
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.) also the kernels can greatly affect these. If we wanted to actually test the rom shouldn't we be testing these with either 1 the same kernel for all or their stock kernels?
for example someone using the stock Fresh kernel may have vastly different results then someone using netarchy's kernel. this would provide skewed results for the rom test.
Same goes for Baked Snacks since there are several kernel options. if using the performance kernel for the performance test then switching to battery saving for battery saving test you will get results showing unachievable results.
I think this is a great idea but if this is going to happen i think "guidelines" should be used so that the data is as close to comparable and accurate as possible. what do you think?
something like
1) for testing purpose you should use the stock kernal with the rom for all tests.
2) with the exception of the OC tests you can not be running setCPU or any other under/overclock programs.
3) the following settings should be used. <list some basic settings>
4) if your rom has built in profiles settings that do not require a reboot or flashing anything you CAN use them.
5)etc
6)etc
If we dont have guidelines i think the results will very greatly on settings and kernel.
Even with doing the above you will still have a decent variance from usage/apps/widgets but at least this would make it as close to a level playing field and testing of the rom itself rather then the kernel/settings/who has what in setcpu
omegasun18 said:
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.)
Click to expand...
Click to collapse
I agree. Using performance profile for the performance test and then battery profile for the battery test will lead to skewed results. Perhaps what should be done is to test each profile against all tests. So you might have DC/Performance Profile and DC/Battery Profile with results for every test. This would tell you how well the battery performs under the performance profile or how well the rom performs under the battery profile.
omegasun18 said:
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.) also the kernels can greatly affect these. If we wanted to actually test the rom shouldn't we be testing these with either 1 the same kernel for all or their stock kernels?
for example someone using the stock Fresh kernel may have vastly different results then someone using netarchy's kernel. this would provide skewed results for the rom test.
Same goes for Baked Snacks since there are several kernel options. if using the performance kernel for the performance test then switching to battery saving for battery saving test you will get results showing unachievable results.
I think this is a great idea but if this is going to happen i think "guidelines" should be used so that the data is as close to comparable and accurate as possible. what do you think?
something like
1) for testing purpose you should use the stock kernal with the rom for all tests.
2) with the exception of the OC tests you can not be running setCPU or any other under/overclock programs.
3) the following settings should be used. <list some basic settings>
4) if your rom has built in profiles settings that do not require a reboot or flashing anything you CAN use them.
5)etc
6)etc
If we dont have guidelines i think the results will very greatly on settings and kernel.
Even with doing the above you will still have a decent variance from usage/apps/widgets but at least this would make it as close to a level playing field and testing of the rom itself rather then the kernel/settings/who has what in setcpu
Click to expand...
Click to collapse
I agree with a baseline but there should also be a performance test done where you have it maxed to the peak and state the battery life you'd get with those settings and numbers.
......
now that I think about it....
Really in the end we are speaking real world examples here and itd be best to just have the results state what rom, what kernel, and what settings you had to get "X" results and then go form there.
I dont care if DC is better on stock kernal and settings than BS. I'd rather know what settings in BS yield what results for people and the same for any other rom.
With the number of changes the dev's put in the roms doing baselines against them is kinda pointless as they might each take advantage of certain things differently. It'd be best to just notate the results for each post and state the changes made to yield the results so people can get more real world conclusions.
sgt. slaughter said:
I agree with a baseline but there should also be a performance test done where you have it maxed to the peak and state the battery life you'd get with those settings and numbers.
......
now that I think about it....
Really in the end we are speaking real world examples here and itd be best to just have the results state what rom, what kernel, and what settings you had to get "X" results and then go form there.
I dont care if DC is better on stock kernal and settings than BS. I'd rather know what settings in BS yield what results for people and the same for any other rom.
With the number of changes the dev's put in the roms doing baselines against them is kinda pointless as they might each take advantage of certain things differently. It'd be best to just notate the results for each post and state the changes made to yield the results so people can get more real world conclusions.
Click to expand...
Click to collapse
The thing is if you do what you suggest .. you arent comparing each roms performance really. If this is supposed to be used as a sort of guide for people to compare the roms themselves then what you said doesnt make sense since it adds a large a mount of varibales tot he "tests". Now if we are trying to compare complete packages and find what works best sure i agree with you completly. however i would not consider that to be comparing roms. which is what the origonal intent LOOKS to be.
When you are trying to compare things to get the most accurate results you compare them in as close to the same conditions and set up as possible. The more you differentiate the things you are comparing the more aspects can influence the results and the more skewed or inaccurate the results are.
If you have extremely random results based off a wide variety of conditions then the results lose there usefulness. In this case if we are trying to test ROMS then we should try to single out the roms and get them as close tot he same footing as we can so we can compare the ROMS and not the tweaks everyone can do. Maybe having another table or thread comparing different settings and tweaks and kernels would be helpful as well?
By stock kernel i mean the stock kernel that comes with each rom. The devs tweak these and make changes to give better performance/battery. I dont mean the stock as in the original froyo kernel. I also disagree that this isnt real world examples. I think it is exactly what it is however it takes out individual tweaks from the user and tries to keep everythign as close to level as possible to yield the best TEST results
Still going to say these will be nice but not what people will be looking for. So what if BS beats out DC outa the box in terms of bat life and performance. Thats nice and all but if you could show that with a few tweaks with set cpu and other things included in the rom that that DC greatly outperforms BS then its completely different.
What really needs to be done is what we both are saying. one done stock with the included kernel with the rom(or whatever the developer suggests using), and then one where users can make there tweaks and post those results.
If I just knew that one rom had better battery life stock and didn't know that I could possibly use a different rom that with a few tweaks gets better battery life and performance I'd rather use the later. Some roms perform differently than others with regards to tweaks being done by the user.
I'd stress that two tests be done, one with stock rom with stuff loaded form the dev's page only, and then one done with tweaks by the user and state the results so we can really get an idea what rom is best at what performance wise at least.
I was wondering if there would ever be something like this!! Great job!!! ...just on the side note, is there anyway to put the features working on the left side closer to the rom? i know a lot of users who care more about working features than technical stuff (linpack etc). I too would love to see this on the wiki!
**edit: also, maybe consider adding kernel box so we can see which kernel is being used w/ which rom and working features etc.
The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc.
This is supposed to show how well a ROM performs by itself and how well it works while oced since a lot of us do us custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
adeyo said:
I was wondering if there would ever be something like this!! Great job!!! ...just on the side note, is there anyway to put the features working on the left side closer to the rom? i know a lot of users who care more about working features than technical stuff (linpack etc). I too would love to see this on the wiki!
**edit: also, maybe consider adding kernel box so we can see which kernel is being used w/ which rom and working features etc.
Click to expand...
Click to collapse
There is a kernel box already there, its to the very right. THis is the custom kernel used during the oc test.
nief1313 said:
The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc.
This is supposed to show how well a ROM performs by itself and how well it works while oced since a lot of us do us custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
Click to expand...
Click to collapse
Thanks for clearing up what your vision for this is.
sgt slaughter. I agree with a lot of your points. I think 2 sets could be done to better show a variety of results. I was simply arguing the merits of doing a rom specific test comparison vs a complete setup specific comparison. You are right that different roms react differently to different tweaks that was the point. BUT not only do different roms act differently, different evos with the same everything react differently to different tweaks and settings. Thus just because user A get these results doesnt always mean User B will too. that's why i thought baseline would be a better gauge on the roms themselves.
I'm lucky enough to have multiple Inc's I can compare side-by-side. This week, I took the time to test-drive a few Kernels.
My goal is to find the (1) most stable, (2) best performing w/good battery life. Basically undervolt kernel testing.
Unfortunately, I really can't find much difference between these popular variants.
The battery life seems to be roughly equal on all of them, as does the stability (barring IcrediKernel, which had some issues in my testing with SkyRaider).
I tested (all current versions as of 1/10/2011):
* Redemptive with Lou's included kernel
* SkyRaider Sense with Ziggy's kernel
* SkyRaider Sense with KingX kernel
* SkyRaider Sense with Incredi kernel
KingX #6 scores almost 100 better than the next best in Quadrant. However, outside of that, I cannot really discern a major difference.
KingX seems to have the most significant changes in his changelog. Ziggy also seems to be brilliant, and yet, I really don't see any real differences between the kernels once implemented on my phone.
Can anyone help me isolate the differences -- perhaps I'm looking in the wrong place? I've basically tried to use everything I can think of, on the phone -- using each kernel, and tested all of them in power-save mode, tethered, etc.
Thanks in advance for any additional points to review..
quadrant is useless.
lou's kernels are great for me.
each phone is different so you'll have to test whichever one works best for you
Sure, of course. I'm familiar with the stock answer to the "which kernel is better" post.
That being said, I was asking something a bit different. I've *been* testing the kernels. The point of my post was to suggest that I cannot discern the difference after spending several hours with them.
With that in mind, I was asking if there is something specific I should be looking for, since I haven't found it (not with battery life, performance, or stability -- not with what I'm testing presently anyway).
Although, in addition to my original question -- of where to look to seek differences ... you do bring up another good point -- why is it that different phones (assuming they are the *same* model/android/radio version -- eg OLED 2.2's), would perform differently with identical kernels?
A few hours is not enough testing time for kernels. You need atleast a full charge down to 0 with a kernel to see how good the battery life is. Also, to judge the performance, you'll need a little more time for that too. Each phone is different. Some processors can take lesser voltages, high clocks than others. I'm not sure why this is, but it is. Honestly, I'm sure all the kernels are very good because the devs are excellent. But, some just work well for others while the same one doesn't for someone else. As I said before, just test out a kernel for a day or two, see how you like each one, and stay with it. If you battery life is being affected greatly, or your phone runs too hot or something, then switch to a different one.
At this point, I have more than 3 days or more on the following kernels:
* Redemptive with Lou's included kernel (3 days)
* SkyRaider Sense with KingX kernel (3 days)
* SkyRaider Sense with Ziggy's kernel (14 days)
* SkyRaider Sense with Stock kernel (22 days)
(Incredi -- I only had about 4 hours over two tests/loads and re-flashed, due to problems)
I've never run my batteries down to zero as you've mentioned. I've run them down to 10-20% on rare occasion.
In essence, what you are saying is that there really is nothing specific to keep an eye out for? If I don't see an obvious difference somewhere, there is no significant difference between the 4 kernels I have listed above? And Quadrant is of no help ... so in short, if they all get the same battery life, I just just pick one randomly?
I just want to believe there must be a more scientific/objective way of evaluating these kernels relative of each other.
if they are all pretty much the same to you, pick the one that makes you happy and that feels like it has the best performance and battery life. Maybe ask one of the devs about some scientific way of how each kernel is different from each other.
The problem is that I've built an app that our company uses over 18 phones that get run 9 hours a day, and the DInc's were overheating.
I went to Skyraider w/stock kernel, and that seemed to address the problem, at least it appears to reboot much less than the stock DInc's.
However, since I've made the commitment/risk of rooting/flashing these phones, I'd like to find some systematic method to determine which is the most efficient kernel to use, considering I have 18 phones in-the-field.
As a software engineer/empiricist, I'm not good at accepting the logic of "if it works, it's good enough". And so my objective is to find someone that may have some additional perspectives beyond that.
If there is a developer who sees this, I'd very much appreciate any information you can provide on how your kernel differs from others. Or someone who has some additional information.
Thank you in advance,
RKM
rkmFL said:
I'm lucky enough to have multiple Inc's I can compare side-by-side. This week, I took the time to test-drive a few Kernels. My goal is to find the (1) most stable, (2) best performing w/good battery life. Basically undervolt kernel testing.
Unfortunately, I really can't find much difference between these popular variants. The battery life seems to be roughly equal on all of them, as does the stability (barring IcrediKernel, which had some issues in my testing with SkyRaider) KingX #6 scores almost 100 better than the next best in Quadrant.
However, outside of that, I cannot really discern a major difference Can anyone help me isolate the differences -- perhaps I'm looking in the wrong place? Thanks in advance for any additional points to review..
Click to expand...
Click to collapse
Hi! One thing that affects performance is SD Card Read Speeds. Ziggy and Incredi have an improved read speed, I just tested both and got 12mb/sec read with a class 4 card. Since HTC released FroYo Android 2.2 for our phone, they implemented a read speed limit of four MB/sec for the SD card. I just tested Lou and King and got read speeds of 4mb/sec from the SD card. All Fourkernels I got a write speed of 4 mb/sec.
Other major differences I think worth mentioning are that Ziggy includes a hosts file to block connections to advertising servers. But of course installing a different kernel leaves the new host file in place. Multi touch, I love the piano and playing games so this matters to me. Ziggy has had a 5 point multi touch enabled for some time. Lou & incredi have implemented in a different way. I am not the one to explain the differences. Lou turned it on for up to five multi touch points(but disabled it in his last build). Incredi had enabled all ten multi touch points but is now also at 5. Debugging. Lou disabled debugging so apps that rely on it will not work. Ex.... PDAnet. Lou did have wireless N disabled, he said he felt due to the minor network speed increase it was not worth the extra battery usage. But reading his change log I see it has since been re enabled.
Which one is best for you? It really does depend on too many factors to say outright. Depending on the apps you have installed, and apps you use the most. I listen to music a lot. Using one that lowers clock speed a bunchwhen the screen is off makes themusic skip. In theory you will get better battery life, but imo, its not worth sacrificing that usability.
Please correct me if I am wrong, mis informed, or steering peoples wrong. I hope this helps to understand some differences.
Overheating. It seems that the consensus is that the 9.01 radio works best for most people. Not me. The 9.01 version makes my phone get very hot. I use the 7.28 radio and it makes a big difference in my phone not getting hot.
What issues did you have with the incredi that made you have to abandon it so quickly?
~TheHoovie
Sent from my HTC Droid Incrediblel.
P.s. did you forget to include Chad/incredi in this threadstitle?
I've been wondering pretty much the same thing, and I have been reading the different changelogs from the respective kernels to find the differences between them. Thanks to you thehoovie for a good explaination, you put to light some things I have been wondering. Very good explaination!
With that said, what has worked best for me, is RR 2.1.3 with Ziggy's new kernel (BFS Jan 2 2011). I get great battery, I can control the freqs the proccessor is at all the way down to 128mhz, the system is very stable, and have had no problems what so ever. I get roughly 2 days out of a full charge with moderate use on a 1350 battery!
@TheHoovie -
Excellent, excellent information, thank you!
I did not include Incredi in the title, because I had problems with it (mentioned in first post). To answer your question, there were two things. One more subtle, that I don't remember off-hand -- and the other, was with downloading from the Internet. I had installed twice, on a SkyRaider ROM, and in both events, Incredi would hang when downloading.
I distribute all of our private, in-house software releases through our website. So not being able to download from the web in my testing .. was a deal killer!
Our users take roughly 900 photos a day, on average. Therefore, SD speed is extremely important, and I never would have tested the differences between kernels. This is exactly the type of feedback I was hoping to find -- in other words, I was not asking "which is best for me", but instead "can someone help me know where to look for differences in performance". Your comment on SD, is a perfect example of such a factor, thank you!
...Does anyone else have any suggestions, beyond SD performance and battery life, as to other factors for comparison/testing?
@m411b -
I cannot imagine getting two days on a 1350mah, this would be amazing! I'm running off to test your suggestion (RR + Ziggy's) now. Just one question: where do you set the CPU frequencies using that RR+Ziggy configuration?
EDIT: I just tested SkyRaider + Ziggy's #15, and it seems to be running very good. Ziggy's #15 also uses a low-power Bluetooth driver, which will be a huge help for us (we use BT to communicate between DInc's and gTablets in our app).
Thank you again for the great info!
One more related question...
Have people been moving away from these Sense ROM's to CM7/Gingerbread, and if so, any feedback on stability?
I keep reading about CM7 adoptions and it's starting to make me wonder if I should give the new Gingerbread version a try.
I have not tested CM since v6 about 45 days ago, but at that point, there were some issues on the DInc.
Suggestion:
1. turn off wifi.
2. turn on gps
Launch Last.fm or pandora - stream your favorite music station.
Launch navigation, Navigate somewhere.. (I actually do this.. I just use gps when I am out running errands for an hour or so)
See how long the following lasts:
1. Battery
2. Time without crashing
That's been my simple testing of kernels. This is not scientific.. its just real world testing IMO
I am currently playing with Lou's #4 vs #8 on the same rom.. I think testing on multiple roms would bring in more factors you cant control.
#4 crashes way too often when running navigation (its fine for day to day use though)
been using Lous #8 on SR3.5 and it blew me away with battery life as well as performance. I flashed #9 yesterday and am gonna give it a day or two before i judge it. I had previously used Chad's and Hydra. Chad's wasnt the best and hyrda was great for OC performance but not for battery life.
Hi All
We have decided to build a comparative list of Rom for comparison. ROM's will be measured by the testers on 5 categories and hopefully we could get a honest opinion from the testers and not just a 5/5 for everything because they are a fanboy ...
ROM's will also be divided into 3 specific categories. Stock (Stock ROM provided from Samsung via update in Kies), Custom Original (Original ROM's by Dev's), Kitchen (Custom Original ROM's cooked and tweaked to perfection by a other Dev)
When providing us feedback on the ROM's please do so in the format below so we could add them to the corresponding list and add them to the graph that will follow in the 3rd Post.
Please try to be as Objective as possible. No point in having everything score 5/5
ROM Name goes here - By Tester
Version of ROM:
Android Version:
ROM Date:
Rom Type:
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:
If you feel the information provided is not accurate please just specify witch ROM you are referring to and what information is not correct as below and then a reason as to why you say so.
Stock Rom
Version: Actually 2.3.5
Reason for Edit: Made a typo when I submitted the rom information
This will help us to update the list timeously and accurately.
Stock Roms
I9100XFA - By Toxicdust
Version of ROM: N/A
Android Version: 2.3.4
ROM Date: 9 Sept 2011
Rom Type: Stock
UI flexibility: Portrait only with no lag at all. Lag presents itself in the application drawer when running a custom launcher with a live wallpaper
Common Bugs: N/A
General user Experience: Everything works as intended, TW is quick as usual with no laggy transitions or any lag in the Application drawer even when a live wallpaper is present.
Browser "html5test.com": 182 plus 1 bonus point
Browser Experience: Quick browsing. Switching tabs sometimes present a bit of Lag.
Link to ROM: N/A
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4.5
Setup: 3.5
Connectivity: 4.0
Look and feel: 3.0
Theme'ing: 0.1 - No built in theme support
Custom Original
Rarity Rom by lilbrat
Version of ROM: v3.85, although at the time development was halted I believe it was up to 4.2 or 4.5
Android Version: 2.3.5
ROM Date: Nov 2011
Rom Type: Custom Original
UI flexibility: Works well with both TW and after markets (currently using Go Launcher EX)
Common Bugs: none
General user Experience: Works very well and very stable though I'm an average user I haven't upgraded to any of the newer kernels or other things for me it works just fine. Battery life is ok ..average 2 days but like I said I'm an average user..few phone calls,sms..wifi and gps occasionally, Bluetooth for headset when I'm out..
Browser "html5test.com": Dolphin HD 7.3.. 182 plus 1, Firefox (Aurora) while still very new (beta with nightly updates..buggy) 318 plus 9
Browser Experience: It works well with Dolphin, and YouTube Facebook ect.
Link to ROM: Development currently has been halted..
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4
Setup: 3.8 takes a while to set up..
Connectivity: 5
Look and feel: 4.3
Theme'ing: 3.5 you need to try different things out that you want to add some things work some don't..
ROM Name goes here
Version of ROM:
Android Version:
ROM Date:
Rom Type: Custom Original
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:
Kitchen
ROM Checkrom revoHD v4 - By adamski123
Version of ROM: v4
Android Version: 2.3.6
ROM Date: latest update feb 8th (new kitchen) v6 coming soon.
Rom Type: Kitchen
UI flexibility: stock touchwiz. Nice and smooth.
Common Bugs: None known of
General user Experience: In my eyes best gingerbread rom. Fast and stable with the option to mod and tweak via the kitchen app.
Browser "html5test.com": i got 182 but i don't recommend taking that score to seriously
Browser Experience: Standard Samsung browser, good and fast, but tab support could be better.
Link to ROM: Will link when I get near a comp.
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4.8
Setup: 4.0
Connectivity: 4.0
Look and feel: 4.0
Theme'ing: 4.8
ROM Name goes here
Version of ROM:
Android Version:
ROM Date:
Rom Type: Kitchen
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:
Graphs as set out as per our criteria. The values given have been converted to account for 20% in each category
{
"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"
}
I hope you know enough to make valid comparisons.
Well done for trying
s2d4 said:
I hope you know enough to make valid comparisons.
Well done for trying
Click to expand...
Click to collapse
Well no one else will put in the effort so I will at least try. If there is any suggestions or fields that should be added please feel free to comment.
I will not personally flash to all the roms at all but will rely solely on user feedback to at least get a basic comparison going in the start.
toxicdust said:
Well no one else will put in the effort so I will at least try. If there is any siggestions or fields that should be added please feel free to comment.
I will not personally flash to all the roms at all but will rely solely on user feedback to at least get a basic comparison going in the start.
Click to expand...
Click to collapse
I see..
I was hoping that detailed comparison could be made.
Like themer roms, kanger roms, original dev roms.
Not just ppl with no clue making comments...
for instance, when jkay releases, numerous rom cooks just packages the framework-re.apk (maybe with png changes), plus add whatever other apk mods others have done, add someone's kernel, zip it up and call it a their rom.
or worse, mix and match apks between other releases and call it their own
Special mention needs to be done to differentiate all this between the good guys and the others.
For example, look at what hyperdroid v6 has done.
Without waiting for jkay, incorporated 14 toggles, added edt/ tsm tweaks, and make it play nice with the Hyperdroidparts to control it all.
Adding their own brand new red pill recovery and kernel, and even sharing the recovery with syah for a community collaboration effort.
Multidpi also came from hyperdroid.., smooth spinners tweaks,
updates to vrtheme via surgeons etc.
EDIT: You might want to remove quadrant as that only kills the credibility of the thread.
Well that's the whole thing. I want to list them but only the main players. Not the mix and match ones cause there are literally hundreds of them and they are all the same in 90% of all aspects.
I am editing the 2nd post a lot so refresh on occasion to see if there is something new.
I think I will stick with what we have now in the listed comparisons. If anyone has anything to add feel free and I will just add it to the list of Items.
s2d4 said:
You might want to remove quadrant as that only kills the credibility of the thread.
Click to expand...
Click to collapse
Any suggestions as to a bench to use that's a little more accurate? I have no idea what to use as a bench tbh
AnTuTu is a good bench.
B3311 said:
AnTuTu is a good bench.
Click to expand...
Click to collapse
-Took out irrelevant joke-
Thanks will replace quadrant with that
Anyway ... I think this is what the OP of that thread was looking for.
Sensation 2.0 rom with his own sexy theme...looks all great..and functions buttery smooth....maybe u can add in the list with other ROMS...
Lol ... I am actually trying to find some of the ROM's and cant even find the original threads as there are so many of them for different things.
If someone could link some of the ROM's we need to list or have listed it would be appreciated.
oinkylicious said:
But there's still nothing useful in here, just some vague statement about battery life on a "stock ROM" "Battery Life: 2 Days Moderate use to 5 Days minimal Use" seriously? Or was this part a joke? And no actual mention of which stock ROM the few random statements referred to (besides 2.3.4, which must be pretty old).
I'm actually against the idea of a compilation thread . Sure you might think it'll remove some of the clutter from these forums and daily "best ROM" threads (in all honesty, it won't, the people starting those threads don't read stickies or search), but it'd be quickly outdated and be full of the usual "I think x ROM is best with y kernel because of z".
For a user to get an idea of current ROMs, all it requires is an opening of the development forum(s), pressing CTRL+f, typing [ROM] and ticking "Highlight all" in whatever browser is used. Read first post for changelog/screenshots and making up own mind.
Click to expand...
Click to collapse
I was against the orginal idea too oinky, but it can work. I'll be in contact with toxicdust shortly and we'll get this done - promise.
You know your **** - help us! Send a PM.
oinkylicious said:
But there's still nothing useful in here, just some vague statement about battery life on a "stock ROM" "Battery Life: 2 Days Moderate use to 5 Days minimal Use" seriously? Or was this part a joke? And no actual mention of which stock ROM the few random statements referred to (besides 2.3.4, which must be pretty old).
I'm actually against the idea of a compilation thread . Sure you might think it'll remove some of the clutter from these forums and daily "best ROM" threads (in all honesty, it won't, the people starting those threads don't read stickies or search), but it'd be quickly outdated and be full of the usual "I think x ROM is best with y kernel because of z".
For a user to get an idea of current ROMs, all it requires is an opening of the development forum(s), pressing CTRL+f, typing [ROM] and ticking "Highlight all" in whatever browser is used. Read first post for changelog/screenshots and making up own mind.
Click to expand...
Click to collapse
Valid points. Thanks for the reply. I am using this stock rom but i should have probably added that I have the extended original 2000mah battery.
I do agree to some extent that it might get dated but when someone does a update or does review a new rom it takes 3 min to give your opinion and do a quick bench and just wrote everything down. I know it will take commitment from the community and obviously Dev's would want to boast with the Roms. There is no better way that a shootout for devs to actually go back and work on their rom to get better performance or less bugs ect ect.
Ultimately Users get better roms and there is a little bit of competition between the Devs for brag rights ofc
All in good sport I have to add.
s2d4 said:
I see..
I was hoping that detailed comparison could be made.
Like themer roms, kanger roms, original dev roms.
Not just ppl with no clue making comments...
for instance, when jkay releases, numerous rom cooks just packages the framework-re.apk (maybe with png changes), plus add whatever other apk mods others have done, add someone's kernel, zip it up and call it a their rom.
or worse, mix and match apks between other releases and call it their own
Special mention needs to be done to differentiate all this between the good guys and the others.
For example, look at what hyperdroid v6 has done.
Without waiting for jkay, incorporated 14 toggles, added edt/ tsm tweaks, and make it play nice with the Hyperdroidparts to control it all.
Adding their own brand new red pill recovery and kernel, and even sharing the recovery with syah for a community collaboration effort.
Multidpi also came from hyperdroid.., smooth spinners tweaks,
updates to vrtheme via surgeons etc.
EDIT: You might want to remove quadrant as that only kills the credibility of the thread.
Click to expand...
Click to collapse
since only the quadrant advice was taken, how are you going to differentiate the level of development by the rom makers?
toxicdust said:
Hi All
Seeing as this tread was motivated by some other trolls in a other thread I decided to take it upon myself to build a comparison list of Rom's out there and add their information to it.
This will ofc be a community effort to eliminate noob threads as some call it so for the last time share your collective knowledge and then you can refer all the noobs to this thread every single time.
If you feel the information in this topic is incorrect then please don't throw a hissy fit. Rather just correct it in a post and I will update the 1st post. If you want your rom to feature in this tread also reffer me to your roms page with all the relevant information so that I could find it there to update the tread with.
Please use the following template to Provide information for the ROM's being tested. This would help in getting them all together and tweaking them where needed.
Version of ROM:
ROM Date:
Battery:
Battery Life:
UI flexibility:
AnTuTu Score:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
If you feel the information provided is not accurate please just specify witch ROM you are referring to and what information is not correct as below and then a reason as to why you say so.
Stock Rom
Version: Actually 2.3.5
Reason for Edit:
Click to expand...
Click to collapse
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependant on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.
I am actually very impressed with whats happening here.
Respect to all of you.
*post may be removed*
s2d4 said:
since only the quadrant advice was taken, how are you going to differentiate the level of development by the rom makers?
Click to expand...
Click to collapse
That's why I need people like you to help and define what is needed so we can get relevant information.
jayerfernandes said:
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependant on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.
Click to expand...
Click to collapse
1. I could split it into the 3 groups and then categorize it accordingly. @s2d4 - would this help or do you think there should be better defined sections for them?
2. Agreed. There are a lot of variables that could make the test vary in results and it is very subjective. Could you give more detail as to what we should be seeing rather then Battery life.
3. If that is true we it could still be useful to the extent of determining if the rom is high in performance or rather a battery saver. I truly think if its the fastest out there it will consume the most battery doing so as well. Although that is subjective but could be relevant.
jayerfernandes said:
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependent on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.
Click to expand...
Click to collapse
Thanks for the suggestions.
Sent a PM to toxicdust, hope the hatchet is well and truly buried (and not in anyone's cranial matter either...). But he's the boss - his idea AFAIC.
1 - Agree completely. I haven't and won't try any CM9/MIUI ROMs, and am not interested in ICS before an official release. Any help/reviews/feedback would be hugely appreciated here.
2 - Agree. Too subjective to bother with, IMO. Forgot to ask toxicdust about this. If you're there toxic, what do you think? Trouble with your suggestion is the subjectivity of "apps everyone uses". For example, I'm the only person on this planet who isn't on Facebook or Twitter, doesn't use Google Maps, and I don't use e-mail on my phone - I don't want to be available to all and sundry 24/7. I'm pretty sure I don't fit a "usual user" profile.. But hey! I'm special... Suggest a list of apps that you think the majority use, and we'll try to collate battery stats from there. Good?
3 - I want to drop benchmark scores completely. Individual use etc makes it too subjective for me, and the last thing a noob needs is seeing a score - "oooohhhh! 3045060604+3 on Quadrant! This must be the ROM for me, lolz"...
Keep the ideas coming.
Gotta swallow my pride - which I do gladly - and admit that this is a damn good idea - we've just got to do it properly.
I can't theme and I can't code - but this ensures I'm doing something for the community.
I can write though
OFF TOPIC
By the way - I've got no problem with the removal of many of my posts on this thread- would just like to know who's doing it?
I realise that I'm not owed an explanation, and I'm not asking for one either - this isn't a democracy, as I've posted myself at least 40606003 times.
I'm not sending a general PM to all mods, so can the mystery mod please PM me?
Once more, I'll stress that I have no problem with you guys deleting - just curious.
Thanks.
Bets $1213256990 that I won't get a reply
---------- Post added at 08:19 PM ---------- Previous post was at 07:56 PM ----------
OmegaRED^ said:
*post may be removed*
Click to expand...
Click to collapse
Know the feeling. Mine are disappearing quicker than Lord Lucan.
I'm pretty sure it's a mod on a grassy knoll with a sidekick in the book depository. I just can't prove it yet
B3311 said:
Thanks for the suggestions....just can't prove it yet
Click to expand...
Click to collapse
To much to quote. Agree on your suggestions I will fix the 1st posts quick. I sent you a PM back.
I reported all the Posts with a "Post not relevant to topic" So that the posts could get deleted Wanted to Start this tread properly and that would just have brought everyone down in any ways
This thread is here to discuss new and old ROMs and KERNELS....
To have a place to openly compare ROMs and KERNELS to find the best combinations to keep our aging devices young!...
(Remember to always thank your developer(s) and donate if you can)
Please feel free to add links, changelogs and opinions (but respect others work and views )
And if someone helped you, remember to hit the "THANKS" button for them!
{
"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"
}
Rom Review Guide (Comparison Chart)
This is a guide of rom's I've tested.....
This is(are) the final update(s)..??
(Remember that this is based upon my own experience and may be biased)
Must haves
Here is a list of links to "must have" files for your phone or computer. It will include programs, kernels, mods and apks... I will try to keep it up to date and welcome suggestions on what to add..
-here- (this is a init. script that will automatically kill the media server saving battery, but not affecting your ability to use media)
-here- (Wug's Nexus Root Toolkit, for rooting/unlocking/flashing/fixing your phone)
-here- (flashing this will allow you to flash AOSP type kernels on CM roms)
-here- (flashing this will allow you to flash CM type kernels on AOSP roms)
-here- (this is an alternative radio for i9023 boosting some signal strength)
-here- (this .apk is for the latest flash player allowing you to use flash content on the web..)
-here- (this is an .apk for MI file explorer, it not only can check files on your phone, but also cloud providers!!)
Flash and install with care as I take no responsibility in the results of your use!!
Better Battery Life Tips :
Disable GPS, 3G, Wifi, Sync when not in use
Disable auto sync of Google and / or other accounts
Set brightness level to automatic or minimum
Disable auto rotation
Close / disable useless background apps
*Also try Greenify from the app store, for more free ram and battery saving*
**THIS IS NOT MY WORK, SO REMEMBER TO THANK THE DEVELOPERS**
YOUR REVIEWS ARE IMPORTANT TO US ! ! !
This is an amazing community of NS die-hards that are constantly looking for the best ways to keep the phone alive.
We need your input on ROMS, KERNELS, APPS, MODS and TWEAKS that can help improve our phone. As well
as tips on what doesn't work or what not to do.
If you try a rom,kernel,app,mod,tweak, please give your experience with it.
START WITH IT'S NAME AND DEVELOPER (LINKS ARE ALSO WELCOMED)
1. Performance
2. Battery life
3. Bugs or other issues
4. Favorite feature(s)
5. How you had it set up (cpu speeds, ect..)
6. Feel free to add any other relevant information
7. Would you recommend it
And remember, that these are opinions, be curtious, use the thanks button and ALWAYS thank your developers.
Okay, this is a bit of script that is a revised version of Killjoy using some input from Supremacy along with anything else shiny that I had to pick up..
-This cannot be used with any other tweak/mod of this nature
-This should only be flashed on a clean install of a rom (minus any mods/tweaks)
-This modifies your build.prop (any other mods may cause undesired effects)
-I suggest rebooting after installation and entering codes into the terminal emulator
-If coming from the original Killjoy or one of my versions, do an uninstall of previous version before installing
Use the Operation Killjoy thread to turn on/ off features as the rest of the modified script works without terminal commands..
THIS IS NOT MY WORK
DO NOT COMPLAIN TO THE ORIGINAL DEVELOPERS WITH ISSUES AS THIS IS A MODIFICATION OF THEIR ORIGINAL DESIGN
DO NOT USE THIS TO TAKE OVER THE WORLD (unless I get free cookies)
I do not take responsibility in any issues you or your phone have before or after flashing, nor for world hunger..
FLASH AT YOUR OWN RISK!!
DOWNLOAD
I thing is not good to compare rom ...because for me rasbeanjelly is the best..for other no
leap_ahead said:
I thing is not good to compare rom ...because for me rasbeanjelly is the best..for other no
Click to expand...
Click to collapse
All rom's are great, but for different reasons.. I would hope that the comparison doesn't diminish from the developers work, but allow for a better idea of what a rom offers.
Which is the best DPI value in your opinion? Slim for example uses very low DPI value but it is still nice. What is the advantages and the disadvantages of using low DPI?
Sent from my Nexus S using Tapatalk 2
NickName98 said:
Which is the best DPI value in your opinion? Slim for example uses very low DPI value but it is still nice. What is the advantages and the disadvantages of using low DPI?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
I use the stock 240 that most custom rom's use, other than issues with apps in the Playstore, I see no advantage nor disadvantage to dpi. It is helpful to lower it if you like having dual panels, but I like to be able to read the already small text on my screen and with my aging eyes there is no need to make it smaller..
Setting.Out said:
Don't look if you don't want the truth
Click to expand...
Click to collapse
Your (or anyone's) ROM review cannot be the absolute truth.
Truth #1: Custom ROM performance, stability, and overall smoothness are highly dependent on how a person prefers to use his particular device on a day-to-day basis.
Truth #2: The stability of a Custom ROM is entirely based on how a person uses the rom's features & system apps, and what kind of 3rd party apps s/he installs and uses the most. Apps found in the google playstore are mainly optimized for Official Android ROM's stability.
To further give users basis on how you do your rom reviews/guides:
1. What apps did you install and uninstall when you flashed the rom?
2. How old is your device?
3. What apps do you use most often? (including system apps)
4. What custom rom features do you use, and how often do you use them?
5. Why won't you use certain features, and what certain features causes instabilities and/or performance drops on certain ROM/s?
6. How long do you test the ROM before you make a conclusion with regards to its speed, smoothness, features, stability, and battery life?
You are not obliged to answer. This is your thread after all
ps. Mirage rom is created by des-franco. People might confuse this with franciscofranco.
ej8989 said:
Your (or anyone's) ROM review cannot be the absolute truth.
Truth #1: Custom ROM performance, stability, and overall smoothness are highly dependent on how a person prefers to use his particular device on a day-to-day basis.
Truth #2: The stability of a Custom ROM is entirely based on how a person uses the rom's features & system apps, and what kind of 3rd party apps s/he installs and uses the most. Apps found in the google playstore are mainly optimized for Official Android ROM's stability.
To further give users basis on how you do your rom reviews/guides:
1. What apps did you install and uninstall when you flashed the rom?
2. How old is your device?
3. What apps do you use most often? (including system apps)
4. What custom rom features do you use, and how often do you use them?
5. Why won't you use certain features, and what certain features causes instabilities and/or performance drops on certain ROM/s?
6. How long do you test the ROM before you make a conclusion with regards to its speed, smoothness, features, stability, and battery life?
You are not obliged to answer. This is your thread after all
ps. Mirage rom is created by des-franco. People might confuse this with franciscofranco.
Click to expand...
Click to collapse
"YOU WANT THE TRUTH,.. YOU CAN'T HANDLE THE TRUTH"... I may be too old for everyone to catch that reference..?
Phew, you made a list..
1. I let Google auto-update my rom(s) with my 100+ apps (too many to list)
2. My device is roughly 2 yrs old (but don't tell it how old it is, it's sensitive)
3. I use FB, Gmail, Yahoo, XDA, Youtube, ect... Some minor games and french lessons (as I should be practicing that instead of this... lol)
4. I use all of them to test, but I don't use most of them as daily drivers as I have no use in some of the features..
5. I think that certain features like Xposed framework and PA settings rob performance and are unstable.. I also don't like to run overclocked. Some rom's/ kernels can handle these features, but I find them pointless.
6. Two battery cycles.. The first is to install/test if it will be buggy, the other is to see how well it holds up to my normal day to day..
And I admit that my reviews are based on one phone (as all phones can vary) and personal usage that is subject to bias and change..
Can you please review 4.1.2 roms?
OnlySkills said:
Can you please review 4.1.2 roms?
Click to expand...
Click to collapse
Any in particular?..
OnlySkills said:
Can you please review 4.1.2 roms?
Click to expand...
Click to collapse
Feel free to share any experience you've had with a rom.. I, and others would like your input as well..
Setting.Out said:
Any in particular?..
Click to expand...
Click to collapse
SlimBean 3.1, HellyBean, CM 10 (which you already have), and other popular ones. Particularly because I am trying to find a good 4.1.2 ROM that is smooth and has great battery life. Currently on Slimbean with marmite, and I'm not liking the battery life (Usually get around 20% screen time usage which is on for 1-1.5 hours only)
Edit: SlimBean 3.1 - it is PACKED with features, 10/10 on that (I have everything I could possibly want). Performance is really great too, little lag sometimes only. The only downside is the battery life as I stated above.
just to say that with my device and with my user experience on the roms you've tested: i agree with a lot of what you say in your rom guide!
nice work!
OnlySkills said:
SlimBean 3.1, HellyBean, CM 10 (which you already have), and other popular ones. Particularly because I am trying to find a good 4.1.2 ROM that is smooth and has great battery life. Currently on Slimbean with marmite, and I'm not liking the battery life (Usually get around 20% screen time usage which is on for 1-1.5 hours only)
Edit: SlimBean 3.1 - it is PACKED with features, 10/10 on that (I have everything I could possibly want). Performance is really great too, little lag sometimes only. The only downside is the battery life as I stated above.
Click to expand...
Click to collapse
I ran Hellybean 4.1.2 for about two weeks and it was great, I did change kernels on it and increased battery life immensely.. Have you tried the newest Marmite with your Slim rom, it should be compatible and would help your battery life.. Also try Greenify and hibernate all your apps minus the launcher and greenify itself.. you will see an improvement.. I also would suggest to limit the apps that want to auto sync and shut down google maps unless you are using it..
Hey setting out, I'm pretty sure that rasbean jelly is 4.2.2 now. Rusty
Jay has been updating it recently
much needed thread
thank you very much OP
this is a much needed thread. i think all devices should have a thread like this.
its very useful to people new to a certain device and to those like me who dont have the time to test all roms available.
i have tested slim and thinkbridge extensively and gamerz, cm, xylon only for short time. settled with slim because it had best battery life in my device and was devoid of unnecessary stuff i wouldnt use.
i think you can expand your comparison to include some prominent/differentiating/special feature of each rom. it would be easier for the readers to get better idea about which rom would fit his/hers needs. for example, i like slim because,
1. i like the "dark slim"
2. it doesnt have all the wall papers or live wall papers that i wouldnt have used anyway, thus, freeing more memory.
thanks. keep up the good work.
Editing
[20-Aug-2018] NEW: For the ranking table with normalized scores of Oreo Treble Kernels head directly to post #421.
Let me first say that is not a "best rom" thread. There is no absolute best rom. What is best for one user may not be best for another. To give a simple example, battery is very important for some users while performance is priority for others.
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats a series of tasks including web browsing, photo and video editing, text editing and data manipulation.
For each rom I made a clean install and a simple setup with basic settings and a few apps necessary to monitor/admin the runs.
The tests are run with the screen brightness calibrated at 200 lumens as required by PC Mark and all sound levels set to zero, so results are better suited for comparison.
Each benchmark run takes over 8 hours. So this test is also a stability test. Some rom/kernel combinations simply fail to complete the test.
Here is the index of all my mido benchmarks compilations:
Treble Oreo Roms ranking table - post #390.
Latest preview of Treble Kernels - post #413.
Latest preview of Treble Roms - post #343.
Previous preview of kernels benchmarks - post #256.
Previous Kernel normalized scores and ranking tables - post #273.
Non-Treble Oreo & Nougat Roms - post #4.
Previous Compilations - Roms & Kernel - post #5.
04-May-2018 - Kernel Poll Results:
I had 75 votes in my kernel poll. Thanks to you all. Here are the poll results:
# Votes / Kernel
34 FrancoKernel
12 ElectraBlue
09 KudKernel
06 Xenial
04 Velvet
03 Revolt
03 Stormguard
02 None of the above
02 ZPX Inferno
00 Chewy-Weeb
75 Total Votes!
.
Reserved
Reserved
The following is the series of Nougat and non-treble Oreo Roms prepared between February and April 2018.
Let me first say that is not a "best rom" thread. There is no absolute best rom. What is best for one user may not be best for another. To give a simple example, battery is very important for some users while performance is priority for others.
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats a series of tasks including web browsing, photo and video editing, text editing and data manipulation.
For each rom I made a clean install and a simple setup with basic settings and a few apps necessary to monitor/admin the runs.
The tests are run with the screen brightness calibrated at 200 lumens as required by PC Mark and all sound levels set to zero, so results are better suited for comparison.
Each benchmark run takes over 8 hours. So this test is also a stability test. Some rom/kernel combinations simply fail to complete the test.
It took almost three weeks to run these tests with two midos dedicated for it 24/7!
If you want to learn more about PC Mark take a look at the site: PC Mark for Android.
For this compilation I picked the following roms:
RR-N-v5.8.5-20180121-mido-Final by @Alexey71 - Alexey71's Sourceforge
RR-N-v5.8.5-20180128-mido by Luis @8224Freak - [ROM][UNOFFICIAL][7.1.2][NIGHTLY][OTA]Resurrection Remix-5.8.5 for Redmi Note 4
liquid_remix-9.0.4-20180205-OFFICIAL-mido by @nikhil020 - [ROM][OFFICIAL][8.1.0] [MIDO] Liquid Remix [9.0.4][UPDATE 05/02/2018]
AospExtended-v5.1-mido-20180122-1306-OFFICIAL by @[email protected] - [ROM][8.1.0_r11][BETA][AOSP][OFFICIAL] AospExtended ROM V5.2 [DUI][10/02/2018]
crDroidAndroid-8.1-20180203-mido-v4.0-BETA by @Soubhik_sk83 - [ROM][OFFICIAL][OREO 8.1]**crDroid v4.0 BETA**[Redmi Note 4][SD][20180215]
PixelExperience_mido-8.1.0-20180206-1530-OFFICIAL by @nikhil020 - [ROM][OFFICIAL][8.1.0][MIDO] Pixel Experience [AOSP][r1]
RR-O-v6.0.0-20180219-mido-Official by @Adesh15 - [ROM][OFFICIAL] Resurrection Remix v6.0.0 [8.1.0][mido][r1]
RR-O-v6.0.0-20180314-mido-Unofficial by @EndLess - [UNOFFICIAL] Resurrection Remix v6.0.0 [8.1.0][mido]
AOSiP-8.1-Official-mido-20180313 by @Adesh15 - [ROM][8.1.0]Android Open Source Illusion Project[mido][OFFICIAL]
omni-8.1.0-20180325-mido-WEEKLY by @khan_frd2002 - [ROM][OFFICIAL][8.1] OmniRom [STABLE]
lineage-15.1-20180327-Extended-mido by @Alexey71 - Alexey71's AFH LineageOS Extended builds
RR-O-v6.0.0-20180405-mido-Unofficial-LuisROM by @8224Freak - [ROM][UNOFFICIAL][7.1.2][NIGHTLY][OTA]Resurrection Remix-5.8.5 (also Oreo in same thread)
RR-O-v6.0.0-20180407-mido-Unofficial by @EndLess - [UNOFFICIAL] Resurrection Remix v6.0.0 [8.1.0][mido]
Of course I could not use all the latest builds, remember it takes weeks to run all benchmarks.
Enough talk. Now Let's see the results:
{
"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"
}
Score is a performance index - the higher the better.
SOT (Screen On Time) is an estimate of the number of hours the device may be used until battery drops dead (from 100% to 0%). It's a very good estimate because the test starts with the battery at 86% and ends when the battery drops to 20%.
There is no clear advantage comparing Oreo roms. They all offer similar performance and battery drain.
Nougat RR is still better in both performance and battery drain, again with no expressive advantage over Oreo.
So any of there roms will serve you well and you should pick one based mainly on the features you want.
25-Feb-2018 Update:
Added RR-O Official. Its performance score is similar to other Oreo roms, but SOT is a little behind - 10:37 hours - one hour less than average. Not a big problem because any number over 10 hours is probably good enough for most people.
07-Mar-2018 Update:
Added RR-O Alexey's build. Its performance score and SOT are below other Oreo roms averages. When compared to official RRO SOT is a little better - 11:06 x 10:37 hours and performance score is worse - 4235 x 4763. My benchmark was done with 2018-0303 build and Alexey has a new build almost everyday. I plan to benchmark it again sometime in the future.
24-Mar-2018 Update:
Added @EndLess's RRO and @Adesh15's AOSiP.
This time I broke the results spreadsheet into two, one for Resurrection Remix builds and one for all other Oreo builds.
Adding two more roms once again proves that there is no major difference between Oreo roms. Any one of these roms offers similar performance and battery SOT.
The new RRO build by @EndLess offers the best combination of performance ans battery for Oreo RR. Still Nougat roms have better figures and there is the RRO LuisBUILD by @8224Freak still to be tested.
For the other Oreo roms, the newcomer AOSiP has a slight disadvantage compared to the others. But again this should not influence your choice. Features should be the deciding factor.
03-Apr-2018 Update:
Added @khan_frd2002's Omni and @Alexey71's LineageOS Extended.
Again no surprises. Omni is very fluid, but has slightly less than average SOT. LA Extended has less than average performance and a good SOT.
All tested roms so far are more than capable to serve you well.
14-Apr-2018 Update:
Added RRO by @EndLess 2018-0407 and RRO by @8224Freak LuisBUILD 2018-0405.
RR Oreo roms are evolving, but still RR Nougat roms have better battery/performance.
@EndLess's RRO reached 12 hours SOT, with below average performance - score was 3878.
@8224Freak's has a better compromise of battery/performance, with 11:29 SOT and 4645 performance score.
Thanks @y2ksnoop for the following extra information, based on his usage experience:
The Endless rom has downclocked the CPU to 1.6GHz for better battery life. Though the bench scores are low, there isn't any hiccups in day to usage. The rom is really smooth and games do run fine without heating for a extended time. The thermal management is excellent and the throttling doesn't kick in early. It's the best RR stable build for day to day usage. The next best would be Luis RR Oreo rom which has SE Linux mode enforced by default.
Click to expand...
Click to collapse
.
This post includes some of my previous compilations. You may find them interesting, but rom and kernel builds are old for obvious reasons.
The following was posted on 14-01-2018, see original post here.
I have just finished testing @Alexey711's Velvet 6.5 kernel that came with RR-N-v5.8.5-20180109-mido-Final new led driver.
Here are the results:
Comparing to Velvet 5.5 battery drain has improved a little and performance is the same.
I did not experience any problems copying files with this build. I use Root Explorer.
Please note that this is not the latest build. Running these benchmarks take a long time and it is difficult to keep up with Alexey711.
The following was posted on 06-01-2018, see original post here.
Here is my latest compilation of PC Mark Battery Life Benchmarks to compare currently available kernels for the Redmi Note 4
If you haven´t read my previous posts and need more info on PC Mark read the explanation at the end of this post.
This time let´s start with the results:
All test were done with @Alexey71's RR-N-v5.8.5-20171219-mido-Final new led driver, using stock kernel and the available custom kernels at this moment.
There is one kernel missing: Stormguard. Unfortunately if failed to complete the benchmarks too many times.
Again there is no clear winner.
if your main goal is battery life and you don't worry about sacrificing some performance your kernel of choice should be Velvet, with an average SOT of 13:28 hours and average performance score of 4092. Good alternatives are Revolt kernel, with 12:52 SOT and 4239 performance, and Xenial kernel, with 12:40 and 4272. Both had more consistent results then Velvet.
If you are looking for the best performance then ZPX Inferno should be your kernel, with an average performance score of 4822 and an average SOT of 12:07 hours. ZPX had almost no variation in SOT between runs, with a mere 0,1% variation.
For a balance between battery and performance the best choices are ElectraBlue, with 4677 and 11:59 and RR Stock kernel, with 4623 and 12:14.
It took almost two weeks to run these tests with two midos dedicated for it 24/7!
This time I calibrated the brightness output of each kernel to 200 lux, as required by PC Mark, so results are better suited for comparison.
Now some words on benchmarks and PC Mark:
Benchmark results are usually misleading, but PC Mark battery life benchmark shines by using day to day tasks to measure phone performance and battery drain. It repeats a series of tasks including web browsing, photo and video editing, text editing and data manipulation.
For these runs I started the benchmarks with battery precisely at 85% and the test automatically stops when battery reaches 20%, so the test consumes 65% of the battery charge. Of course the screen is always on during the whole test.
If you want to learn more about PC Mark take a look at the site: PC Mark for Android.
Where to get the kernels:
Stock/RRN - Alexey71's AFH
Revolt - [Kernel][mido] ReVolt Kernel [Los/Aosp]
ElectraBlue - [KERNEL][mido] ElectraBlue Kernel 8.1 For Redmi Note 4
Xenial - [Kernel][Xenial][Mido]
Velvet - Adesh15's Velvet AFH
ZPX Inferno - ZeroProjectX´s mido AFH
.
svbarbosa said:
Ok. This is the last one.
Click to expand...
Click to collapse
Hey. Remove my RR and Add PE https://www.androidfilehost.com/?w=files&flid=250537
By default the balance profile (cpu1.6- gpu510), you need to change the profile to perfomance
Alexey71 said:
Hey. Remove my RR and Add PE https://www.androidfilehost.com/?w=files&flid=250537
By default the balance profile (cpu1.6- gpu510), you need to change the profile to perfomance
Click to expand...
Click to collapse
These benchmarks take so long that I prefer to leave the numbers just for comparison. Even if the rom is not available anymore. Hope you don't mind.
Is there any chance you build RR-O? Your builds are the best and my personal preference is RR. This is no secret.
Such an honor having @Alexey71 and @sachin n as the first two to thank my thread.
svbarbosa said:
Is there any chance you build RR-O? Your builds are the best and my personal preference is RR. This is no secret.
Click to expand...
Click to collapse
Unfortunately no, I liked PE
Hey, nice tests! But what about Franco Kernel? Please test it with both Nougat and Oreo... Thx https://forum.xda-developers.com/re...el-francokernel-r1-4th-feb-lineageos-t3744668
https://kernels.franco-lnx.net/RedmiNote4/
Sent from my Redmi Note 4x
Can you add dirty unicorns nougat 11.7.2 version for comparison ?
Alexey71 said:
Unfortunately no, I liked PE
Click to expand...
Click to collapse
+1, hi @AlexY71 is there a thread for your pe?
Thanks, good work
What about stock miui 9.Try to add it next time. any way you did a great job ?
Great work man. Just one note - try to compare the same governors and i/o schedulers. Now, you are comparing a little bit incomparable, cfq vs maple...
Keep it up.
Alexey71 said:
Unfortunately no, I liked PE
Click to expand...
Click to collapse
Is there any chance of adding network traffic indicator on your PE builds?
Alexey71 said:
Unfortunately no, I liked PE
Click to expand...
Click to collapse
Nice riview bro
Can you do the same test using the official global rom and the official beta rom? Thanks.. Very nice topic!
Alexey71 said:
Unfortunately no, I liked PE
Click to expand...
Click to collapse
Well, if you change your mind please keep RR-O in the top of your list of "next to build" roms.
sajty said:
Great work man. Just one note - try to compare the same governors and i/o schedulers. Now, you are comparing a little bit incomparable, cfq vs maple...
Click to expand...
Click to collapse
I know. Depending on tweaks the benchmark results may vary a lot. @Zile995 also pointed out that tweaks could have a great impact on results.
But it takes so long to run the benchmarks that I would never finish them if I had to start trying different options for each rom/kernel.
So I have decided to always test the roms and kernels "as they come". No modifications at all. I just leave it up to the devs to decide what is best for their builds.
spasoje.lugonja.3 said:
Hey, nice tests! But what about Franco Kernel? Please test it with both Nougat and Oreo... Thx https://forum.xda-developers.com/re...el-francokernel-r1-4th-feb-lineageos-t3744668
https://kernels.franco-lnx.net/RedmiNote4/
Click to expand...
Click to collapse
Kevin Saiza said:
Can you add dirty unicorns nougat 11.7.2 version for comparison ?
Click to expand...
Click to collapse
mithun mpk said:
What about stock miui 9.Try to add it next time. any way you did a great job
Click to expand...
Click to collapse
drakylucas said:
Can you do the same test using the official global rom and the official beta rom? Thanks.. Very nice topic!
Click to expand...
Click to collapse
I will try my best to accommodate requests, but no promises.
Too many roms and kernels and too little time.