Sensor values stuck at zero after a low battery?

Your phone's motion or compass readings stay at zero after the battery ran low. That can happen because of a permission, power-saving setting, browser limitation, or a sensor problem. A zero reading alone does not prove the hardware is broken.

Use the Sensors Test to see which sensors your browser can read, then check whether the values respond as you move the device.

Test the sensors

1. Open the Sensors Test on the device with the problem. Sensor tests need to run on the device being checked.
2. If the browser asks for permission, allow access to the requested sensors or location. The available prompts depend on your device and browser.
3. Place the device on a stable surface, then gently tilt or rotate it. Watch the motion, gyroscope, compass, light, and location readings separately. Do not shake the device or move it near an edge.
4. Charge the device, turn off its battery-saving mode temporarily, and repeat the test. If possible, try a second browser on the same device.

For a fair comparison, test one sensor at a time and note which values change. A phone may not have every sensor the test can check, and a computer may have very few. A missing reading is not automatically a fault.

What the result means

Values change when you move the device

The browser is receiving sensor data. The earlier zeros may have been temporary, or the device may have been still while you watched the reading. If values stop again after the screen locks or the battery saver returns, repeat the test with those conditions changed.

One sensor stays at zero, but others respond

This points to a sensor-specific limitation, permission, or fault. For example, a device may not have a compass, or the browser may not expose that sensor. Check the device specifications and browser permissions before assuming the component has failed.

Every reading stays at zero

Check permission and browser support first. If the browser does not support a sensor API, it may show no useful readings even when the device has the hardware. Try another current browser, then restart the device and test again while it is charged.

Location stays at zero or does not update

Location uses a separate permission and depends on the device's location service. A zero value is not proof that the phone is physically at those coordinates. Allow location access for the browser and test outdoors or near a window if the device is relying on satellite positioning.

How to fix it

1. Charge the device and restart it. Let the battery rise above the low-battery warning, then restart the phone or computer. A restart can restore a sensor service that stopped responding as the device shut down or entered a low-power state.
2. Turn off battery saver for one test. On Android, check Settings › Battery › Battery Saver or the similarly named power-saving setting. On iPhone, use Settings › Battery › Low Power Mode. On Windows 11, check Settings › System › Power & battery › Energy saver. On macOS, check System Settings › Battery › Low Power Mode. Names can vary by device and OS version. Turn the feature back on after testing if you need it.
3. Allow the browser's sensor permissions. Open the site's permissions from the browser address bar and allow any listed motion, orientation, or location access. On iPhone, check Settings › Apps › Safari › Motion & Orientation Access, or Settings › Safari › Motion & Orientation Access on older iOS versions. On Android, open the browser's site settings for the page and look for motion sensor or location access. The available controls differ by browser.
4. Check location access separately. On Android, review Settings › Location › App location permissions and allow the browser while using it. On iPhone, check Settings › Privacy & Security › Location Services, then select the browser if it appears. On Windows 11, check Settings › Privacy & security › Location. On macOS, check System Settings › Privacy & Security › Location Services. These controls affect location readings, not necessarily motion sensors.
5. Try another browser and reload the test. A browser may lack support for a sensor, block access in a private window, or keep an old permission choice. Close the page, reopen it in a current browser, and approve the request if one appears.
6. Install system updates and retest. If the readings remain stuck across browsers after a restart, install available device and browser updates. Avoid repeatedly draining the battery to zero as a way to test it.

When it may be a hardware fault

If the same sensor stays unresponsive in more than one browser after charging, restarting, and checking permissions, test it in another app that uses that sensor. If it also fails there, especially after a drop, liquid exposure, or repair, the sensor or its connection may need service. Back up the device and contact the manufacturer or a repair shop. A browser test can show that data is unavailable, but it cannot identify a damaged part by itself.

Why a low battery may be part of the timing

Low-power modes can limit background activity and change how quickly a device reports data. The exact behavior depends on the model and operating system. A low battery does not usually prove that a motion sensor was damaged, and switching off battery saver is a comparison test, not a permanent fix.

Sensor support also varies by browser and device. Some readings need permission, and some sensors are not present at all. The Sensors Test can show what the browser makes available, but it cannot confirm every hardware feature or measure the battery's health.