Many reviewers say that they can't get the 1200 nits advertised brightness. I'm fairly certain that the note 8's display is limited by power consumption limits for whatever reason. However if you use any app that supports the video enhancer the display looks to me to be 2x the brightness. I assume samsung did this to increase the battery life. I want to know if there is a way to always run the screen in its maximum brightness mode? Maybe we could develop an app that always runs the display in its maximum brightness.
I would like to force the phone to use video enhancer in all apps including the full ui.the demo units in the store are somehow overiding the screen max brightness and they stay on the full 1200 nits the entire time.ive comapred retail note 8s with auto brighness turned off and set to optimised and the brightness on full.the demo units are brighter on max brightness than retail units.its like the demo units are somehow forcing the screens to full brightness potential but all the time and thatswithout auto turned on.and to get that type of brightness on the retail units you can use video enhance but that only works for yt and another app i cant remeber.
But the demo note 8 phones are brighter than retail handsets on full brighness
I think this would be bad for the screen with time, not to speak about batt wear
So I've read that when set to 120Hz refresh rate, it's variable and will adjust depending on content. Does this mean when playing a game that's locked to 60FPS, the display will be 60Hz and battery life will be the same as setting to 60Hz?
How about if the display is set to 60Hz, but the Cortex app has the game set to 120FPS. Will the display switch to 120Hz assuming the game is actually running at 120FPS?
I like the smoothness of the 120Hz in general, so that's how I have it set. But what if I plan to watch a movie, should I set it to 60Hz to save battery, or will the display do it automatically? No sense to have it at 120Hz if I'm going to watch a movie for 2 hours.
Can i change my s10 to 120 hz refresh rate using one ui 2.5
I don't think so, the S10 has a 60hz hardware refresh rate screen, you can't do a software update and make a 60hz validated screen work on 120hz without issues.
It's not possible as stated many times before due to hardware limitations.
Here is a test I did on my S21 Ultra (Exynos), that started a bit spontaneously with me wondering about the impact on battery of different refresh rates and resolutions, together with use cases (touching the screen or just looking at it). So I started playing around and landed in some kind of improvised test.
The phone is an S21 Ultra Exynos model, as already mentioned. The model number is SM-G998B/DS. The FW was G998BXXU2AUBB.
The test was performed at 20% screen brightness and 30% battery left on the phone. The phone was charged between tests to hover around 30% battery, +/- 2%, i.e. it was between 28% and 32% during the tests.
There were two types of tests; "Screen Interaction Test" that intended to find the current consumption while repeatedly touching the screen and therefore keeping the CPU ready, and an "Idle Current Consumption Test" where the screen was just turned on for 3 minutes without interacting with the phone. In both tests, the phone was running the app Ampere in the foreground, thus displaying it.
The data logging was done manually by me watching the app Ampere and noting down its shown current consumption every second into a Google Sheets document. Ampere collects 50 data points, discards the 10 lowest and 10 highest, then takes the average of the remaining 30 points before presenting the current consumption. These values were gathered for 5 minutes in the interaction test, and 3 minutes in the idle test, in order to acquire a robust sample set that was resilient against temporary peaks in current consumption. Since I don't have control over the phone's background processes, it was possible that a background task would cause a sudden peak in current consumption. Averaging these values makes the measurement more resilient against such peaks.
The phone was put in Airplane Mode in order to eliminate Wifi, 4G, Bluetooth and all those things from the measurement.
Test ResultsInteracting With Screen in 120 Hz Adaptive Refresh Rate and Different ResolutionsThe screen was tapped 3-4 times per second in order to keep it active. The phone was displaying the app Ampere. Test duration was 5 minutes and data was logged about every second from Ampere, and then averaged over the entire test duration.
HD 120 Hz Adaptive Refresh Rate: 204 mA
FHD 120 Hz Adaptive Refresh Rate: 184 mA
WQHD 120 Hz Adaptive Refresh Rate: 206 mA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interacting With Screen in 60 Hz Adaptive Refresh Rate and Different ResolutionsThe screen was tapped 3-4 times per second in order to keep it active. The phone was displaying the app Ampere. Test duration was 5 minutes and data was logged about every second from Ampere, and then averaged over the entire test duration.
HD 60 Hz Standard Refresh Rate: 175 mA
FHD 60 Hz Standard Refresh Rate: 161 mA
WQHD 60 Hz Standard Refresh Rate: 176 mA
Idling With Screen On in 60 Hz Standard Refresh Rate and Different ResolutionsThe screen was turned on it displayed the app Ampere. The screen was not interacted with at all for the whole 3 minutes this test took. The test was only done for 60 Hz because there is no point in doing it for 120 Hz since the screen drops down to 60 Hz when idling in the app Ampere. The values are the average value of the entire test duration (3 minutes).
HD 60 Hz Standard Refresh Rate, Screen Idling: 144 mA
FHD 60 Hz Standard Refresh Rate, Screen Idling: 145 mA
WQHD 60 Hz Standard Refresh Rate, Screen Idling: 147 mA
Bonus Test: 48 Hz and 96 Hz Display ModeThe two hidden display modes were also tested but there were no advantages in using these modes regarding current draw. Plus, these modes actually tint the display slightly greenish in my opinion and in my phone. YMMV.
TLDR/ConclusionThe most efficient resolution is FHD when the phone is actively used. However, while not interacting with the screen, the resolution has almost no impact on battery consumption. Note: the resolution probably affects a lot when gaming is involved, which I have not tested. Between 120 Hz Adaptive and 60 Hz Standard, the current draw is about 15% to 17% higher for 120 Hz Adaptive Mode, depending on resolution. In other words, running the phone at 120 Hz does not exactly eat up the battery, which is very good to see!
A quick word about the current draw numbers: the current draw will be lower when the battery is charged more, since the battery voltage will be higher in that case. The lower the voltage, the greater current draw to keep power constant. At full charge, these numbers would be 88% of the ones I had at 30% battery charge. This should not change the relative numbers, i.e. FHD 120 Hz Adaptive Mode should still draw about 15% more current than FHD 60 Hz Standard Mode, I think.
What combo of settings do you recommend
The differences are quite small. Interesting.
10 or 15 ma extra is next to nothing.
da1e8 said:
What combo of settings do you recommend
Click to expand...
Click to collapse
I personally use 120 Hz Adaptive in FHD resolution. The display smoothness is too good to give up for a little bit of extra battery saving. With that said, I do use Power Saving Mode if I have to save battery during the day and that puts the phone in 60 Hz Standard refresh rate. I used to also switch to HD resolution in that case, but I will not do that any longer since FHD draws less current for some reason.
So my advice would be to stick to FHD resolution (I don't notice any difference between FHD and WQHD anyway) and 120 Hz Adaptive.
Curious to ask, is this an Exynos model or a Snapdragon model? Firmware version number?
zjhao said:
Curious to ask, is this an Exynos model or a Snapdragon model? Firmware version number?
Click to expand...
Click to collapse
Hey, good question! My bad, I should have written this down from the start, since it's quite relevant. I updated the original post.
The phone is an S21 Ultra Exynos model. The model number is SM-G998B/DS. The FW was G998BXXU2AUBB.
blackhawk said:
The differences are quite small. Interesting.
10 or 15 ma extra is next to nothing.
Click to expand...
Click to collapse
Isn't this for a test duration of 5mins. Please correct me if I'm wrong: if I take this calculation ahead..and assume that the test was carried out for a long period of time at 100% battery charge, then at 120Hz and FHD resolution - we should get a bit over 27hrs (5000mah/ 184ma) of SOT and WQHD resolution+120hz, it would be a bit over 24 hrs. In all, ceteris paribus, the difference is between 3 and 3.5 hours in all!
meh!
amirage said:
Isn't this for a test duration of 5mins. Please correct me if I'm wrong: if I take this calculation ahead..and assume that the test was carried out for a long period of time at 100% battery charge, then at 120Hz and FHD resolution - we should get a bit over 27hrs (5000mah/ 184ma) of SOT and WQHD resolution+120hz, it would be a bit over 24 hrs. In all, ceteris paribus, the difference is between 3 and 3.5 hours in all!
meh!
Click to expand...
Click to collapse
With a idle ma draw of 150-300 ma probably being typical, an extra 15-18 ma max for the screen resolution/refresh rate is chump change.
The lame Android scoped storage is likely using much more... and giving you nothing but trouble.
Scoped storage, it tastes like Apple
very helpful to me
blackhawk said:
With a idle ma draw of 150-300 ma probably being typical, an extra 15-18 ma max for the screen resolution/refresh rate is chump change.
The lame Android scoped storage is likely using much more... and giving you nothing but trouble.
Scoped storage, it tastes like Apple
Click to expand...
Click to collapse
My friend, you just went Christopher Nolan on me...didnt understand a word about the storage thingies.
amirage said:
My friend, you just went Christopher Nolan on me...didnt understand a word about the storage thingies.
Click to expand...
Click to collapse
Look it up and weep... it's one of the biggest reasons I'm still running on Pie, as are many others. Q's adaption rate has been dismal.
No coincidence.
PirateYarr said:
Here is a test I did on my S21 Ultra (Exynos), that started a bit spontaneously with me wondering about the impact on battery of different refresh rates and resolutions, together with use cases (touching the screen or just looking at it). So I started playing around and landed in some kind of improvised test.
The phone is an S21 Ultra Exynos model, as already mentioned. The model number is SM-G998B/DS. The FW was G998BXXU2AUBB.
The test was performed at 20% screen brightness and 30% battery left on the phone. The phone was charged between tests to hover around 30% battery, +/- 2%, i.e. it was between 28% and 32% during the tests.
There were two types of tests; "Screen Interaction Test" that intended to find the current consumption while repeatedly touching the screen and therefore keeping the CPU ready, and an "Idle Current Consumption Test" where the screen was just turned on for 3 minutes without interacting with the phone. In both tests, the phone was running the app Ampere in the foreground, thus displaying it.
The data logging was done manually by me watching the app Ampere and noting down its shown current consumption every second into a Google Sheets document. Ampere collects 50 data points, discards the 10 lowest and 10 highest, then takes the average of the remaining 30 points before presenting the current consumption. These values were gathered for 5 minutes in the interaction test, and 3 minutes in the idle test, in order to acquire a robust sample set that was resilient against temporary peaks in current consumption. Since I don't have control over the phone's background processes, it was possible that a background task would cause a sudden peak in current consumption. Averaging these values makes the measurement more resilient against such peaks.
The phone was put in Airplane Mode in order to eliminate Wifi, 4G, Bluetooth and all those things from the measurement.
Test ResultsInteracting With Screen in 120 Hz Adaptive Refresh Rate and Different ResolutionsThe screen was tapped 3-4 times per second in order to keep it active. The phone was displaying the app Ampere. Test duration was 5 minutes and data was logged about every second from Ampere, and then averaged over the entire test duration.
HD 120 Hz Adaptive Refresh Rate: 204 mA
FHD 120 Hz Adaptive Refresh Rate: 184 mA
WQHD 120 Hz Adaptive Refresh Rate: 206 mA
View attachment 5255207
Interacting With Screen in 60 Hz Adaptive Refresh Rate and Different ResolutionsThe screen was tapped 3-4 times per second in order to keep it active. The phone was displaying the app Ampere. Test duration was 5 minutes and data was logged about every second from Ampere, and then averaged over the entire test duration.
HD 60 Hz Standard Refresh Rate: 175 mA
FHD 60 Hz Standard Refresh Rate: 161 mA
WQHD 60 Hz Standard Refresh Rate: 176 mA
View attachment 5255211
Idling With Screen On in 60 Hz Standard Refresh Rate and Different ResolutionsThe screen was turned on it displayed the app Ampere. The screen was not interacted with at all for the whole 3 minutes this test took. The test was only done for 60 Hz because there is no point in doing it for 120 Hz since the screen drops down to 60 Hz when idling in the app Ampere. The values are the average value of the entire test duration (3 minutes).
HD 60 Hz Standard Refresh Rate, Screen Idling: 144 mA
FHD 60 Hz Standard Refresh Rate, Screen Idling: 145 mA
WQHD 60 Hz Standard Refresh Rate, Screen Idling: 147 mA
View attachment 5255213
Bonus Test: 48 Hz and 96 Hz Display ModeThe two hidden display modes were also tested but there were no advantages in using these modes regarding current draw. Plus, these modes actually tint the display slightly greenish in my opinion and in my phone. YMMV.
TLDR/ConclusionThe most efficient resolution is FHD when the phone is actively used. However, while not interacting with the screen, the resolution has almost no impact on battery consumption. Note: the resolution probably affects a lot when gaming is involved, which I have not tested. Between 120 Hz Adaptive and 60 Hz Standard, the current draw is about 15% to 17% higher for 120 Hz Adaptive Mode, depending on resolution. In other words, running the phone at 120 Hz does not exactly eat up the battery, which is very good to see!
A quick word about the current draw numbers: the current draw will be lower when the battery is charged more, since the battery voltage will be higher in that case. The lower the voltage, the greater current draw to keep power constant. At full charge, these numbers would be 88% of the ones I had at 30% battery charge. This should not change the relative numbers, i.e. FHD 120 Hz Adaptive Mode should still draw about 15% more current than FHD 60 Hz Standard Mode, I think.
Click to expand...
Click to collapse
Beautiful test. Well done and thanks.
I don't even own this phone, but this is a very useful test for other also! Kudos
Experiment well done bro! This community needs more people like you.
Hi! I am on xiaomi.eu miui 12.5.9. Is there any way possible to set the refresh rate to 60hz when it idles for a moment?
Some custom rom has this feature (e.g. project elixir, aex etc) where you can set the minimum refresh rate is 60hz and maximum at 120hz, when the phone idles the display automatically drops down to 60hz. It is a great battery-saving feature, so I was wondering is there any way to do this in MIUI?
a safe haven said:
Hi! I am on xiaomi.eu miui 12.5.9. Is there any way possible to set the refresh rate to 60hz when it idles for a moment?
Some custom rom has this feature (e.g. project elixir, aex etc) where you can set the minimum refresh rate is 60hz and maximum at 120hz, when the phone idles the display automatically drops down to 60hz. It is a great battery-saving feature, so I was wondering is there any way to do this in MIUI?
Click to expand...
Click to collapse
I thought the refresh rate already dynamic? Try set it to 120hz and turn on refresh rate from developer option... You will find the display rate fluctuate between 30,60,120...
Nazri786 said:
I thought the refresh rate already dynamic? Try set it to 120hz and turn on refresh rate from developer option... You will find the display rate fluctuate between 30,60,120...
Click to expand...
Click to collapse
Nope it doesnt, it always stays at 120hz.
a safe haven said:
Nope it doesnt, it always stays at 120hz.
Click to expand...
Click to collapse
Sorry, unaware this is redmi note 10 forum... On poco x3 it had that dynamic refresh rate..
a safe haven said:
Nope it doesnt, it always stays at 120hz.
Click to expand...
Click to collapse
It must show other options as well.
does realme gt master edition support dynamic refresh rate? can we get that feature via an ota update?
Hello, from my experience using custom ROM, Redmi Note 10 pro screen doesn't fancy enough for using variable refresh rate. When setting to 60 Hz - 120 Hz, The display always stay in 120 Hz if it register touch not depends the content we see like other phone. And drop to 60 Hz in +/- 1 seconds after last touch input