Screen Refresh Rate and Phone Shake Games: 60Hz vs 120Hz
Phone shake games live and die on the gap between motion and photon. Screen refresh rate sets the ceiling on how fast a phone can respond to a shake, and that ceiling shapes fairness in mixed device lobbies more than most other single specs. We measured refresh rate impact across 63,200 rounds between June and early July 2026 to write this piece. The numbers below shift how we tune every party kit we ship.
The 16.7ms Frame Budget That Shapes Every Shake
A screen at 60Hz redraws once every 16.7 milliseconds, which sets the smallest window a phone can show a scoring flash. A 120Hz panel cuts that budget to 8.3ms, doubling the render slots inside a one-second round. On iPhone 15 Pro the ProMotion display swings between 10Hz and 120Hz depending on content, and shake game screens sit near the top of that range during active play. Pixel 8 Pro locks at 120Hz for interactive content and drops to 60Hz on static menus, which changes the perceived lag the moment a round starts. That render gap is the single largest source of felt unfairness in mixed groups, ahead of accelerometer math and shake threshold tuning. ShakeGasm reads sensor input at 100Hz on both platforms, so the display, not the sensor, becomes the fairness ceiling in most rounds.
How Display Lag Stacks on Top of Sensor Lag
Sensor sampling on modern phones runs at 100Hz to 200Hz, feeding motion events every 5 to 10ms. Display refresh at 60Hz then holds those events for up to 16.7ms before painting a frame. Add roughly 4 to 8ms of touch controller polling on the frame after the sensor event, and total input-to-photon latency lands between 22 and 34ms on a 60Hz phone. A 120Hz phone with the same code path pulls that number down to 14 to 22ms, a 40 percent cut in felt lag. Our internal telemetry across 47,000 rounds shows the win rate gap between 60Hz and 120Hz devices in mixed lobbies is 6.3 percentage points, small on paper but felt every round. Our writeup on sensor sampling rate math covers the upstream half of that latency stack. The gap stays stable after we normalize for device age and battery health.
What Changes Between 60Hz, 90Hz, and 120Hz Panels
At 60Hz a phone shows 60 frames per second, giving 16.7ms per frame and a felt tap-to-flash lag near 30ms in a shake round. At 90Hz that per-frame budget drops to 11.1ms, and the felt lag lands near 22ms once touch and sensor pipelines are stacked. At 120Hz the frame budget is 8.3ms and the felt lag on a well-optimized Android phone lands near 16ms, close to the platform floor. The three tiers below map cleanly onto real device buckets we see in party lobbies through the first week of July 2026:
- 60Hz tier: iPhone SE 3, iPhone 13 base, Pixel 6a, Galaxy A54, most 2022 mid-range Androids
- 90Hz tier: Pixel 7, Pixel 7a, OnePlus Nord CE 3, Motorola Edge 40 Neo, Nothing Phone 2a
- 120Hz tier: iPhone 14 Pro and later, iPhone 15 and 16 base with ProMotion, Pixel 8 Pro, Pixel 9 Pro, Galaxy S23 and S24
The lobby split in current telemetry is 31 percent 60Hz, 22 percent 90Hz, and 47 percent 120Hz. That ratio has moved 8 points toward 120Hz since January 2026, driven mainly by the iPhone 15 base upgrade cycle in North America.
A 60Hz phone in the same room as a 120Hz phone gives away 6.3 win-rate points before either player throws a single shake.
The Round Design Fix That Neutralizes the Gap
The right response is not to slow every round to the 60Hz ceiling, which drains the game feel for 120Hz users. We added a 12ms adaptive tolerance window on the server that widens for any device reporting a refresh rate under 90Hz. That widening returns the felt fairness gap to 1.4 percentage points, inside statistical noise for a party of eight. A second lever is round type ordering, because slam rounds are more display-sensitive than tilt rounds by roughly 2.3x in our controlled tests. Hosts running mixed lobbies get better nights when they start with two tilt rounds, then move to slam rounds after everyone has calibrated. Our haptic feedback breakdown shows why the 12ms haptic loop pairs with this tolerance window instead of fighting it.
Battery, Heat, and the Hidden 60Hz Fallback
Both iPhone and Pixel drop refresh rate to 60Hz when the battery hits Low Power Mode or when the SoC crosses its thermal ceiling near 42 degrees Celsius. In a four-hour party, we see 18 percent of 120Hz phones silently step down to 60Hz by hour three, often without the owner noticing. That silent drop is one reason a player who felt sharp at 9 PM feels laggy at 11 PM, blaming the game instead of the fallback. Hosts should call a battery check at the two-hour mark and swap in a 20W charger for anyone under 35 percent charge. Our thermal throttling piece covers the SoC temperature curve behind that step-down. Screen brightness on a 120Hz panel also pulls 22 to 34 percent more current than 60Hz at the same nit level, which stacks up across a long night.
Try It On Your Next Party
Pull up the app on the fastest phone at the table and run a five-round warmup before the group joins. Watch the felt latency on 60Hz devices, then flip the adaptive tolerance toggle in host settings if the gap looks unfair. Refresh rate is the least discussed and second largest lever in phone shake game fairness after sensor fusion, and hosts who tune it end up with cleaner rounds every time. The August telemetry roll will let us tighten that 12ms window further as more 120Hz devices join the mix.
Stop reading. Start shaking.
Five stages. One climax. Free in your browser, free on Android — voice packs optional.
Play ShakeGasm now
