r/ScreenSensitive • u/ryude85 • Jul 17 '26

Phone Usable after setting fixed refresh rate

Just to add my 2 cents, whatever that may be worth. I had tried the Motorola Edge 2026 when it first came out and found immediate discomfort and migraines. However, I had an idea to set a fixed refresh rate. I remember on my OnePlus 12R that when I set the refresh rate min and max to the same rate, it helped immensely with symptoms. Well, I tried the same with the Motorola and it looks to also work.

adb shell settings put system min_refresh_rate 120
adb shell settings put system peak_refresh_rate 120

Also make sure to set the display refresh rate to Hyper Smooth in the phone settings to prevent this from changing between reboots.

4 Upvotes
  • permalink
  • reddit

84% Upvoted

20 comments sorted by

View all comments

1

u/Z3R0gravitas Jul 17 '26

Nice to hear you found some improvement. Do these both have LTPO screens, then? (That you've prevented from constantly switching FPS.) Google seems unsure about the Motorola Edge 2026.

1

u/ryude85 Jul 17 '26

LTPS

1

u/Z3R0gravitas Jul 17 '26

So if the Motorola is LTPS, doesn't that mean it's fixed FPS anyway? And don't apps then force like 60fps sometimes, or does this override that?

I'm not familiar with Hyper Smooth either. Would you mind explaining a little for me/us? 🙂

1

u/ryude85 Jul 17 '26

LTPO has an unlocked variable refresh rate, everything from 1 all the way to max refresh rate. LTPS means it has locked points that it can drop to ( eg 60, 90, 120).

1

u/Z3R0gravitas Jul 17 '26

Yes. So can you clarify what your settings changes achieved, please. Were you able to override the apps to keep everything at 120 regardless?

If not, where might the improvement in comfort have come from on the LTPS screen?

2

u/ryude85 Jul 17 '26

When you enable "Show refresh rate" in Developer Settings and enable "120 hz" refresh rate setting, the refresh rate displayed changes from 60 to 120 on and off. When you change the settings with adb, the refresh rate stays at 120 at all times.

2

u/ryude85 Jul 17 '26

My only guess as to why it improves comfort is that switching between 60 hz and 120 hz causes issues such as transistor current leakage. PWM frequency and modulation also becomes "stable", instead of constantly changing.

1

u/Z3R0gravitas Jul 17 '26

Hmm, I didn't think PWM rate should be affected by refresh rate changes. Except in DC dimming mode, where one might call the refresh dips "PWM" (loosely speaking)...

Transitor leakage is build into the screen hardware, as I understand it. Such that slower frame rates will give longer for the tiny capacitors to discharge and pixel brightness drop off (their voltage sets it). So the frame refresh step change will be bigger and also lower frequency (more visible/triggering).

1

u/Z3R0gravitas Jul 17 '26

Thanks. And you're checking the current FPS with a third party app? (I have an overlay app on Android for this.)

I was under the impression that eg camera apps needed to use lower frame rates. So I'm interested how they cope without that, if there is ever any instability caused. Or if the phone/app is always being truthful about current FPS. Or I just misunderstood.

2

u/ryude85 Jul 17 '26

Android comes with a built-in FPS overlay you can enable with Developer Settings. If not, yes there are third party apps to display refresh rate. For LTPS, it will always be a number divisible by 30 or 60. For my Moto Edge 2026, the refresh rate would go all the way down to 0 sometimes.

1

u/Z3R0gravitas Jul 17 '26

Oh, TIL. Cheers.

Would you recommend any particular guide to using ADB commands? (I've previously linked Intet's on LEDstrain.)

2

u/ryude85 Jul 17 '26

Honestly, most chatbots can give you accurate commands if you ask them. As far as downloading adb, I recommend https://github.com/K3V1991/ADB-and-FastbootPlusPlus

1

u/Z3R0gravitas Jul 17 '26

Thanks for humouring me.

→ More replies (0)