Blog

Motion permissions for an AR learning activity

Check phone motion access for an AR lesson, grant browser permission, and test sensor readings to tell whether the issue is settings or hardware.

Ryan MitchellHardware tests Tests 5 min read

An AR lesson may stay still when you tilt your phone, or it may show a message asking for motion access. The cause could be a blocked browser permission, a device that does not provide the sensor to websites, or a sensor problem.

Check the phone in the same browser you use for the activity. TooLab's Sensors Test can show whether motion and gyroscope readings change as you move the device. It cannot grant permission for another site, but it can help you narrow down the cause.

Check motion access

  1. Open the Sensors Test on the phone and allow access if the browser asks for it. The test runs in the browser, so use the same browser and device as the AR activity.
  2. Hold the phone still, then tilt it slowly forward, backward, and side to side. Look for motion or gyroscope readings that change with the movement.
  3. Return to the AR lesson and reload the page. If it asks for motion access, choose Allow. Some browsers only show a motion permission prompt after you tap a button or other page control.
  4. Try the lesson again and move the phone gently. If the sensor test responds but the lesson does not, check that lesson's site permission and browser support.

Keep the phone over a desk or another safe surface while checking. You do not need to shake it, spin it, or walk around to see whether basic tilt readings change.

What the result means

Motion readings change when you tilt the phone

The browser can receive motion data from the device. If the AR activity remains still, its site permission may be blocked, the activity may not support your browser, or it may need you to tap a control before it can use motion.

Readings stay still or are not available

The browser may not expose that sensor, the device may not have it, or permission may be unavailable. A desktop computer often has no phone-style orientation sensor. Try the activity on a supported phone or tablet before treating this as a hardware fault.

The browser reports that access is blocked

The site or browser has denied access. Change the permission for the AR lesson's website, reload the page, and grant access when prompted. If you previously chose a blocking option, the browser may not ask again until you change the saved site setting.

The sensor test responds, but the AR lesson does not

The phone's sensor is producing readings in this browser, so the problem is more likely to be specific to the lesson, its browser support, or its saved permission. Test the lesson in a current browser that supports motion access, and check whether the page gives a separate instruction to enable motion.

How to fix it

  1. Reload the lesson after granting access. A page that was open before you changed a permission may not notice the change. Close or reload it, then try again.
  2. Check the website's browser permission. In Chrome or Edge, select the site controls icon beside the address bar, open Site settings, and allow Motion sensors if that option appears. The wording and available controls can vary by browser and device. In Safari on a Mac, open Safari › Settings › Websites and review the permissions available for the site. Safari may not list a motion control there.
  3. Enable motion access in Safari on iPhone or iPad. Open Settings › Safari › Motion & Orientation Access and turn it on if the option is present. Return to Safari, reload the AR lesson, and try again. Menu names can vary by iOS version.
  4. Check Android site settings. In Chrome, open Settings › Site settings and look for Motion sensors. If it is listed, make sure access is not blocked for the AR lesson. You can also open the lesson's site controls from the address bar and review its permissions.
  5. Try a direct interaction with the page. Tap the lesson's start or enable control before moving the phone. Some browsers require a user action before a page can request motion access. Do not assume a missing prompt means the sensor is broken.
  6. Update the browser and reopen the lesson. Older browsers or embedded browsers inside another app may not support the feature the activity needs. Open the lesson directly in an up-to-date browser instead of an in-app preview.
  7. Restart the device if readings remain stuck. Restarting can clear a browser or sensor service that stopped responding. Run the Sensors Test again before reopening the lesson.

On Windows 11, there is no general Windows privacy switch that gives a website access to phone-style motion sensors. Check the browser's site settings instead. Windows location access is separate from motion data. On macOS, the browser can only use sensors the computer and browser expose, and a permission cannot add hardware that is not present.

When it may be a device problem

Compare results in the Sensors Test after restarting the device and checking the browser permission. If readings remain missing or unchanged in more than one supported browser, the device may lack the required sensor or have a hardware fault. If the same sensor also fails in other activities that use it, contact the device maker or a repair shop. A browser test cannot inspect the sensor's internal circuitry, so it cannot confirm a hardware failure on its own.

Motion permission is not camera permission

An AR activity may need motion data to follow how you tilt or turn the phone. It may also need the camera to place digital objects over the live view. Those are separate capabilities. Allowing motion does not automatically allow the camera, and a working camera does not prove motion access is available. If the lesson shows a separate camera prompt, review that permission separately.

Only grant access to a lesson you trust, and change the permission back afterward if you do not want the site to use it again.

More articles