Related
For a lot of phones, auto-brightness can maximally output a higher brightness than the 100% brightness setting available to the user. Auto-brightness can sometimes output 600 nits vs. only 400 nits at 100% manual brightness.
I know this is the case for some phones (samsung Galaxy S5 for sure), but is LG G2 one of them? If so, is it possible to mod the LG G2 so that manual brightness does output the true maximum amount at 100%?
It could be risky and cause overheating, although the G2 already limits the maximum manual brightness when it overheats.
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.
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
For you gamers out there
Finally I solved the thermal throttling problem in this lovely device.
BEWARE **YOUR PHONE WILL HEAT MORE**
first using your root explorer go to system/etc, you will find 3 files related to thermal throttling:
1. thermal-engine-8996-normal.conf
2. thermal-engine-8996-perf.conf
3. thermal-engine.conf
These files related to the configuration in the settings->power manager->power plan.
If you chose performance then your phone will use the perf.conf
If you chose Smart power-save your phone will use normal.conf
Edit:
After further investigation it seems that no matter what setting I choose the file that is active always the normal.conf.
perf.conf seems not affecting anything at all. Needs futher investigation.
That is the mechanic, now for the fun part:
Open the file you wish to edit using text editor.
The key is in these two sections
Code:
[SKIN_CPU_MONITOR]
#algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 59000 62000
thresholds_clr 56000 60000
actions cluster0+cluster1 cluster0+cluster1
action_info 1400000+1700000 1500000+1824000
override 5000
[SKIN_GPU_MONITOR]
#algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 41000 42000
thresholds_clr 39000 40000
actions gpu gpu
action_info 510000000 401800000
override 5000
As you can see the values above are a little bit different from yours, it's because I already change a bit.
The parts you should take consideration are thresholds, thresholds_clr, actions, and action_info.
Thresholds means in what temperature the device should throttle
Thresholds_clr means in what temperature the device will stop throttling
Actions mean which item to be throttled
Cluster0 = Little CPU
Cluster1 = Big CPU
GPU = GPU
so for example above
thresholds 59000
thresholds_clr 56000
actions cluster0+cluster1
action_info 1400000+1700000
Means it will start throttling at 59 celcius and stop throttling at56 celcius, the item to be throttled are little CPU which become 1400 mhz and big CPU which become 1700 mhz
You can add many parameters just by using spaces like example above.
Okay, hope it helps. If you confuse, just use my values above and unleash the 60fps beast. Muahahaha
Edit:
This is my current setting
Code:
[SKIN_CPU_MONITOR]
#algo_type monitor
sampling 1000
sensor tsens_tz_sensor11
thresholds 48000 50000
thresholds_clr 45000 49000
actions cluster0+cluster1 cluster0+cluster1
action_info 1500000+1824000 1400000+1700000
override 5000
Instead of emmc thermostat I use tsens_tz_sensor11 which is the temperature of the CPU core itself, I think it is better
Finally someone make magisk module for this (thanks nfsmw_gr), not yet tried it myself though
https://forum.xda-developers.com/showpost.php?p=76793058&postcount=14
I've already moved on to stock b01 oreo rom, now it is located in /system/vendor/etc/thermal-engine.conf
Here is my current config
Code:
[SKIN_CHG_LIMIT]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 39000 41000
thresholds_clr 38000 40000
actions battery battery
action_info 1 2
[SKIN_CPU_MONITOR_NORMAL]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 36000 39000 42000
thresholds_clr 35000 38000 41000
actions cluster0+cluster1 cluster0+cluster1 cluster0+cluster1
action_info 1500000+1824000 1400000+1700000 1300000+1438000
override 5000
[SKIN_GPU_MONITOR_NORMAL]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 41000 42000
thresholds_clr 39000 40000
actions gpu gpu
action_info 510000000 401800000
override 5000
Thank you so much.
Is this valid for destroying the phone without voiding the warranty?
aLexzkter said:
Is this valid for destroying the phone without voiding the warranty?
Click to expand...
Click to collapse
Lol, I'm pretty sure there's a failsafe for temps
You'd probably want to also undervolt if you are removing thermal throttling to give yourself a little more headroom. Hellsgate kernel supports undervolting
Been doing similar for months and mentioned about it a few times in various places.
I don't think using the CPU temperature sensor is suitable for throttling as it peaks largely and fluctuates rapidly with corresponding load. The reason emmc_therm (quiet_therm in AOSP ROMs) is probably used for a suitable consistent reading. The related default temperature throttles need to be adjusted to reflect the changed sensor and it's nature. What will happen on your config is sudden throttling on CPU load that will unthrottle rapidly when load is decreased but the battery/device isn't likely any cooler.
Btw on AOSP I can't get any changes to stay after rebooting with disemmcwp system writable too. I'm guessing the kernel or something regenerates the defined values at startup. I found having the file modified through a Magisk module works however.
Sent from my Xperia Z3C using XDA Labs
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
dalebaxter01 said:
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
Click to expand...
Click to collapse
I would like this as well if it's not much hassle.
dalebaxter01 said:
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
Click to expand...
Click to collapse
put your changed file into this template https://forum.xda-developers.com/mi-5/how-to/how-to-disable-thermal-throttling-t3636574
Infy_AsiX said:
Been doing similar for months and mentioned about it a few times in various places.
I don't think using the CPU temperature sensor is suitable for throttling as it peaks largely and fluctuates rapidly with corresponding load. The reason emmc_therm (quiet_therm in AOSP ROMs) is probably used for a suitable consistent reading. The related default temperature throttles need to be adjusted to reflect the changed sensor and it's nature. What will happen on your config is sudden throttling on CPU load that will unthrottle rapidly when load is decreased but the battery/device isn't likely any cooler.
Btw on AOSP I can't get any changes to stay after rebooting with disemmcwp system writable too. I'm guessing the kernel or something regenerates the defined values at startup. I found having the file modified through a Magisk module works however.
Sent from my Xperia Z3C using XDA Labs
Click to expand...
Click to collapse
Yeah, this is also what I found. At first I just looked at which temp is the highest and use that sensor for the trigger. But then when I use cpu-z to observe the reading, I found that emmc_therm is the most consistent and not fluctuate drastically so much. Therefore I'm back using emmc_therm right now
Seeing this thread gives me flashback in the Android M days where a xposed module was needed to disable a system task killer that would kill my games if they used too much battery once I turn off screen _-_
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
otaconremo said:
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
Click to expand...
Click to collapse
You should always keep your eyes on the temp. My rule of thumb is under 55 degree is ok, above that is no no. If your games always reach above 55 then you should re-tweak your thermal config.
Use dev check pro to observe the temp, though it doesn't have widget for emmc_therm only the cpu therm, you can still see what's going on under the screen
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
otaconremo said:
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
Click to expand...
Click to collapse
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
iyancoolbgt said:
You should always keep your eyes on the temp. My rule of thumb is under 55 degree is ok, above that is no no. If your games always reach above 55 then you should re-tweak your thermal config.
Use dev check pro to observe the temp, though it doesn't have widget for emmc_therm only the cpu therm, you can still see what's going on under the screen
Click to expand...
Click to collapse
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
nfsmw_gr said:
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
Click to expand...
Click to collapse
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
Mind sharing your own config?
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
I believe my battery is too degraded already. That only happens when my batt is below 20% and I was still gaming. That's why I'm very careful already when I'm getting lowbat. Btw, I'm using stock chinese mf5 version. The overheating message is from the Mi-Assistant app (Power Manager).
nfsmw_gr said:
Mind sharing your own config?
Click to expand...
Click to collapse
I did awhile back but I guess it's a little scattered across posts. I was about to edit in another paragraph with more info but I'll put it here now instead. I'll consider cleaning up the new stuff to share, performance profiles is just a varied collection of performance levels.
I've setup various CPU GPU performance profiles to switch between using Tasker. From testing, the highest I'd go without a fan is 1600/1800 big and 1300 small. With a constant load at these frequencies the battery will still hit up to around 50degC, matching the much higher perf allowed with a fan.
Here's a tidbit to get y'all thinking about environmental impact on heat. Stock Daydream sets a Sustainable Performance mode that uses all cores at 1200MHz. In the Daydream Headset V1, the back of the phone actually has an air gap behind it because of raised nubs inside the headset. Yet with all this the battery can rather easily heat to over 55degC after a few dozen minutes. The headset v2 has a built in heatsink, with minor improvement apparently. Also on an off-topic note, that Sustained Performance mode gets stuck to on after using Daydream on stock N. Things no one notices unless you actually monitor
---------- Post added at 10:12 PM ---------- Previous post was at 10:09 PM ----------
otaconremo said:
I believe my battery is too degraded already. That only happens when my batt is below 20% and I was still gaming. That's why I'm very careful already when I'm getting lowbat. Btw, I'm using stock chinese mf5 version. The overheating message is from the Mi-Assistant app (Power Manager).
Click to expand...
Click to collapse
Yeah sounds like my guess about an undervolted degraded battery. Oh I had that frozen so never got that alert. I'd assume it occurs when battery is 55degC or so, that's when Daydream alerts too for example.
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
Maybe I'm just too cautious But still, too much heat makes my hands really not comfortable.
I know we can customize which temperature to show, but no emmc_therm unfortunately. Reading your comment make me thinking, if the real concern is the battery temp, then why not using it as the trigger for the thermal config? It is listed as 'battery' in cpu-z list of thermal sensors. It means that we can use it right?
nfsmw_gr said:
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
Click to expand...
Click to collapse
Thanks, that's so cool. I'll put it on the first post
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