Google Play services now extends Motion Assist, the bubble overlay built to ease motion sickness, beyond Pixel to other Android phones. Android Authority reported the expansion after Google added Motion Assist to its Play services v26.37 release notes this week. Google's support documentation separately says the feature works on Android devices running Android 17 or higher with updated Google Play services.
The catch: Google's documented requirement is Android 17 or newer with an updated version of Play services, not just any Android phone, Android Authority reported. The hands-on reporting cited here specifically confirms it running on Pixel and Samsung Galaxy Fold 8-series devices.
Pixel phones got it first. Samsung's Galaxy Fold 8-series followed, spotted by 9to5Google on an earlier Play services build over a week ago.
Google's stated Android 17 requirement and the phones reporters have actually watched run Motion Assist are still two different lists. Here's what the feature does, how to check your own phone, and what the rollout timeline does and doesn't confirm.
What Motion Assist actually does
Motion Assist puts small moving bubbles along the edges of the screen, using the phone's motion sensors to sync those shapes to the vehicle's movement in real time. The goal, per 9to5Google, is to cut down on motion sickness whether you're in a car, bus, or another moving vehicle.
The premise, per Google, is to help the brain reconcile what the eyes see on a static screen with what the body feels while riding along. It's the same basic idea behind Apple's Motion Cues on iPhone, as The Verge notes.
Once enabled, the bubbles are customizable. Pick a shape (circle, square, pentagon, diamond), a color (Dynamic Color to match your system theme, or a fixed red, yellow, green, or blue), adjust an opacity slider, and optionally randomize color and shape every few seconds. It can trigger automatically when the phone detects a moving vehicle, or manually via a Quick Settings tile, with a silent notification offering a one-tap way to shut it off.
Google keeps the language hedged in its own release notes. The feature "can help mitigate motion sickness," not eliminate it, echoing earlier documentation that said it "may help reduce" symptoms. By Google's own description, this is a mitigation tool, not a promised fix, and no source in this reporting includes independent testing of how well it actually works.
Which Motion Assist Android 17 phones qualify
Google's baseline is simple on paper: Android 17 or higher, plus a current version of Google Play services, according to Android Authority. Android Central ties the broader non-Pixel push specifically to Play services version 26.37.
In practice, the list of phones reporters have actually watched run it is short. Pixel devices got it first, arriving earlier this month as part of Google's September Android Drop. 9to5Google then found it working on Samsung's Galaxy Fold 8-series running Android 17, on an earlier Play services build, more than a week before Android Central's v26.37 reporting.
Those are the device families specifically observed in the reporting so far, not a confirmed complete list. Availability isn't tied to any published device roster, so an Android 17 phone from another manufacturer that meets the stated requirements on paper isn't automatically guaranteed to show the toggle.
How to check if your phone qualifies
Checking takes a few minutes and doesn't require installing anything new.
Confirm you're on Android 17. Open Settings > About phone and check the version. Anything older is excluded by Google's stated requirement, no matter how current Play services is, per Android Authority.
Make sure Google Play Services is up to date. Google doesn't specify a minimum version on its support page, and 9to5Google observed Motion Assist working on version 26.33.32.
Search Settings for "Motion Assist." Both 9to5Google and The Verge point to Settings search as one reported way to find the setting if it's reached your phone.
Or use the full menu path. If search comes up empty, try Settings > Google > All services > Personal & device safety > Motion assist, where it sits alongside Advanced Protection and Theft Protection.
If none of that surfaces the setting, it doesn't necessarily mean your phone is excluded. It may just mean the server-side rollout hasn't reached that device yet, though the available reporting doesn't rule out other causes.
What's confirmed and what's still unclear about the rollout
9to5Google first flagged Motion Assist reaching Android 17 phones three weeks ago, when the feature was appearing on only one of the outlet's test devices despite several eligible phones on hand. That report tied the patchy rollout to a server-side component gating activation independent of the installed software version.
By last week, 9to5Google reported the feature had "widely rolled out" across its Pixel and Galaxy Fold 8-series devices running Play services v26.33.32. The Verge separately cited Google's Mishaal Rahman describing Motion Assist as "generally available" in Android 17 around the same time.
This week, Android Central tied the broader non-Pixel push to a newer build, Play services v26.37, which also bundled unrelated fixes like Wear OS health-metric syncing and an easier-to-find Driving Do Not Disturb setting. Since 9to5Google had already reported that server-side gating three weeks earlier, the safer read is to treat Android 17 with current Play services as an eligibility requirement, not a guarantee of immediate access.
None of this reporting establishes a complete list of supported manufacturers, models, or regions beyond the Pixel and Galaxy Fold 8-series devices reporters have hands-on. Nothing here explains why one eligible phone might get the toggle before another running the identical Play services version, and no regional rollout list has surfaced yet.
Check Android 17 under About phone, confirm Play services has updated past v26.37, and search Settings for "Motion Assist." If the toggle still doesn't show up, check again after future Play Services updates rather than assuming your phone is excluded. A missing toggle doesn't by itself prove the phone is unsupported; rollout timing, Play Services status, or device compatibility could still be factors.
Comments
Be the first, drop a comment!