How to check sensor response after a system reset
Check motion, compass, light, location, and vibration after a system reset, then find out whether permissions or hardware are causing a failure.
After a factory reset, settings reset, or operating system reinstall, a phone or computer may stop responding to motion, direction, light, location, or vibration. Sometimes a permission was turned off. Other times, the device or browser does not expose that sensor at all.
Test the device itself before changing settings again. The Sensors Test checks the sensors your browser can access, so you can see whether the problem is in the hardware, a permission, or browser support.
Test the sensors after the reset
- Open the Sensors Test on the device you reset. A test on another phone or computer will not show whether this device's sensors work.
- Allow a permission request if the browser asks for access. Location may need its own permission. If you previously blocked a request, the browser may not ask again until you change the site's permission.
- Try each sensor the test offers. Slowly tilt and rotate the device for motion, gyroscope, or compass readings. Cover and uncover the light sensor if the device has one. Follow any on-screen instruction for location or vibration.
- Keep the device still for a few seconds, then move it again. Watch whether the readings change and whether they return to a steady value when the device is still.
Test in the same browser you use for the task that failed. Keep the phone or tablet flat when checking compass direction, and move away from magnets, speakers, and metal objects that can affect a compass. Some computers do not have a compass, light sensor, or vibration motor, and some browsers cannot access sensors that are present.
What the result means
Readings change when you move the device
The browser is receiving data from that sensor. If an app still does not react, check that app's permissions and settings, then check whether it is using the same sensor feature. A browser test cannot confirm that another app is configured correctly.
A sensor appears, but its reading stays still
First, make sure the device is actually moving or that the light sensor is being covered. Remove a thick case if it blocks a sensor opening. If the reading remains unchanged, check permissions and try again after restarting the device.
The browser asks for permission, but the test still has no reading
The operating system may also be blocking access, or the permission may have been denied earlier. Location is especially permission-sensitive. Allow location for the browser in both the browser's site settings and the operating system, then reload the test.
A sensor is missing from the test
This does not automatically mean it is broken. The device may not include that sensor, the operating system may not expose it to a browser, or the browser may not support access to it. For more on those limits, see which sensors a web page can access.
The readings work in the test but not after a restart
The sensor itself may be working while a setting, driver, or service is failing to start. Repeat the test after a restart and check for system updates. If the issue returns each time, note which sensor is affected and whether the problem began immediately after the reset.
How to fix sensor access
- Check that you are testing the right device. Open the test on the phone, tablet, or computer that has the problem. Keep it awake and move it gently. A browser test on a separate computer cannot read the phone's sensors.
- Allow access for the site. Open the browser's site controls beside the address bar and review the permissions for TooLab. Allow the relevant permission, then reload the page. The names and availability of motion and sensor permissions vary by browser.
- Allow location in the operating system. On Windows 11, open Settings › Privacy & security › Location and turn on location services and access for desktop apps if those options are available. On macOS, open System Settings › Privacy & Security › Location Services and allow location for your browser. On Android, check Settings › Location and the browser's app permissions. On iPhone or iPad, check Settings › Privacy & Security › Location Services, then select the browser or Safari Websites and choose an appropriate access option.
- Check motion access on a phone. On iPhone or iPad, look under Settings › Privacy & Security › Motion & Fitness for an access setting that applies to the browser or app. Android menus vary by manufacturer, so check the browser's permissions in Settings and any available physical activity or sensor access options. Not every phone or browser offers a separate switch.
- Restart the browser and device. Close the browser fully, reopen the test, and try again. If the sensor readings still do not respond, restart the device to reload system services.
- Install available system updates. On Windows 11, check Settings › Windows Update, including optional driver updates if available. On macOS, check System Settings › General › Software Update. On phones, use the system update screen provided by the device maker. After updating, run the test again.
When it may be a hardware problem
If a sensor does not respond in the browser or in other features that use it, after permissions are enabled and the device has restarted, the sensor or its connection may be faulty. Check the manufacturer's built-in diagnostics or support instructions, if available. A browser test can show that readings are missing, but it cannot identify a damaged component or prove that a sensor is calibrated correctly.
If the device was dropped, repaired, or exposed to liquid before the problem started, contact the manufacturer or a repair shop. If it is still under warranty, ask about service before opening it yourself.
Why a reset can change the result
A reset may clear browser permissions, operating system privacy choices, or device settings. A full reinstall can also remove or replace drivers that help the operating system communicate with a sensor. The browser only reports sensors the device and operating system make available to it, so a missing browser reading is not a complete hardware diagnosis. For a useful comparison, run the same test on the same device before and after changing one setting at a time. You can also read why a sensor test must run on the device being checked.
The Sensors Test runs in your browser on the device being checked. Sensor readings are not uploaded by the test.
