Mobile Sensor Test - Gyroscope & Accelerometer
Comprehensive check for mobile sensors. Read real-time data from gyroscopes, accelerometers, and orientation sensors to verify motion sensitivity.
Requests device sensors only while the test is active and keeps processing in your browser whenever possible.
Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Device Orientation and Motion APIs, secure HTTPS, hardware availability, and browser policy.
Availability and Permissions
Control and sampling
real time readings
event log
Devicesensor.tipsTitle
Sensor Guide
Check permissions and move device to verify readings.
Confirm environment and permissions
First make sure it is running in the mobile browser and security context, and grant motion/direction permissions.
Start collecting and observe the frequency
After starting the collection, first check the event frequency and update time to confirm whether the event is really being reported.
Perform a simple action to verify the reading
Verify that the acceleration, gyroscope, and orientation values change reasonably by shaking/rotating the device slightly.
What this tool checks
This page checks whether motion and orientation sensors are exposed to the browser and whether live values change when you move the device.
sensor permission
Confirms whether the browser allows motion or orientation data to be requested on this device.
accelerometer activity
Shows whether acceleration values respond when you tilt or move the device.
gyroscope / orientation changes
Helps verify whether angle and rotation-related signals are updating in real time.
axis responsiveness
Makes it easier to see whether one axis appears frozen or incorrect.
event continuity
Useful for spotting update stalls, very low sample rates, or browser pausing.
mobile troubleshooting hints
Helps separate unsupported desktop behavior from actual mobile sensor problems.
What this tool cannot confirm
Sensor tests depend on what the browser exposes, so they are a practical feature check rather than a full hardware calibration.
desktop support is often limited
Many desktop browsers and devices do not expose these APIs even though the page itself is fine.
not a hardware calibration tool
It cannot certify the exact accuracy of accelerometers or gyroscopes the way engineering tools can.
permissions differ sharply by browser
Some platforms require user gestures, special prompts, or specific Safari behaviors before values appear.
background behavior can change readings
Browsers may throttle, smooth, or pause sensor events when power saving or backgrounding is involved.
How the result is generated
The result is generated from browser motion and orientation events and the live values exposed by the current device.
permission / gesture
The page requests the required motion-related permission or user action when needed.
sensor event subscription
The browser starts listening for device motion and orientation events.
live value sampling
The page samples acceleration, rotation, or orientation values as they change.
client-side visualization
Values are displayed locally so you can see whether movement produces expected changes.
local interpretation
The result is based on whether the browser exposes active, changing sensor signals during the test.
Interpret your results
Use the sensor result to decide whether the issue is unsupported browser access, permission state, or the device itself.
| Observed sensor result | Likely meaning |
|---|---|
| No values at all | Unsupported browser, missing permission, or a non-sensor desktop environment. |
| Values do not change | The device is not moving, one sensor path is frozen, or the browser is not updating events. |
| Only some axes respond | Orientation lock, partial sensor exposure, or a device-specific sensor issue. |
| Very noisy values | Normal hand shake, sensor drift, or unstable sampling frequency. |
| Smooth live updates | Basic browser sensor access is working correctly on this device. |
Supported browsers and known limitations
Motion sensor support varies strongly by platform, with mobile browsers generally offering more than desktop browsers.
| browser | permission behavior | motion support | orientation support | known limitations |
|---|---|---|---|---|
| Chrome | Usually works on supported mobile hardware | Good | Good | Desktop Chrome often has little or no useful sensor data. |
| Edge | Similar to Chrome | Good | Good | Windows desktops often expose limited sensor paths. |
| Firefox | Depends on platform support | Basic to good | Basic to good | API support can be more conservative than Chromium. |
| Safari | Often requires explicit user permission on Apple devices | Good | Good | Gesture and permission rules are stricter. |
| iOS Safari | Prompt often required | Good | Good | Background tabs and privacy settings can stop updates. |
| Android Chrome | Usually available on supported Android hardware | Good | Good | Device vendor sensor quality still varies widely. |
Use cases
This tool is most useful when a browser feature depends on motion or orientation data working right now on the device.
before mobile AR or sensor demos
Confirm that motion and orientation values are actually reaching the browser.
after a mobile OS update
Check whether browser sensor permissions changed after the update.
when a tilt-based site feels broken
Use the test to separate page logic issues from missing sensor access.
when comparing browsers on one phone
See whether Safari and Chrome expose the same sensor behavior on the same device.
when debugging orientation features
Confirm whether the browser receives live rotation changes as expected.
FAQ
Frequently asked questions and troubleshooting suggestions about device sensor (acceleration/gyroscope/direction) testing.
What can be measured on this page?
It will monitor DeviceMotion (acceleration/angular velocity) and DeviceOrientation (alpha/beta/gamma, etc.) events, and display permission status, event frequency and real-time readings to help you quickly determine whether the device sensor is reporting normally.
Why is the value always "-"?
The most common causes are: unauthorized, non-secure context (not HTTPS), sensorless desktop browser, or system/browser disabled Motion and Orientation Access. It is recommended to click "Refresh Status" first, then click "Request Authorization", and confirm that the system settings allow it.
Why does iOS Safari need to click "Request Authorization"?
Safari on iOS 13+ uses the requestPermission() authorization model for motion/direction events. The authorization pop-up window must be triggered by user gestures, otherwise the event will not be reported or empty data will be returned.
Why is the event frequency 0/s?
Usually it means that the monitoring is not effective or intercepted by the system: permission is not granted, the browser does not support it, the page is not in a safe context, or the system switch is turned off. It may also be that the device does not have a corresponding sensor (rare).
What does alpha/beta/gamma mean?
They represent the orientation angle of the device on 3 axes (unit °), but different browsers/devices have different implementations of coordinate systems and reference directions, so they are more suitable for verification of "whether it is changing/continuous" rather than strict engineering measurements.
Will this upload sensor data?
Won't. The page only reads and displays sensor events in the local browser and does not upload the data to the server.
Related guides
Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.
Is Your Phone Lying? How to Diagnose Hidden Sensor Failures Before They Ruin Your Game
Modern smartphones rely on invisible heroes: gyroscopes and accelerometers. When these sensors fail, everything from immersive AR experiences to simple screen rotation breaks down. This article explores why sensor drift happens, how physical drops silently damage internal components, and why second-hand buyers must test motion hardware before purchasing. Using the 'Mobile Sensor Test' tool, we provide a step-by-step guide to validating real-time motion data, ensuring your device is ready for high-performance gaming and accurate navigation. Don't let faulty hardware ruin your digital experience; learn to spot the signs of sensor failure today.
Is Your Phone Lying? How to Diagnose Hidden Sensor Failures Before They Ruin Your AR Experience
Modern smartphones rely on invisible heroes: gyroscopes and accelerometers. When these sensors fail, everything from immersive AR games to basic screen rotation breaks down. This article explores common symptoms of sensor degradation, such as drift in motion games or unresponsive orientation after a drop. We provide a practical, step-by-step guide using the Mobile Sensor Test tool to visualize real-time data, validate hardware integrity, and troubleshoot issues without visiting a repair shop. Whether you are a developer validating app compatibility or a buyer inspecting a second-hand device, learn how to interpret live metrics to ensure your device's motion sensitivity is up to par.
Is Your Phone Lying? How to Diagnose Hidden Sensor Failures Before They Ruin Your Game
Ever wondered why your racing game drifts uncontrollably or your AR furniture floats in mid-air? The culprit is often a failing gyroscope or accelerometer. This practical guide explores how to use mobile sensor testing tools to diagnose hardware issues before they become frustrating problems. We cover scenarios ranging from validating motion data during app development to inspecting second-hand phones for hidden damage after drops. By following a simple three-step workflow—granting permissions, running live diagnostics, and analyzing real-time metrics—you can verify if your device's orientation and gravity sensors are functioning correctly. Whether you are a gamer, a developer, or a cautious buyer, learning to read these vital signs ensures your mobile experience remains smooth and responsive.
Feedback / report a bug
Tell us your browser, device, and what happened.
Did this result look wrong?
Comments(0)