How to test gyroscope rotation before an AR activity

If an AR object spins, lags, or points the wrong way during a lesson, the device may not be reporting rotation as expected. A quick check before class can help you separate a sensor problem from an issue in the AR activity.

Use the Sensors Test on the same phone or tablet you plan to use. It can show gyroscope and motion readings in your browser. The check confirms whether the browser receives rotation data, but it does not prove that every AR app will track correctly.

Test gyroscope rotation

1. Open the Sensors Test on the phone or tablet you will use for the activity. A computer test will not tell you whether the mobile device's sensor works.
2. Find the gyroscope or rotation readings. If the browser asks for sensor access, allow it. If the test cannot access the sensor, check the results section below before changing settings.
3. Hold the device still for a few seconds. Note whether the readings settle or continue to change while the device is resting.
4. Rotate the device slowly to the left and right, then return it to its starting position. Repeat by tilting it forward and back, and then turning it like a steering wheel. Move one way at a time so you can see which readings respond.
5. Repeat the same movements once more. Check whether the readings respond consistently and settle again when you stop moving.

Keep the movement gentle and controlled. You do not need to spin the device quickly or move it through a full circle. Sensor axes and sign conventions vary, so focus on whether the readings change smoothly with movement rather than expecting a particular number or direction.

What the result means

Readings change smoothly as you rotate

The browser is receiving gyroscope data, and the sensor responds to movement. If the AR lesson still behaves badly, check the activity's own permissions and tracking instructions. A working gyroscope does not confirm that the app can use the camera or recognize the room.

Readings stay almost the same while the device moves

The browser may not have access to the sensor, the browser may not support the required sensor feature, or the device may not have a gyroscope. Try the permission and browser checks below. If the same result appears in another supported browser on the same device, the sensor may be unavailable or faulty.

Readings change while the device is resting

A small amount of movement in the values can be normal. Large, repeated jumps while the device is still may point to noisy sensor data, movement from your hands or desk, or an access issue. Rest the device on a stable surface and repeat the check.

One movement seems to affect a different axis

This alone does not mean the gyroscope is broken. The display orientation, how you hold the device, and the browser's axis convention can change how rotation appears. Test each movement separately and look for a repeatable response, not a specific axis label.

The browser cannot access sensor readings

This is not the same as a failed sensor. The browser, site permissions, device settings, or a managed device policy may block access. Try the steps below, then compare with the AR activity itself if it offers a sensor or tracking check.

How to fix missing or uneven readings

1. Hold the device steady. Set it on a level surface and wait a few seconds before judging the readings. A soft couch, moving desk, or hand movement can make a resting sensor look unstable.
2. Check sensor access on your phone or tablet. In Chrome on Android, open Chrome menu › Settings › Site settings › Motion sensors, if that option is available, and allow access for the site. On iPhone or iPad, check Settings › Apps › Safari › Motion & Orientation Access. On older iOS versions, the Safari setting may appear under Settings › Safari.
3. Check browser site permissions. Open the browser's site information or permissions menu for the test page and look for a motion or sensor permission. The label and availability vary by browser. Reload the page after changing a permission.
4. Try a current mobile browser. Sensor support can differ between browsers and device models. Close the test, open it in another updated browser, and repeat the same slow rotations.
5. Check whether the device has a gyroscope. Some lower-cost tablets and older devices do not include one. A rotation sensor reading may be unavailable even if the device can detect other movement.
6. Restart the device and retest. A restart can clear a temporary browser or sensor service problem. If the test still cannot read rotation, check the device maker's support information or ask the activity provider which browsers and devices they support.

Windows 11 does not provide a general gyroscope permission switch in Settings › Privacy & security. macOS likewise has no universal gyroscope toggle in System Settings › Privacy & Security. If you are testing on a computer, the browser may simply not expose a suitable motion sensor. Use the phone or tablet that will run the AR activity.

A gyroscope check is not an AR tracking test

A gyroscope detects how quickly a device rotates. An AR activity may also need camera access, a suitable camera view, and a way to recognize surfaces or objects in the room. Those parts can fail even when the rotation readings look normal.

If the device passes this check but the AR scene still drifts, verify that the activity can use the camera and follow its setup instructions. For a related check of tilt readings, see how to check device tilt before using an AR app.