Short answer: the setting in Display tells you what the phone is configured for; it does not tell you what the panel is currently doing. To know the real rate you have to measure it, because adaptive refresh, battery saver and heat all silently drop it.
Where the setting lives
Android: Settings â Display, then look for one of:
- Motion smoothness (Samsung) â Standard / Adaptive
- Refresh rate (Pixel, OnePlus) â 60 Hz / 120 Hz / Auto
- Screen refresh rate (Xiaomi)
iPhone: there is no refresh rate setting. ProMotion models (Pro from the 13 Pro onward) switch between 10 and 120 Hz automatically. Non-Pro models are fixed at 60 Hz. The only related control is Settings â Accessibility â Motion â Limit Frame Rate, which caps ProMotion at 60 Hz.
Measuring what it is actually doing
The setting and the reality diverge constantly. To measure it, you need something that counts real animation frames over time â our screen info tool does this in the browser by timing 150 consecutive frames and taking the median interval.
To get a meaningful reading:
- Turn battery saver off â it forces 60 Hz on nearly every phone
- Make sure the phone is not hot
- Keep the content moving while measuring, or adaptive panels will drop the rate
- Charge above 20% â some phones throttle refresh at low battery
If you measure 60 Hz on a phone set to 120 Hz with all of the above satisfied, the browser may simply not be on the high-refresh path, which is common. Check with a native app before concluding the panel is the problem.
Why adaptive refresh exists
A display running at 120 Hz redraws 120 times per second whether or not anything changed. On a static page that is 119 wasted redraws, each costing power.
Adaptive panels (LTPO, and similar) vary the rate with the content:
| Content | Typical rate |
|---|---|
| Static page, always-on display | 1â10 Hz |
| Reading, scrolling slowly | 30â60 Hz |
| Fast scrolling | 120 Hz |
| Video at 24 fps | 24 or 48 Hz |
| Gaming | Matches the game's frame rate |
This is why a measurement taken on a static page reads low and is not a fault. It is the panel working correctly.
What forces a phone back to 60 Hz
- Battery saver / power saving mode â the most common cause by far
- Low battery, typically under 15â20%
- High temperature â thermal management drops refresh before it drops CPU clocks
- Specific apps â some apps request 60 Hz explicitly, and many games cap themselves
- Video playback at a lower frame rate
- Always-on display
Refresh rate vs touch sampling rate
These are different numbers and manufacturers happily blur them in marketing:
- Refresh rate (Hz) â how often the display redraws
- Touch sampling rate (Hz) â how often the digitiser checks for your finger
A phone can advertise "240 Hz touch sampling" alongside a 120 Hz display. Higher touch sampling reduces input latency, which matters in games, but it has nothing to do with how smooth scrolling looks.
Is it worth paying for?
The honest position:
- 60 â 90 Hz: clearly visible to almost everyone. Scrolling and animations look obviously smoother.
- 90 â 120 Hz: subtle. Many people cannot reliably distinguish them in a blind comparison during normal use.
- 120 â 144 Hz+: essentially imperceptible outside of competitive gaming.
The battery trade-off is real but smaller than often claimed on modern LTPO panels, because they spend most of their time at low rates. On a cheaper phone with a fixed 120 Hz panel and no adaptive capability, the cost is constant and more noticeable.
