DeviceOK
SearchDevice checks
Home / Fixes / Browser Motion Sensor Not Working

sensor · evidence-led troubleshooting

Browser Motion Sensor Not Working

Use a focused DeviceOK test first, then follow the evidence from browser/device state before changing drivers, firmware, or hardware.

Reviewed 2026-08-113 diagnostic steps1 official sources
Run Motion testSee fault tree ↓

What this symptom means

This symptom concerns the sensor path. Start with a neutral DeviceOK test where available so the next step is based on evidence rather than a generic reset sequence.

Diagnostic principleWeb sensor access depends heavily on device, browser, permission and secure-context rules. A missing browser reading does not prove the physical sensor is absent or broken.

Fault tree

Sensor fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

1
Browser/API unavailable

Evidence: The OS/app can use the sensor but DeviceOK cannot request it.

Next: Check browser support and permission; use native diagnostics when the API is unavailable.

2
Permission

Evidence: Sensor exists but access is blocked or never granted.

Next: Check browser/site and OS motion/location permission.

3
Physical/OS sensor issue

Evidence: Native apps and DeviceOK both fail where supported.

Next: Use OEM diagnostics/service.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next
Live values changeThe browser is receiving sensor events.App-specific interpretation if another app still fails.
API unsupportedNo conclusion about physical hardware can be drawn.Native diagnostics or another supported browser/device.
Permission deniedThe test was blocked before hardware could be evaluated.Permission settings.
Values fixed/implausibleEvents exist but may be stale, emulated or faulty.Compare native sensor app/OEM diagnostics.

Fast baseline

Rule out the simple causes first

  1. 1

    Run DeviceOK Motion Sensor Test over HTTPS on the physical mobile/tablet device.

  2. 2

    Grant motion/orientation permission if the browser requests it.

  3. 3

    Check browser compatibility and compare a second supported browser.

Full sequence

Work from reversible checks to invasive ones

Avoid destructive resets, unofficial driver packages, firmware flashing, or replacing hardware before the simpler detection, permission, connection and configuration checks are exhausted.

  1. 1

    If native compass/motion apps work but the browser does not, treat it as browser permission/support first.

  2. 2

    If neither browser nor OEM diagnostics see the sensor, a wider device sensor issue is possible.

  3. 3

    Do not infer accelerometer/gyroscope hardware failure solely from an unsupported browser.

Platform branches

Where the setting lives

Mobile

  • Check motion/orientation/location permission
  • Test in a supported browser
  • Compare with a native compass/maps/sensor function

Desktop

  • Many desktops simply do not expose motion sensors
  • Do not infer a fault from unsupported API
  • Use OEM hardware inventory/diagnostics
If it works in DeviceOK

If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.

If it also fails here

No browser events may still be permission/API support rather than failed sensor hardware. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

  • Native diagnostics also report sensor failure
  • Sensor-dependent safety/navigation feature is unreliable
  • Physical damage/liquid exposure
Changed one variable?After every meaningful change, repeat the same test under the same conditions and compare the result. Retest under the same condition so the result is comparable.
Retest Motion test