New Android Feature Brings Motion Assist to Ease Car Sickness
- Google is developing a new system-level feature called Motion Cues for Android designed to reduce vehicle motion sickness for passengers using their phones, according to reporting published by...
- The Motion Cues feature mitigates sensory mismatch by displaying visual elements that mimic the movement of a vehicle, according to Android Authority.
- Evidence discovered in Android Canary releases indicates that Google is building Motion Cues for a future Android 17 release.
Google is developing a new system-level feature called Motion Cues for Android designed to reduce vehicle motion sickness for passengers using their phones, according to reporting published by Android Authority. Motion sickness occurs due to a sensory conflict where a person’s eyes focus on a stationary smartphone screen while their inner ears register physical movement.
How Android Motion Cues Mitigates Vehicle Motion Sickness
The Motion Cues feature mitigates sensory mismatch by displaying visual elements that mimic the movement of a vehicle, according to Android Authority. The system places dots on the phone screen that shift in real time based on data collected from the device’s motion sensors. This visual trick effectively moves the screen alongside the user’s physical trajectory. Apple introduced a similar capability called Vehicle Motion Cues in iOS 18, though third-party Android applications like KineStop have offered alternative implementations since 2018.
Technical Limitations and Android 17 Development
Evidence discovered in Android Canary releases indicates that Google is building Motion Cues for a future Android 17 release. Android Authority reports that while the feature currently exists in a dormant and functional state within Google Play Services, earlier tests showed that motion dots failed to appear over critical system elements such as the status bar, notifications, Quick Settings, lock screen, and volume panel. Because the feature previously relied on standard Android overlay APIs restricted for security reasons, it could not draw over system components. To bypass this limitation, Android 17 introduces a system-level Motion Cues API that transfers rendering responsibility directly to SystemUI, the system application managing those critical interface layers. Code references including MotionCuesService, IMotionCuesCallback, MotionCuesData, and MotionCuesSettings show that Google Play Services will define the parameters of the dots while SystemUI handles the actual on-screen display. Access to this functionality requires a restricted DRAW_MOTION_CUES permission, ensuring unauthorized third-party apps cannot clutter the interface.