Mobile Sensor Test - Gyroscope & Accelerometer | Online Tool Box - Mic, Cam, Net Speed, Screen Test

Home All ToolsSensors

Mobile Sensor Test - Gyro/Accel

Read Gyroscope & Accelerometer data on mobile devices.

Availability and Permissions

Security context (HTTPS)

No (may cause the sensor to be unavailable)

DeviceMotionEvent

Not available

Permissions:unknown

DeviceOrientationEvent

Not available

Permissions:unknown

deviceorientationabsolute

Not sure/unavailable (common)

Most browsers do not provide this event.

You are not in a security context now. Mobile browsers may limit motion/orientation events;

Control and sampling

Not collected

Event frequency: Motion 0/s, Orientation 0/s

real time readings

Acceleration (excluding gravity) m/s²Update: -

|a|：-

Acceleration (including gravity) m/s²interval：-

|a|：- (about - g)

Gyroscope rotationRate (°/s)Update: -

alpha

beta

gamma

Direction (alpha/beta/gamma, °)Update: -

alpha

beta

gamma

absolute：falseheading：-accuracy：-

Tip: If the value is always "-", it usually means that it is not authorized, the device does not have a corresponding sensor, or the browser/system has disabled "Motion and Direction" access.

event log

No logs yet

Quick troubleshooting

• Try to open it with a mobile browser; desktop browsers usually do not have sensor events

• Look at "Availability and Permissions" first: If it's not HTTPS or permissions aren't granted, the reading will most likely always be "-".

• iOS Safari often requires explicit authorization: first click "Request Authorization", then click "Start Collection". If the system turns off "Motion and Orientation Access", there will always be no data.

• When the reading is abnormal, first look at the event frequency (Motion/Orientation times per second) and "update" time; a frequency of 0 often means that the monitoring is not effective or is intercepted by the system.

Sensor Guide

Check permissions and move device to verify readings.

Step 1

Confirm environment and permissions

about 10 seconds

First make sure it is running in the mobile browser and security context, and grant motion/direction permissions.

Try to use a mobile browser to open it (desktop browsers usually have no sensor events)

Confirm to be in HTTPS (non-secure contexts may be restricted)

If prompted that authorization is required: Click "Request Authorization" and select Allow in the system pop-up window.

If there is still no data: Check whether "Motion and Orientation Access" is turned off in system settings (common on iOS)

Tip: iOS Safari requires "user gesture" to trigger authorization, so please complete the authorization operation in the same click.

Step 2

Start collecting and observe the frequency

about 10 seconds

After starting the collection, first check the event frequency and update time to confirm whether the event is really being reported.

Click "Start Collection"

Observe whether "Event frequency: Motion/Orientation times per second" is greater than 0

Observe whether "Update: xxms/xxs" continues to refresh (the smaller it is, the newer it is)

If the frequency is 0: usually it is unauthorized/not supported/monitoring is not effective.

Step 3

Perform a simple action to verify the reading

about 15 seconds

Verify that the acceleration, gyroscope, and orientation values change reasonably by shaking/rotating the device slightly.

Shake the device slightly: observe whether there is any obvious change in "acceleration (excluding gravity)"

Rotate the device slowly: observe whether the rotationRate (°/s) changes

Change the device orientation: observe whether alpha/beta/gamma changes (different device coordinate systems will vary)

If the direction-related data is abnormal: try to stay away from strong magnetic interference, or switch the browser and test again

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.