Android 17 May Add Motion Cues to Reduce Motion Sickness
- Google is developing a software feature for the Android operating system called Motion Cues designed to reduce travel-induced motion sickness for passengers riding in vehicles, according to reporting...
- To combat this mismatch, the upcoming Android feature places animated dots on the screen that shift in real-time based on data from the device's internal motion sensors, effectively...
- Evidence of the Motion Cues feature first emerged in late 2024, but the tool remained dormant within Google Play Services.
Android 17 to Introduce Native Motion Cues
Google is developing a software feature for the Android operating system called Motion Cues designed to reduce travel-induced motion sickness for passengers riding in vehicles, according to reporting by Android Authority. Motion sickness occurs during travel due to a sensory conflict where a passenger’s eyes focus on a stationary smartphone while the inner ear detects motion.
To combat this mismatch, the upcoming Android feature places animated dots on the screen that shift in real-time based on data from the device’s internal motion sensors, effectively matching the visual feedback to the movement of the vehicle.
Overcoming System API Restrictions
Evidence of the Motion Cues feature first emerged in late 2024, but the tool remained dormant within Google Play Services. According to an APK teardown analysis by Assemble Debug cited by Android Authority, the feature is fully functional but hindered by a significant architectural limitation in current Android versions.
The current implementation relies on Android’s standard overlay application programming interface, or API. For security reasons, Android prevents standard apps from drawing graphics over critical system components such as the Settings app, status bar, notifications, Quick Settings, lock screen, or volume panel. This restriction stops malicious actors from tricking users, but it also prevents the motion-sickness dots from appearing over essential user interface elements.
Shifting Rendering to SystemUI
To resolve this obstacle, Google plans to introduce a system-level Motion Cues API in the Android 17 update.
The new system-level architecture utilizes a dual-layer approach where Google Play Services determines the placement and look of the dots, while SystemUI handles the actual on-screen display. According to Android Authority, the code includes components named MotionCuesService, IMotionCuesCallback, MotionCuesData, and MotionCuesSettings.
Security Controls and Third-Party Limits
These services allow a client application to define specific coordinates, colors, radii, and spacing for the dots, rendering them on a privileged window layer using a startMotionCuesSession command. To prevent unauthorized third-party apps from cluttering the screen with unwanted visual elements, Android restricts the API through a new DRAW_MOTION_CUES permission. This permission is limited to privileged system apps or software signed by the platform certificate, ensuring SystemUI ignores data from unverified sources.
Following Apple and Pioneering Precedents
Google’s upcoming feature closely mirrors Apple’s Vehicle Motion Cues, which launched in iOS 18 to address the same passenger discomfort. However, neither company was the first to introduce the concept to mobile devices.
A free third-party Android application named KineStop implemented the exact same concept back in 2018. Compatible with devices running Android 7.0 or later, KineStop requires users to manually grant display permissions and start the service to achieve the same stabilizing visual effect. While third-party tools have offered this capability for years, the upcoming Android 17 implementation integrates the functionality natively at the operating system level.