Check device tilt in a mobile browser's private mode

Your phone is moving, but a website shows no tilt values, or the readings seem frozen when you open the page in a private tab. Private browsing can handle permissions differently, but a blank reading can also come from a browser setting, an unsupported sensor, or a phone that is not moving enough for the test to detect a change.

Use the Sensors Test to check motion and orientation readings on the phone itself. Comparing private and normal tabs in the same browser helps you narrow down whether private mode is involved.

Check tilt values in private mode

1. Open the Sensors Test in a private or incognito tab on the phone you want to check. Sensor values come from the device, so testing on a computer will not tell you what the phone reports.
2. If the browser asks to access motion or orientation data, allow it. Some browsers ask only after you tap or interact with the page. If there is no prompt, continue and check whether any live readings appear.
3. Set the phone on a steady surface, note the readings, then slowly tilt it forward, backward, and to each side. Keep the movement gentle. You are checking whether values change as the phone moves, not whether they reach a particular number.
4. Open the same test in a regular tab in the same browser and repeat the movement. Keep the phone in the same place and use similar movements so you can make a fair comparison.

Private tabs may close when you leave them, and a permission granted in one tab may not carry over to another session. If you see a prompt again in private mode, that does not by itself mean the sensor is broken.

What the result means

Readings change in both private and regular tabs

The browser can receive motion data in both modes. A small delay or difference between readings can be normal. Tilt values depend on how the phone is held and how the browser reports its orientation, so use the movement response rather than expecting the phone to show zero while it rests on a table.

Readings change in a regular tab but not in private mode

The phone's sensors are probably working. Private mode may not have a saved permission, the browser may be limiting access there, or the permission was denied for that session. Allow access if prompted, then reload the page and test again. If private mode keeps showing no data, use a regular tab for the sensor check.

Readings stay still in both modes

This points to a broader access or compatibility issue, not just private browsing. The browser may lack access to the sensor API, the phone's settings may block motion access, or the device may not provide that sensor to this browser. Try another current browser on the same phone before assuming the hardware has failed.

Some sensor readings work, but tilt does not

A phone can expose one type of sensor while another is unavailable or restricted. For example, a compass reading and a tilt reading are different checks. A working compass does not prove that the browser can receive orientation data. For more on permission behavior, see Understanding motion sensor permissions.

How to fix sensor access

1. Interact with the page before testing. Tap the page, then tilt the phone again. Some mobile browsers require a direct interaction before a website can request motion data. If a permission prompt appears, choose Allow.
2. Check the browser's site permission. Open the browser's site settings for TooLab and look for a motion or sensor permission if one is listed. Set it to allow, then reload the page. Names and controls vary by browser, and some browsers do not show a separate motion setting.
3. Check the phone's motion access setting. On iPhone in Safari, look for Settings › Apps › Safari › Motion & Orientation Access and turn it on if the setting is available. On older iOS versions, Safari may appear directly under Settings. Motion permission behavior varies across iOS versions and browsers.
4. Review Android app permissions. On Android, open Settings › Apps › [your browser] › Permissions. If Physical activity is listed, allow it for the test. Browser and Android versions differ, and this permission may not appear on every phone.
5. Retry in a regular tab, then restart the browser. Private tabs can use temporary permission state. If the readings still do not move in a normal tab, close other browser tabs, reopen the browser, and test again. Avoid repeatedly granting permissions if no prompt appears.
6. Update or switch browsers. If one browser shows tilt readings and another does not, the difference is likely browser support or settings. Keep using the browser that works, or check for an available browser update.

Why private mode can behave differently

Private browsing mainly limits what the browser saves after the session, such as browsing history and some site data. It does not guarantee that every device feature will be blocked, and it does not guarantee that a permission granted in a regular tab will be available in a private tab. Browsers may ask again, use a temporary choice, or apply stricter privacy rules.

Keep the comparison simple: use the same phone, browser, page, and movement. If values work in a regular tab but not a private one, that is useful evidence of a mode or permission difference. If values are missing everywhere, check browser support and phone settings before treating it as a hardware fault.

The Sensors Test reads values from the phone while it is open in your browser. The sensor readings stay on your device.