Diagnostics
Gyroscope Sensor Diagnostics
Before blaming the hardware, check what your browser actually provides. This page lists every motion-sensor API your browser supports, its permission state, and the real rate at which gyroscope data arrives.
Browser capability check
These checks run as soon as the page loads. They only detect what is available and never trigger a permission prompt.
| Check | Result | What it means |
|---|---|---|
| Checking your browser… (requires JavaScript) | ||
Live data probe
Detecting an API is not the same as receiving data. This probe listens for three seconds and reports how many gyroscope readings actually arrive, and how often. Keep the device in your hand or move it gently.
What each check means
Secure context
Motion sensors are considered sensitive, so browsers only expose them to pages loaded over HTTPS (or localhost during development).
DeviceOrientationEvent and DeviceMotionEvent
These two long-standing web APIs are supported in all major mobile browsers. DeviceOrientationEvent reports the device’s angles (alpha, beta, gamma). DeviceMotionEvent reports acceleration and the gyroscope’s rotationRate in degrees per second. The main tester uses both.
Permission prompt
Safari and other browsers on iPhone and iPad add a requestPermission() step. The page can only call it after you tap something, and iOS then shows its own Allow/Don’t Allow dialog. Android browsers have no prompt. Access is managed in site settings instead.
Generic Sensor API
Gyroscope, Accelerometer and the orientation-sensor classes are a newer, more direct interface, available mainly in Chromium-based browsers on Android. If it is missing, the tester still works through the older events.
Permission states
Where supported, the Permissions API reports whether this site may use the gyroscope, accelerometer and magnetometer. denied means motion sensors were switched off for this site or for all sites in the browser’s settings.