Why a sensor test must run on the device being checked
A browser sensor test reads hardware and permissions on the device running it. Learn why remote checks fail and how to test the right phone or tablet.
You want to check a phone or tablet's motion, compass, light, or vibration sensor, but you opened the test on a computer. That can only tell you about the computer. A browser sensor test reads the device it is running on, not a nearby device you want to inspect.
Run the Sensors Test on the phone, tablet, or computer you are checking. It can show what that device's browser can access, which depends on both the installed hardware and the permissions you allow.
Run the test on the device you want to check
- Open the Sensors Test in a browser on the exact device you want to test. Opening it on a laptop does not test a phone beside it.
- Allow the browser to use any requested permissions. Location access may be needed for a location reading. Motion and orientation access can also depend on the browser and its permission settings.
- Keep the device still for a moment, then tilt it, turn it, or move it gently. Watch whether the motion, gyroscope, or compass information changes. For light, change the lighting near the device and check whether its reading responds.
- If the test includes vibration, try it while holding the device. Compare the result with what you can feel, and repeat the check after confirming the device is not muted or in a mode that blocks vibration.
- If you are troubleshooting a specific app, test the device in the same browser you use for that app, then check the app's own permissions separately.
A browser does not automatically pass sensor readings from a phone to a computer over Wi-Fi, Bluetooth, or a cable. Unless you have set up a separate sensor-sharing system, the browser can only check the device where the page is open.
What the result means
Motion or gyroscope information changes when you move the device
The browser is receiving movement data from the device. This is a useful sign that the available motion sensors and browser access are working. It does not prove that every motion sensor is perfectly calibrated or that a particular app is using the same readings.
The reading stays still while the device is still
That can be normal. A steady reading is what you would expect when the device is not moving. Try a few different movements, such as tilting forward and backward and rotating the device, while watching the test.
A sensor is missing or does not change
The device may not have that sensor, the browser may not expose it, or access may be blocked. For example, many desktop computers do not have the same motion and orientation sensors as phones. A missing reading by itself is not proof that hardware is broken.
Location is unavailable or seems inaccurate
Location is provided through the browser and operating system's location service. It may use GPS, nearby Wi-Fi networks, cellular information, or a combination. A location result does not prove that the device's GPS receiver alone is working, and indoor readings can be imprecise.
Vibration does not happen
The device may not support browser vibration, the browser may restrict it, or the vibration setting may be disabled. Some computers and tablets have no vibration motor. Check whether vibration works in another normal feature on the same device before assuming the motor has failed.
How to fix a missing sensor reading
- Check the permission prompt. If you denied access, open the browser's site permissions from the icon beside the address bar and allow the permission the test needs. Reload the page afterward. A browser can have location access turned off for one site even when location works elsewhere.
- Turn on location access when testing location. In Windows 11, open Settings › Privacy & security › Location and enable location services and access for desktop apps if shown. On macOS, open System Settings › Privacy & Security › Location Services and allow access for the browser. On Android, check Settings › Location, then the browser's app permissions. On iPhone or iPad, check Settings › Privacy & Security › Location Services and the browser's access.
- Look for motion permissions on the phone. Some mobile browsers ask before sharing motion or orientation data with a website. Review the prompt when it appears and check the browser's site settings if you previously blocked it. On iPhone or iPad, also review Settings › Privacy & Security › Motion & Fitness where applicable.
- Try another supported browser on the same device. Sensor access varies between browsers and operating systems. If the reading works in one browser but not another, the difference is likely browser support or permission handling, not a failed sensor.
- Restart the browser and device. Close the page, quit the browser, and reopen the test. Restart the device if permissions look correct but readings remain unavailable.
When the sensor itself may be faulty
Suspect hardware only after testing on the device itself, allowing permissions, and trying more than one movement or lighting condition. If a phone's motion readings remain absent in several supported browsers and built-in features that rely on motion also fail, the sensor or its connection may be damaged. If the device was dropped or exposed to liquid, avoid opening it yourself. Check the warranty or have a repair shop inspect it.
For a compass problem, move away from magnetic cases, speakers, and metal objects, then test again. A compass can give unreliable directions near magnetic interference even when the sensor is responding. Location problems are different: poor indoor reception or disabled location services can affect the result without a faulty compass.
Why the test cannot check a device from another screen
Web pages run inside the browser on the device where you opened them. The browser asks that device's operating system for sensor information and applies its own permission rules. A laptop test therefore reports the laptop's available sensors, not the sensors in a phone connected by USB or sitting next to it.
The test also cannot make hardware appear where none exists. A desktop may report no motion sensor because it has none, while a phone may have one that its browser does not expose. Treat the result as a check of what the current device and browser can provide, rather than a complete hardware inventory.
Because location can reveal where you are, allow it only when you need to check location, then remove the site's permission if you do not want it to keep access.
