Why this keeps happening
One hidden calculation method
Apps that never show the method give you times that quietly disagree with your local mosque all year.
Notifications killed by battery saver
Scheduled alarms are the first thing aggressive power management drops.
Stale location
An app that cached your location on a trip keeps calculating for the wrong city.
How to fix it
- 1
Match your mosque's convention
Ask which calculation method your mosque uses and select the same one.
- 2
Apply a per-prayer offset
If Fajr is consistently two minutes early, correct that prayer alone rather than all five.
- 3
Exempt the app from battery optimisation
This single Android setting fixes the majority of missed adhan notifications.
- 4
Confirm your location is live
Re-grant location permission after travelling, or set your city manually.
How our approach compares
| Capability | Salah Companion: Prayer Times | Typical alternatives |
|---|---|---|
| Shows the calculation method | Yes, and lets you change it | Usually hidden |
| Per-prayer offsets | Yes | Rare |
| Ads inside reminders | None | Common |
| Offline qibla | Yes | Often needs data |
Frequently asked
Why do prayer time apps disagree with each other?
They use different calculation conventions for the sun angle at Fajr and Isha. Neither is wrong — they follow different established standards. Match the one your local mosque uses.
Do I need an internet connection?
No. Once your location and method are set, times and the qibla compass are calculated on your device.
Why did my adhan notification not play?
Almost always battery optimisation. Exempt the app in Android settings and re-open it once so alarms are rescheduled.