I am running RR and am getting under 40k with antutu benchmark
i am wondering why it is so low and if someone can help me.
i am running xposed with the following modules
amplify - not blocking anything though yet
app settings - used for a couple apps that need 640 dpi to operate since i am running at 480 dpi
blacklist
boot manager
google offline voice
greenify
iFont
unbelovedhosts
xinstaller
xprivacy - not blocking anything with it yet
youtube adaway
is there any apps that would cause such a low performance. i tried installing the kernel by @BayButcher and modifying it to his battery suggestions and i am about to try his performance setup for his kernel to see if that does anything. but i was getting near 50k with stock so i figure i should be better with CM12.1 or RR.
johnbravado said:
I am running RR and am getting under 40k with antutu benchmark
i am wondering why it is so low and if someone can help me.
i was getting near 50k with stock so i figure i should be better with CM12.1 or RR.
Click to expand...
Click to collapse
In thermal settings, you will have to set the temperature higher. Intellithermal aggressively throttles the CPU. I set it for 65 degrees for just "normal" operations, because it seems to start throttling 10 degrees sooner than what you set.
So for a benchmark that makes you feel better, set the degree limit even higher. How high is however high you are willing to risk... Also, before you take the benchmark tests, stick the phone in the freezer with a ziplock bag for a few minutes to let it really cool down. Then start the test, put it back in the freezer while the test is running. The phone will run faster longer while cool, and won't throttle the CPU.
I mean, benchmarks are for bragging rights, yes?
When you finish the benchmarks test, then put the degree limit back down to like 65 degrees for everyday use.
______
50,000 -- here's Antutu results at 65 degrees throttling and freezer trick. I could get higher if I set my thermal setting even higher -- which would be safe temporarily as long as I chilled the phone first IN the freezer and kept it there during testing.
{
"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"
}
ChazzMatt said:
In thermal settings, you will have to set the temperature higher. Intellithermal aggressively throttles the CPU. I set it for 65 degrees for just "normal" operations, because it seems to start throttling 10 degrees sooner than what you set.
So for a benchmark that makes you feel better, set the degree limit even higher. How high is however high you are willing to risk... Also, before you take the benchmark tests, stick the phone in the freezer with a ziplock bag for a few minutes to let it really cool down. Then start the test, put it back in the freezer while the test is running. The phone will run faster longer while cool, and won't throttle the CPU.
I mean, benchmarks are for bragging rights, yes?
When you finish the benchmarks test, then put the degree limit back down to like 65 degrees for everyday use.
Click to expand...
Click to collapse
I agree benchmarks are for bragging, but they are still a benchmark. if stock out of the box i can get a 48-49k benchmark and i do some mods and can get a 55k benchmark that is for bragging. but if it drops to 40k something is broke. . I am going to try the increased temperature and run another test. the performance setup only got me to 41k.
i am really confused now. i reinstalled computerfreeks ROM which before bootloader unlock gave me 50k and now it gave me 35k. i am going back to RR because I like it more but need to find out what caused performance issues.
johnbravado said:
I agree benchmarks are for bragging, but they are still a benchmark. if stock out of the box i can get a 48-49k benchmark and i do some mods and can get a 55k benchmark that is for bragging. but if it drops to 40k something is broke. . I am going to try the increased temperature and run another test. the performance setup only got me to 41k.
i am really confused now. i reinstalled computerfreeks ROM which before bootloader unlock gave me 50k and now it gave me 35k. i am going back to RR because I like it more but need to find out what caused performance issues.
Click to expand...
Click to collapse
My main point is while the custom ROM may give you increased performance and options, the default kernel thermal throttling points (for frequency as well as for core -- two separate settings) may be sabotaging benchmark tests.
I increased frequency point to 65 degrees, because that REALLY means 55 degrees, for some reason.
I didn't even touch the "core" thermal setting...
And my 50,000 result was on stock 640 dpi.
Cm12 is the same way. Low benchmark. I'm saying with exposed and stock
Sent from my XT1254 using Tapatalk
tecsironman said:
Cm12 is the same way. Low benchmark. I'm saying with exposed and stock
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I'm on CM, but with @baybutcher27 kernel. See my benchmark results above.
ChazzMatt said:
I'm on CM, but with @baybutcher27 kernel. See my benchmark results above.
Click to expand...
Click to collapse
Yeah, but you obtained those results by tweaking the phone and subjecting it to non-real world conditions. I can get 52K on the stock rom by doing absolutely nothing and having a bunch of xposed modules active, and I think that's the issue that the OP is concerned about. The relationship between benchmark scores and real world performance is debatable, but I think he has a valid point.
johnbravado said:
I agree benchmarks are for bragging, but they are still a benchmark. if stock out of the box i can get a 48-49k benchmark and i do some mods and can get a 55k benchmark that is for bragging. but if it drops to 40k something is broke. . I am going to try the increased temperature and run another test. the performance setup only got me to 41k.
i am really confused now. i reinstalled computerfreeks ROM which before bootloader unlock gave me 50k and now it gave me 35k. i am going back to RR because I like it more but need to find out what caused performance issues.
Click to expand...
Click to collapse
The caused of the performance issues is simple heat vs battery level.
Has the device get hot it get low score because more throttle down, has the battery gets low same ting there is a setting to lock the clock under a frequency if the battery get too low, it starts only at 20%.
very simple table:
Code:
thresholds 80 85 90
thresholds_clr 79 84 89
actions cpu cpu cpu
action_info 2265600 1958400 1728000
this is editable this is in the file
system/etc/thermal-engine-quark.conf
I never try to edit it but you can.
But in my test I find that there is more then this file make the performance get low, and for me is just the battery as it get low the performance get too, but the battery is only responsible for some very little % of this the heat is 90 to 95% responsible.
So be aware that you problem is more heat you heat your device installing ROM make and restore backup don't give time to the device cools down and test.
No matter the ROM you try that will be the result, unless you can set the temp threshold higher like in a custom Kernel.
baybutcher27 said:
The caused of the performance issues is simple heat vs battery level.
Has the device get hot it get low score because more throttle down, has the battery gets low same ting there is a setting to lock the clock under a frequency if the battery get too low, it starts only at 20%.
very simple table:
Code:
thresholds 80 85 90
thresholds_clr 79 84 89
actions cpu cpu cpu
action_info 2265600 1958400 1728000
this is editable this is in the file
system/etc/thermal-engine-quark.conf
I never try to edit it but you can.
But in my test I find that there is more then this file make the performance get low, and for me is just the battery as it get low the performance get too, but the battery is only responsible for some very little % of this the heat is 90 to 95% responsible.
So be aware that you problem is more heat you heat your device installing ROM make and restore backup don't give time to the device cools down and test.
No matter the ROM you try that will be the result, unless you can set the temp threshold higher like in a custom Kernel.
Click to expand...
Click to collapse
I am willing to buy into the heat issue since i am changing between ROMS and such so i got a few things against me
1) chargin phone
2) restoring different ROM
3) not giving adequate time to cool
i am going to let eveything settle a little with RR and retest. i am using your kernel and used your performance recomendations. i am not a gamer i just do not like clicking a button and waiting. or wa5tching me type faster than the phone can output to a field
TheSt33v said:
Yeah, but you obtained those results by tweaking the phone and subjecting it to non-real world conditions. I can get 52K on the stock rom by doing absolutely nothing and having a bunch of xposed modules active, and I think that's the issue that the OP is concerned about. The relationship between benchmark scores and real world performance is debatable, but I think he has a valid point.
Click to expand...
Click to collapse
Yes exactly. i did nothing between test a and test b except unlock bootloader and install RR, CM12.1. and yet i got a huge performance drop. but same issue was with the computerfreek version which is like stock. so i am thinking it has to do with something else not playing friendly.
i would assume if with stock out the box i could pull 50k then with RR and a kernel boost i should be able to pull 52k.
TheSt33v said:
Yeah, but you obtained those results by tweaking the phone and subjecting it to non-real world conditions. I can get 52K on the stock rom by doing absolutely nothing and having a bunch of xposed modules active, and I think that's the issue that the OP is concerned about. The relationship between benchmark scores and real world performance is debatable, but I think he has a valid point.
Click to expand...
Click to collapse
Tweaking the phone? Mostly all I did was change the CUSTOM kernel throttling conditions. When you root your phone, from that point on you are TWEAKING your phone. Give me a break.
Yeah, I also cooled the phone, so that is non-real world conditions, but changing the quite arbitrary throttling point is quite logical when it's been PROVEN that throttling point affects performance and actually starts throttling even sooner!
Read this.
xxspookyxx said:
I think change gorvenor to conservative dont solve the problem.
To me dont make any difference, the better Gorvernor works well with my Moto maxx are Interactive_pro.
To getter better performance of my phone, i need change Thermal Frequency Throttle to 80º C, most custom roms use Intellithermal method, and they are very sensivity to temperature.
If you choose 80º C, they will reach in max 70º to begin the throttle the processor.
Stock Custom Roms are 60ºC in Thermal Frequency Throttle, i change to 80ºC and my phone are very fast now.
Click to expand...
Click to collapse
So, on your custom ROM kernel, change your governor, change your throttle points.
OK i am satisfied here. i unplugged the phone and benchmarked at 50.7k. apparently charging the phone cripples its productivity. i did not think it would cripple it that bad. and if this is a known thing i apologize for the posting.
i can now go back to enjoying the awesome RR and tweaking it.
ChazzMatt said:
I'm on CM, but with @baybutcher27 kernel. See my benchmark results above.
Click to expand...
Click to collapse
Yes sir I saw that.. Maybe I'll give cm12 another shot with butchers kernel. I'm at work ATM with just my otg and little time.
Sent from my XT1254 using Tapatalk
My Turbo that I haven't bootloader unlocked. All stock with some stuff disabled in settings.
ChazzMatt said:
Tweaking the phone? Mostly all I did was change the CUSTOM kernel throttling conditions. When you root your phone, from that point on you are TWEAKING your phone. Give me a break.
Click to expand...
Click to collapse
Yeah, okay, so all you did was change some throttling conditions. But you know what I had to do in order to get a higher benchmark than the one you got? Nothing. At room temperature. That's a problem. One of the main purposes of unlocking one's phone is increasing performance, not reducing it.
If the problem is simply an incorrectly set throttle point, all you should have to do to get 52K at room temperature is change the throttle point high enough, right? No cooling required. So let's see that. If you can get 52K without melting your phone in a normal usage environment, then good. No worries. Mine didn't even get hot during the benchmark, so you should be able to easily exceed my 52K score. If not, there is an issue that I think should be addressed.
---------- Post added at 09:33 PM ---------- Previous post was at 09:24 PM ----------
johnbravado said:
OK i am satisfied here. i unplugged the phone and benchmarked at 50.7k. apparently charging the phone cripples its productivity. i did not think it would cripple it that bad. and if this is a known thing i apologize for the posting.
i can now go back to enjoying the awesome RR and tweaking it.
Click to expand...
Click to collapse
Charging = heat generation = throttling, so yes, that would do it. I'm still curious to see if CM and this custom kernel can break 52K though. I'm waiting for CM13 before I make the switch, but I might reconsider if I have to sacrifice some performance. The technical power of this phone was half the reason I bought it.
Stock cm12.1 benched 48,000 screen on.
Screen off it was 43,000.
I'm happy with it. I also think the battery life is mildly better.
Sent from my DROID Turbo using XDA Free mobile app
ChazzMatt said:
Tweaking the phone? Mostly all I did was change the CUSTOM kernel throttling conditions. When you root your phone, from that point on you are TWEAKING your phone. Give me a break.
Yeah, I also cooled the phone, so that is non-real world conditions, but changing the quite arbitrary throttling point is quite logical when it's been PROVEN that throttling point affects performance and actually starts throttling even sooner!
Read this.
So, on your custom ROM kernel, change your governor, change your throttle points.
Click to expand...
Click to collapse
Can I just flash butchers kernel and not mess with it? Is it good to go after flash or will I have to play around with settings?
Sent from my XT1254 using Tapatalk
After you flash it there is nothing saying you need to change anything.
I would imagine he has the presets at what he thinks is best.
Sent from my DROID Turbo using XDA Free mobile app
Just FYI, I'm running computerfreek's latest unlocked ROM with xposed and about 10 modules. No changes to thermal setting (don't know the default for this ROM either), and just have it sitting on the desk. I'm also, getting unbelievable battery life with servicely, amplify.
tecsironman said:
Can I just flash butchers kernel and not mess with it? Is it good to go after flash or will I have to play around with settings?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
the writer of the kernel has said it needs some adjustments since he does not turn them on by default. but he gives 2 setups, 1 for battery and 1 for performance on post #2. i just set it up as per post #2 until i understand more what is going on with the kernel.
Related
Hello, here are some benchmark i made to test if some features being used in kernel development are usefull, useless, bull**** or make things worse.
HOW I DID THE TESTS
DEVICE= i9023.
ENVIRONMENT= fixed 25° Celsius.
OS= ANDROID 4.4.1 JRO03E Factory Image by Google.
SOFTWARE USED= 0xBenchmark 1.1.5 - AnTuTu Benchmark 2.9 - Screen Timeout Toggle.
OTHER TOOLS= A/C Charger / Standard Chronometer.
KERNEL= Kernels are built from source using the standard herring defconfig.
Additional notes:
The system is booted up once, every tutorial is closed, 0xbenchmark, Antutu and Screen Timeout Toggle are installed, airplane mode is toggled, system is rebooted in recovery, battery stats are deleted, cache and dalvik are cleared, system is nand backupped.
Every test starts after 30 min of phone off to let him cool, restoring the nand backup and waiting 5 min after system is booted up. Phone is connected to A/C charger.
Kernel are swapped after the nand restore.
Tests are done 5 times and then the average is calculated && till results are almost the same every run.
TEST N. 1
".. i use teh latest toolchain, mah kernel is imba ima pro !!111!1one!!eleven"
Google toolchain 4.4.3 vs Google toolchain 4.6
This test is inspired by an Ezekeel work that demonstrate how every different toolchain from the google base 4.4.3 used to compile our NS kernel resulted in 0 increased performance. Same goes for "optimized" compiler flags. You can see some bench here.
What i'm going to do is to test latest google prebuilt toolchain and see if it differs from above test.
- 0xBenchmark reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
Linpack [COLOR="Red"]18,81[/COLOR] 18,31
C [COLOR="Red"]21,65[/COLOR] 21,15
FFT [COLOR="Red"]13,92[/COLOR] 13,59
JSOr [COLOR="Red"]39,79[/COLOR] 39,14
MCi [COLOR="Red"]7,20[/COLOR] 6,60
Smm [COLOR="Red"]17,80[/COLOR] 17,45
dLUmf [COLOR="Red"]29,61[/COLOR] 29,17
- AnTuTu reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
RAM [COLOR="Red"]260[/COLOR] 257
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 105
GFX 2D [COLOR="Red"]278[/COLOR] 277
GFX 3D [COLOR="Red"]1115[/COLOR] 1111
TL;DR
USING LATEST GOOGLE TOOLCHAIN DOES IMPROVE KERNEL PERFORMANCE? NO
TEST N.2
"..undervolting teh lcd display MUST save battery!!"
LCD @ 3.0 V vs LCD undervolted to 2.4V
Same environment as before. Since % battery are not always accurate i made 3 tests:
2.1: let phone fully discharge, charge it up for 30 min. Boot it up, put max brightness and count how much time passes till it poweroff by himself.
2.2: let phone fully charge, boot it up, put max brightness and count how much time passes till it loose 10 points %.
2.3: let phone fully charge, boot it up, put max brightness and count how much time passes till it goes from 60% to 50%.
RESULTS
After days of tests, can pretty sure say that at the cost of 20% undervolt (from 3.0 to 2.4) there isn't any noticeable battery saving. What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
Remember these tests were made on a slcd panel not amoled.
Did i say these tests were made on an i9023?
Tests made on slcd i9023.
TL;DR
THERE IS ANY NOTICEABLE BATTERY SAVING UNDERVOLTING THE LCD?NO
TEST 3
".. ye ye but removing lot of crap makes mah kernel faster!"
Stock Kernel vs Config tweaked (debug and crap removed) Kernel
Removed all possible debuggers, governors, tv tuners radio and all unused crap.
Let's see if it's really better.
- 0xBenchmark reds results are better.
Code:
Stock Kernel Cleaned Kernel
Linpack [COLOR="Red"]18,81[/COLOR] 18,72
C [COLOR="Red"]21,65[/COLOR] 21,54
FFT [COLOR="Red"]13,92[/COLOR] 13,65
JSOr 39,79 [COLOR="Red"]39,85[/COLOR]
MCi [COLOR="Red"]7,20[/COLOR] 6,77
Smm 17,80 [COLOR="Red"]17,82[/COLOR]
dLUmf [COLOR="Red"]29,61[/COLOR] 29,54
- AnTuTu reds results are better.
Code:
Stock Kernel Cleaned Kernel
RAM 260 [COLOR="Red"]261[/COLOR]
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 104
GFX 2D 278 278
GFX 3D 1115 [COLOR="Red"]1116[/COLOR]
TL;DR
REMOVING CRAP FROM KERNEL LIKE UNUSED DRIVERS, USELESS GOVERNORS, ALL DEBUGS, DO INCREASE KERNEL PERFORMANCE? NO
TEST 4
".. ye ye u fools seeking big numberz! Merging kernel with latest linux mainline makes teh battery drop fastah"
Kernel merged with linux 3.0.39 / 3.0.40 / 3.0.41
Same standard condition, let phone full drain with all 4 kernels in idle / airplane mode and standard usage.
RESULTS
After comparing 4 different kernel the battery stats were all the same, no weird wakelocks no battery drains. Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome work!
Good work.
I respect your work.
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain? I'm not too familiar with all the technical stuff, so if anyone can explain exactly what the kernel is, that might help explain things even further. I do know, and everyone else (hopefully), more aggressive scaling can have an effect on battery life . Nice to see another test showing undervolting is pretty much not needed and isn't worth the instability it may cause. But hey, whatever floats your boat.
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
"It depends on what the meaning of the word 'is' is."
"... I didn't inhale ..."
what CPU speed(high/low) are you benchmarking, I don't see it posted.
I'll just come out and say it: seems fishy.
I've seen you obsessed before at some kernel "myths" like thalamus claim that latest mainline updates were hurting performance/battery and to be honest I don't see in these studies a sufficient amount of rigor, objectivity and data to withdraw any conclusions except your clear agenda against some things that are said.
For example, some flaws:
1. 0xBenchmark and AnTuTu only measure one kind of performance, you may think you are gauging something when you're not.
2. A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
3. Such benchmarks have fluctuations, they are not particularly accurate.
4. The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
6. And once more, removing debug/crap should improve other things which were completely ignored (mm, pm, etc).
7. The last test just doesn't make sense, there are too many things involved to be that linear.
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Long story short, I can't really bring myself to take this too seriously as it lacks data and there's just too much hate undermining the credibility of the post. I should also mention that I don't have a position regarding each of those claims; I believe we should experiment, analyse, collect feedback and withdraw conclusions for everything but this just didn't convince me, especially when it comes to your neutrality. Thanks though.
chronophase1 said:
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain?
Click to expand...
Click to collapse
I guess I know whom you are talking about, but may be you have not read his latest thread. lol...
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
I am glad this test has proved it actually doesn't matter.
anshumandash said:
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
Click to expand...
Click to collapse
I said generally, which is correct. The vast majority of the time the kernel has nothing to do with battery drain.
And yes, merging mainline does make a difference.
If you actually bother to read my blog post, you will see I don't actually mention battery drain at all as my reasons for ditching mainline updates.
Personally, I don't use the Nexus S enough to notice increases / decreases in drain, it's my development phone. However, quite a lot of users *have* told me that they have noticed improvements since I rolled back. Perhaps they are all wrong too?
It's not wakelocks, it's not obvious drain, it's subtle increases in drain which are impossible to track down.
However, In the case of the GNex when I merged to .40 I got 6% an hour drain, but when I went back to .31, I got less than 1% an hour drain. Merging back up again gives me the 6% an hour drain again with *nothing* else changed. It doesn't take a genius to figure out that it must be the kernel merging which has caused it, or is someone going to argue with that too? Lol.
I'm not entirely sure what myths have been busted here. It seems like a non kernel developer wasted their time to prove utterly nothing, which amuses me slightly. Do you honesty think I apply any modification, tweak or anything without testing the impact? If it makes no difference, it doesn't go in.
Removing unused stuff is simply to make the compile slightly quicker and the resulting zImage smaller. I don't believe there are any performance improvements to gain by doing that, but what is the point having junk built in which isn't needed?
As for removing all debugging, it's not a good idea, because how are you going to get a stacktrace if you panic? Again, that is something I won't do, and I know it makes little difference.
Anyway, if you want to test more accurate real world usage, use the 2D tests on 0xBench. They are CPU bound and they are greatly affected by small changes. Here are some I did a few weeks ago to test the best toolchain for the Nexus 7.
As you can see, there clearly is a difference between the speed of code that they produce. Raw speed is one thing, but graphics benchmarks more accurately represent real usage.
tl;dr: Ignore the agenda driven opinions and dubious results in the first post, they are meaningless.
simms22 said:
what CPU speed(high/low) are you benchmarking, I don't see it posted.
Click to expand...
Click to collapse
Performance, 1000.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
knzo said:
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Click to expand...
Click to collapse
If you read carefully i tested the battery with daily use aswell.
Quoting myself : " Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge..
knzo said:
A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
Click to expand...
Click to collapse
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
After tons of test around the web can pretty much assure you that toolchains may give something good compiling the OS ITSELF not the kernel.
knzo said:
The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
Click to expand...
Click to collapse
This is a rude attitude. Why don't you explain why the methods are wrong?
If after days of testing with almost just the lcd on, seeing wich charge lasted longer isn't good feel free to explain why.
Maybe i should've used a tester? I simply want to see if my phone last longer with lcd undervolt, simply.
About data results: the results is around 5%, would it better if i wrote how much every % lasted and then making simple math operations? No thanks.
i don't like to edit OP posts so i'll write it here. Quoting myself:
What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
i meant 10 minutes more screen time
knzo said:
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
Click to expand...
Click to collapse
I disabled them one by one aswell and never noticed an increase performance. So your statement is wrong. I don't have the config anymore but for sure kernel, slub dm and cgroup subsys were disabled.
I develop my own rom and kernel just for myself. I make these tests for myself not to prove anything, i'm just sharing.
These tests took me one week to be made. Do you really think i would ruin them posting wrong informations or ruining my reputation?
Actually i was surprised by some of them.
You're welcomed to made them again or better since you didn't like the methods.
atl4ntis said:
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
Click to expand...
Click to collapse
That single sentence sums up this entire thread.
Basically, you started these tests with an agenda which was to validate ezekeels tests and you 'proved' what you wanted to prove to fit your agenda.
Anyone can do that. It doesn't actually prove anything though, it just generates FUD. Congrats.
No just one test and just becouse similar test were made.
Go troll somewhere else.
atl4ntis said:
No just one test and just becouse similar test were made.
Go troll somewhere else.
Click to expand...
Click to collapse
I'm not trolling. I'm rightly questioning your extremely dubious results and the fact you have an agenda, which you clearly do. If you don't want people to question them, perhaps go and post them on Rootzwiki instead where they will be blindly accepted as gospel.
The definition of trolling is here.
Your post is simply confusing users and generating FUD, but perhaps *that* is your true agenda, is it not?
If you think these tests are wrong just provide some proof instead of offending people or talking about agenda or even worse reporting them as wrong because "other people said so" instead of testing them by yourself or saying some issues are not trackable.lol.
Some moderator should get rid of this thanks.
I think the OP has good intentions and had shown aptitude in collecting data, which deserves praise.
Just because something isn't perfect in the first attempt doesn't mean it deserves to be torn down.
Efforts like this need to be carefully nurtured because they go towards dispelling the prevalent aura of general guff that is spouted here in the development section on a daily basis.
To improve the study, make sure you are clear about the test conditions, and run the same test repeatedly until the mean and median converge to within some acceptable tolerance, e.g. 1%
You can then use standard deviation to make accurate statements about the data including its variability.
If you run multiple benchmarks you can later do regression testing to eliminate the tests that aren't correlated to the end result. You can combine the results of multiple benchmarks using the geometric mean.
If that's confusing, then I'll happily explain it in more detail.
Any more shenanigans, this thread gets locked. Either discuss the post like an adult or don't post.
You quoted my post about battery screens + on screen buttons but have not answered what is the deal with it.
What are those on screen buttons doing there on a official ROM for the 9023?
Already answered but maybe i wasn't clear enough.
I tested those kernel with daily usage aswell, that mean with mods apps and every crap i use daily. Those ss refers to the daily usage with my rom.
Hi,
I saw BravoMotolora's article about CPU binning, and I thought that it would be great if we compare CPU bin and voltages.
It will be great to know the relationship between voltage and PVS number.
Please follow this procedure
1. Install a custom kernel that lets you do undervolt, e.g. franco.Kernel
2. Do what BravoMotolora said
3. Undervolt your N5 by 25MV
4. Run Antutu
Then, you might see your N5 rebooting or giving you a Antutu score.
If you get the score, go and try the procedure again
I got to -50MV with PVS1 N5.
Please post your results(undervolt that you did and your N5's PVS) here!
Can you not do this?
Do not do what? I mean most of guys here will do undervolt to save battery anyway so won't it be good to share some intel?
Sent from my Nexus 5 using XDA Premium HD app
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
you do realize that many custom kernels set their voltages different than default/stock, and differ among themselves? for example, if you go -50mV less on using franco kernel, and go -50mV less using trinity kernel, it means nothing because their voltages differ to begin with. i mean you cant really compare each others voltages that way. you would need to write your voltages in real numbers, and cpu speed steps.
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
johndrmr said:
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agreed. i personally do better with underclocking, than with undervolting.
simms22 said:
agreed. i personally do better with underclocking, than with undervolting.
Click to expand...
Click to collapse
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
This phone does pretty well arlt idle I think. Can't imagine you would see much gain from UV.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
klin1344 said:
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
Click to expand...
Click to collapse
I have a PVS 2 and can undervotl -75mV accross the board and -87.5mV at 300Mhz.
So 2,26Ghz I can run at 0.975 Volt.
CM11 with Bricked Kernel.
Together with Sync off, Google hotword off and optimized automatic brightness I get constantly 5 - 5,5 hours screen on time with websurfing, mail and music stream.
Marcel
menting said:
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
Click to expand...
Click to collapse
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
rajendra82 said:
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
Click to expand...
Click to collapse
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
I agree with you here. 1036 mhz is a great CPU speed for running the device and most apps. Most games UC the CPU for better battery temp like in PPSSPP. Less temperature throttle and more stable frames per second.
Benchmarks are a difference story though but who cares about those. UC is lag free, and buttery smooth so why not?
Sent from my Nexus 5 using Tapatalk
zz_marcello said:
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
Click to expand...
Click to collapse
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
simms22 said:
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
Click to expand...
Click to collapse
You can do everything you are already doing, but also undervolt, and your battery life will increase, without affecting your performance. Your performance will be different than my performance (because I don't underclock), however imperceptible as it may be. So undervolting is still better than not undervolting, even for you.
Using EX kernel 3.27, underclocked to 1.5Ghz, undervolted to "700 min" and using "stock" thermal throttling setting. Rock solid and it barely even gets warm now. Responsiveness and performance is only a touch worse than stock; the only places I really notice any performance reduction is in intensive games and app install times. Battery life is massively improved.
Greetings,
This driver is obtained from Qualcomm's 07 Aug 14 drivers for "Qualcomm Adreno 3xx GPU on Nexus 4, 5 & 7 devices running Google Android 4.4.4 KitKat".
All credits go to the folks at Qualcomm for making the developer version of these lib files available for us to play with.
This is for testing purposes only. Please don't flash without backing up first and then start screaming if something happens to your phone!
The package only contains files for Adreno 300 and 330. I cooked the packaged to be flashable on our SM-G900T or any SM-G900 with the Adreno 330 chipset.
I'm on a "XtreStoLite_G900T_ROM_v1.3_UVU1BNG3" ROM, which is a super clean/slim version of the stock rom. This is also Android 4.4.2, my AnTuTu benchmark results dropped from 37400 to 35800 after flashing this package.
I'm requesting someone with a KitKat 4.4.4 ROM to test this and report back their before and after benchmarks.
I appreciate your feedback,
Hmm, interesting.. I'm only on 4.4.2 or I would help out..
Turned out the 3D performance on antutu version 5 with this driver puts our phone one head and shoulder above everyone else!
Sent from my SM-G900T using XDA Free mobile app
Commodore 64 said:
Turned out the 3D performance on antutu version 5 with this driver puts our phone one head and shoulder above everyone else!
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
And this means....... I'm sorry but I don't understand the purpose... Is this supposed to make Tw snappier?
Thanks in advance!
It is updating the video (graphics) drivers. It probably improves the touchWiz performance as well (don't have evidence to support this), but what i noticed was a huge performace increase in the 3D graphics score. This will make games run alot smooter and more efficiently.
To clarify, this file resembles how your Mac/PC has a video card with say NViDIA or ATi video cards and they have their own driver releases. Our phones graphic chipset is designed by Qualcomm and it gets its own drivers as well. Hope I answered your question, and didn't make it worse!
Sent from my SM-G900T using XDA Free mobile app
In order to get any real "TouchWiz/Nova/Apex/etc" performance increase from it you'd have to flash this, then venture into Developer's Options and enable Force GPU rendering and Disable Hardware Overlays. And even then our device is so performance driven that you likely would likely not even realize the difference other than giving the CPU a break for a few cycles and possibly seeing a battery life increase depending on whether the CPU or GPU pulls more juice. These drivers are largely made to increase the 3D performance of your device when gaming and while it wasn't meant for us I'm glad to see someone took the time to let us benefit from it.
I'm going to flash it on an NG4 (4.4.2) release and see how it holds up to GPU rendering no hardware overlays. I don't game so if you want an objective test on that someone will have to pick up my slack. I'll report back when I know if it truly impacts it.
Tried flashing the update and ran into a couple random fcs for a few apps. Nothing device-breaking or anything, but I also didn't notice any real difference in performance or framerate in games. But I do appreciate you posting this, I'm always up for trying a little experimentation on my device to find something new. Thanks man.
AlkaliV2 said:
In order to get any real "TouchWiz/Nova/Apex/etc" performance increase from it you'd have to flash this, then venture into Developer's Options and enable Force GPU rendering and Disable Hardware Overlays. And even then our device is so performance driven that you likely would likely not even realize the difference other than giving the CPU a break for a few cycles and possibly seeing a battery life increase depending on whether the CPU or GPU pulls more juice. These drivers are largely made to increase the 3D performance of your device when gaming and while it wasn't meant for us I'm glad to see someone took the time to let us benefit from it.
I'm going to flash it on an NG4 (4.4.2) release and see how it holds up to GPU rendering no hardware overlays. I don't game so if you want an objective test on that someone will have to pick up my slack. I'll report back when I know if it truly impacts it.
Click to expand...
Click to collapse
Anything?
Thanks in advance!
Slicktune said:
Anything?
Thanks in advance!
Click to expand...
Click to collapse
Don't worry, I didn't forget about you. It takes a few days to really put it through its paces. But here is what you want to know: It works in 4.4.2 Touchwiz (Alliance Rom B4 for me)
Performance Increase in ROM function and control with "Turn Off Hardware Overlays" and Force GPU Rendering: Check
So I tested this by underclocking my CPU to the point where lag was perceivable in things likes app launching, keyboard typing, app draw opening, etc. I dropped it down to about 1200Mhz on all cores and then disabled HW Overlays. It was night and day. After the GPU took over rendering my CPU clock speed hardly moved all of the items previously lagging went right back to being fluid.
So does it help with Rendering in the ROMs? Yes, it definitely can.
The other concern people have is with battery life that goes with GPU rendering and the claims are that the GPU uses more power than the GPU. In my preliminary testing, what I noticed was lower overall CPU temps while Hardware Overlays was off, lower CPU clock speeds since it didn't need to render apps, and a small decrease in battery life.
In the power draw category I need more time with BetterBatteryStats and I need to adjust some variables. I want to underclock the GPU to the point of perceivable lag (if that is possible) and then I want to adjust the governor with KTweaker and see if I can't get better battery life. I will simultaneously lower CPU speeds to keep my core temperatures down and keep the battery cool. If these things are successful and battery life is interchangeable between the two, I may run the GPU full time for rendering the ROM. Keep in mind though, only custom kernels allow this kind of tweaking. If you use a stock ROM you are stuck with CPU and GPU clock speeds where they are so battery will drain faster.
Give me about a week to test my theory on this and see if I can find an equilibrium for CPU and GPU temperature and speed. I'll post the profile I used with KTweaker when I have my results. Until then, if you want to help and find your own settings and post them here along with battery life that would be awesome.
Edit: For what it is worth, to test application launch speeds and UI fluidity with the GPU I completely turned off system animations, I set Nova Launcher Animations Speed to Faster than light and scroll speed to "Fast" (personal preference). I got the same, or better response time using the GPU to render the UI.
AlkaliV2 said:
Don't worry, I didn't forget about you. It takes a few days to really put it through its paces. But here is what you want to know: It works in 4.4.2 Touchwiz (Alliance Rom B4 for me)
Performance Increase in ROM function and control with "Turn Off Hardware Overlays" and Force GPU Rendering: Check
So I tested this by underclocking my CPU to the point where lag was perceivable in things likes app launching, keyboard typing, app draw opening, etc. I dropped it down to about 1200Mhz on all cores and then disabled HW Overlays. It was night and day. After the GPU took over rendering my CPU clock speed hardly moved all of the items previously lagging went right back to being fluid.
So does it help with Rendering in the ROMs? Yes, it definitely can.
The other concern people have is with battery life that goes with GPU rendering and the claims are that the GPU uses more power than the GPU. In my preliminary testing, what I noticed was lower overall CPU temps while Hardware Overlays was off, lower CPU clock speeds since it didn't need to render apps, and a small decrease in battery life.
In the power draw category I need more time with BetterBatteryStats and I need to adjust some variables. I want to underclock the GPU to the point of perceivable lag (if that is possible) and then I want to adjust the governor with KTweaker and see if I can't get better battery life. I will simultaneously lower CPU speeds to keep my core temperatures down and keep the battery cool. If these things are successful and battery life is interchangeable between the two, I may run the GPU full time for rendering the ROM. Keep in mind though, only custom kernels allow this kind of tweaking. If you use a stock ROM you are stuck with CPU and GPU clock speeds where they are so battery will drain faster.
Give me about a week to test my theory on this and see if I can find an equilibrium for CPU and GPU temperature and speed. I'll post the profile I used with KTweaker when I have my results. Until then, if you want to help and find your own settings and post them here along with battery life that would be awesome.
Edit: For what it is worth, to test application launch speeds and UI fluidity with the GPU I completely turned off system animations, I set Nova Launcher Animations Speed to Faster than light and scroll speed to "Fast" (personal preference). I got the same, or better response time using the GPU to render the UI.
Click to expand...
Click to collapse
Thanks for the detailed response, can I flash this over a cm rom or only "touch wiz" and/or after I updated/flash this no Mauer what rom I flash will it stay. ..?
Thanks in advance! I'm still a bit confused...
Slicktune said:
Thanks for the detailed response, can I flash this over a cm rom or only "touch wiz" and/or after I updated/flash this no Mauer what rom I flash will it stay. ..?
Thanks in advance! I'm still a bit confused...
Click to expand...
Click to collapse
I haven't tried it on CM yet, I'm about to flash the 09/04 build of CM11 by Albinoman with KT's kernel. But I won't flash these drivers prior to running the build 24 hours or so to make sure there aren't bugs that existed before flashing the files. So, if you've been running CM for awhile and want to test this build just nandroid, flash, and report any issues.
AlkaliV2 said:
I haven't tried it on CM yet, I'm about to flash the 09/04 build of CM11 by Albinoman with KT's kernel. But I won't flash these drivers prior to running the build 24 hours or so to make sure there aren't bugs that existed before flashing the files. So, if you've been running CM for awhile and want to test this build just nandroid, flash, and report any issues.
Click to expand...
Click to collapse
Ooo that sounds like a killer combo cm + kt kernel + adreno update = project slip n slide lol nah but I'm really curious of what results you might get [emoji4]
And once I flash this, can I go back or will it erase the update once I flash a different rom?
Thanks in advance!!
Slicktune said:
Ooo that sounds like a killer combo cm + kt kernel + adreno update = project slip n slide lol nah but I'm really curious of what results you might get [emoji4]
Click to expand...
Click to collapse
I'll keep you posted. I wasn't impressed overall with it's performance in Touchwiz on battery life with the CPU underclocked, so I am branching out to a more AOSP-like build. I'll keep you posted to what I find out.
Commodore 64 said:
Turned out the 3D performance on antutu version 5 with this driver puts our phone one head and shoulder above everyone else!
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
This can't be right because right now I haven't flashed the driver update and look at My score
Now imagine that's without kt kernel just stock kernel, I'm on xtralite 3.5a t-mobile, so what if I flashed the kt kernel AAAAND the adreno update.... would my phone explode?!?!
I'm thinking twice now whether I should flash thisor not. ..
You have a good point. I think antutu v5 also rescaled their scoring system. Anyway, post your new score if you decided you want to give it a shot.
Sent from my SM-G900T using XDA Free mobile app
This maybe off topic, but does this works on other devices like Z2 or HTC M8 using the same GPU?
43718 before
43292 after
All I did was reboot into recovery, flash the ZIP and then run the test, same clock speed etc..
92drls said:
43718 before
43292 after
All I did was reboot into recovery, flash the ZIP and then run the test, same clock speed etc..
Click to expand...
Click to collapse
Lower score, what about gaming?
Slicktune said:
This can't be right because right now I haven't flashed the driver update and look at My score
Now imagine that's without kt kernel just stock kernel, I'm on xtralite 3.5a t-mobile, so what if I flashed the kt kernel AAAAND the adreno update.... would my phone explode?!?!
I'm thinking twice now whether I should flash thisor not. ..
Click to expand...
Click to collapse
Commodore 64 said:
You have a good point. I think antutu v5 also rescaled their scoring system. Anyway, post your new score if you decided you want to give it a shot.
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
92drls said:
43718 before
43292 after
All I did was reboot into recovery, flash the ZIP and then run the test, same clock speed etc..
Click to expand...
Click to collapse
HD-man said:
Lower score, what about gaming?
Click to expand...
Click to collapse
You guys make me sad. Benchmarks are not now, nor will they ever be, an acceptable means for telling you how capable your device is. Your scores in AnTuTu are about as capable of telling you your phone's speed as your ESN is at telling people who your phone belongs to. It is just arbitrary numbers that will fluctuate up and down based on the slightest inconsistencies.
Drivers, just like in Windows/Linux/Mac, are meant to optimize the performance of your hardware. That's it. This driver likely optimizes the GPU cycles to make it more efficient and lower heat output while performing better in games. You know why hardware review sites start out with benchmarks saying what it can do in a perfect world but still ends the review by telling you it gets 75 FPS in Borderlands 2? They do that because while synthetic tests are nice, what would be the point if our games don't play better? It is the same concept here.
I'm begging you, uninstall AnTuTu, re-install your favorite mobile game and just base performance off of whether it plays better or not.
Side Note: Drivers didn't appear to do anything in AOSP CM11 when I gave it a try. Sorry I am so late on reporting in, college takes up a lot of my time. Also, using the GPU to draw your applications does eat more battery whether you use these drivers or not. So there is no marked improvement from lowering CPU speed and using GPU only to render.
92drls said:
43718 before
43292 after
All I did was reboot into recovery, flash the ZIP and then run the test, same clock speed etc..
Click to expand...
Click to collapse
AlkaliV2 said:
You guys make me sad. Benchmarks are not now, nor will they ever be, an acceptable means for telling you how capable your device is. Your scores in AnTuTu are about as capable of telling you your phone's speed as your ESN is at telling people who your phone belongs to. It is just arbitrary numbers that will fluctuate up and down based on the slightest inconsistencies.
Drivers, just like in Windows/Linux/Mac, are meant to optimize the performance of your hardware. That's it. This driver likely optimizes the GPU cycles to make it more efficient and lower heat output while performing better in games. You know why hardware review sites start out with benchmarks saying what it can do in a perfect world but still ends the review by telling you it gets 75 FPS in Borderlands 2? They do that because while synthetic tests are nice, what would be the point if our games don't play better? It is the same concept here.
I'm begging you, uninstall AnTuTu, re-install your favorite mobile game and just base performance off of whether it plays better or not.
Side Note: Drivers didn't appear to do anything in AOSP CM11 when I gave it a try. Sorry I am so late on reporting in, college takes up a lot of my time. Also, using the GPU to draw your applications does eat more battery whether you use these drivers or not. So there is no marked improvement from lowering CPU speed and using GPU only to render.
Click to expand...
Click to collapse
I figured since the OP stated he got less points in Antutu, I would go ahead and use the same app and test to compare...
F*ck me right?
Regardless, I don't notice anything different either, my stats are in the sig.
Hi all,
So I got a question related to MI3W, the cooling system of it, and mainly:
Is it normal that while I'm doing basic stuff like internet browsing, using Tapatalk, Skype, whatever, the phone temperature is usually around 45-60°C? I think that's waaaay too much. Also I can feel the back and front of the phone(display) heating a lot. One thing I would like to say is that it's not dependent on any ROM or kernel, I'm facing this issue even in MIUI.
Now, this is not such a problem, but, the real problem appears when it comes to games or performance demanding apps. To get higher framerate or performance, I switch to High Performance mode (performance governor). But then, the SoC temperature rises to 90°C and I can't even touch the display so I won't burn myself.
Now, this sometimes happens even in idle mode, even though it's not this high temperature, but still it's about 60-70°C.
It could get pretty unpleasant if I received a call and had to put the burning phone on my face.
So I'm wondering if there's anything I can do with this issue and if anyone else has it, and if this is eventually an issue of the whole MI3 model.
Last thing, no other phone with S800 has this issue, I saw Xperia Z1 mini and Nexus 5 and none of them had such a crazy temperatures, I know this version of S800 is the one with overclocked GPU but still, it's not that much of difference and I don't think it receives any right to heat as much as it does to me.
{
"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"
}
Thank you for your feedback and hopefully this gets solved.
MI3W 64GB/Tapatalk
These apps won't tell you actual CPU temperature. The only place where you can find right one is at CPU-Z - Sensors - CPU Temperature
Me_Ashish_ said:
These apps won't tell you actual CPU temperature. The only place where you can find right one is at CPU-Z - Sensors - CPU Temperature
Click to expand...
Click to collapse
This app is actually accurate, CPU-Z reports the same temperatures, it just shows more sensors so I thought it would be better to just show a single temperature..
MI3W 64GB/Tapatalk
TofikLupus said:
This app is actually accurate, CPU-Z reports the same temperatures, it just shows more sensors so I thought it would be better to just show a single temperature..
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
Nope I'm talking about that single one shown in Sensors
Me_Ashish_ said:
Nope I'm talking about that single one shown in Sensors
Click to expand...
Click to collapse
Not sure what the single one is, but i'm sure it's not the SoC temperature. CPU-Z of my friend who owns Xperia Z1 mini was showing 30-35°C in the tab with many sensors. Even after calculating Pi to 10,000,000 decimal places it didn't go above 40°C.. and his calculation time was even higher than mine. I found out that the calculation time is dependent on the SoC temperature, if it's overheating then the performance is lower. So I can't try it more times because it usually rises to 60-70°C.
MI3W 64GB/Tapatalk
TofikLupus said:
View attachment 3544726View attachment 3544727View attachment 3544729
Not sure what the single one is, but i'm sure it's not the SoC temperature. CPU-Z of my friend who owns Xperia Z1 mini was showing 30-35°C in the tab with many sensors. Even after calculating Pi to 10,000,000 decimal places it didn't go above 40°C.. and his calculation time was even higher than mine. I found out that the calculation time is dependent on the SoC temperature, if it's overheating then the performance is lower. So I can't try it more times because it usually rises to 60-70°C.
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
There, under sensors 31.6 degree. Not talking about any of those thermal temperatures
Me_Ashish_ said:
There, under sensors 31.6 degree. Not talking about any of those thermal temperatures
Click to expand...
Click to collapse
But what are the other temperatures then? And why my phone gets burning hot? This doesn't make sense at all.
MI3W 64GB/Tapatalk
TofikLupus said:
But what are the other temperatures then? And why my phone gets burning hot? This doesn't make sense at all.
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
I don't know but I do know the one I mentioned is the actual one.
Ans my phone too gets burning hot on gaming and stuff. It can't be helped, the story of MI phones.
Me_Ashish_ said:
I don't know but I do know the one I mentioned is the actual one.
Ans my phone too gets burning hot on gaming and stuff. It can't be helped, the story of MI phones.
Click to expand...
Click to collapse
Okay, thanks for letting me know it's not an issue just for me but in general. I like this phone but I'm a bit dissapointed by this not well thought off cooling. I'm sometimes afraid the heat would destroy the LCD at one point because sometimes it's really intensive. Mostly after flashing an update for a ROM and upon the "Optimizing apps" screen.
One strange thing that I don't get though, is why nobody else is complaining about it, nor any reviews of the phone are mentioning this excessive heating.
I've been thinking about this for some while now.
MI3W 64GB/Tapatalk
Don't use while charging and stay with balance power profile. These are mainstream device so don't push these to limits very often (these are not dedicated gaming device) and limited passive cooling for SOC. Otherwise you will inviting a premature component failure. Device temperature is also closely associated with ambient temp so if your ambient is close to 24is C the device will sustain performance bit better.
dchinu said:
Don't use while charging and stay with balance power profile. These are mainstream device so don't push these to limits very often (these are not dedicated gaming device) and limited passive cooling for SOC. Otherwise you will inviting a premature component failure. Device temperature is also closely associated with ambient temp so if your ambient is close to 24is C the device will sustain performance bit better.
Click to expand...
Click to collapse
The problem is I can't use it while charging anyway, because the phone otherwise discharges faster than charges.
Also mostly I use balanced performance mode, since I know it starts to heat a lot and it gives me way too much performance for what i need most of the time. But when it's time for games, I need to use high performance mode otherwise the game isn't running so smooth. And in case of Piano Tiles, I experience unpleasant random stuttering of the game, which pretty much makes it unplayable. And that's not even any resource demaning game. So I'm forced to switch to HiPerf. mode anyway But it's really not that I'm overloading the phone and having it as a rendering station
About Mi3 being mainstream: I don't believe it's mainstream for its initial price, even though it was cheaper than other manufacturer's devices. Anyway, I will be careful with it. Still I don't get, if this is a mainstream device, why did Xiaomi use S800 SoC? It was a flagship when it was released 2 years ago. To me it looks like a fail from this point of view, trying to make a mainstream device(not so much dedicated to cooling) using high end components(which in fact need a better cooling).
MI3W 64GB/Tapatalk
Unfortunately MIUI has bad thermal tweaks...blah blah..
So i suggest you to lower the screen resolution from FHD to HD (Not much of difference) and lower the lcd density. By this u will see hell lot of difference (I tested this method myself).
** Secondly try using a good ROM with Better cpu and thermal tweaks like if u want MIUI taste then try "SMIUI"
Or use Mettallium OS (I use this myself)
*** (OPTIONAL) u can flash some .zips that contain some tweaks and many improvement (u can find them on XDA easily)
like Lspeed etc.
I was facing the overheating issues but lowering down the resolution does the magic.
U can find resolution guide in MI3 GENERAL.
have a gr8 day
Yes it does heats up during installing roms (optimizing apps). I cool it off by air forced cooling (holding device in front of cooler during installation else battery discharges by 20 percent).
Normal heating during gaming, but stays cool in daily use... on cm 12.1 stock kernel
If you are using miui. Try God's Kernel R3 or R4. And report.
That seems to be the problem of Snapdragon 800.
TofikLupus said:
Hi all,
So I got a question related to MI3W, the cooling system of it, and mainly:
Is it normal that while I'm doing basic stuff like internet browsing, using Tapatalk, Skype, whatever, the phone temperature is usually around 45-60°C? I think that's waaaay too much. Also I can feel the back and front of the phone(display) heating a lot. One thing I would like to say is that it's not dependent on any ROM or kernel, I'm facing this issue even in MIUI.
Now, this is not such a problem, but, the real problem appears when it comes to games or performance demanding apps. To get higher framerate or performance, I switch to High Performance mode (performance governor). But then, the SoC temperature rises to 90°C and I can't even touch the display so I won't burn myself.
Now, this sometimes happens even in idle mode, even though it's not this high temperature, but still it's about 60-70°C.
It could get pretty unpleasant if I received a call and had to put the burning phone on my face.
So I'm wondering if there's anything I can do with this issue and if anyone else has it, and if this is eventually an issue of the whole MI3 model.
Last thing, no other phone with S800 has this issue, I saw Xperia Z1 mini and Nexus 5 and none of them had such a crazy temperatures, I know this version of S800 is the one with overclocked GPU but still, it's not that much of difference and I don't think it receives any right to heat as much as it does to me.
View attachment 3544214
Thank you for your feedback and hopefully this gets solved.
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
Okay, so a little update - Recently I reached an incredible temperature of 107°C on the CPU chip!!! And then thermally shut down. I think this isn't fun anymore. I don't know if i have some defective piece or if it's normal for all MI3's but I'm starting to think about returning the phone or just claiming a replacement. Both the front and back of the phone gets hot very soon, just by watching some youtube vids or browsing internet...or JUST having the phone simply unlocked and idling. The temperatures don't go under 40°C. I think that this is the reason why MI3 was cheaper than other phones with the same SoC.
In the worst case, I will revert the partition table back to stock, install latest MIUI 7 on it and send it to a service center.
MI3W 64GB/Tapatalk
TofikLupus said:
Okay, so a little update - Recently I reached an incredible temperature of 107°C on the CPU chip!!! And then thermally shut down. I think this isn't fun anymore. I don't know if i have some defective piece or if it's normal for all MI3's but I'm starting to think about returning the phone or just claiming a replacement. Both the front and back of the phone gets hot very soon, just by watching some youtube vids or browsing internet...or JUST having the phone simply unlocked and idling. The temperatures don't go under 40°C. I think that this is the reason why MI3 was cheaper than other phones with the same SoC.
In the worst case, I will revert the partition table back to stock, install latest MIUI 7 on it and send it to a service center.
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
Which rom are you using? And kernel?
24likan said:
Which rom are you using? And kernel?
Click to expand...
Click to collapse
The superhigh temperatures were in recovery and before the phone boots up. I was reaching 80-90°C in any ROM, including MIUI(while gaming) and 60-70°C at normal use. Sadly, no ROM affects the temperature, it's always high. I was using all stock kernels, until yesterday, when I flashed Moshi stock kernel, expecting lower temperatures. Well, they were lower, but still 60°C with JUST watching youtube videos, that's a bit too much.
I think Xiaomi just didn't think off the cooling well, because Nexus 5 and Galaxy S5 don't suffer from so high temperatures, 60°C at most while gaming, and people at forums complain about getting 50°C while i'm glad to have 45°C in idle state. And I'm not talking about the surface temperature, I'm talking about the on-chip temperature, which to me is more important.
MI3W 64GB/Tapatalk
GUYS - What if https://youtu.be/hZDNpp--E0Y was applied to MI3? Maybe my device is just poorly greased and the heat doesn't transfer to the aluminium plate effectively. That could be a solution, if it's possible, which I believe it is, because MI3 has the same aluminium plate on the back of the LCD as a heatsink(i believe it is aluminium).
MI3W 64GB/Tapatalk
TofikLupus said:
GUYS - What if https://youtu.be/hZDNpp--E0Y was applied to MI3? Maybe my device is just poorly greased and the heat doesn't transfer to the aluminium plate effectively. That could be a solution, if it's possible, which I believe it is, because MI3 has the same aluminium plate on the back of the LCD as a heatsink(i believe it is aluminium).
MI3W 64GB/Tapatalk
Click to expand...
Click to collapse
I understand your problem. May be yours is a hardware problem. But try flashing God's kernel R3 or R4
{
"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?