{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, I'm sure many of us have the burning question of which ROM/kernel any of us should use when it comes to pure performance. With so many ROMs out there, ones based on OOS, Havoc, Paranoid Android, crDroid, OmniROM, MIUI, the list just absolutely goes on. I want to use this thread as a way to inform people of any potential performance gains/loss when it comes to choosing a ROM, as well as just a thread to compare/talk about benchmarks in general.
So I've taken the liberty to run five different setups, (I can take some more as requests, if necessary.) and ran A LOT of benchmarks between all of them to see which ROM provides the best performance. These tests include four various games, some synthetic benchmarks, and storage tests. At the end of it all, I ran all the tests with some pretty heavy kernel based performance modifications that gave a surprising amount of performance gains in some scenarios.
The ROM setups I am using are:
Completely Stock (OOS Beta 11 with zero modifications)
Stock OOS Beta 11 but Magisk / xXx NoLimits xXx 10.1 / Data Formatted as F2FS
HavocOS 3.3 Build 3/17 w/ F2FS
Paranoid Android Quartz Beta 5 w/ F2FS
& Paranoid Android Quartz Beta 5 w/ F2FS AND SmurfKernel 3.5.1 rc17 slmk w/ Overclocks Enabled
All benchmarks were ran under the scrcpy ADB screen mirroring software, and under the settings I've used, it's shown to not provide any amount of performance loss. The command/options I've ran are "scrcpy --render-expired-frames -b 2M -m 768". That makes scrcpy not drop any lost frames (which will increase delay but make frame rate recording much more accurate), have a bitrate of 2Mbit/s, and have a screen height of only 768, which is easy for the phone to do while not incurring any performance loss. Game performance was recorded using MSI Afterburner over the scrcpy window, which isn't THE MOST accurate, but is the only option available due to certain apps not being able to be run under OOS (i.e. KFMARK actually offers these features in app, but crashes on OOS.)
So, lets get started, first, with the gaming benchmarks. I've chosen these games because they are the only ones that are intensive enough on the phone's hardware that can run without hitting the game's frame rate cap. The overclocking kernel of choice for these tests are @pappaschlumpf's SmurfKernel, all my settings can be found here.
GAMES:
Game 1:
Game 2:
Game 3:
Game 4:
ANTUTU:
3DMARK:
Test 1:
Test 2:
Test 3:
Test 4:
Test 5:
GFXBench 5.0:
Set 1:
Set 2:
Set 3:
Set 4:
Geekbench 5
AndroBench (Storage):
Set 1:
Set 2:
So, what is the takeaway from all this? Which is the winner of the best performing ROM? I think the short answer is, well, no one. Long answer? It really depends. Currently, I don't think ROMs alone can offer any amount of increase in CPU/GPU, giving any extra gaming performance. That seems to be solely up to the kernel.
At a glance, it may look like Havoc offers an immense increase in gaming performance from looking at all of the benchmarks. However, after checking Kernel Tuner, I actually noticed its kernel overclocks the GPU to 675 MHz, (up from 585).
Strangely, OOS seems to offer better SQLite performance than both other ROMs until some serious kernel tweaking is introduced. It may look like xXx NoLimits xXx gives higher storage based scores, but the gains were due to /data being formatted to F2FS. Thus, it seems like NoLimits provides zero recordable performance difference. Not sure what they mean by Speed/RAM optimized. Maybe it's just purely a debloating and keep-more-apps-in-Ram tool.
CPU scores between all ROMs is all within margin of error. I noticed higher MEM/Storage benchmark scores on AOSPA, as well as slightly faster app install times. However I imagine that comes from the fact that it uses the @arter97 kernel, not due to the ROM itself.
So, with all this said, I think the best ROM to choose is whichever one you feel like has the best features / ability to be a daily driver, not what you think will be better performance. I am personally sticking with Paranoid Android because some others have one or two annoying bugs that they haven't squashed and apps like Reachability Cursor and KFMark work seamlessly on it (unlike OOS).
remarkable
I miss crDroid, AOSPA and TreskMOD in that comparison. Good work anyway !
Mystenes said:
I miss crDroid, AOSPA and TreskMOD in that comparison. Good work anyway !
Click to expand...
Click to collapse
How on earth did you miss AOSPA?
rejectedjs said:
How on earth did you miss AOSPA?
Click to expand...
Click to collapse
Should be AOSiP
Mystenes said:
Should be AOSiP
Click to expand...
Click to collapse
AOSiP is based on pure AOSP and doesn't have any official Android 10 releases, it's still running Pie, so I don't want to waste time getting into it. TreskMod is just another mod of OmniROM, which HavocOS is already largely based from. crDroid looks interesting, so I'm currently running it and trying it out for myself and will update with benchmarks eventually.
for a reliable test, you must flash the same kernel with same settings in all roms, smurf kernel for example works in stock and customs.
You have smurf kernel with forced 90 hz, the same setup must be in all customs and is misconfigured, if you have surfaceflinger boost on, you must disable frame commit boost and viceversa.
how about call of duty mobile game?did you test it out?thanksyou
Toni Moon said:
for a reliable test, you must flash the same kernel with same settings in all roms, smurf kernel for example works in stock and customs.
You have smurf kernel with forced 90 hz, the same setup must be in all customs and is misconfigured, if you have surfaceflinger boost on, you must disable frame commit boost and viceversa.
Click to expand...
Click to collapse
I know SmurfKernel works on OOS / AOSP, the overclocking benchmarks weren't there to show "Look! SmurfKernel + AOSPA is so much better than others!", it's to show people how much of a difference overclocking can make, for them to make the decision of whether they think SmurfKernel's overclocking is worth flashing for or not. I didn't flash the same kernel to all ROMs because that's not the way the developers intended it to be. If the developers wanted their rom to be best experienced under SmurfKernel, they would have either explicitly stated it or packaged it in with the ROM. For example, the way AOSPA does with arter97's kernel. Flashing Smurf to everything would have defeated the purpose of comparing the ROMs.
xNovaLeader said:
how about call of duty mobile game?did you test it out?thanksyou
Click to expand...
Click to collapse
Call of Duty Mobile already runs at it's frame rate cap of 60FPS on our phones, there would be zero difference between ROMs.
rejectedjs said:
I know SmurfKernel works on OOS / AOSP, the overclocking benchmarks weren't there to show "Look! SmurfKernel + AOSPA is so much better than others!", it's to show people how much of a difference overclocking can make, for them to make the decision of whether they think SmurfKernel's overclocking is worth flashing for or not. I didn't flash the same kernel to all ROMs because that's not the way the developers intended it to be, if the developers wanted their rom to be best experienced under SmurfKernel, they would have either explicitly stated it, or packaged it in with the ROM, like the way AOSPA does with arter97's kernel. Flashing Smurf to everything would have defeated the purpose of comparing the ROMs.
Call of Duty Mobile already runs at it's frame rate cap of 60FPS on our phones, there would be zero difference between ROMs.
Click to expand...
Click to collapse
isee..thanks for the info..its suck when its come to flagship phone with higher refreshrate..
Wow, that's great! Now it seems almost strange why this wasn't done so far What about battery? It would be interesting to benchmark idle / active drain (maybe in 2 scenarios like chrome browsing and other in gaming?), just a though
spawnn617 said:
Wow, that's great! Now it seems almost strange why this wasn't done so far What about battery? It would be interesting to benchmark idle / active drain (maybe in 2 scenarios like chrome browsing and other in gaming?), just a though
Click to expand...
Click to collapse
I would like to do a battery life test but there are so many variables that would really come down to end user experience that I don't think it would be an accurate representation of the ROM's performance. If there's an app that just constantly drains the battery life, maybe I could try that, but I feel like that would take a really long time to post results for since that would be one ROM's results a day.
Thanks for this. I'm currently running OOS 10.3.1AA with arter97 r54 kernel ?? pretty happy with performance and kernel overall.
Best thread I've seen on xda in years. Thanks for this! :good:
Pfeffernuss said:
Best thread I've seen on xda in years. Thanks for this! :good:
Click to expand...
Click to collapse
Thanks! Lol, I'm glad it's getting some attention considering all the time I spent wiping and having to restart so much to get all the info!
rejectedjs said:
I would like to do a battery life test but there are so many variables that would really come down to end user experience that I don't think it would be an accurate representation of the ROM's performance. If there's an app that just constantly drains the battery life, maybe I could try that, but I feel like that would take a really long time to post results for since that would be one ROM's results a day.
Click to expand...
Click to collapse
PCMark has a battery test which works really well, but it takes like 9 hours to run haha
Would be awesome to see though
Thua far, the absolute smoothest experience Ive had on this phone has been OOS + Smurf + xXx. Without smurf, Ive seen no difference with or without xXx, however with it, the phone is butter smooth, its an enormous difference. Benchmarks on my phone are lower because I keep clocks low to save on battery, however even then the phone blazes through everything. Has a few kinks here and there that are admittedly quite annoying, though, so I am looking into other kernels a bit. Appreciate the post. Ill probably continue avoiding AOSP roms, Oxygen has spoiled me, such a good Rom.
Ruvaldak said:
Thua far, the absolute smoothest experience Ive had on this phone has been OOS + Smurf + xXx. Without smurf, Ive seen no difference with or without xXx, however with it, the phone is butter smooth, its an enormous difference. Benchmarks on my phone are lower because I keep clocks low to save on battery, however even then the phone blazes through everything. Has a few kinks here and there that are admittedly quite annoying, though, so I am looking into other kernels a bit. Appreciate the post. Ill probably continue avoiding AOSP roms, Oxygen has spoiled me, such a good Rom.
Click to expand...
Click to collapse
Arter kernel is a rather nippy and no stutters or hickups noticed yet, perhaps give that a whirl!
And how about battery drain ? Sot and idle ?
Related
http://board.teamwhiskey.com/viewtopic.php?f=3&t=53&start=0
Project is simple in design and is a work in progress, overclock as far as we can go with ample supplied voltage for maximum stability. These are the screenshots taken last night from the last few builds of the evening, were up to something like 40 builds so far trying to get everything just the way we want it to run, look, and feel.
Currently we are overclocking both the GPU and CPU using both base frequency modifiers and multipliers. This is allowing us to directly push the GPU to its stable limit while adjusting out the CPU accordingly.
Project Developers
Morfic and Viralblack of Team Whiskey. This is and will continue to be Morfic's baby until the phone prints money and/or can transform into a jet.
The Short and Long term goals are the following:
-To optimize the kernel with the best toolchains available to us
-Inject vital code enhancements for stability and to extend the feature set of the SGS Vibrant line
-To determine Min/Max Voltage, Bus Clock, and Multiplier values for Maximum Overclock and Maximum Effecient Overclock
-Continue to push the GPU to its theoretical maximum independant of CPU clock values.
Target Numbers and Current Results.
CPU Target 2.0GHz, Current Maximum Overclock 1.6 Stable (Time limitation only, havent rebuilt to try more)
GPU Target 85 FPS Stable Bench, Current 78 FPS
At current this is a JFD Stable build thats more than fairly bulletproof on battery life. To use with JI6 builds just flash Eugene's JFD/JI6 support package.
{
"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"
}
This is NOT a hoax or scam, these are real DDMS screenshots from the build currently in progress, as it has not yet been released we do not have code or kernels available until we know its running smoothly. The following zImage is a prerelease alpha. Its strictly for proof of concept. This kernel is mildly optimized and includes the CPU and GPU overclocks. In three of three test phones the CPU was stable, in two of three phones the GPU was stable. One test phone was not able to complete neocore under this coding.
Battery life has proven about the same as traditional OC/UV kernels. This is NOT our finished product, this is an Alpha for proof of concept for other developers. Run at your own risk. There is no failsafe, this does not require SetCPU to engage. It comes out of the box at 1.6GHz with steppings of 1,2,4,8,16
Currently, tested incorporations with the zMod have shown that overclocking renders the zMod unstable and bricks the device. I personally preferred to use RyanZAs OCLF v2.2 APK.
I had one out of 20 quadrant runs fail because I switched scheduler away from deadline. CFQ proved to be less stable for one reason or another when running quadrant.
This thread will be updated as work progresses, Do not flash this if you do not know what youre doing. Suggestions are welcome for integrated features you would like to see in this kernel, we will not however be fielding bug reports as this right now is staged as a Prerelease Alpha or RC0.
If when this is flashed your phone crashes and is unable to work, my suggestion is odin the stock kernel back in place and wait for a lighter overclock version to be released.
Download -
Removed while core is being rewritten
EDIT 10/28:
To update the project and to iterate why the download link was removed, the kernel seems to be misbehaving and we havent yet nailed down the correction as of yet.
As many people pointed out once it was released, the kernel seems to slow down 3D graphics. With this information and taking a day to go through all the options and data available to me, we discovered this issue isnt limited to just 3D graphics.
Imagine if you were running at 10MPH, and while you were running time slowed down but the slowdown didnt effect you. So youre still running at 10MPH but to the rest of the slowed down world, now youre running at 15MPH, even though your speed and direction havent changed.
The changes in the code for one reason or another arent playing nice with the Android system. Instead of pushing the clock up, in most cases, what its doing is simply slowing the internal clock down to the tune of about 30%. This is what is actually providing the benchmark gains that were being recorded, not an actual gain. This doesnt mean that the project is dead, we are recompiling to get a stable overclock with the new configurations. This doesnt mean the project was a failure, it just means we need to rewrite the alpha.
Edit 10/30 -
So, we are having distinct issues removing the timing error from the kernel while maintaining the integrity of the time system. So, being that the timing is much more important, we began rewriting it all from scratch. This is currently marked as Project Core in the same forums. Core is taking the best of the overclocking and fine tuning that this kernel has and combining it with energy effeciency and stability a daily driver phone needs.
So, we will be balencing the high end power thats desired and the low power use that is needed in this new project. With that being said, I dont believe that 1.6GHz (in my own humble opinion) is even remotely necessary for 99 percent of phone, let alone for daily use. This project is being succeeded by Core to make a power friendly daily driver kernel.
The kernel will still be available from the forums Alpha/Beta Download Section, but will not be supported as its being replaced by Core.
We found the redline Now we need to find the happy medium. If you enjoyed this release, youll love Core and Core with zMod.
Thread Locked until release, OP PM me when you want to release it
Good work TW
You guys should start working on a 2.2 version (Once you get this one smooth)
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
n2ishun said:
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
Click to expand...
Click to collapse
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Eazail70x7 said:
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Click to expand...
Click to collapse
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Master™ said:
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Click to expand...
Click to collapse
Yeah, mine will get warm, but I've never seen it get real hot.
testing now . just flash with clockwork? this is super cool guys. props
blackerwater said:
testing now . just flash with clockwork?
Click to expand...
Click to collapse
Yes, its CWM flashable, but be careful with it. There is no failsafe, if your phone cant handle the overclock itll just crash as its set automatically to 1.6GHz topend
So far so good. Just got a linpack of 12.062. Outstanding job guys!
doesn't work yet. just sits on vibrant screen. its cool ill just flash back ji6 zimage then it should boot. im on stock ji6..... I have a vibrant that can handle 1.3mhz for sure and voodo so ill keep playing with it.
Will this run with stock ji6?
Thank you so much for uploading! I reread about it in phandroid and was about to ask around for it
Sent from my SGH-T959 using XDA App
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
Right now ive only tested it on Fusion personally
Viralblack said:
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Click to expand...
Click to collapse
Excellent. I hope you guys can get an Epic soon and work some magic. Also good to hear thatyou'll be working with other devs. Good luck
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Have you tried flashing the back kernel support file for JI6 then flash this kernel?
Whitehawkx said:
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Click to expand...
Click to collapse
ok ill give that a shot. thanks
Will this work with voodoo?
Bionix Fusion 1.0 Jacs Xmod Oc/Uv Kernel Color fix Voodoo
Hello, here are some benchmark i made to test if some features being used in kernel development are usefull, useless, bull**** or make things worse.
HOW I DID THE TESTS
DEVICE= i9023.
ENVIRONMENT= fixed 25° Celsius.
OS= ANDROID 4.4.1 JRO03E Factory Image by Google.
SOFTWARE USED= 0xBenchmark 1.1.5 - AnTuTu Benchmark 2.9 - Screen Timeout Toggle.
OTHER TOOLS= A/C Charger / Standard Chronometer.
KERNEL= Kernels are built from source using the standard herring defconfig.
Additional notes:
The system is booted up once, every tutorial is closed, 0xbenchmark, Antutu and Screen Timeout Toggle are installed, airplane mode is toggled, system is rebooted in recovery, battery stats are deleted, cache and dalvik are cleared, system is nand backupped.
Every test starts after 30 min of phone off to let him cool, restoring the nand backup and waiting 5 min after system is booted up. Phone is connected to A/C charger.
Kernel are swapped after the nand restore.
Tests are done 5 times and then the average is calculated && till results are almost the same every run.
TEST N. 1
".. i use teh latest toolchain, mah kernel is imba ima pro !!111!1one!!eleven"
Google toolchain 4.4.3 vs Google toolchain 4.6
This test is inspired by an Ezekeel work that demonstrate how every different toolchain from the google base 4.4.3 used to compile our NS kernel resulted in 0 increased performance. Same goes for "optimized" compiler flags. You can see some bench here.
What i'm going to do is to test latest google prebuilt toolchain and see if it differs from above test.
- 0xBenchmark reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
Linpack [COLOR="Red"]18,81[/COLOR] 18,31
C [COLOR="Red"]21,65[/COLOR] 21,15
FFT [COLOR="Red"]13,92[/COLOR] 13,59
JSOr [COLOR="Red"]39,79[/COLOR] 39,14
MCi [COLOR="Red"]7,20[/COLOR] 6,60
Smm [COLOR="Red"]17,80[/COLOR] 17,45
dLUmf [COLOR="Red"]29,61[/COLOR] 29,17
- AnTuTu reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
RAM [COLOR="Red"]260[/COLOR] 257
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 105
GFX 2D [COLOR="Red"]278[/COLOR] 277
GFX 3D [COLOR="Red"]1115[/COLOR] 1111
TL;DR
USING LATEST GOOGLE TOOLCHAIN DOES IMPROVE KERNEL PERFORMANCE? NO
TEST N.2
"..undervolting teh lcd display MUST save battery!!"
LCD @ 3.0 V vs LCD undervolted to 2.4V
Same environment as before. Since % battery are not always accurate i made 3 tests:
2.1: let phone fully discharge, charge it up for 30 min. Boot it up, put max brightness and count how much time passes till it poweroff by himself.
2.2: let phone fully charge, boot it up, put max brightness and count how much time passes till it loose 10 points %.
2.3: let phone fully charge, boot it up, put max brightness and count how much time passes till it goes from 60% to 50%.
RESULTS
After days of tests, can pretty sure say that at the cost of 20% undervolt (from 3.0 to 2.4) there isn't any noticeable battery saving. What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
Remember these tests were made on a slcd panel not amoled.
Did i say these tests were made on an i9023?
Tests made on slcd i9023.
TL;DR
THERE IS ANY NOTICEABLE BATTERY SAVING UNDERVOLTING THE LCD?NO
TEST 3
".. ye ye but removing lot of crap makes mah kernel faster!"
Stock Kernel vs Config tweaked (debug and crap removed) Kernel
Removed all possible debuggers, governors, tv tuners radio and all unused crap.
Let's see if it's really better.
- 0xBenchmark reds results are better.
Code:
Stock Kernel Cleaned Kernel
Linpack [COLOR="Red"]18,81[/COLOR] 18,72
C [COLOR="Red"]21,65[/COLOR] 21,54
FFT [COLOR="Red"]13,92[/COLOR] 13,65
JSOr 39,79 [COLOR="Red"]39,85[/COLOR]
MCi [COLOR="Red"]7,20[/COLOR] 6,77
Smm 17,80 [COLOR="Red"]17,82[/COLOR]
dLUmf [COLOR="Red"]29,61[/COLOR] 29,54
- AnTuTu reds results are better.
Code:
Stock Kernel Cleaned Kernel
RAM 260 [COLOR="Red"]261[/COLOR]
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 104
GFX 2D 278 278
GFX 3D 1115 [COLOR="Red"]1116[/COLOR]
TL;DR
REMOVING CRAP FROM KERNEL LIKE UNUSED DRIVERS, USELESS GOVERNORS, ALL DEBUGS, DO INCREASE KERNEL PERFORMANCE? NO
TEST 4
".. ye ye u fools seeking big numberz! Merging kernel with latest linux mainline makes teh battery drop fastah"
Kernel merged with linux 3.0.39 / 3.0.40 / 3.0.41
Same standard condition, let phone full drain with all 4 kernels in idle / airplane mode and standard usage.
RESULTS
After comparing 4 different kernel the battery stats were all the same, no weird wakelocks no battery drains. Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome work!
Good work.
I respect your work.
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain? I'm not too familiar with all the technical stuff, so if anyone can explain exactly what the kernel is, that might help explain things even further. I do know, and everyone else (hopefully), more aggressive scaling can have an effect on battery life . Nice to see another test showing undervolting is pretty much not needed and isn't worth the instability it may cause. But hey, whatever floats your boat.
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
"It depends on what the meaning of the word 'is' is."
"... I didn't inhale ..."
what CPU speed(high/low) are you benchmarking, I don't see it posted.
I'll just come out and say it: seems fishy.
I've seen you obsessed before at some kernel "myths" like thalamus claim that latest mainline updates were hurting performance/battery and to be honest I don't see in these studies a sufficient amount of rigor, objectivity and data to withdraw any conclusions except your clear agenda against some things that are said.
For example, some flaws:
1. 0xBenchmark and AnTuTu only measure one kind of performance, you may think you are gauging something when you're not.
2. A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
3. Such benchmarks have fluctuations, they are not particularly accurate.
4. The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
6. And once more, removing debug/crap should improve other things which were completely ignored (mm, pm, etc).
7. The last test just doesn't make sense, there are too many things involved to be that linear.
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Long story short, I can't really bring myself to take this too seriously as it lacks data and there's just too much hate undermining the credibility of the post. I should also mention that I don't have a position regarding each of those claims; I believe we should experiment, analyse, collect feedback and withdraw conclusions for everything but this just didn't convince me, especially when it comes to your neutrality. Thanks though.
chronophase1 said:
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain?
Click to expand...
Click to collapse
I guess I know whom you are talking about, but may be you have not read his latest thread. lol...
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
I am glad this test has proved it actually doesn't matter.
anshumandash said:
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
Click to expand...
Click to collapse
I said generally, which is correct. The vast majority of the time the kernel has nothing to do with battery drain.
And yes, merging mainline does make a difference.
If you actually bother to read my blog post, you will see I don't actually mention battery drain at all as my reasons for ditching mainline updates.
Personally, I don't use the Nexus S enough to notice increases / decreases in drain, it's my development phone. However, quite a lot of users *have* told me that they have noticed improvements since I rolled back. Perhaps they are all wrong too?
It's not wakelocks, it's not obvious drain, it's subtle increases in drain which are impossible to track down.
However, In the case of the GNex when I merged to .40 I got 6% an hour drain, but when I went back to .31, I got less than 1% an hour drain. Merging back up again gives me the 6% an hour drain again with *nothing* else changed. It doesn't take a genius to figure out that it must be the kernel merging which has caused it, or is someone going to argue with that too? Lol.
I'm not entirely sure what myths have been busted here. It seems like a non kernel developer wasted their time to prove utterly nothing, which amuses me slightly. Do you honesty think I apply any modification, tweak or anything without testing the impact? If it makes no difference, it doesn't go in.
Removing unused stuff is simply to make the compile slightly quicker and the resulting zImage smaller. I don't believe there are any performance improvements to gain by doing that, but what is the point having junk built in which isn't needed?
As for removing all debugging, it's not a good idea, because how are you going to get a stacktrace if you panic? Again, that is something I won't do, and I know it makes little difference.
Anyway, if you want to test more accurate real world usage, use the 2D tests on 0xBench. They are CPU bound and they are greatly affected by small changes. Here are some I did a few weeks ago to test the best toolchain for the Nexus 7.
As you can see, there clearly is a difference between the speed of code that they produce. Raw speed is one thing, but graphics benchmarks more accurately represent real usage.
tl;dr: Ignore the agenda driven opinions and dubious results in the first post, they are meaningless.
simms22 said:
what CPU speed(high/low) are you benchmarking, I don't see it posted.
Click to expand...
Click to collapse
Performance, 1000.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
knzo said:
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Click to expand...
Click to collapse
If you read carefully i tested the battery with daily use aswell.
Quoting myself : " Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge..
knzo said:
A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
Click to expand...
Click to collapse
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
After tons of test around the web can pretty much assure you that toolchains may give something good compiling the OS ITSELF not the kernel.
knzo said:
The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
Click to expand...
Click to collapse
This is a rude attitude. Why don't you explain why the methods are wrong?
If after days of testing with almost just the lcd on, seeing wich charge lasted longer isn't good feel free to explain why.
Maybe i should've used a tester? I simply want to see if my phone last longer with lcd undervolt, simply.
About data results: the results is around 5%, would it better if i wrote how much every % lasted and then making simple math operations? No thanks.
i don't like to edit OP posts so i'll write it here. Quoting myself:
What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
i meant 10 minutes more screen time
knzo said:
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
Click to expand...
Click to collapse
I disabled them one by one aswell and never noticed an increase performance. So your statement is wrong. I don't have the config anymore but for sure kernel, slub dm and cgroup subsys were disabled.
I develop my own rom and kernel just for myself. I make these tests for myself not to prove anything, i'm just sharing.
These tests took me one week to be made. Do you really think i would ruin them posting wrong informations or ruining my reputation?
Actually i was surprised by some of them.
You're welcomed to made them again or better since you didn't like the methods.
atl4ntis said:
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
Click to expand...
Click to collapse
That single sentence sums up this entire thread.
Basically, you started these tests with an agenda which was to validate ezekeels tests and you 'proved' what you wanted to prove to fit your agenda.
Anyone can do that. It doesn't actually prove anything though, it just generates FUD. Congrats.
No just one test and just becouse similar test were made.
Go troll somewhere else.
atl4ntis said:
No just one test and just becouse similar test were made.
Go troll somewhere else.
Click to expand...
Click to collapse
I'm not trolling. I'm rightly questioning your extremely dubious results and the fact you have an agenda, which you clearly do. If you don't want people to question them, perhaps go and post them on Rootzwiki instead where they will be blindly accepted as gospel.
The definition of trolling is here.
Your post is simply confusing users and generating FUD, but perhaps *that* is your true agenda, is it not?
If you think these tests are wrong just provide some proof instead of offending people or talking about agenda or even worse reporting them as wrong because "other people said so" instead of testing them by yourself or saying some issues are not trackable.lol.
Some moderator should get rid of this thanks.
I think the OP has good intentions and had shown aptitude in collecting data, which deserves praise.
Just because something isn't perfect in the first attempt doesn't mean it deserves to be torn down.
Efforts like this need to be carefully nurtured because they go towards dispelling the prevalent aura of general guff that is spouted here in the development section on a daily basis.
To improve the study, make sure you are clear about the test conditions, and run the same test repeatedly until the mean and median converge to within some acceptable tolerance, e.g. 1%
You can then use standard deviation to make accurate statements about the data including its variability.
If you run multiple benchmarks you can later do regression testing to eliminate the tests that aren't correlated to the end result. You can combine the results of multiple benchmarks using the geometric mean.
If that's confusing, then I'll happily explain it in more detail.
Any more shenanigans, this thread gets locked. Either discuss the post like an adult or don't post.
You quoted my post about battery screens + on screen buttons but have not answered what is the deal with it.
What are those on screen buttons doing there on a official ROM for the 9023?
Already answered but maybe i wasn't clear enough.
I tested those kernel with daily usage aswell, that mean with mods apps and every crap i use daily. Those ss refers to the daily usage with my rom.
Hey all. Which ROM, kernel, and governor do you recommend I use on my N6? There are so many options that I figured I'd ask. Currently running Benzo ROM and the kernel it came with. Thanks!
"Best" ROM.
There is no such thing as a best ROM.* The question itself is ambiguous.* "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded.* You will likely be able to read about this in the ROM threads.* ROMs do not impact battery life.* The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel.* What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life.* Let's get this cleared up.* Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life".* This is actually wrong.* Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning.* The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings.* This is what we refer to as out-of-the-box settings.* The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance.* The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
rootSU said:
"Best" ROM.
There is no such thing as a best ROM.* The question itself is ambiguous.* "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded.* You will likely be able to read about this in the ROM threads.* ROMs do not impact battery life.* The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel.* What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life.* Let's get this cleared up.* Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life".* This is actually wrong.* Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning.* The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings.* This is what we refer to as out-of-the-box settings.* The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance.* The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
this. and its very well said at that.
Thanks for the reply root.... However, nowhere did I ask what the "best" ROM is, I totally disagree that the stability will be equivalent because there are AOSP ROMs out there that are all in alpha for 5.1, as well as stock ROMs that may have certain rather experimental things, with nightlies being released. I guess the goal of my query was to find out what people have set some of their variables to (ROM, settings, kernel, kernel settings) to get better battery life with minimal performance drop.
YevOmega said:
nowhere did I ask what the "best" ROM is
Click to expand...
Click to collapse
Its my generic answer. Copy and paste. But you asked for recommendations and that gets the same answer because other than semantics, there's no difference in the question.
YevOmega said:
I totally disagree that the stability will be equivalent because there are AOSP ROMs out there that are all in alpha for 5.1, as well as stock ROMs that may have certain rather experimental things, with nightlies being released
Click to expand...
Click to collapse
That's you're prerogative but I'm not really talking about feature sets. That aspect of the answer is more generic, usually for people coming from HTC or Samsung where "camera sux" because the binaries were never released.
YevOmega said:
I guess the goal of my query was to find out what people have set some of their variables to (ROM, settings, kernel, kernel settings) to get better battery life with minimal performance drop.
Click to expand...
Click to collapse
Performance uses power, which uses battery. There is no way to get more battery life back than the amount of performance you're willing to sacrifice. Its a direct correlation.
I can tell you my settings, but they're not magic. Everything I gain in battery life, I lose in performance.
Edit. I think a good thing to do would be to pick a kernel based on features, then speak to users of that kernel to see how they set it up
@YevOmega, please check post #5 of the stickied Q&A thread for details on this question.
Sent from my Nexus 6 using Tapatalk
YevOmega said:
Hey all. Which ROM, kernel, and governor do you recommend I use on my N6? There are so many options that I figured I'd ask. Currently running Benzo ROM and the kernel it came with. Thanks!
Click to expand...
Click to collapse
The answer depends on how many ROM/kernel/governor combinations there, because that is how many answers you are likely to get. Stock based are usually the most stable, and everything is likely to work the way its's supposed to while CM/AOSP ROMs will have more cusomization and tweaks but are often troubled by instability or things that are broken. Me, I'm on Stock rooted 5.1 for now, until I flash something else. What is it that's important to you when it comes to the ROM?
I want it to be crisp most importantly, but it's nice to have things like PIE. Minimal bloatware, because yes there are still some system apps that I don't want but can't uninstall without jumping through hoops.
rootSU said:
Its my generic answer. Copy and paste. But you asked for recommendations and that gets the same answer because other than semantics, there's no difference in the question.
That's you're prerogative but I'm not really talking about feature sets. That aspect of the answer is more generic, usually for people coming from HTC or Samsung where "camera sux" because the binaries were never released.
Performance uses power, which uses battery. There is no way to get more battery life back than the amount of performance you're willing to sacrifice. Its a direct correlation.
I can tell you my settings, but they're not magic. Everything I gain in battery life, I lose in performance.
Edit. I think a good thing to do would be to pick a kernel based on features, then speak to users of that kernel to see how they set it up
Click to expand...
Click to collapse
Again, please read my statement. I understand that I can't just get better battery life out of thin air. I said minimal performance loss, not none. There is a variety of optimizations and my hope is that there are combinations that will improve my battery life without compromising performance too much.
YevOmega said:
Again, please read my statement. I understand that I can't just get better battery life out of thin air. I said minimal performance loss, not none. There is a variety of optimizations and my hope is that there are combinations that will improve my battery life without compromising performance too much.
Click to expand...
Click to collapse
You've misinterpreted what I've said. There is no minimal. Its loss or its not. Its an direct correlation. If you want to save x battery you must sacrifice y performance. There's no magic, smaller z performance that still gets you x battery.
I didn't say you wanted to get battery out of thin air (perhaps you need to read my statement). I'm saying you want to get battery out of medium air, but I'm telling you that it only comes out of thick air.
Let me try something else.
To increase battery by 6, you must decrease performance by 6. There is no magic setting that will allow you to get 6 battery out of 3 performance. If you only want to sacrifice 3 performance, you'll only get 3 battery.
Break it down. What uses battery most?
-Screen
-Radio
-CPU
So forgetting screen and radio which are out of the scope of this thread, let's look at CPU.
CPU voltage is controlled by the kernel. The kernel has a table that has a predetermined amount of voltage for every clock cycle step. As you can see here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So how you save power on CPU is to either prevent certain CPU frequency being used, limit the time it is being used for or try to not need that frequency. This will save 6 battery, but will lose 6 performance because in each case that battery is being saved, the CPU frequency is not being used. Its a relative battery to performance ratio.
So I can list all the kernel settings that will save you battery, but they all have an equal performance hit - which is what I'm trying to explain.
Alright thanks. Go for it. I have vindicator kernel, as a reminder, so if you don't mind listing some settings, that would be nice ?. Thanks!
YevOmega said:
Alright thanks. Go for it. I have vindicator kernel, as a reminder, so if you don't mind listing some settings, that would be nice ?. Thanks!
Click to expand...
Click to collapse
I use elementalx, but here's some things I like to do.
1 set up threshold higher (99) CPU ramps up at 99% load
2 hot plugging set to 2 cores offline when not in use
3 turn off all touch boosts
rootSU said:
I use elementalx, but here's some things I like to do.
1 set up threshold higher (99) CPU ramps up at 99% load
2 hot plugging set to 2 cores offline when not in use
3 turn off all touch boosts
Click to expand...
Click to collapse
How much SOT do you get, and what carrier are you on?
YevOmega said:
How much SOT do you get, and what carrier are you on?
Click to expand...
Click to collapse
It depends. At home, I can get 6 or maybe 7. On a work day, perhaps 4 or rarely 5.
I live in the UK so not sure the Carrier matters.
YevOmega said:
How much SOT do you get, and what carrier are you on?
Click to expand...
Click to collapse
rootSU said:
It depends. At home, I can get 6 or maybe 7. On a work day, perhaps 4 or rarely 5.
I live in the UK so not sure the Carrier matters.
Click to expand...
Click to collapse
Carrier only matters if you are comparing signal strength in regards to the same bands. Kernels can also allow you to undervolt if you forgot, there are other things we can do such as drop voltage on certain parts of the device, though this can cause instability.
Optimizations on ROM and kernel side can reduce the overhead on the CPU and we can also increase throughput on several aspects of the device such as memory and BUS. Other things that "may" increase battery life could be removing code for rotational storage and using flash based alternatives/optimizing it for non-rotational storage.
Thanks. And yeah, I know why carrier matters
{
"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"
}
Master of Speed (Click)
The T800 travels from the FUTURE to bring YOU the POWER AND BATTERY of a Galaxy S10+ to your beloved S7, while fighting obsolescence...
Version III features:
° 8 hours of battery life sustained with Aosp
9 hours of SOT
° About twice or more the speed with no Lag por shutter
° Vídeo about how to apply UV properly and recommended ROM and kernel and many extras (Such as GPU Turbo and FPS screen uncap) All of that in only 8 hours! And for free!!
This revolutionary CREATION of mine will give you the SAME optimization as Apple do with it's phones (Tremendous battery life and smoothness) But with two or three times the amount of ram, better screens twice the cores, battery ,etc. So:
HERE IS THE AWESOME SPEED YOU CAN SPECT:
https://m.youtube.com/watch?v=6kolVhdtl3M&feature=youtu.be
AND HERE IS A BENCHMARK WHERE YOU CAN SEE TEMPERATURES OF 20 OR MORE DEGREES LESS THAN STOCK ROM, WHILE SAVING BATTERY
https://youtu.be/9DOjie9QFb4
"65% of charge in 30 minutes full charge achieved in less than a hour..." With Aosp only
Q: Why does the manufactures do this bad on stock on purpose?
Two things, MARKETING and PROGRAMMED OBSOLESCENCE which lead them to even put 10 core when a Apple device with two high power cores (Iphone 7 plus) eats it (Mediatek 10 core setup)
Q: What kind of results will i experiment?
With LATEST LINEAGE 16 + Morokernel + this AWESOME PROFILE and with a non-degraded battery you will experience the performance of a Samsung Galaxy S10 with the battery life (and also charging speed, if you have a QC 3.0 charger... of the Latest huawei/honor phones (8 hours SOT, 65% in 30 min) feeling the ui completely lag free, the apps opens right at the moment, and scrolling is like butter. Also runs very very well like a SD 855
So i upload you the profile, you will need the following:
Morokernel installed
Mtweaks latest
Download the latest LAG_TERMINATOR™
Open Mtweaks menu and select "profiles" then import the latest "LAG_TERMINATOR™" profile of mine.
APPLY THIS SETTINGS ON BOOT AND YOU ARE DONE. Vídeo settings:
https://youtu.be/CYIRS8nc0Lc
You have to apply this settings on Mtweaks to Morokernel and you are Done. You can also flash the attached zip's to uncap 60fps in all the system animations and GPU turbo for more gaming/phone normal use performance.
1Morokernel and mtweaks download (all in 1 flashable zip) (Works on aosp and TW roms) https://androidfilehost.com/?w=files&flid=295574
2DOWNLOAD NOW THIS AWESOMENESS:
https://www.mediafire.com/file/k964wlh4c4qz5ol/LAG_TERMINATOR™.json ***SEE THE ABOVE YOUTUBE VIDEO AND APPLY THE SAME SETTINGS AND LATTER YOU WILL ENJOY THIS.[/COLOR][/U]
Disclaimer: You don't have the right to post my content in any site without my explicit permission.
Note: If you want me to buy some toys/good sweets to my dear cat you can always donate some money to my paypal: http://paypal.me/DonateLAGTERMINATOR Thank you
------------
Hi! touching my phone and having common sense let me know that the Exynos GPU and the low power cores/high power cores have a little nonsense regarding to STOCK thermal and CPU/GPU freq/usage, so, i change between low power cores to high power cores at 50% it's minimum frequences and let the system to use ONLY the high power cores, heavy underclocked, since our phone have thermal copper plate to avoid high temperatures there should be no problem.
But the MORE INTERESTING part of it, it's that this Exynos allows to underclock a LOT among other things, except the GPU which doesn't go really well with underclocking so, when i do this mod, i was able to boost the overall system performance (daily use) like our S7 Exynos is like two or three generations after it regarding to performance! While turning on only hardcore CPU's and not the EIGHT OF THEM the phone not only runs wayyy better, but also runs VERY stable and cold, even better than stock.
Regarding battery life, the overall pack which you only have to import through "Morotweaks" you not only have a lot more benefits regarding low power consumption, but, when you use the powerfull cores ONLY at higher frequency, the Exynos is able to deep sleep more often than before... Regarding additional benefits into the battery life/heat area.
Any chance to have this profile running on thunderstorm kernel?
Thank you for sharing your work!
Thanks! Testing!
What about Reflux Kernel?
Therazorsedge said:
Hi! touching my phone and having common sense let me know that the Exynos GPU and the low power cores/high power cores have a little nonsense regarding to STOCK thermal and CPU/GPU freq/usage, so, i change between low power cores to high power cores at 50% it's minimum frequences and let the system to use ONLY the high power cores, heavy underclocked, since our phone have thermal copper plate to avoid high temperatures there should be no problem.
But the MORE INTERESTING part of it, it's that this Exynos allows to underclock a LOT among other things, except the GPU which doesn't go really well with underclocking so, when i do this mod, i was able to boost the overall system performance (daily use) like our S7 Exynos is like two or three generations after it regarding to performance! While turning on only hardcore CPU's and not the EIGHT OF THEM the phone not only runs wayyy better, but also runs VERY stable and cold, even better than stock.
Regarding battery life, the overall pack which you only have to import through "Morotweaks" you not only have a lot more benefits regarding low power consumption, but, when you use the powerfull cores ONLY at higher frequency, the Exynos is able to deep sleep more often than before... Regarding additional benefits into the battery life/heat area.
So i upload you the profile, you will need the following:
Morokernel installed
Mtweaks latest
Download the latest LAG_TERMINATOR™ zip
You have to go through the menu and select "profiles" then import the latest "LAG_TERMINATOR™" zip profile of mine.
You will experiment like you have a S10 instead of a S7 and you will be able to save a lot of battery and heat.
I recommend you the rom AOSIP but you can use every Aosp/Tw rom out there, even with other kernel compatible with Mtweaks/Thundertweaks but i recomend only this rom. Enjoy it.
DOWNLOAD NOW THIS AWESOMENESS:
https://www.mediafire.com/file/k964wlh4c4qz5ol/LAG_TERMINATOR™.json
Disclaimer: You don't have the right to post my content in any site without my explicit permission.
Note: If you want me to buy some toys/good sweets to my dear cat you can always donate some money to my paypal: [email protected] Thank you, Miau!!!
Click to expand...
Click to collapse
my phone is flying now, thank u so much
not compatible with stock kernel, am i right ?
I see minimum CPU clock of big cores is locked to 1664 MHz. So no low clocks = high battery drain....
It's compatible with lineage 16 and MoRoKernel-AllInOne-CSC4-v7.0.1?
danyel980 said:
It's compatible with lineage 16 and MoRoKernel-AllInOne-CSC4-v7.0.1?
Click to expand...
Click to collapse
yes
Ubimo said:
I see minimum CPU clock of big cores is locked to 1664 MHz. So no low clocks = high battery drain....
Click to expand...
Click to collapse
The magic of this is explained on the first post video. My S7 now feels like a ****ing S10 with better battery
Also try the latest Lineage OS!!! My friend.
You will sabe a lot of heat and battery
Ubimo said:
I see minimum CPU clock of big cores is locked to 1664 MHz. So no low clocks = high battery drain....
Click to expand...
Click to collapse
danyel980 said:
It's compatible with lineage 16 and MoRoKernel-AllInOne-CSC4-v7.0.1?
Click to expand...
Click to collapse
You can run it in EVERY KERNEL AND EVERY ROM that supports UNDERVOLTING, and you'll THEN EXPERIMENT IF YOU DO IT'S TREMENDOUS INCREASES ON BATTERY LIFE AND POWER like your phone is a galaxy S10 (but with better battery)...
I.m.Tuga said:
Any chance to have this profile running on thunderstorm kernel?
Thank you for sharing your work!
Click to expand...
Click to collapse
You are wellcome, you can donate through paypal so i buy new toys to my cat
You can allways in any moment tell us here your FANTASTIC RESULTS with LAG_TERMINATOR™ Profile of mine
Hesperus01 said:
What about Reflux Kernel?
Click to expand...
Click to collapse
It should work, you can try and tell us here the difference, if it uses UV you'll be fine. Also your battery speed charge level increases, tell us
Works great, feels very smooth but it feels very hot too! I´ve undervolt -75mw in CPU , -50mw in GPU and -56,25 in MIF-INT-DISP-CAM, what more can i do?
kienzi said:
my phone is flying now, thank u so much
Click to expand...
Click to collapse
Well i'm glad to see i'm helping others with this revolutionary arrangement, keep in tune for more updates!
Ubimo said:
I see minimum CPU clock of big cores is locked to 1664 MHz. So no low clocks = high battery drain....
Click to expand...
Click to collapse
You need to read the full post and try it for yourself to see this incredible and AWESOME RESULTS!!!
JuanMat97 said:
Works great, feels very smooth but it feels very hot too! I´ve undervolt -75mw in CPU , -50mw in GPU and -56,25 in MIF-INT-DISP-CAM, what more can i do?
Click to expand...
Click to collapse
You only have to view the first post youtube config video, and make you s7 literally fly colder than before
There seems to be a problem with Mtweaks, so you have to copy the values by hand, pretty easy actually
Also i recommend you try latest lineage 16 for the BEST RESULTS.
Therazorsedge said:
You only have to view the first post youtube config video, and make you s7 literally fly colder than before
There seems to be a problem with Mtweaks, so you have to copy the values by hand, pretty easy actually
Also i recommend you try latest lineage 16 for the BEST RESULTS.
Click to expand...
Click to collapse
for best results I think I'll wait next release cuz with bug fixes on camera hal
I installed profile, and manually edit voltages like in the video but my phone heats, on charger even more
Hello! I was excited when I found your creation, but on my hyper rom v3 with Thunderstorm kernel, the most of the values don't seem to be the same as yours (like the video you've posted).
I can relate that my S7 doesn't heat so hard while charging, but it charges slower (which is not a bad thing). Also Spectrum profiles have reduced to 2 profiles, sometimes 3 (if I toggle them fast - balanced, "battery" and Gaming), instead of 4. I tried to record my screen to show you, but I got lots of freezes lasting 5 to 10 seconds . Do I need to move to AOSP in order to get the right tweaks, or could you please rearange values for Thunderstorm kernel?
I've been trying a few custom ROMs (ArrowOS and Ricedroid) and a few custom kernels (Vantom and Sleepy) and I've noticed that the battery life is just worse. I went from an active drain of 10%/hr and an idle drain of 0.5%/hr (on debloated MIUI) to an active drain of around 12-15%/hr and an idle drain of 0.8-1.0%/hr (on Ricedroid+Sleepy, best one so far in my experience), which is an obvious increment in comparison.
I've also seen a huge number of people complaining about terrible drain on basically every custom ROM I've seen on here.
It's confusing because performance also seems to take a hit, so it's an overall worse experience, outside of the additional functionality which is often pretty great (both ArrowOS and Ricedroid look amazing).
So why is the battery life so much better on MIUI compared to these almost (?)-AOSP custom ROMs? What can I do to further increase battery life AND performance?
Linkoh said:
So why is the battery life so much better on MIUI compared to these almost (?)-AOSP custom ROMs?
Click to expand...
Click to collapse
Because MIUI has too aggressive battery management which result in apps not working as it should (i.e notification not coming). One of the reasons I use custom rom.
Linkoh said:
I've been trying a few custom ROMs (ArrowOS and Ricedroid) and a few custom kernels (Vantom and Sleepy) and I've noticed that the battery life is just worse. I went from an active drain of 10%/hr and an idle drain of 0.5%/hr (on debloated MIUI) to an active drain of around 12-15%/hr and an idle drain of 0.8-1.0%/hr (on Ricedroid+Sleepy, best one so far in my experience), which is an obvious increment in comparison.
I've also seen a huge number of people complaining about terrible drain on basically every custom ROM I've seen on here.
It's confusing because performance also seems to take a hit, so it's an overall worse experience, outside of the additional functionality which is often pretty great (both ArrowOS and Ricedroid look amazing).
So why is the battery life so much better on MIUI compared to these almost (?)-AOSP custom ROMs? What can I do to further increase battery life AND performance?
Click to expand...
Click to collapse
I´d suggest that you apply GMS Doze magisk module, Naptime app (from Francisco Franco, which also includes a magisk module) and also apply restrictions on battery usage of most Google stuff.
That really makes a difference.
I haven´t tried it yet on the RN10PRO (as my bootloader only unlocks this Sunday), but on Poco F2 Pro, while using Ricedroid and Immensity Kernel - these dozing/restriction tricks made active drain stay around 8%/hr (vs 12.5%/hr previously) and idle drain to go down to 0.4%/hr (vs 1.1%/hr previously).
Good luck
Patoilo said:
I´d suggest that you apply GMS Doze magisk module, Naptime app (from Francisco Franco, which also includes a magisk module) and also apply restrictions on battery usage of most Google stuff.
That really makes a difference.
I haven´t tried it yet on the RN10PRO (as my bootloader only unlocks this Sunday), but on Poco F2 Pro, while using Ricedroid and Immensity Kernel - these dozing/restriction tricks made active drain stay around 8%/hr (vs 12.5%/hr previously) and idle drain to go down to 0.4%/hr (vs 1.1%/hr previously).
Good luck
Click to expand...
Click to collapse
Yo thank you for the tips, I'm definitely gonna try your strategy and I'm excited to see if it works for me too! Can I ask you what kind of apps you restricted? It would be great Also did you restrict GMS or did you just put it on "optimised"?
It hasn't been my experience with Arrow 12.1 vs MIUI 13, not a like for like comparison though to be fair.
MIUI was constantly chirping away to Xiaomi and Google, and my locked down vanilla Arrow install barely does anything while idle so the battery life is pretty impressive.
I charged it to 100% yesterday, since then I've watched some stuff on youtube, listened to an audiobook, made a few calls, messed around with wallpapers etc...and it's at 70%.
Can't really say much in terms of gaming performance since dropping the play store has cut off the games I'd usually install. General usage is at least as snappy as MIUI was, probably faster since I have 1/4 of the stuff installed.
SaulPanzer said:
It hasn't been my experience with Arrow 12.1 vs MIUI 13, not a like for like comparison though to be fair.
MIUI was constantly chirping away to Xiaomi and Google, and my locked down vanilla Arrow install barely does anything while idle so the battery life is pretty impressive.
I charged it to 100% yesterday, since then I've watched some stuff on youtube, listened to an audiobook, made a few calls, messed around with wallpapers etc...and it's at 70%.
Can't really say much in terms of gaming performance since dropping the play store has cut off the games I'd usually install. General usage is at least as snappy as MIUI was, probably faster since I have 1/4 of the stuff installed.
Click to expand...
Click to collapse
Yeah, my stock MIUI was terrible both performance-wise and battery-wise, but after debloating it (by disabling basically every Xiaomi service / app) my phone was flying with amazing battery.
I'm guessing that you've flashed the vanilla / degoogled ROM, right? This sounds like a good idea. I flashed the gapps version and my experience was not nice, and just restricting Google Services' battery usage made my phone go 0.1%/hr overnight which is insane.
Though, active drain remains insanely high around 15%/hr... Can't find out why
Linkoh said:
I'm guessing that you've flashed the vanilla / degoogled ROM, right?
Click to expand...
Click to collapse
Vanilla ArrowOS 12.1, no gapps or anything like that and I'm not rooted if makes a difference.
I use F-droid for most things and a few I grabbed from the official GIT repos like brave-browser, yubikey stuff and session, netguard is blocking everything I don't actively use.
Also I'm using Nova launcher instead of Quickstep, I haven't tested to see if that makes a change to the battery life.
If you're after all the fancy extras then that won't work for you, it's slick and I like the feel of the phone but definitely feels minimal.
SaulPanzer said:
It hasn't been my experience with Arrow 12.1
Click to expand...
Click to collapse
Same. My phone charges in ~20 minutes and lasts several days without charging. With more screentime, thats obviously reduced but ive never had a phone/rom combo that lasts as long as this one. I hate MIUI for their agressive battery management which brings more bugs and less batterylife. And its so good that even though i want to upgrade to the next android version, im going to stay right where i am because it seems like no rom can keep up with this.
SaulPanzer said:
Vanilla ArrowOS 12.1, no gapps or anything like that and I'm not rooted if makes a difference.
I use F-droid for most things and a few I grabbed from the official GIT repos like brave-browser, yubikey stuff and session, netguard is blocking everything I don't actively use.
Also I'm using Nova launcher instead of Quickstep, I haven't tested to see if that makes a change to the battery life.
If you're after all the fancy extras then that won't work for you, it's slick and I like the feel of the phone but definitely feels minimal.
Click to expand...
Click to collapse
Hmm that's interesting. I don't rely on much Google stuff (except GPay and Maps which are very hard to replace), so this actually sounds appealing to me. Can I ask you to send a screenshot of Accubattery / BatteryGuru if possible? I have had horrible luck with battery life so far it seems
Linkoh said:
Hmm that's interesting. I don't rely on much Google stuff (except GPay and Maps which are very hard to replace), so this actually sounds appealing to me. Can I ask you to send a screenshot of Accubattery / BatteryGuru if possible? I have had horrible luck with battery life so far it seems
Click to expand...
Click to collapse
I think GPay needs extra stuff that I don't have but I don't use it so not 100% on that and I use Organicmaps but not like a car GPS so no idea if it's capable of that.
I installed Accubattery yesterday with the phone at ~97%, pretty light usage and fell asleep with a video streaming on the phone since then.
For fair disclosure I'm not entirely sure how accurate the battery measurements are since my phone says there's still nearly 1.5h of charge time left when it hits full charge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SaulPanzer said:
I think GPay needs extra stuff that I don't have but I don't use it so not 100% on that and I use Organicmaps but not like a car GPS so no idea if it's capable of that.
I installed Accubattery yesterday with the phone at ~97%, pretty light usage and fell asleep with a video streaming on the phone since then.
For fair disclosure I'm not entirely sure how accurate the battery measurements are since my phone says there's still nearly 1.5h of charge time left when it hits full charge.
View attachment 5780339
Click to expand...
Click to collapse
Wow, actually insane. Thank you for sharing the screenshots! Can I ask you if you noticed any kind of hiccups or lags? Do you run it on 120hz?
Linkoh said:
Wow, actually insane. Thank you for sharing the screenshots! Can I ask you if you noticed any kind of hiccups or lags? Do you run it on 120hz?
Click to expand...
Click to collapse
No problem, I run it on 60hz since I don't game or do any video stuff.
There are options for 60Hz-60Hz/60Hz-120Hz/120Hz-120Hz, I can select them but with my usage I don't notice any visible difference and leave it on 60.
No lag that I can notice apart from data lag (loading a site like twitch takes a second or 2 for all the thumbnails to load, the browser itself opens instantly).
I've had 1 hiccup in the month or so I've used the ROM, for some reason the fingerprint unlock didn't work 1 time and I had to restart the phone.
I just restarted to test it and from hitting restart it only takes 17 seconds to reboot back to the lock screen so no major hassle.
The other problems are ones I make for myself by using a non Gapps vanilla ROM, so limited customization, can't install a fancy camera app, certain apps won't install without rooting etc...(non issues for me personally).