Refresh rate stuck at 60hz - Xiaomi Poco X3 NFC Questions & Answers

I have just realised that my device, which I have only had for 2 days, is stuck on 60hz refresh rate and I can't manually change it back to 120hz in display settings. When I press on it in display settings it just doesn't do anything - ie it doesn't open the screen with the bouncing balls and the 2 options. Does anyone know how to fix this? It definitely worked before but I got a MIUI update yesterday and I wonder if that has broken it. According to my settings I am running Global 12.0.2 Stable.

Related

OnePlus 8 Screen flicker

Is anybody else facing this problem?
Here is the link - https://imgur.com/gallery/nuchOmQ
Have you got the brightness set to automatic? I've seen that behaviour when I have it set but not when I don't.
Alan
alan sh said:
Have you got the brightness set to automatic? I've seen that behaviour when I have it set but not when I don't.
Alan
Click to expand...
Click to collapse
It's not set on automatic
Noticed this when I first got the phone. It went away after a couple of system updates.
I guess it's about the refresh rate, i switched it to 60Hz and the flickering problem went away.
I noticed something similar on the latest open beta even though all the auto adjustment toggles have been switched off.
I fixed mine I guess. Flashed android 10 oos on both slots and used evira kernel. Dunno which one fixed it but so far no flickering or no changing of screen tone/colors.
It's the switch in refresh rate i think, I've been having it on Oxygen 10, don't think I've noticed it on Oxygen 11 beta
Perhaps yeah. but on OB1/a11 it's more noticeable for me so I switched back to the lastest OOS stable(a10) on both slots and running a custom kernel. No issues till now running 90hz.
I just put on the stable 21 and still getting it from time to time. Feels like it's more noticeable yellow tinge than before.

Touch lag issue when using Adaptive smooothness

I got my Note 20 Ultra back on November and encountered an annoying issue when Adaptive refresh rate is turned on and watching YouTube videos. When YouTube first starts the display will run at 120hz, but after a few seconds it will drop to 60hz. When the refresh rate drops, the first touch of the screen is interpreted as a touch and hold instead of a single press. The display will then jump back to 120hz, but the display still thinks I'm pressing and holding the screen when I've already let go. If I then touch the screen again while in 120hz the phone thinks I've done a double tap (presumable completing the first tap and then immediately registering the second tap), which causes the video to seek forward or backward, depending on where I pressed on the screen the second time. If I tap the screen the one time but allow the screen to drop back to 60hz after it jumps to 120hz from the first tap, then the first tap seems to be ignored as my second tap acts like a tap and hold again.
What's interesting is that as long as the display stays at 120hz, all taps after the scenario above work fine. A single tap will open the playback overlay (pause/play button, seek arrows, etc) like it's supposed to, but once I leave the display alone and it drops to 60hz this whole problem starts all over again. Since adaptive refresh is tied to the brightness sensor, this problem does not present itself in a dark room since the display stays at 120hz in a dark room. Also, if I turn off adaptive refresh rate and have the display stay at 60hz all the time then the problem is not present either. I also will occasionally get non responsiveness on Brave Browser but I can't say for sure if they are related.
This has frustrated me so much I did a factory reset and interestingly the issue did not re-appear at first with a fully updated YouTube. Once I updated/installed other apps (including Galaxy store apps) the problem returned. I don't have display overlay apps installed, so I suspect it's a Galaxy store app but I can't pinpoint which one. I don't believe this is a hardware issue, so I'm curious if anyone on the thread has had a similar issue. I'd like to report this to Samsung but I have no idea where to even report this.
Sounds like you've figured it's a software program. You should update one at a time and see if you can pinpoint the issue. Try to not to install 3rd party software until all you need to update gets updated and phone is working fine.
Or
I would say try using a package disabler and try disabling the apps you suspect to see if any improvements. It might not be a Samsung app as others would be facing the same issue you're having.
As always don't restore settings/app data from backup etc other than media, messages, logs.
I'm using adaptive and everything is working fine on my end. Snapdragon variant here. Albeit I keep a number of Samsung apps disabled as i don't use or need them running in background for no reason.
lennie said:
Sounds like you've figured it's a software program. You should update one at a time and see if you can pinpoint the issue. Try to not to install 3rd party software until all you need to update gets updated and phone is working fine.
Or
I would say try using a package disabler and try disabling the apps you suspect to see if any improvements. It might not be a Samsung app as others would be facing the same issue you're having.
As always don't restore settings/app data from backup etc other than media, messages, logs.
I'm using adaptive and everything is working fine on my end. Snapdragon variant here. Albeit I keep a number of Samsung apps disabled as i don't use or need them running in background for no reason.
Click to expand...
Click to collapse
Can you provide a list of apps which you have disabled through adb?
have you tried diff version of youtube that can help
RISHI RAJ said:
Can you provide a list of apps which you have disabled through adb?
Click to expand...
Click to collapse
I use package disabler pro bought from their website. It gives me a great on demand enable/disable option.
My use case might be a bit different from yours as I have about 160 packages disabled at a given time. I guess I can provide a list and you chose what you want from it.
I'll try uninstalling apps again to see if the problem can be resolved that way. On the latest version of Youtube it worked fine before I started installing more apps. I kind of don't want to do a full factory reset but if I have to so I can narrow that my be my only option. I'm wondering if there is another software I can run on my phone to see if any apps are interfering with the display or adaptive refresh rate?
I ended up doing a factory reset on my phone. The issue went away for the most of the day but returned again by night time. Same issue - when at 120hz and drops to 60hz the issue is present. It's not just Youtube, it's on any app, including the home screen. The first tap is always interpreted as a tap and hold, so single tapping an app icon brings up the tap and hold menu, and single tapping on the home screen brings up the home screen customization screen. Another test I did was turn off auto brightness, then turn my brightness down to the lowest setting. After that the display stayed at 120hz and the issue did not return until I either set the brightness up manually or turn auto brightness back on. I also tried in safe mode, and the issue was not present there either, but I can't tell if the device every went into 120hz or not since all 3rd party apps are disabled. At this point I have no idea what it is. The app setup was fine during the day, no new apps were installed, but the issue returned. Seems like I have no choice to but turn adaptive smoothness off and leave it at 60hz.
Just to add a little more interesting information here. I had someone else use the refresh rate monitor app on their Note 20 ultra (Tmobile variant), and their display operates differently than my Verizon variant. On the Tmo variant, when the screen drops to 60hz and the screen is tapped, the refresh rate drops to below 60 (12, 34, 48, etc) but then goes back up to 120hz after the app opens. Mine just goes immediately to 120hz and then gets that tap-and-hold behavior. So clearly the screens software or firmware is behaving differently here. I'm wondering if we have any other Verizon variant Note 20 Ultra users on this forum that could also test?

Oppo A53 Refresh Rate bug after ColorOS 11.1 update

Today I updated my OPPO A53 [CPH2127] and everything works just fine.
but after I restart the device, the refresh rate become 60hz even the 90hz option is turned on. The only one thing that rendered at 90hz is lockscreen.
Is there any solution to this problem?

Android 12 - refresh rate is broken, 90hz all the time

I just noticed that my Pixel 4 XL (currently has the newest Android 12/November patch) does not cycle between 60 and 90 hz anymore. I just noticed an unexpectated and new drain on the battery and finally found the culprit.
Yes, I checked developer options, the phone is NOT forcing 90hz. I checked with developer options (show refresh rate) and the phone is constantly, meaning 100% using 90hz, it never changes to 60. No matter what I do - Youtube, phone, scrolling, doing nothing, idling, homescreen, newspaper app, Audible - it matters not. It is constantly forcing 90hz WITHOUT having ever clicked the 90hz force toggle. This is putting a drain on the battery that is just unacceptable.
Can you guys confirm this?
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
blackhawk said:
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
Click to expand...
Click to collapse
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Morgrain said:
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Click to expand...
Click to collapse
I would re-flash with the latest full image, leaving the script intact (allowing the data partition to be wiped). This may be inconvenient but it's the only way you will know if there is a hardware issue with the phone. I'd also like to know what led you to the refresh rate. In other words, what made you look there. The stock battery monitor is not very good and even looking at system apps (screen, ambient display) you only get time and a percentage of the battery.
is the same on 12 and 11, i just installed 11 and is always 90hz
yes i can confirm, i had the same issue and i just boght my pixel 4 xl 10 days ago. updated to android 13 beta now and it still has the same problem. really weird but i think that google just decided that its best for google pixel 4 owners to have 90hz all the time now cause u know its "more common" now
Google changed how Smooth display works during the cycle of the phone. IIRC it was the same on A11 too. Basically the only time it goes 60hz is during battery saving mode & in some specific apps that prohibit it. It also disables it when HBM is on.
That doesn't make a lot of sense, you can save much more energy by just raising to 90hz for touch and animations and otherwise reduce to 60hz independently of the battery state.
I had the pixel 7 Pro for a while and can confirm that it works there as expected (60 for static content & no touch events, otherwise raises up to 120hz), just not for the pixel 4 XL.
This does seem like a bug to me and explains why battery life (SOT) got so much worse. I wonder if it's an intended degradation to get people to upgrade..
Fix it with adb, set minimal refresh rate
adb shell settings put system min_refresh_rate 1.0
adb shell settings put system peak_refresh_rate 90.0
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
onemandivision said:
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
Click to expand...
Click to collapse
Confirm you have extra dim disabled, and brightness 60%
Confirmed, does not make a difference
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
onemandivision said:
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
Click to expand...
Click to collapse
No problem, glad i helped!
Feel free to visit my optimization threads, it might help improve your battery life and performance.
One last remark: It didn't really work well at first, at least not as consistently as on the pixel 7 that I've tried. After some trial and error, playing around with various settings, the culprit seems to have the "increase touchscreen sensitivity" setting that I had enabled. Since turning it off, the switching between 60 and 90Hz is much better. Brightness and extra dim don't seem to play a role.
Battery life also seems to have improved a lot (now at ~50% at the end of the day compared to <20% before)

Question 12s ultra LTPO problem (refresh rate) in EU ROM

I think the LTPO2 is not working properly on eu rom currently im on last update 13.0.11 and i can see that the refresh rate is not going to 1fps in main menu or in settings, the frames going only low to 90fps in Facebook and i think this draining a lot of battery. Could you check on your phones how it is, go in developer settings and enable "show refresh rate" to see do you have this problem as well and if there is any solution for that, thanks
mititko123 said:
I think the LTPO2 is not working properly on eu rom currently im on last update 13.0.11 and i can see that the refresh rate is not going to 1fps in main menu or in settings, the frames going only low to 90fps in Facebook and i think this draining a lot of battery. Could you check on your phones how it is, go in developer settings and enable "show refresh rate" to see do you have this problem as well and if there is any solution for that, thanks
Click to expand...
Click to collapse
Adjust brightness.
Screen in FHD+ 60Hz
Minimum brightness: stay at 60
Brightness in the middle: goes to 30
Maximum brightness: goes to 10
With any other settings, the minimum reached is 10.
Surely a particular scenario is needed to reach 1.
You were going to 1 with the stock rom?
https://xiaomi.eu/community/threads...-rate-not-working-correctly.61079/post-650620
NOSS8 said:
Adjust brightness.
Screen in FHD+ 60Hz
Minimum brightness: stay at 60
Brightness in the middle: goes to 30
Maximum brightness: goes to 10
With any other settings, the minimum reached is 10.
Surely a particular scenario is needed to reach 1.
You were going to 1 with the stock rom?
https://xiaomi.eu/community/threads...-rate-not-working-correctly.61079/post-650620
Click to expand...
Click to collapse
Thank you for information, i have never used the phone with stock CH ROM, but now i have realised the brightest is the main thing as well, thanks and it works alright

Categories

Resources