How to check device tilt after granting sensor access

You granted a browser permission to use motion sensors, but you still need to know whether the device is reporting tilt correctly. A useful check is to watch the readings while you move the device slowly through a few positions.

The Sensors Test checks motion and gyroscope data, along with other sensors your device and browser make available. Use it on the device you want to check, since a computer cannot report sensor readings from your phone.

Check tilt values in the browser

Open the Sensors Test on the phone or tablet you want to test. If the browser asks to use motion or sensor data, allow access for the page.
Keep the device still on a level surface for a moment. Look at the motion readings before you move it. Some values may continue to change slightly even while the device is resting.
Pick the device up and slowly tilt the top edge toward and away from you. Then tilt it from side to side. Watch whether one or more readings respond to each movement.
Rotate the device gradually from portrait to landscape, then return it to its starting position. Move it smoothly rather than shaking it, so you can tell which movement caused a change.
Set it flat again and wait for the readings to settle. Repeat the same movements once more to see whether the response is consistent.

Different devices and browsers may show sensor data in different units or use different axis names. Focus first on whether the readings respond to movement and return to a similar state when you repeat the same position. A single number by itself is not a universal pass or fail value.

What the readings can tell you

The values change when you tilt the device

The browser is receiving motion data, and the device is responding to your movement. If a motion-based app still reacts incorrectly, the issue may be in that app's controls, calibration, or interpretation of the sensor values rather than a complete lack of sensor access.

The values change, but the direction seems wrong

Check whether the app expects the phone to be held in a different orientation. Rotating the device can change which physical movement corresponds to a particular axis. A phone case, a magnetic mount, or nearby metal can also affect compass readings, but these do not usually explain every motion reading moving in the wrong direction.

The values stay still while you move the device

The page may not have permission, the browser may not support the motion feature, or the device may not have a usable sensor for that reading. Some desktop computers have no built-in motion sensors. A browser test cannot create sensor hardware that the device does not have.

The values jump while the device is resting

Small changes can be normal. Sensors are not perfectly motionless, and a soft or uneven surface can move slightly when you touch the device. Put it on a firm, level surface and leave it untouched for a few seconds. If the readings continue to jump substantially, close other sensor-using pages and test again.

If permission was granted but readings are missing

Reload the page after allowing access. Some browsers apply a permission change only after the page refreshes or the sensor request is started again. Close any old test tab, reopen the page, and grant access if asked.
Check the browser's site permission. Open the browser's site controls for the page and look for a motion or sensor permission. Change a blocked setting to allow, then reload. The exact menu wording depends on the browser.
Check Safari's motion setting on iPhone or iPad. In current versions of iOS and iPadOS, go to Settings › Apps › Safari › Motion & Orientation Access and turn it on. On older versions, find Safari directly in Settings. Return to the page and try again.
Check the site setting in Chrome on Android. Open Chrome's menu, then go to Settings › Site settings › Motion sensors if that option is available. Allow access for the page and reload it. Menu options can vary by Android version and browser.
Try a regular browser tab. Private browsing, managed devices, or privacy extensions may restrict sensor access. Test in a standard tab and temporarily disable relevant restrictions if you are allowed to do so.
Test the device itself, not a remote session. Remote desktop software and browser emulators may not pass physical sensor data through. Open the test directly on the phone or tablet.

Granting permission does not guarantee that every sensor value will be available. A browser can expose only the readings supported by the device, operating system, and browser. The page also needs to be allowed to use the relevant feature, and some browsers require a direct action on the page before motion access starts.

When the problem may be hardware

If the same readings remain unavailable in more than one compatible browser after checking permissions, restart the device and test again. Remove a case or mount if it contains magnets, and make sure the device is not being held against a vibrating surface. If the sensors still do not respond in apps that normally use them, the sensor may be disabled by a device setting or have a hardware fault.

Compare the result with another phone or tablet if one is available, but test each device on itself. If only one device fails after permissions and browser access are confirmed, contact the device maker or a repair shop. A browser-based sensor test can show what the browser receives, but it cannot inspect the sensor circuit or diagnose an internal hardware failure.