When phone compass or AR direction is wrong

Separate permissions, magnetic interference and sensor drift from astronomical calculations, then fall back to numerical directions.

AR is an aid

The calculated azimuth comes from time and coordinates. Phone orientation comes from sensors, calibration and browser support. A drifting AR marker does not automatically imply the same error in astronomical coordinates. Check numerical azimuth and altitude first.

Troubleshoot the symptom

SymptomFirst check
Direction frozenMotion permission and browser support
Direction jumpingMagnetic case, vehicle or metal railing
Constant offsetCalibration and true versus magnetic north
In-app browser failsOpen in Safari or Chrome

Follow your device’s calibration instructions. Figure-eight movements may help but are not a universal fix.

Use numerical guidance

At azimuth 225°, face southwest; at altitude 30°, look upward from the horizon. Camera permission is optional. Moon Where uses true north, so check the reference used by another compass app.

Report reproducible errors

Include device, browser, time, approximate area and displayed azimuth. Do not submit your exact home coordinates. This checklist is general guidance, not a certification based on testing every phone.

Report an issue

Purpose planner · Moon classroom · Observing places

Sources and review

Moon Where operator · Reviewed: 2026-10-07. AI assisted drafting; explanation reviewed against cited sources and application code. Hypothetical examples are identified.

Today’s Moon · Moonrise

Sources, responsibility and limitations

Lunar calculations use SunCalc in the browser. Cloud and precipitation forecasts come from Open-Meteo after coordinates are rounded to two decimal places. Terrain, buildings, haze and compass calibration can make a real observation differ from the estimate.

Content owner: Moon Where? operator · Last reviewed: October 7, 2026