A phone responds to movement through a chain: sensors measure physical changes, software interprets those measurements, and an app decides what to do. When rotation or a gesture behaves unexpectedly, check each part of that chain. Begin with a familiar supported feature rather than assuming the hardware has failed.
Separate the measurements from the feature
Scroll sideways for all columns. Keyboard users can focus the table and use the arrow keys.
| Input | What it supplies | Typical use |
|---|---|---|
| Accelerometer | Acceleration along device axes, including the gravity contribution. | Tilt and motion interpretation. |
| Gyroscope | Rate of rotation around device axes. | Tracking changes in orientation. |
| Magnetometer | Magnetic-field measurements. | A heading reference when combined with other information. |
| Derived motion estimate | Software combines or processes sensor inputs. | Orientation, gestures, and activity-related features. |
Android’s motion-sensor documentation distinguishes physical measurements from software-derived gravity, linear acceleration, and rotation estimates. Its position-sensor documentation explains magnetic inputs and orientation. Available sensors and derived outputs vary by device.
A stationary accelerometer can still report gravity. A rotating phone can change the readings on its individual axes without traveling across a room. A compass heading is another quantity again. These distinctions help explain why one working feature does not validate every other motion-related feature.
Check the setting and the app first
Look for the system's Auto-rotate or orientation-lock control. Then choose an app and view documented to support landscape orientation. Some views intentionally keep a fixed layout. Apple’s rotation troubleshooting recommends checking Portrait Orientation Lock and trying an app such as Safari or Calculator that supports rotation.
For gestures, check the exact phone manual and the feature's own switch. A lift-to-wake action, an accessibility shortcut, and a game's tilt steering may use different conditions. Repeating one gesture in an unrelated app is a weak test.
Review only the relevant permissions. Android's step-counter and step-detector APIs require activity-recognition permission on Android 10 and later, as described in the motion documentation. A denied activity permission is a different issue from the screen's orientation lock. On other platforms, use the corresponding app and system privacy instructions.
Run a controlled, gentle check
- Record the phone model, OS version, app version, feature, and exact symptom.
- Hold the phone securely above a soft surface in a normal viewing position. Use ordinary movements; do not shake, throw, or drop it as a diagnostic.
- Check rotation lock, open a known supported view, and turn the phone from portrait to landscape. Record whether the view changes.
- Repeat in a second supported app. If one works and the other fails, investigate the failing app's layout, setting, or update first.
- For a compass symptom, move away from nearby magnetic accessories or large metal objects and follow that app's documented guidance. For other symptoms, use the manufacturer's relevant troubleshooting procedure.
- Restart through the normal device procedure if recommended, repeat the same test, and give support your before-and-after observations if the problem persists.
Change one setting at a time and restore settings you only changed for testing. Broad resets can remove useful configuration while leaving the original cause unclear.
Keep the conclusion as narrow as the test
A successful orientation test establishes that this feature worked under these conditions. A step estimate depends on the algorithm, how the phone is carried, and which activity it recognizes. A short comparison with a counted walk can reveal a mismatch, but it does not establish medical accuracy or a universal correction factor.
Likewise, a compass reading near magnetic material can be misleading even when the phone otherwise works normally. Follow the tool's calibration instructions only when applicable; a generic figure-eight movement is not a repair for every sensor or app problem.
For software authors, detect sensor availability, handle missing data, and provide a usable alternative control. Explain permission requests at the point of use and test more than one device configuration.
The phone-haptics guide covers vibration feedback produced by the phone. The location-services guide covers position estimates and navigation. Keeping input, output, and location distinct makes troubleshooting more precise.