Related
Many users of this device (including myself) have noticed bad touch input sensitivity when using the 144Hz mode, but not in 60Hz or Auto. I have found quite an odd solution that at least fixes the issue on my end, and I'd like more people to test this, so please, comment down below.
Okay, for this I don't believe you need root. Go to settings and enable USB debugging, find the Motorola Edge 20 USB drivers online and ADB & Fastboot of you choice.
Once you have done all of that, open ADB & Fastboot in a terminal and write the following without the quote marks and the comments that start with a dash (make sure your display is on and the phone is connected to the computer):
"adb devices"
-this command will make a message pop up on your phone asking you if you allow the current computer to access your phone, press allow
"adb shell settings put system peak_refresh_rate 120"
-this will make it so that your max refresh rate can be 120Hz. Keep in mind you can set this to either 48, 60, 90, 120 or 144.
"adb shell settings put system min_refresh_rate 120"
-this will set your minimum refresh rate that the phone will default to when it thinks that it doesn't need the maximum refresh rate. Again it can be set to 48, 60, 90, 120 or 144.
Note: You do not need to reboot, the changes are instant. You can freely use the power saving feature (it sets the refresh rate to 60 when enabled) as turning it off retains the parameters set. The parameters also remain after rebooting. You will have to re-introduce these commands only if you switch the refresh rate option in the settings. This is for the most part a one-time fix.
What this basically does is set the refresh rate parameters for your phone. Android has adaptive refresh rate that oscillates based on the content you watch. The "min_refresh_rate" is the lowest refresh rate your phone will use when conserving power (e.g sitting idle on a .pdf file or watching a 60fps video) and the "peak_refresh_rate" is the highest refresh rate the phone will reach when doing tasks it deems appropriate for 120fps. At least in theory. The reality is that setting any sort of parameters that aren't a fixed refresh rate (e.g 144Hz peak with 90Hz min) will be refused by your device, and it will choose to switch to 60Hz when it feels like it even if you have specifically set it to not do that.
I have used the phone for about a week now with these settings, and I'm positive it is better with 120Hz min and peak. You do not get touch issues at this refresh rate and your phone also doesn't annoyingly switch to 60Hz when scrolling through a web browser or Instagram. It is pinned to 120Hz. Although it sucks that the device is not usable at 144Hz, this is the best solution at the moment until Motorola decides to fix their device.
I unfortunately doubt this fixes the issues with the Indian release of the phone. From my understanding, the Indian market has received a varient that has an AMOLED display that comes with issues far more severe than what I've experienced on my unit. Hopefully it is a software issue rather than a hardware one.
-Username: Required
I'll try this later tonight. Thanks for the tip.
Also, Motorola has announced in their forum that there is a fix coming for the touch issue in a software update.
dannejanne said:
I'll try this later tonight. Thanks for the tip.
Also, Motorola has announced in their forum that there is a fix coming for the touch issue in a software update.
Click to expand...
Click to collapse
Yes, I know this. But we all know Motorola is very slow with updates. If we get that fix by the end of the year we'll be very lucky. Set the refresh to 120 and 120 respectively. I feel that the phone is way more usable this way. I'll update the guide too.
Username: Required said:
Yes, I know this. But we all know Motorola is very slow with updates. If we get that fix by the end of the year we'll be very lucky. Set the refresh to 120 and 120 respectively. I feel that the phone is way more usable this way. I'll update the guide too.
Click to expand...
Click to collapse
My touch still had problems in 144Hz mode after doing this. In auto I never really had an issue. However it is useful to let the phone run at 120Hz all the time.
dannejanne said:
My touch still had problems in 144Hz mode after doing this. In auto I never really had an issue. However it is useful to let the phone run at 120Hz all the time.
Click to expand...
Click to collapse
You shouldn't have touch problems with 120Hz fixed.
Username: Required said:
You shouldn't have touch problems with 120Hz fixed.
Click to expand...
Click to collapse
No I don't, only in 144Hz mode. Didn't have issue in auto mode before fixing the refresh rate either. Anyway let's hope the future update will fix 144Hz mode.
dannejanne said:
No I don't, only in 144Hz mode. Didn't have issue in auto mode before fixing the refresh rate either. Anyway let's hope the future update will fix 144Hz mode.
Click to expand...
Click to collapse
Yeah. Let's hope that it's at least not hardware related and can actually be fixed.
Running 144hz no touch issues hear Smooth as butter ,
Hello since first build on one UI 4.0 im facing refresh rate / screen strutter when edge lighting comes on.
Have done factory reset when receiving the first build of one UI 4.0
Anyone can confirm if another factory reset is needed? As restoring my games and apps take quite alot of time and data.
Current build is the latest BULC
Exynos dual sim model
Hi, I've sometimes noticed that too, although not 100% sure if it's simply related to this:
Picture in Picture, Split Screen etc - Refresh Rate drops to 60Hz (EXYNOS)
Hi there, I'd not noticed this before the Android 12 update, but refresh rate appears to drop from 120Hz to 60Hz when using Picture in Picture or Split Screen views. Can anyone else reproduce this please? You can confirm this by going into...
forum.xda-developers.com
Can you please test that scenario too? Thanks.
There are a lot of moments throughout a lot of applications when adaptive refresh rate just decides that it's the moment to use 60hz. The one that annoys me the most is the unlock animation.
Hello there!
I am facing an issue, which I believe is destroying the user interface . The issue is like- when you have quite a few notifications and if you try to open the quick panel, you can see drastic frame drops while swiping down the panel.
I have started to see this issue after one UI 4 update, earlier on 3.1 there was no such issues.
Moreover, if you try to open the panel again, you will not notice any kind of stutters. Also, if you use 60Hz instead of 120, you will not notice this problem.
We need to access the quick panel countless of times in a day and to witness such lag everytime is very frustrating and annoying.
I tried to use one shade, power shade, but those apps have problems of their own. They don't provide any solution for the problem.
I even cleared the cached partition, but the problem is persistent.
Anyone knows a fix of the problem??
enough people have faced the same issue that it's likely to be addressed by Samsung this month or next.
there's no user actionable fixes for firmware problems.
Thank you sir for replying.
On a side note: i tried to use 120hz with power saving mode on using galaxy max hz, did the adb part, but it didn't work on my s20 Fe. Do you know any fix?
Dan_382 said:
Thank you sir for replying.
On a side note: i tried to use 120hz with power saving mode on using galaxy max hz, did the adb part, but it didn't work on my s20 Fe. Do you know any fix?
Click to expand...
Click to collapse
heard there's some weird quirk where maps helps get around the limitation.
it's posted in one our sections somewhere.
Thank you, found the discussion, it works)
I don't really know how to explain or describe this problem I am having. But while I'm staring at my screen for example in the settings menu I can see the color or the background change from one color to another and it keeps going back and forward. I tried to get screen recordings and screenshots but it does not get captured during screen recordings even tho it's happening while recording. Has anyone else experienced this problem?
Edit: I think it has something to do with the refresh rate going from 60 to 120. I noticed this because I have my refresh rate monitor on the status bar
Adaptive brightness?
adamlee2012 said:
This is happening to me with Reddit, while I'm scrolling it's fine but if I stop scrolling the screen colour temperature changes drastically. Since the June update.
Click to expand...
Click to collapse
So I noticed it only happens when the refresh rate goes down to 48hz. I use Galaxy max Hz app to force 48hz when its just idling. When I set it to 60hz it's fine
orlans21 said:
So I noticed it only happens when the refresh rate goes down to 48hz. I use Galaxy max Hz app to force 48hz when its just idling. When I set it to 60hz it's fine
Click to expand...
Click to collapse
Yes, i remove the app because of this issue
adamlee2012 said:
This is happening to me with Reddit, while I'm scrolling it's fine but if I stop scrolling the screen colour temperature changes drastically. Since the June update.
Click to expand...
Click to collapse
Reddit - me too
Hello,
I actually have a Mi 11 Ultra which is running latest offcial EU rom (13.0.7), and i'm facing problem with the drop of refresh rate.
The refresh rate is set on 120Hz but sometimes, it drops and i can feel it when i scroll in parameters menu etc....
To fix that i lock/unlock the phone several times and it goes back to 120Hz refresh rate. I think, i'm getting this problem since the transition between MIUI 12.5 and 13.0 .
Are you facing this issues or did you already fix it ?
Thank you.
Yes same problem here on global rom, this started happening to me as well when I transitioned from 12.5 to 13. Not even with root and terminal emulator to force 120hz seemed to work. We can only wait for an update
xNAPx said:
Yes same problem here on global rom, this started happening to me as well when I transitioned from 12.5 to 13. Not even with root and terminal emulator to force 120hz seemed to work. We can only wait for an update
Click to expand...
Click to collapse
Glad to see that i'm not the only one who is facing this issue.
I hope, it will fix with further update...
Had the same issue, it was fixed for me with version 13.0.7 (EEA).
The problem is related with the Mirror Screen. Try to disable it.
schijndel said:
Had the same issue, it was fixed for me with version 13.0.7 (EEA).
The problem is related with the Mirror Screen. Try to disable it.
Click to expand...
Click to collapse
For me it's still there in 13.0.7 (EEA), and even with the rear display disabled, the refresh rate drops sometimes and i have to lock/unlock to get back the 120Hz refresh rate...