I see that people are having mixed opinions when it comes to Overclocking the display on k20 pro. So can we have some feedback by people who used it for Decent - Long term, just enough so we can have a clear idea of whether it is safe to daily drive Overclocked display mod or not.
If you carry about ur phone, dont oc. I've heard that screen cables [if i can call it like that(probably not)]
are so small that from overclocking they can just be damaged. I would rather overclock an actual clock(wtf)
And the fact that when i wanted to overclock my pc monitor from 75hz i was able to overclock it to only 81hz... Yes i've tested the 82hz but monitor just couldnt handle it. So imagine how it would be on ur mobile.
And if u wanna just slightly oc ur display,
First u wont see any difference at all
And second ur display will start to suffer a bit.
(I would recommend oc sreen if u wanna buy a new phone lel)
Edit: i think i didnt read the topic carefully so....
Ur screen can even die
hrdlw said:
If you carry about ur phone, dont oc. I've heard that screen cables [if i can call it like that(probably not)]
are so small that from overclocking they can just be damaged. I would rather overclock an actual clock(wtf)
And the fact that when i wanted to overclock my pc monitor from 75hz i was able to overclock it to only 81hz... Yes i've tested the 82hz but monitor just couldnt handle it. So imagine how it would be on ur mobile.
And if u wanna just slightly oc ur display,
First u wont see any difference at all
And second ur display will start to suffer a bit.
(I would recommend oc sreen if u wanna buy a new phone lel)
Edit: i think i didnt read the topic carefully so....
Ur screen can even die
Click to expand...
Click to collapse
Yeah I have a similar insight but I find 75hz way more bare-able to my eyes. I spend a lot of time on my computer and my monitor is 240 hz so almost all screens disappoint me. Though I find 75 hz a lot more better than 60. Have you tried the mod for a significant amount of time? On the phone?
The main issue is the AMOLED display, i've seen LCD's getting retention marks after a long time using overclocking, but amoleds have the risk of burn-in and I would never recommend messing with this if you want to use your device for more than 1 year, I bet it would get burn-in marks in some weeks after using 75hz or above. It's best to stay safe and take care of your device in my opinion, but that it's up to you.
LuanHalaiko said:
The main issue is the AMOLED display, i've seen LCD's getting retention marks after a long time using overclocking, but amoleds have the risk of burn-in and I would never recommend messing with this if you want to use your device for more than 1 year, I bet it would get burn-in marks in some weeks after using 75hz or above. It's best to stay safe and take care of your device in my opinion, but that it's up to you.
Click to expand...
Click to collapse
I didn't know burn-in issues had anything to do with the refresh rate. Maybe I need to learn more about why that happens. Other than the burn-in issues you think OC to 75 will harm in some other way?
Nick_101d said:
I didn't know burn-in issues had anything to do with the refresh rate. Maybe I need to learn more about why that happens. Other than the burn-in issues you think OC to 75 will harm in some other way?
Click to expand...
Click to collapse
I have been running the phone at 75hz since the start and I bought the phone in May 2019. I have yet to see any flickering, tinting or artefacts. I would say there is a risk but give the fact that over hundreds to thousands of users overclock their display on the 9t pro and have yet to report a permanent issue, it is rather safe since the voltage and current is not altered. Then again, millions of users overclock their computer monitor for decades and have yet to see any irreversible effect.
Menoobone said:
I have been running the phone at 75hz since the start and I bought the phone in May 2019. I have yet to see any flickering, tinting or artefacts. I would say there is a risk but give the fact that over hundreds to thousands of users overclock their display on the 9t pro and have yet to report a permanent issue, it is rather safe since the voltage and current is not altered. Then again, millions of users overclock their computer monitor for decades and have yet to see any irreversible effect.
Click to expand...
Click to collapse
Thank you! That's what I was looking for! Can you link me to the mod thread that you use?
Menoobone said:
I have been running the phone at 75hz since the start and I bought the phone in May 2019. I have yet to see any flickering, tinting or artefacts. I would say there is a risk but give the fact that over hundreds to thousands of users overclock their display on the 9t pro and have yet to report a permanent issue, it is rather safe since the voltage and current is not altered. Then again, millions of users overclock their computer monitor for decades and have yet to see any irreversible effect.
Click to expand...
Click to collapse
Actually can you help me even more? I am on evo X and I flashed the module without reading the instructions. I headed to https://forum.xda-developers.com/k20-pro/themes/magisk-modules-k20pro-mi9t-pro-one-t4093255 so I missed on the instructions and I dont have my stock dtbo! Can you send your dtbo or help me get it back someway??
Nick_101d said:
Actually can you help me even more? I am on evo X and I flashed the module without reading the instructions. I headed to https://forum.xda-developers.com/k20-pro/themes/magisk-modules-k20pro-mi9t-pro-one-t4093255 so I missed on the instructions and I dont have my stock dtbo! Can you send your dtbo or help me get it back someway??
Click to expand...
Click to collapse
You have to help yourself for that. Different firmware, kernels, and even the different versions require different DTBO. There is no universal DTBO. AFAIK, Immensity and F1XY kernel blocks screen OC. Also, certain DTBO only works for certain type of fingerprint implementation, such as Mi9fod,Mi9fod advance,Losfod,MIUIFOD etc. Some works in terms of OC but will screw up your fingerprint, while others have the fingerprint working but OC not working. You also have to take note of the DC implementation.
Again, you have to help yourself and do some research. I would suggest you start with the standard 75hz_nodimming version and older versions of Immensity kernel and try. Do note that flashing the wrong DTBO can render your device unbootable and it might even cause the recovery to not boot.
Nick_101d said:
Yeah I have a similar insight but I find 75hz way more bare-able to my eyes. I spend a lot of time on my computer and my monitor is 240 hz so almost all screens disappoint me. Though I find 75 hz a lot more better than 60. Have you tried the mod for a significant amount of time? On the phone?
Click to expand...
Click to collapse
I couldnt make it work
---------- Post added at 01:00 AM ---------- Previous post was at 12:69 AM ----------
LuanHalaiko said:
The main issue is the AMOLED display, i've seen LCD's getting retention marks after a long time using overclocking, but amoleds have the risk of burn-in and I would never recommend messing with this if you want to use your device for more than 1 year, I bet it would get burn-in marks in some weeks after using 75hz or above. It's best to stay safe and take care of your device in my opinion, but that it's up to you.
Click to expand...
Click to collapse
What do you think about some videos on youtube that "may" prevent burnin?
---------- Post added at 01:11 AM ---------- Previous post was at 01:00 AM ----------
Menoobone said:
I have been running the phone at 75hz since the start and I bought the phone in May 2019. I have yet to see any flickering, tinting or artefacts. I would say there is a risk but give the fact that over hundreds to thousands of users overclock their display on the 9t pro and have yet to report a permanent issue, it is rather safe since the voltage and current is not altered. Then again, millions of users overclock their computer monitor for decades and have yet to see any irreversible effect.
Click to expand...
Click to collapse
So it's kinda simmiliar to overclocking a pc cpu without touching voltage, right?
Menoobone said:
I have been running the phone at 75hz since the start and I bought the phone in May 2019. I have yet to see any flickering, tinting or artefacts. I would say there is a risk but give the fact that over hundreds to thousands of users overclock their display on the 9t pro and have yet to report a permanent issue, it is rather safe since the voltage and current is not altered. Then again, millions of users overclock their computer monitor for decades and have yet to see any irreversible effect.
Click to expand...
Click to collapse
PC monitors are LCDs (IPS or VA panels most of the time), amoled will always get burn-in marks after some time, it's just the way they age, overclocking on amoleds is quite risky as I said before, the voltage dosn't matter in this scenario, by overclocking a 60hz amoled panel you are just forcing the pixels to update even faster than normal (they obviously wasn't made for that, you get side effects like discoloration), in theory burn-in marks have way more change to appear on a overclocked panel than a 60hz one.
Of course, I'm here just to spread info, everyone can do whatever they want to their devices, if I'm wrong on something I apologize, this is what I know from studying displays along these years
LuanHalaiko said:
PC monitors are LCDs (IPS or VA panels most of the time), amoled will always get burn-in marks after some time, it's just the way they age, overclocking on amoleds is quite risky as I said before, the voltage dosn't matter in this scenario, by overclocking a 60hz amoled panel you are just forcing the pixels to update even faster than normal (they obviously wasn't made for that, you get side effects like discoloration), in theory burn-in marks have way more change to appear on a overclocked panel than a 60hz one.
Of course, I'm here just to spread info, everyone can do whatever they want to their devices, if I'm wrong on something I apologize, this is what I know from studying displays along these years
Click to expand...
Click to collapse
I agree with what you said. I would also like to share my experience and knowledge. I have been working in a display company for quite a while. From my experience, most of the grade A OLED displays can usually run about 20% ish higher frame rate than what is advertised at the given voltage and current. Bumping the voltage will give us a higher sustained refresh rate aka being more stable but that would usually result in a lower life span. As much as I am aware, overclocking the refresh rate on OLED should not cause burn in issues but discoloration or tinting is inevitable for grade A- and below displays. LCD however, have a lower margin of % in terms of overclockability at about 10-15% ish depending on panel type and quality.
Some of the users get green tint or high latencies when running at 75hz while the others don't. For my set, it does not have the said issues at a but there are indeed multiple users getting mild temporary tint when applying overclock. That could be due to insufficient voltage for this particular display hence the instability unlike other displays that actually shows sign of distress due to being forced over their capabilities. We can only advise to monitor and OC at your own risk as the quality of the panel used is not very consistent. I have another set that still managed 84hz on GSI Havoc without issues but my main set can only run stable at 75hz. As for those that have permanent issues with their display, it's said that they actually overclocked to 84hz/90hz so that's another story I guess?
As far as I'm aware, Xiaomi intentionally lowered the voltage on MIUI so the display can only overclock by 10-15% to a maximum of 69hz, 75hz is still possible on custom kernel and AOSP. Correct me if I'm wrong.
Menoobone said:
[...]As far as I'm aware, Xiaomi intentionally lowered the voltage on MIUI so the display can only overclock by 10-15% to a maximum of 69hz, 75hz is still possible on custom kernel and AOSP. Correct me if I'm wrong.
Click to expand...
Click to collapse
Thanks for the info, it really helps when someone who has direct contact with this type of technology. I also agree with what you said above but even if voltage is consistant it still is a mod that pushes the display to its limits, we can't deny the possibility of a future damage and the fact no one had issues until now could indicate that it's harmless, but it can also mean that nobody is noticing it until it gets really bad, that's just a theory tho.
I think everything was answered by our ideas, so for a short answer to the people who want to use it:
Is display overclocking on amoled safe?
-> Yes it is, amoleds could be damaged by increased voltage rather then increased refresh rate, so use it with minor dropbacks like the colors being a bit off.
Menoobone said:
You have to help yourself for that. Different firmware, kernels, and even the different versions require different DTBO. There is no universal DTBO. AFAIK, Immensity and F1XY kernel blocks screen OC. Also, certain DTBO only works for certain type of fingerprint implementation, such as Mi9fod,Mi9fod advance,Losfod,MIUIFOD etc. Some works in terms of OC but will screw up your fingerprint, while others have the fingerprint working but OC not working. You also have to take note of the DC implementation.
Again, you have to help yourself and do some research. I would suggest you start with the standard 75hz_nodimming version and older versions of Immensity kernel and try. Do note that flashing the wrong DTBO can render your device unbootable and it might even cause the recovery to not boot.
Click to expand...
Click to collapse
No worries. I actually fixed it by dirtyflashing the current EVO X 4.5 rom(which my device was running currently)
That seems to have fixed the yellow tint as well as the refresh rate is back to 60hz.
Menoobone said:
I agree with what you said. I would also like to share my experience and knowledge. I have been working in a display company for quite a while. From my experience, most of the grade A OLED displays can usually run about 20% ish higher frame rate than what is advertised at the given voltage and current. Bumping the voltage will give us a higher sustained refresh rate aka being more stable but that would usually result in a lower life span. As much as I am aware, overclocking the refresh rate on OLED should not cause burn in issues but discoloration or tinting is inevitable for grade A- and below displays. LCD however, have a lower margin of % in terms of overclockability at about 10-15% ish depending on panel type and quality.
Some of the users get green tint or high latencies when running at 75hz while the others don't. For my set, it does not have the said issues at a but there are indeed multiple users getting mild temporary tint when applying overclock. That could be due to insufficient voltage for this particular display hence the instability unlike other displays that actually shows sign of distress due to being forced over their capabilities. We can only advise to monitor and OC at your own risk as the quality of the panel used is not very consistent. I have another set that still managed 84hz on GSI Havoc without issues but my main set can only run stable at 75hz. As for those that have permanent issues with their display, it's said that they actually overclocked to 84hz/90hz so that's another story I guess?
As far as I'm aware, Xiaomi intentionally lowered the voltage on MIUI so the display can only overclock by 10-15% to a maximum of 69hz, 75hz is still possible on custom kernel and AOSP. Correct me if I'm wrong.
Click to expand...
Click to collapse
I am using 82 hz mod on candy kernal without any problem
K20 pro user said:
I am using 82 hz mod on candy kernal without any problem
Click to expand...
Click to collapse
I'm also using 82hz since I got this phone in 2019. No problem with the screen. The only problem is the limited ROMs you can use that supports higher refresh rates when you want to change ROMs.
Cocoyg said:
I'm also using 82hz since I got this phone in 2019. No problem with the screen. The only problem is the limited ROMs you can use that supports higher refresh rates when you want to change ROMs.
Click to expand...
Click to collapse
Till now r u using overclocked display ??
vicky#kick said:
Till now r u using overclocked display ??
Click to expand...
Click to collapse
Yes. Still no problem with my phone's screen.
Burn-in is and isn't an issue.
I've owned 3 amoled devices, loads of use and no burn-in. But that's because I don't keep it on full brightness.
But every other phone I've seen from other people, S2, S3, galaxy note 5 (twice). All have burn-in. Brightness is more likely to cause it than display hz. I've run mine at 69hz since launch. No issues.
But... Only overclock if you have the superior Samsung display. And not the cheap Visionox panel some people have.
Bought in 2020, started OC in late 2021
2 months of 72hz, 8 months of 81hz, 2-3 months of 102hz
Still in great condition as when I bought it
Related
Well I downloaded cpu master (free) to just mess around with my photon, and come to find out, the governor for the cpu is set to performance, but gave me the option to change it to powersave, so I switch it and I'll report back to you guys and see if I've found the holy Grail to even better battery life
Sent from my MoPho using XDA App
That's awesome
Sent from my MB855 using xda premium
Wait until I or another dev gets onDemand governor enabled...
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster. If you scale the CPU back massively while it is set to sleep, however, you will save a lot of battery.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
well, i don't know about your phone or what else you have setup, but my phone didn't lag and it seemed to help, i currently have my evo 3d active so my photon just sits there, so i can give a good feedback of idle time, but i can tell you after switching the governor, it went down 1% in 2 hours, now i say that's an improvement, so when i get back home i'll really give you guys some feedback
P.S. with any phone i had that had a fully custom kernal, i always used conservative governor
Well, perhaps it's just the apps I have running then. As I said, when it's set to sleep, it works pretty well with the powersave mode, otherwise, doesn't seem to make any real difference. Guess it's different for everyone cause of the **** they're running on their phone.
mrinehart93 said:
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster.
Click to expand...
Click to collapse
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
my2cents said:
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
Click to expand...
Click to collapse
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
mrinehart93 said:
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
Click to expand...
Click to collapse
Interesting...I hadn't thought about using an OC kernel and underclocking it back to stock. I wonder what that does, if anything, to performance.
The other concern that I have is that overclocking typically means more heat, which means more battery use... Just figured I would throw that out there too.
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
A2CKilla said:
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
Click to expand...
Click to collapse
and just an update, in another 4 hours, it's only gone down 2%!!!!!! come on guys, these numbers can't lie, but remember this is idle feedback, i'll re-activate my photon at the end of the week (missing the beast!) to give more detail feedback on heavy usage and most importantly 4g!!
Development. Development. Development.
Sent from my MB855 using xda premium
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
scoobdude said:
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Let me start this off by saying that I am an agricultural engineer by trade. With that said, I would agree that engines have an efficiency range. However, I would not agree that it is at x throttle. Rather, it is a x load. And most cars are designed to be at optimal load at about 60 mph (wind resist, weight, etc. play a role in this). You're right, it does require more fuel to get to that speed because the load is higher until that speed is reached. Furthermore, higher speeds (greater than 60 mph) do NOT translate into higher fuel mileages because the load increases to maintain the higher speed (because there is more wind resistance, among other things).
I know a bit about electricity too, but I don't fully understand the physics behind circuit boards. However, I think the analogy still holds. I can get to 60 mph as fast as I want, but the faster I do it the more energy is required. Therefore, even though it is done faster it still requires more energy, which also creates more heat, both of which use the battery. So, I continue to contend that there is a happy medium that most be found and I think electronic engineers aren't to far off.
Here is a little more reading about car efficiency, if you are interested: http://www.mpgforspeed.com/
I believe your confusing overclocking and overvolting. We are putting x volts into the processor so the more cycles we can get in x volts the better. If we have to overvolt to overclock then we see big battery hits.
Sent from my MB855 using Tapatalk
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
again it depends on how the overclock is achieved. In most cases overclock is achieved by dumping more electricity into the cpu this will impact battery life, however alot of chips these days can be overclocked at the same volts essentially upping the "MPG" or clocks per volt.
A2CKilla said:
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
Click to expand...
Click to collapse
I agree with this for the most part. When it comes to power the end result is watts, which is essentially equal to volts x amps. It is not perfect because of a power factor, but it is close. Therefore, if you lower the voltage, the amperage goes up because the same watts are required to run the processor. The inverse is also true. These processors have voltage ranges that they will safely run in, but in the end, they require the same energy (in watts) to function at a given load. Change one a little bit (the voltage for example) and the other (amperage) compensates. Change it a lot and it likely wont work. Again, this is how it works for your typical home appliances. For a circuit board, it might be a slightly different story, but I imagine the science does not change.
---------- Post added at 03:57 PM ---------- Previous post was at 03:47 PM ----------
scoobdude said:
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
You may be right. Perhaps Saab designed their fuel efficiency at 70 mph. It's possible because many speed limits are now at or near that, but in general, optimal fuel consumption is going to be at or near 60 mph. Obviously gear ratios and such play a huge role in fuel economy. It is like using a custom rom, typically your mods will make it perform better, but the best fuel economy or battery life will come with a stock like setup.
Sure a corvette can have HP and economy. There is a power to weight ratio and lots of aerodynamics involved, which again is designed at a specific speed. But there is no way that a dragster will have a good fuel efficiency. To my point, there is a balance...
I agree, we are off topic a little bit, but the conversation is interesting, nonetheless.
By the way, can a mod move this to general, please?
Hey, this is my first post here! **Edited for... uh... clarity and to add some information. Hopefully it's more readable now.
I found a way to control and manage the thermal throttling of the device.***
Modern smartphones create a lot of heat, and usually the casing of the device or the aluminum midframe chassis is used as a heatsink. Unlike a laptop, it does not have a cooling fan, so it must rely on the passive dissipation of heat through the casing of the device and the display panel to keep the CPU temperature down. On the Nexus 6P, there is decent thermal contact between the processor IC and the midframe. However, due to both the fact that the RAM is layered over top of the CPU and because the thermal contact is still not ideal, it is difficult to keep the CPU as cool as a computer implementation.
In order to reduce heat production and control the temperature of the device, the OEM implements thermal engine for Qualcomm MSM chipset in order to slow the frequency of the CPU and GPU cores down when the temperature is high.
Right now it is set to 50C throttling temperature, presumably so that the heat production does not cause the display panel to heat up to the touch, as at lower powers, the thermal mass of the aluminum frame plus passive dissipation will make case temperature increases not very noticeable. However, at 50C, the CPU will often throttle even at medium load, because the hardware does not make it easy to keep the temperature under that. This has been true for every phone I have worked with in the past and some are even worse at this.
Personally, I find that having a high (>45C) surface temperature is not a huge problem (You can decide that for yourself. if it is a problem for you, this won't help you. You can't change the power efficiency limit of the processor). In my use case, when I have a lot of applications open, especially Firefox in desktop mode, or 4-way Android M multitasking or something like that (or just typing to a lot of people in Facebook Messenger or something similar). I kinda use the thing like a computer so obviously it has extended periods of high CPU workload and the device starts to throttle back to something like 1344 or 960MHz or even lower.
Given this, what I want to do is change the CPU throttle temperature to a higher one. Generally, we don't need to worry about protecting the processor hardware because it has built in thermal shutdown/reset functions should something go wrong. It's at something like 110C, which sounds high, but as someone who uses a MacBook Pro, it is normal to see the CPU temperature that high! Intel generally throttles at a much higher temperature because they don't care about the actual temp of the heat sink, only that of the processor die.
In the past kernel I tried, there was an option to set up the thermal throttling temperature (God's Kernel). However, I switched to the AK kernel recently, due to its High Performance Audio feature. This kernel did not include support for this configuration.
I am running MH19Q Marshmallow stock.
I used File Explorer with root access to go to system/etc I think and there is a file called thermal_engine.conf or similar. If you edit it, you see there are a lot of values. Actually basically if you look around, there are a lot of temperature values in there seperated by the things they control. I would like to explain more, but I think it is better if you can open up your file and my file side by side and see for yourself what's different. The gist is that there's a table of values and a bunch of actions to take when they're hit, and of course, there are release temperatures, which are basically the lower hysterisis limit I think. The temperature values look like 44000 or 43000 by default, which means 44C and 33C (celcius)and I changed mine to 97000 (97 C)
Here you can find the content of the file. Type in the pastebin website, then put slash QYhi05rE.
I didnt keep my old file.... sorry about that... Perhaps someone can post it if they have it.
With stuff set to 97 C, the device heats up a lot more, obviously, but it's manageable. If you have something like Cinema 4K open for a long time, of course it will get to like 50C on the surface (That is quite unconfortable to put your hand on, but I'm okay with it). Hangouts video calling seems to be the worst and sometimes the battery will get higher than 50C and then stop charging. Given the design of the phone, by the time the battery gets too hot to be safe, the system will probably shutdown or restart, and you'll notice it LONG before anything becomes a problem.
Thanks for looking!
***Do this at your own risk, as with all root mods and tricks. Obviously this has the risk of breaking things or causing hardware to fail. High temperatures on BGA soldered chips have been observed to increase the failure rates, even in stuff like routers and TVs and other stuff that you don't generally think of as having thermal issues. My last phone (Note 5) kinda broke after a little while, although I'm not sure if me doing this caused it. (Appears to be display panel issue, but have not tested). All I know is that earlier that day I was outside filming on it and processing video, and that the area above the SoC got rather warm to the touch. Which should be read as "painfully hot" to most.
file removed? add disclaimer pls
LarryChendragon2099 said:
Hey, this is my first post here! **Edited for... uh... clarity and to add some information. Hopefully it's more readable now.
I found a way to control and manage the thermal throttling of the device.***
Modern smartphones create a lot of heat, and usually the casing of the device or the aluminum midframe chassis is used as a heatsink. Unlike a laptop, it does not have a cooling fan, so it must rely on the passive dissipation of heat through the casing of the device and the display panel to keep the CPU temperature down. On the Nexus 6P, there is decent thermal contact between the processor IC and the midframe. However, due to both the fact that the RAM is layered over top of the CPU and because the thermal contact is still not ideal, it is difficult to keep the CPU as cool as a computer implementation.
In order to reduce heat production and control the temperature of the device, the OEM implements thermal engine for Qualcomm MSM chipset in order to slow the frequency of the CPU and GPU cores down when the temperature is high.
Right now it is set to 50C throttling temperature, presumably so that the heat production does not cause the display panel to heat up to the touch, as at lower powers, the thermal mass of the aluminum frame plus passive dissipation will make case temperature increases not very noticeable. However, at 50C, the CPU will often throttle even at medium load, because the hardware does not make it easy to keep the temperature under that. This has been true for every phone I have worked with in the past and some are even worse at this.
Personally, I find that having a high (>45C) surface temperature is not a huge problem (You can decide that for yourself. if it is a problem for you, this won't help you. You can't change the power efficiency limit of the processor). In my use case, when I have a lot of applications open, especially Firefox in desktop mode, or 4-way Android M multitasking or something like that (or just typing to a lot of people in Facebook Messenger or something similar). I kinda use the thing like a computer so obviously it has extended periods of high CPU workload and the device starts to throttle back to something like 1344 or 960MHz or even lower.
Given this, what I want to do is change the CPU throttle temperature to a higher one. Generally, we don't need to worry about protecting the processor hardware because it has built in thermal shutdown/reset functions should something go wrong. It's at something like 110C, which sounds high, but as someone who uses a MacBook Pro, it is normal to see the CPU temperature that high! Intel generally throttles at a much higher temperature because they don't care about the actual temp of the heat sink, only that of the processor die.
In the past kernel I tried, there was an option to set up the thermal throttling temperature (God's Kernel). However, I switched to the AK kernel recently, due to its High Performance Audio feature. This kernel did not include support for this configuration.
I am running MH19Q Marshmallow stock.
I used File Explorer with root access to go to system/etc I think and there is a file called thermal_engine.conf or similar. If you edit it, you see there are a lot of values. Actually basically if you look around, there are a lot of temperature values in there seperated by the things they control. I would like to explain more, but I think it is better if you can open up your file and my file side by side and see for yourself what's different. The gist is that there's a table of values and a bunch of actions to take when they're hit, and of course, there are release temperatures, which are basically the lower hysterisis limit I think. The temperature values look like 44000 or 43000 by default, which means 44C and 33C (celcius)and I changed mine to 97000 (97 C)
Here you can find the content of the file. Type in the pastebin website, then put slash QYhi05rE.
I didnt keep my old file.... sorry about that... Perhaps someone can post it if they have it.
With stuff set to 97 C, the device heats up a lot more, obviously, but it's manageable. If you have something like Cinema 4K open for a long time, of course it will get to like 50C on the surface (That is quite unconfortable to put your hand on, but I'm okay with it). Hangouts video calling seems to be the worst and sometimes the battery will get higher than 50C and then stop charging. Given the design of the phone, by the time the battery gets too hot to be safe, the system will probably shutdown or restart, and you'll notice it LONG before anything becomes a problem.
Thanks for looking!
***Do this at your own risk, as with all root mods and tricks. Obviously this has the risk of breaking things or causing hardware to fail. High temperatures on BGA soldered chips have been observed to increase the failure rates, even in stuff like routers and TVs and other stuff that you don't generally think of as having thermal issues. My last phone (Note 5) kinda broke after a little while, although I'm not sure if me doing this caused it. (Appears to be display panel issue, but have not tested). All I know is that earlier that day I was outside filming on it and processing video, and that the area above the SoC got rather warm to the touch. Which should be read as "painfully hot" to most.
Click to expand...
Click to collapse
Not new.
This has been around and discussed for a while.
I have been running a modified thermal-engine.conf since day one.
First things first, I understand the dangers of this, and that I could fry my device. I'm just looking for answers, not lectures.
I'm wondering how to go about disabling (or at least fixing) the thermal throttle on my device. I'm not sure how other people's HAM2's act in regards to this, but mine seems hyper-sensitive. It's near-impossible to use in the summer, even in the shade. It's warm to the touch, yes, but hardly hot enough to make everything freeze and lag like crazy.
It's running PAC on build 11.27.15 (5.1). It was running beautifully in the winter, but it's becoming a bear to deal with now. Is there a way to either disable it or set the trigger temperature higher (preferred)? I can monitor it if it's disabled, but I would prefer to simply set it higher if that's an option (or at least, to not allow it to throttle as severely). I'd appreciate some help with this.
So, now your phone is ok when idle(ex when screen off)? I am suspecting you have some 'bad' backgroud keep cpu usage high. Check software first before think about adjust throttle.
Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag.
It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge.
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified.
I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery.
Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion.
I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed.
Infy_AsiX said:
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
Click to expand...
Click to collapse
I read half of that to be honest, but just one thing: To make things harder, ZTE added added a write protection on the system. To disable it you have to use a computer and connect your phone with ADB, then issue "adb reboot disemmcwp" (like DISable EMMC Write Protection). Otherwise all the changes that you made get undone after a reboot, and obviously you'd have to reboot after modifying that file
On LOS you can use BeastMode (even if your phone isn't an A2017U) which for me is the best friggin kernel I've used in performance terms. There you can change thermal limits
Infy_AsiX said:
Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag.
It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge.
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified.
I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery.
Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion.
I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed.
Click to expand...
Click to collapse
I have noticed the same performance many months ago.
I tried changing the thermal values with both ways through the conf file or a custom kernel but all implementations seem to be faulty as nothing changed.
In the end I gave up because I couldn't find a solution for this.
But I figured because my games clash of clans, ppsspp, gba emulators don't lag I din't care much.
If you find a solution let me/us know.
Or post the modded confs you're using as well if you can.
That's all from me.
I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on.
The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout.
The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress.
edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod.
Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said:
I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on.
The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout.
The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress.
edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod.
Click to expand...
Click to collapse
That's weird... what are the ambient temps where you live? Here it's anything between 20 and 30 degrees and mine never gets that hot, and it barely throttles. Of course you shouldn't game while charging, that WILL throttle the phone.
I have a big old CPU heatsink without a fan, and when I charge the phone at night I just put it upon the heatsink. It keeps the battery around the ambient temp, which I guess helps with battery degradation.
A nice app for monitoring the CPU is Trepn profiler, you can program it to show you anything like frequencies and temps on 2 separate graphs for example
Is there any IMG file to Overclock the display to 75hz for RN9 Pro
it's simply not possible because the screen on this phone only supports 60Hz, you can't make it any higher
@akramhadji how do you know ?
can you overclock your pc monitor from 60 Hz to 120 Hz? no
same thing with phones, it's a hardware limitation, you can't improve it by flashing a file.
@akramhadji , please don't give input on things you clearly have no idea on , you create noise for those searching for information .maybe it makes u feel good to have thanks ,but try to curb it aite .
demonfruzz said:
@akramhadji , please don't give input on things you clearly have no idea on , you create noise for those searching for information .maybe it makes u feel good to have thanks ,but try to curb it aite .
Click to expand...
Click to collapse
it seems that you're the one who has no idea what he's talking about :/ there's no such thing as display overclocking on phones...
You cant overclock displays, you can however fool it into thinking its running at a higher rate. But it wont change anything other than displaying a higher number in test apps.
Many displays can actually be overclocked and run fine at actual higher refresh rate depending on manufacturer and hardware. That overclocking also has its limitations. Some 60hz panels run fine at 75 or maybe 80+ hz, some causes pixel skipping if overclocked and some simply don't go past 60-65hz.. Same limitations exists on phones, their display is underclocked so hardware don't go on full load and damage anything. Similar reason why note 9 pro comes with 33w charger but actually supports 30w
@akramhadji ignorance and arrogance ,keep it up .many of your kind in this world ,I won't waste anymore time .beyond savable
well, if we look at other phones :
the realme 6 : 6.6 inch 20:9, 2400 x 1080 pixel 399 PPI, capacitive, IPS, Corning Gorilla Glass 5, glossy: yes, 90 Hz
the redmi 9 : 6.67 inch 20:9, 2400 x 1080 pixel 395 PPI, capacitive, IPS, Corning Gorilla Glass 5, FHD+, glossy: yes, 60 Hz
so they changed the display, might point out to the redmi display choice being only 60hz capable.
What happens if you increase display refresh rate, well you have increase GPU usage, and depending on the type of connection between the SOC and the LCD you can have increase compression in the bus. So its a trade, do you want that?
demonfruzz said:
@akramhadji ignorance and arrogance ,keep it up .many of your kind in this world ,I won't waste anymore time .beyond savable
Click to expand...
Click to collapse
I don't see how I was being ignorant or arrogant :/ I responded very respectfully...
anyways, I do not believe there is a way to overclock a phone display without causing damage to it
akramhadji said:
I don't see how I was being ignorant or arrogant :/ I responded very respectfully...
anyways, I do not believe there is a way to overclock a phone display without causing damage to it
Click to expand...
Click to collapse
Sorry sir but there is, I've done it to many of my phones. My last phone, mi a2 was overclocked to 63 or 65 hz, im not 100% sure.
akramhadji said:
can you overclock your pc monitor from 60 Hz to 120 Hz? no
same thing with phones, it's a hardware limitation, you can't improve it by flashing a file.
Click to expand...
Click to collapse
5 seconds of Google searches will give you thousands of results that says otherwise... Display overclocking is a real thing and done by many, why spread misinformation?
https://www.google.com.au/search?q=display overclocking
akramhadji said:
it seems that you're the one who has no idea what he's talking about :/ there's no such thing as display overclocking on phones...
Click to expand...
Click to collapse
Weird how I could overclock the display on my old phone then, huh?
https://forum.xda-developers.com/xz...nel-screen-frame-rate-lineageos-15-1-t3930057
https://forum.xda-developers.com/xz-premium/development/rom-zfsodp-july-t3946205
ares93 said:
You cant overclock displays, you can however fool it into thinking its running at a higher rate. But it wont change anything other than displaying a higher number in test apps.
Click to expand...
Click to collapse
Again, this is false. You can overclock displays, I've done it many times.
yes we can overlock display i have redmi 7 and my refresh rate is 75hz ,
razerphynx said:
5 seconds of Google searches will give you thousands of results that says otherwise... Display overclocking is a real thing and done by many, why spread misinformation?
https://www.google.com.au/search?q=display overclocking
Weird how I could overclock the display on my old phone then, huh?
https://forum.xda-developers.com/xz...nel-screen-frame-rate-lineageos-15-1-t3930057
https://forum.xda-developers.com/xz-premium/development/rom-zfsodp-july-t3946205
Again, this is false. You can overclock displays, I've done it many times.
Click to expand...
Click to collapse
yes we can
@akramhadji & @ares93
Sorry but you guys have no clue! Just overclocked my Notebook Display from 60 to 100 hz on an old MSI GT60 from 2012.. Why shouldn't this work on Android too?
Double Post..
akramhadji said:
can you overclock your pc monitor from 60 Hz to 120 Hz? no
same thing with phones, it's a hardware limitation, you can't improve it by flashing a file.
Click to expand...
Click to collapse
Bro we can overclock our monitor
Since no one bothered to come to my thread, I'll just say it here, the Redmi Note 9 Pro 5G has the same display as the phone we are talking about here but it has 120hz. Oh wait, MI 10T Lite and Poco X3 also have the same display that support higher refresh rate, so it is definitely software capped. (Can't verify part numbers rn tho) and PC monitors can be overclocked anyone who says otherwise definitely doesn't know what they are talking about
.