Motion tracking stopped after restart? Check this
Check whether motion tracking stopped because of sensor permission, a low-battery power state, or a hardware fault, then work through focused browser checks.
Motion tracking worked before your phone or tablet ran low on battery, but stopped after you restarted it. The sensor may be fine: a browser permission, power-saving setting, or temporary sensor-service problem can interrupt readings.
Test the device itself before changing app settings. The Sensors Test checks motion and gyroscope readings in your browser, so you can see whether the device reports movement at all.
Check motion tracking after a restart
- Open the Sensors Test on the phone or tablet you want to check. A test on another device cannot tell you whether this device's sensors work.
- Keep the page open in the foreground. If the browser asks for motion or sensor access, allow it for the test.
- Set the device on a steady, level surface for a few seconds. Then tilt it slowly forward, backward, and to each side. Watch whether the motion or gyroscope readings change with your movement.
- Turn the device a quarter turn and repeat the movements. If the readings respond, check the compass separately by moving the device slowly through a figure eight, away from metal objects.
- Recharge the device for a while, restart it once more, and repeat the same movements in the same browser. This comparison helps separate a temporary low-power state from a repeatable fault.
Use gentle movements. Quick shaking makes it harder to tell normal sensor response from noise, and is not needed to test whether tracking works.
What the result means
Readings change smoothly when you tilt the device
The sensor is reporting motion to the browser. The original app may have lost permission, paused its tracking, or failed to resume after the restart. Check that app's own settings and reload it after confirming the browser test works.
There are no readings, or they stay fixed
The browser is not receiving motion data. A blocked site permission, unsupported browser feature, or sensor service that has not resumed can cause this. Try the permission and restart checks below before assuming the sensor is broken.
Readings jump while the device is still
A little movement is normal, but large or constant jumps while the device rests on a stable surface may indicate interference, a calibration issue, or a sensor problem. Remove a magnetic case or accessory and test again on a clear surface.
The test works, but the original app still does not
The hardware can provide motion data in this browser. The problem is more likely in the app, its permission, or its tracking setup. Close and reopen the app, check its access to motion data, and test it again with the device unlocked and in the foreground.
How to fix it
- Charge the device and turn off battery saver temporarily. A very low charge can trigger power-saving behavior, but battery saver does not disable sensors on every device. Charge it, turn off Battery Saver or Low Power Mode for one comparison, then repeat the test.
- Check the browser's site permission. Open the browser's site controls from the address bar and look for motion or sensor access, if that option is available. On Android Chrome, check Chrome › Settings › Site settings › Motion sensors. Reopen the page after changing a permission.
- Check the phone's motion access setting. On iPhone or iPad, open Settings › Apps › Safari › Motion & Orientation Access and allow access if the setting is present. On some iOS versions, Safari settings appear directly under Settings › Safari. This setting applies to Safari pages, not every browser app.
- Check that sensors are not disabled on Android. Look for a Sensors Off tile in Quick Settings, if your device has one, and turn it off. The tile is a device-wide control and can prevent apps and browsers from receiving sensor data.
- Close other apps that use motion tracking. Quit navigation, fitness, camera, and augmented-reality apps, then reload the test. Some devices or apps handle sensor access poorly when several activities compete for it.
- Try a supported browser and a fresh page. Update the browser, close the old tab, and open the Sensors Test again. Sensor access varies by browser and device, so a result in one browser may not match another.
- Restart after charging. If readings remain absent, charge the device, restart it, unlock it, and test again before opening other apps. This can clear a temporary service problem left after a shutdown at very low charge.
On Windows 11, there is no general Settings › Privacy & security switch for browser motion sensors. Check the browser's site permissions instead. On macOS, there is also no general motion-sensor permission switch for browsers; use the browser's website or site settings where available. A Windows convertible may have motion sensors, while most desktop computers and Mac laptops do not, so an empty result on those computers may simply mean the hardware is absent.
When it may be a hardware fault
Suspect hardware if motion readings stay absent or erratic after charging, restarting, allowing browser access, and trying another compatible browser. Also test a second motion-enabled app on the device. If multiple apps fail in the same way, the issue is less likely to be limited to one webpage.
Check for a recent drop, liquid exposure, or screen repair, and contact the device maker or repair shop if the sensor stopped working afterward. A browser test can show that motion data is missing, but it cannot identify a damaged sensor or repair it.
Why tracking can differ between apps
A browser test checks what the browser can read from the device, not whether every app's tracking system is working. Apps may use different sensors, combine motion with location, or require the page to stay active. If the Sensors Test responds but one app does not, focus on that app's permissions and restart behavior rather than repeatedly stressing the device with more sensor tests.
